VB.NET to c# convert

[Michael Nicol]

Hey all

Our company recently started using .net and started in VB.NET. We've since
changed to c#, but has some code already written in VB.NET. I'm looking for
a converter that will just take vb.net and convert it into farely nice c#.
I've found one or two, but they do some strange stuff and was wondering if
there is a Microsoft converter or one generally accepted as being good by
the community?

[Cowboy \(Gregory A. Beamer\) [MVP]]

Re: VB.NET to c# convert

There are none that are perfected. The best option is convert and fix.

One of the issues is there are training wheels available for VB.NET that are
not present in C#. While most of the converters do great translating VB.NET
to C#, when both are using .NET classes, the VB shortcuts often blow the
translation up. The more your team has used the VB functions, etc., the less
likely you have a clean translation. Most of the translator writers I have
conversed with are C# developers, so you can see the bias. ;-)

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************** *************** *************** ***
Think Outside the Box!
*************** *************** *************** ***
"Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=blue]
> Hey all
>
> Our company recently started using .net and started in VB.NET. We've[/color]
since[color=blue]
> changed to c#, but has some code already written in VB.NET. I'm looking[/color]
for[color=blue]
> a converter that will just take vb.net and convert it into farely nice c#.
> I've found one or two, but they do some strange stuff and was wondering if
> there is a Microsoft converter or one generally accepted as being good by
> the community?
>
>
>[/color]

[Michael Nicol]

Re: VB.NET to c# convert

Thanks...

Figured as much... Oh the joys / legacy of VB and the allowance of things
that just shouldn't be... ;)



"Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM> wrote
in message news:%23mKeHueh EHA.4064@TK2MSF TNGP12.phx.gbl. ..[color=blue]
> There are none that are perfected. The best option is convert and fix.
>
> One of the issues is there are training wheels available for VB.NET that[/color]
are[color=blue]
> not present in C#. While most of the converters do great translating[/color]
VB.NET[color=blue]
> to C#, when both are using .NET classes, the VB shortcuts often blow the
> translation up. The more your team has used the VB functions, etc., the[/color]
less[color=blue]
> likely you have a clean translation. Most of the translator writers I have
> conversed with are C# developers, so you can see the bias. ;-)
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> *************** *************** *************** ***
> Think Outside the Box!
> *************** *************** *************** ***
> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=green]
> > Hey all
> >
> > Our company recently started using .net and started in VB.NET. We've[/color]
> since[color=green]
> > changed to c#, but has some code already written in VB.NET. I'm looking[/color]
> for[color=green]
> > a converter that will just take vb.net and convert it into farely nice[/color][/color]
c#.[color=blue][color=green]
> > I've found one or two, but they do some strange stuff and was wondering[/color][/color]
if[color=blue][color=green]
> > there is a Microsoft converter or one generally accepted as being good[/color][/color]
by[color=blue][color=green]
> > the community?
> >
> >
> >[/color]
>
>[/color]

[One Handed Man \( OHM - Terry Burns \)]

Re: VB.NET to c# convert

Ya know what, I found that the conveters I used mostly work ok, they seem to
have trouble converting event handlers back into the delegate declaration
required by C#. Ive done a lot of translation both ways, and I find VB to C#
dead easy most of the time, but the other way is normally a bit of a pain.

Its a case of hacking it till it works Im afraid.




