VB.NET to c# convert

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
Thu Aug 19 07:53:30 CDT 2004

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@woolworths.co.za> wrote in message
news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
>
>
>

Michael
Thu Aug 19 08:09:07 CDT 2004

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.netNoSpamM> wrote
in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
> 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@woolworths.co.za> wrote in message
> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
> >
> >
> >
>
>

One
Thu Aug 19 08:26:33 CDT 2004

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@woolworths.co.za> wrote in message
news:%23D%23X92ehEHA.1156@TK2MSFTNGP10.phx.gbl...
> 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.netNoSpamM>
wrote
> in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
> > 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@woolworths.co.za> wrote in message
> > news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
> > >
> > >
> > >
> >
> >
>
>

Nicholas
Thu Aug 19 08:28:12 CDT 2004

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.com


"Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
news:%23D%23X92ehEHA.1156@TK2MSFTNGP10.phx.gbl...
> 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.netNoSpamM>
> wrote
> in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
>> 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@woolworths.co.za> wrote in message
>> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
>> >
>> >
>> >
>>
>>
>
>

Mark
Thu Aug 19 08:41:51 CDT 2004

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.com> wrote in
message news:Ow$b$BfhEHA.556@TK2MSFTNGP10.phx.gbl...
> 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.com
>
>
> "Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
> news:%23D%23X92ehEHA.1156@TK2MSFTNGP10.phx.gbl...
> > 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.netNoSpamM>
> > wrote
> > in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
> >> 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@woolworths.co.za> wrote in message
> >> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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
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?
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

One
Thu Aug 19 08:43:02 CDT 2004

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.com> wrote in
message news:Ow$b$BfhEHA.556@TK2MSFTNGP10.phx.gbl...
> 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.com
>
>
> "Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
> news:%23D%23X92ehEHA.1156@TK2MSFTNGP10.phx.gbl...
> > 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.netNoSpamM>
> > wrote
> > in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
> >> 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@woolworths.co.za> wrote in message
> >> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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
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?
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

André
Thu Aug 19 09:26:13 CDT 2004

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

André Nogueira

"Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
>
>
>

One
Thu Aug 19 11:25:07 CDT 2004

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

"mscertified" <rupert@tigerlily.com> wrote in message
news:15BC700C-37AF-4129-8675-2A595F97DAAB@microsoft.com...
> One of the major selling points of .NET is that it is language
independent,
> so its pointless converting source languages.
>
> "Michael Nicol" wrote:
>
> > 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?
> >
> >
> >
> >

André
Thu Aug 19 11:40:49 CDT 2004

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$yeSkghEHA.556@TK2MSFTNGP10.phx.gbl...
> 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
>
> "mscertified" <rupert@tigerlily.com> wrote in message
> news:15BC700C-37AF-4129-8675-2A595F97DAAB@microsoft.com...
>> One of the major selling points of .NET is that it is language
> independent,
>> so its pointless converting source languages.
>>
>> "Michael Nicol" wrote:
>>
>> > 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?
>> >
>> >
>> >
>> >
>
>

Jon
Thu Aug 19 11:51:40 CDT 2004

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

Option Strict On

Imports System

Class Test

