From: Mark Hurd on 25 Feb 2010 18:52 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: (new SqlCommand("COMMIT TRANSACTION", holder.Connection)).ExecuteNonQuery(); the SharpDevelop converter left them the same without the semicolon and I found the following works and is acceptable Call (New SqlCommand("COMMIT TRANSACTION", holder.Connection)).ExecuteNonQuery() But the query to these newsgroups was about the general syntax. -- Regards, Mark Hurd, B.Sc.(Ma.) (Hons.) "Patrice" <http://www.chez.com/scribe/> wrote in message news:eCFjxOhtKHA.6140(a)TK2MSFTNGP05.phx.gbl... >> 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 >
First
|
Prev
|
Pages: 1 2 Prev: Print values dynamically on a form Next: How to integrate excel worksheet in browser ? |