--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
news:%23D%23X92 ehEHA.1156@TK2M SFTNGP10.phx.gb l...[color=blue]
> Thanks...
>
> Figured as much... Oh the joys / legacy of VB and the allowance of things
> that just shouldn't be... ;)
>
>
>
> "Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM>[/color]
wrote[color=blue]
> in message news:%23mKeHueh EHA.4064@TK2MSF TNGP12.phx.gbl. ..[color=green]
> > There are none that are perfected. The best option is convert and fix.
> >
> > One of the issues is there are training wheels available for VB.NET that[/color]
> are[color=green]
> > not present in C#. While most of the converters do great translating[/color]
> VB.NET[color=green]
> > to C#, when both are using .NET classes, the VB shortcuts often blow the
> > translation up. The more your team has used the VB functions, etc., the[/color]
> less[color=green]
> > likely you have a clean translation. Most of the translator writers I[/color][/color]
have[color=blue][color=green]
> > conversed with are C# developers, so you can see the bias. ;-)
> >
> > --
> > Gregory A. Beamer
> > MVP; MCP: +I, SE, SD, DBA
> >
> > *************** *************** *************** ***
> > Think Outside the Box!
> > *************** *************** *************** ***
> > "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> > news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=darkred]
> > > Hey all
> > >
> > > Our company recently started using .net and started in VB.NET. We've[/color]
> > since[color=darkred]
> > > changed to c#, but has some code already written in VB.NET. I'm[/color][/color][/color]
looking[color=blue][color=green]
> > for[color=darkred]
> > > a converter that will just take vb.net and convert it into farely nice[/color][/color]
> c#.[color=green][color=darkred]
> > > I've found one or two, but they do some strange stuff and was[/color][/color][/color]
wondering[color=blue]
> if[color=green][color=darkred]
> > > there is a Microsoft converter or one generally accepted as being good[/color][/color]
> by[color=green][color=darkred]
> > > the community?
> > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

