VB.NET to C# converters?

  • Thread starter Thread starter aaa
  • Start date Start date
Yeah, I don't see what good this converter is. It only seems to be able to
convert projects built in this IDE. If I import a VStudio project then try
to convert the convert option is greyed out.



Markus Thurner said:
Are there any VB.NET to C# project converters out there?
Click to expand...

I use SharpDevelop [1] as my preferred IDE, it has quite a nice
converter form VB to C# (Tools -> Convert Buffer).

hth
thoean

[1] http://www.icsharpcode.net/OpenSource/SD/Default.aspx
Click to expand...
 
My question would be "why on earth do you need one?" I don't mean to be
flippant, really, but with the interoperability between languages that the
CLR gives you, why can't you leave the VB code alone, and do any new work in
C#? What's the scenario I'm not seeing that makes you want a converter?
 
It's common for single projects to be assigned to individual developers - if
you inherit a VB.NET project and feel more comfortable in C# then you may
want to convert it. Also, it's common for a shop to standardize on one or
the other - for a developer in such a shop, a converter may be useful.

We offer converters that go in both directions:
Instant C#: VB.NET to C#
Instant VB: C# to VB.NET

Both have free and supported Demo Editions.
 
This is how I convert between languages, if I have to:

- Get the Lutz Roeder's Felfector tool from
http://www.aisto.com/roeder/dotnet/: This can disassemble any compiled DLL
to IL, VB.net or C# code (and many more languages including C++ are
supported)

- Then get the Reflector.FileDisassembler from
http://www.denisbauer.com/NETTools/FileDisassembler.aspx: This add-in can
exports code from any DLL to any language that the Reflector supports.

Even though this process requires a little bit more work, it is not error
prone, and best of all it's free and works across a lot more languages. It
is also guaranteed to work because you are working from a compiled DLL and
not source code.

Hope this helps!

Shariq Khan
(e-mail address removed)
 
Marcos Stefanakopolus said:
My question would be "why on earth do you need one?" I don't mean to be
flippant, really, but with the interoperability between languages that the
CLR gives you, why can't you leave the VB code alone, and do any new work in
C#? What's the scenario I'm not seeing that makes you want a converter?
Click to expand...

Very simple: you have a piece of sample code in one language, and you
want to use it in a project which is in another language. It's not a
good idea to use different assemblies just because you can't convert a
piece of code into the desired language.

Another use is for helping people in newsgroups - if someone wants to
see some code in VB.NET, and I only know C#, I'm relatively stuck
without a converter.
 
Back
Top