Shared Sub Main
Dim x as UInt32 = Convert.ToUInt32(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.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

One
Thu Aug 19 11:57:54 CDT 2004

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.com> wrote in message
news:MPG.1b8eeaf9269867b798b1ee@msnews.microsoft.com...
> <"One Handed Man \( OHM - Terry Burns \)" <news.microsoft.com>> wrote:
> > OK then, tell me how you would create a Unsigned Int in VB.NET, which
you
> > can do in C#
>
> Option Strict On
>
> Imports System
>
> Class Test
>
> Shared Sub Main
> Dim x as UInt32 = Convert.ToUInt32(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.com>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too

Peter
Thu Aug 19 12:25:02 CDT 2004

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

"Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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
Thu Aug 19 12:50:54 CDT 2004

I can see a reasoning in maintainability. If your company standardizes on
C#, you do not necessarily want to cross-train devs in VB.NET. I have no
problem in either language, but I can see good reasons to standardize, esp.
for smaller companies without many devs.

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

************************************************
Think Outside the Box!
************************************************
"Nicholas Paldino [.NET/C# MVP]" <mvp@spam.guard.caspershouse.com> wrote in
message news:Ow$b$BfhEHA.556@TK2MSFTNGP10.phx.gbl...
> 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.com
>
>
> "Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
> news:%23D%23X92ehEHA.1156@TK2MSFTNGP10.phx.gbl...
> > 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.netNoSpamM>
> > wrote
> > in message news:%23mKeHuehEHA.4064@TK2MSFTNGP12.phx.gbl...
> >> 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@woolworths.co.za> wrote in message
> >> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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
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
Thu Aug 19 12:53:26 CDT 2004

I think the issue is the devs of the original used the "training wheels"
inherent in VB, which means the C# program, once decompiled, would have
references back to Microsoft.VisualBasic and
Microsoft.VisualBasic.Compatibility, adding weight that need not be there.
Decompilation is a good start.

If I were doing it this way, I would decompile and remove all VB reference
statements and fix all the explosions. It is an option. Salamander
decompiler is even sweeter, but a bit pricey for some shops.

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

************************************************
Think Outside the Box!
************************************************
"Peter Vervoorn" <newsuser@vervoorn.com> wrote in message
news:4124e220$0$78772$e4fe514c@news.xs4all.nl...
> Could you compile what you have and then use anakrino or similar to
> decompile into c# source?
>
> "Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
> news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
> >
> >
> >
>
>

jpierce
Thu Aug 19 20:38:07 CDT 2004

"Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message news:<u#cvSSehEHA.3992@TK2MSFTNGP11.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 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?

Hi Mike,

Our Decompiler.NET product does a good job with translating VB to C#
into high level readable code that compiles and runs correctly. It is
also priced very reasonably compared to some of the other
alternatives. You can download a free trial version and confirm that
it works well for you from our web site at:
http://www.junglecreatures.com/

Jonathan Pierce
President
Jungle Creatures, Inc.
http://www.junglecreatures.com/

Ralf
Fri Aug 20 04:04:47 CDT 2004

Get a copy of Reflector (http://www.aisto.com/roeder/dotnet/) which allows
you to look at VB.net code in C# and vice versa. The file disassembler
add-in is quite useful to get the files written to disk
(http://www.denisbauer.com/NETTools/FileDisassembler.aspx).

You can also find some VB.net to C# converters on Google


"Michael Nicol" <michaelnicol@woolworths.co.za> wrote in message
news:u%23cvSSehEHA.3992@TK2MSFTNGP11.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 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?
>
>
>

Syed
Sun Aug 22 03:13:02 CDT 2004


Have you tried the latest #develope IDE, from http://www.icsharpcode.com

they seems to have option of coverting VB.net code to C# and vice versa.
and they also support option of importing & exporting Visual .Net 2003
proojects.


hope this might help.



"Michael Nicol" wrote:

> 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?
>
>
>
>

Daren
Tue Aug 31 03:19:11 CDT 2004

I've been using http://www.instantcsharp.com/ on the csharpnuke.com project

It handles most of the vb.net to c# quirks,

I'd certainly recommend looking at it.


"Michael Nicol" wrote:

> 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?
>
>
>
>

tb_anywhere
Wed Sep 01 05:28:01 CDT 2004

There is tools that converts vb and vb.net to c#.
free download!!.
http://www.e-iceblue.com

sudheer
Tue Apr 19 13:53:03 CDT 2005

You can use this link to convert page by page.
http://www.developerfusion.com/utilities/convertvbtocsharp.aspx



"Michael Nicol" wrote:

> 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?
>
>
>
>