[Nicholas Paldino [.NET/C# MVP]]

Re: VB.NET to c# convert

Michael,

I am just curious, since it is in VB.NET, why not leave compiled
assemblies as they are, and then just make sure all new development is done
in C#? All you have to do is add an assembly reference, and it works.

This way, you don't have to spend resources on something that is really
just a preference, and not a need (you gain almost nothing by changing the
code to C#).


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard. caspershouse.co m


"Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
news:%23D%23X92 ehEHA.1156@TK2M SFTNGP10.phx.gb l...[color=blue]
> Thanks...
>
> Figured as much... Oh the joys / legacy of VB and the allowance of things
> that just shouldn't be... ;)
>
>
>
> "Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM>
> wrote
> in message news:%23mKeHueh EHA.4064@TK2MSF TNGP12.phx.gbl. ..[color=green]
>> There are none that are perfected. The best option is convert and fix.
>>
>> One of the issues is there are training wheels available for VB.NET that[/color]
> are[color=green]
>> not present in C#. While most of the converters do great translating[/color]
> VB.NET[color=green]
>> to C#, when both are using .NET classes, the VB shortcuts often blow the
>> translation up. The more your team has used the VB functions, etc., the[/color]
> less[color=green]
>> likely you have a clean translation. Most of the translator writers I
>> have
>> conversed with are C# developers, so you can see the bias. ;-)
>>
>> --
>> Gregory A. Beamer
>> MVP; MCP: +I, SE, SD, DBA
>>
>> *************** *************** *************** ***
>> Think Outside the Box!
>> *************** *************** *************** ***
>> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
>> news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=darkred]
>> > Hey all
>> >
>> > Our company recently started using .net and started in VB.NET. We've[/color]
>> since[color=darkred]
>> > changed to c#, but has some code already written in VB.NET. I'm
>> > looking[/color]
>> for[color=darkred]
>> > a converter that will just take vb.net and convert it into farely nice[/color][/color]
> c#.[color=green][color=darkred]
>> > I've found one or two, but they do some strange stuff and was wondering[/color][/color]
> if[color=green][color=darkred]
>> > there is a Microsoft converter or one generally accepted as being good[/color][/color]
> by[color=green][color=darkred]
>> > the community?
>> >
>> >
>> >[/color]
>>
>>[/color]
>
>[/color]

[Mark Broadbent]

Re: VB.NET to c# convert

exactly. Whole point of the framework.
Otherwise what happens if your company changes it's mind again and goes for
C++.net or Python.net!


"Nicholas Paldino [.NET/C# MVP]" <mvp@spam.guard .caspershouse.c om> wrote in
message news:Ow$b$BfhEH A.556@TK2MSFTNG P10.phx.gbl...[color=blue]
> Michael,
>
> I am just curious, since it is in VB.NET, why not leave compiled
> assemblies as they are, and then just make sure all new development is[/color]
done[color=blue]
> in C#? All you have to do is add an assembly reference, and it works.
>
> This way, you don't have to spend resources on something that is[/color]
really[color=blue]
> just a preference, and not a need (you gain almost nothing by changing the
> code to C#).
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard. caspershouse.co m
>
>
> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> news:%23D%23X92 ehEHA.1156@TK2M SFTNGP10.phx.gb l...[color=green]
> > Thanks...
> >
> > Figured as much... Oh the joys / legacy of VB and the allowance of[/color][/color]
things[color=blue][color=green]
> > that just shouldn't be... ;)
> >
> >
> >
> > "Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM>
> > wrote
> > in message news:%23mKeHueh EHA.4064@TK2MSF TNGP12.phx.gbl. ..[color=darkred]
> >> There are none that are perfected. The best option is convert and fix.
> >>
> >> One of the issues is there are training wheels available for VB.NET[/color][/color][/color]
that[color=blue][color=green]
> > are[color=darkred]
> >> not present in C#. While most of the converters do great translating[/color]
> > VB.NET[color=darkred]
> >> to C#, when both are using .NET classes, the VB shortcuts often blow[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> >> translation up. The more your team has used the VB functions, etc., the[/color]
> > less[color=darkred]
> >> likely you have a clean translation. Most of the translator writers I
> >> have
> >> conversed with are C# developers, so you can see the bias. ;-)
> >>
> >> --
> >> Gregory A. Beamer
> >> MVP; MCP: +I, SE, SD, DBA
> >>
> >> *************** *************** *************** ***
> >> Think Outside the Box!
> >> *************** *************** *************** ***
> >> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> >> news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..
> >> > Hey all
> >> >
> >> > Our company recently started using .net and started in VB.NET. We've
> >> since
> >> > changed to c#, but has some code already written in VB.NET. I'm
> >> > looking
> >> for
> >> > a converter that will just take vb.net and convert it into farely[/color][/color][/color]
nice[color=blue][color=green]
> > c#.[color=darkred]
> >> > I've found one or two, but they do some strange stuff and was[/color][/color][/color]
wondering[color=blue][color=green]
> > if[color=darkred]
> >> > there is a Microsoft converter or one generally accepted as being[/color][/color][/color]
good[color=blue][color=green]
> > by[color=darkred]
> >> > the community?
> >> >
> >> >
> >> >
> >>
> >>[/color]
> >
> >[/color]
>
>[/color]

[One Handed Man \( OHM - Terry Burns \)]

Re: VB.NET to c# convert

Thats fine provided you are able to leave the compiled assemblies compiled,
if you need to maintaine them, this then becomes more of an issue.

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"Nicholas Paldino [.NET/C# MVP]" <mvp@spam.guard .caspershouse.c om> wrote in
message news:Ow$b$BfhEH A.556@TK2MSFTNG P10.phx.gbl...[color=blue]
> Michael,
>
> I am just curious, since it is in VB.NET, why not leave compiled
> assemblies as they are, and then just make sure all new development is[/color]
done[color=blue]
> in C#? All you have to do is add an assembly reference, and it works.
>
> This way, you don't have to spend resources on something that is[/color]
really[color=blue]
> just a preference, and not a need (you gain almost nothing by changing the
> code to C#).
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard. caspershouse.co m
>
>
> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> news:%23D%23X92 ehEHA.1156@TK2M SFTNGP10.phx.gb l...[color=green]
> > Thanks...
> >
> > Figured as much... Oh the joys / legacy of VB and the allowance of[/color][/color]
things[color=blue][color=green]
> > that just shouldn't be... ;)
> >
> >
> >
> > "Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM>
> > wrote
> > in message news:%23mKeHueh EHA.4064@TK2MSF TNGP12.phx.gbl. ..[color=darkred]
> >> There are none that are perfected. The best option is convert and fix.
> >>
> >> One of the issues is there are training wheels available for VB.NET[/color][/color][/color]
that[color=blue][color=green]
> > are[color=darkred]
> >> not present in C#. While most of the converters do great translating[/color]
> > VB.NET[color=darkred]
> >> to C#, when both are using .NET classes, the VB shortcuts often blow[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> >> translation up. The more your team has used the VB functions, etc., the[/color]
> > less[color=darkred]
> >> likely you have a clean translation. Most of the translator writers I
> >> have
> >> conversed with are C# developers, so you can see the bias. ;-)
> >>
> >> --
> >> Gregory A. Beamer
> >> MVP; MCP: +I, SE, SD, DBA
> >>
> >> *************** *************** *************** ***
> >> Think Outside the Box!
> >> *************** *************** *************** ***
> >> "Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
> >> news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..
> >> > Hey all
> >> >
> >> > Our company recently started using .net and started in VB.NET. We've
> >> since
> >> > changed to c#, but has some code already written in VB.NET. I'm
> >> > looking
> >> for
> >> > a converter that will just take vb.net and convert it into farely[/color][/color][/color]
nice[color=blue][color=green]
> > c#.[color=darkred]
> >> > I've found one or two, but they do some strange stuff and was[/color][/color][/color]
wondering[color=blue][color=green]
> > if[color=darkred]
> >> > there is a Microsoft converter or one generally accepted as being[/color][/color][/color]
good[color=blue][color=green]
> > by[color=darkred]
> >> > the community?
> >> >
> >> >
> >> >
> >>
> >>[/color]
> >
> >[/color]
>
>[/color]

[Herfried K. Wagner [MVP]]

Re: VB.NET to c# convert

* "Michael Nicol" <michaelnicol@w oolworths.co.za > scripsit:[color=blue]
> Our company recently started using .net and started in VB.NET. We've since
> changed to c#, but has some code already written in VB.NET. I'm looking for
> a converter that will just take vb.net and convert it into farely nice c#.
> I've found one or two, but they do some strange stuff and was wondering if
> there is a Microsoft converter or one generally accepted as being good by
> the community?[/color]

I don't know a good converter for this purpose, but why don't simply
leave the code in VB.NET? This would save a lot of work and would not
have any disadvantages.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Cor Ligthert]

Re: VB.NET to c# convert

[color=blue]
> I don't know a good converter for this purpose, but why don't simply
> leave the code in VB.NET? This would save a lot of work and would not
> have any disadvantages.[/color]

Read the message from OHM, I find that a good point.

And as Rakesh said, after too much C# it's always a bit of a chore to think
in
vb.net :)

Cor

[André Nogueira]

Re: VB.NET to c# convert

Just out of curiosity, why did you change from VB.Net to C#?

André Nogueira

"Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=blue]
> Hey all
>
> Our company recently started using .net and started in VB.NET. We've
> since
> changed to c#, but has some code already written in VB.NET. I'm looking
> for
> a converter that will just take vb.net and convert it into farely nice c#.
> I've found one or two, but they do some strange stuff and was wondering if
> there is a Microsoft converter or one generally accepted as being good by
> the community?
>
>
>[/color]

[One Handed Man \( OHM - Terry Burns \)]

Re: VB.NET to c# convert

OK then, tell me how you would create a Unsigned Int in VB.NET, which you
can do in C#

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"mscertifie d" <rupert@tigerli ly.com> wrote in message
news:15BC700C-37AF-4129-8675-2A595F97DAAB@mi crosoft.com...[color=blue]
> One of the major selling points of .NET is that it is language[/color]
independent,[color=blue]
> so its pointless converting source languages.
>
> "Michael Nicol" wrote:
>[color=green]
> > Hey all
> >
> > Our company recently started using .net and started in VB.NET. We've[/color][/color]
since[color=blue][color=green]
> > changed to c#, but has some code already written in VB.NET. I'm looking[/color][/color]
for[color=blue][color=green]
> > a converter that will just take vb.net and convert it into farely nice[/color][/color]
c#.[color=blue][color=green]
> > I've found one or two, but they do some strange stuff and was wondering[/color][/color]
if[color=blue][color=green]
> > there is a Microsoft converter or one generally accepted as being good[/color][/color]
by[color=blue][color=green]
> > the community?
> >
> >
> >
> >[/color][/color]

[André Nogueira]

Re: VB.NET to c# convert

I was wondering if you could do that, I needed it for a project... My
question is answered now =S

Andre Nogueira

"One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in message
news:O$yeSkghEH A.556@TK2MSFTNG P10.phx.gbl...[color=blue]
> OK then, tell me how you would create a Unsigned Int in VB.NET, which you
> can do in C#
>
> --
>
> OHM ( Terry Burns )
> . . . One-Handed-Man . . .
> If U Need My Email ,Ask Me
>
> Time flies when you don't know what you're doing
>
> "mscertifie d" <rupert@tigerli ly.com> wrote in message
> news:15BC700C-37AF-4129-8675-2A595F97DAAB@mi crosoft.com...[color=green]
>> One of the major selling points of .NET is that it is language[/color]
> independent,[color=green]
>> so its pointless converting source languages.
>>
>> "Michael Nicol" wrote:
>>[color=darkred]
>> > Hey all
>> >
>> > Our company recently started using .net and started in VB.NET. We've[/color][/color]
> since[color=green][color=darkred]
>> > changed to c#, but has some code already written in VB.NET. I'm
>> > looking[/color][/color]
> for[color=green][color=darkred]
>> > a converter that will just take vb.net and convert it into farely nice[/color][/color]
> c#.[color=green][color=darkred]
>> > I've found one or two, but they do some strange stuff and was wondering[/color][/color]
> if[color=green][color=darkred]
>> > there is a Microsoft converter or one generally accepted as being good[/color][/color]
> by[color=green][color=darkred]
>> > the community?
>> >
>> >
>> >
>> >[/color][/color]
>
>[/color]

[Jon Skeet [C# MVP]]

Re: VB.NET to c# convert

<"One Handed Man \( OHM - Terry Burns \)" <news.microsoft .com>> wrote:[color=blue]
> OK then, tell me how you would create a Unsigned Int in VB.NET, which you
> can do in C#[/color]

Option Strict On

Imports System

Class Test

Shared Sub Main
Dim x as UInt32 = Convert.ToUInt3 2(0)
End Sub

End Class

There's not a lot you can do with it once you've created it,
admittedly, but you can create it...

--
Jon Skeet - <skeet@pobox.co m>

http://www.pobox.com/~skeet

If replying to the group, please do not mail me too

[One Handed Man \( OHM - Terry Burns \)]

Re: VB.NET to c# convert

I realise this, I was making a point about language differences for the
benefit of the poster above me.

Cheers

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"Jon Skeet [C# MVP]" <skeet@pobox.co m> wrote in message
news:MPG.1b8eea f9269867b798b1e e@msnews.micros oft.com...[color=blue]
> <"One Handed Man \( OHM - Terry Burns \)" <news.microsoft .com>> wrote:[color=green]
> > OK then, tell me how you would create a Unsigned Int in VB.NET, which[/color][/color]
you[color=blue][color=green]
> > can do in C#[/color]
>
> Option Strict On
>
> Imports System
>
> Class Test
>
> Shared Sub Main
> Dim x as UInt32 = Convert.ToUInt3 2(0)
> End Sub
>
> End Class
>
> There's not a lot you can do with it once you've created it,
> admittedly, but you can create it...
>
> --
> Jon Skeet - <skeet@pobox.co m>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too[/color]

[Peter Vervoorn]

Re: VB.NET to c# convert

Could you compile what you have and then use anakrino or similar to
decompile into c# source?

"Michael Nicol" <michaelnicol@w oolworths.co.za > wrote in message
news:u%23cvSSeh EHA.3992@TK2MSF TNGP11.phx.gbl. ..[color=blue]
> Hey all
>
> Our company recently started using .net and started in VB.NET. We've
> since
> changed to c#, but has some code already written in VB.NET. I'm looking
> for
> a converter that will just take vb.net and convert it into farely nice c#.
> I've found one or two, but they do some strange stuff and was wondering if
> there is a Microsoft converter or one generally accepted as being good by
> the community?
>
>
>[/color]