From: Mark Hurd on
The actual scenario is due to C# code converted to VB.NET by
SharpDevelop. The code is the Microsoft ASP.NET provider toolkit sample
code. It includes about a dozen calls like this:


the SharpDevelop converter left them the same without the semicolon and
I found the following works and is acceptable

Call (New SqlCommand("COMMIT TRANSACTION",

But the query to these newsgroups was about the general syntax.

Mark Hurd, B.Sc.(Ma.) (Hons.)

"Patrice" <> wrote in message
>> with New String(New Char(){"a"c,"b"c,"0"c})
>> .WL()
>> end with
> Some more context could help. It could be just
> Console.WriteLine("ab0") or perhaps CStr("ab0").WL()? The first one
> could be the same in VB6 (create an autoinstanciating Console calls
> that does what you want).
> In this particular example, my personal preference would be still to
> consider that I have a console object I'm writing to rather than
> telling a particular datatype it has a method to write to the console
> (or perhaps a stream writer that could redirect to the console to keep
> something general)...
> A bit hard to give a more accurate advice without knowing what is your
> overall goal beyond the syntax issue...
> --
> Patrice