5

I have been tasked with moving a rather large project from VB.Net to C#. Are there any converters, and if so what should I watch for? Are there areas of the code that are known to be problem areas during a conversion like this (Data Access Layer, etc..)

  • 3
    Why would you want to? You can use C# code in a VB.NET app. Why go through the trauma of conversion? – cletus May 24 '09 at 07:47
  • I was going to comment the same way, but I figured they must have a reason (like harder to find VB.NET developers?) – Mitch Wheat May 24 '09 at 08:01
  • I was thinking the same thing. Why not legacy the VB code, and slowly migrate to C#. VB.Net maintenance shouldn't be that arduous, since it's so close to C# in terms of runtime anyway. – Will Hartung Jun 26 '09 at 00:28

3 Answers3

4

Please see these SO posts:

Community
  • 1
  • 1
Mitch Wheat
  • 295,962
  • 43
  • 465
  • 541
2

There's an open source C#/VB.net IDE called SharpDevelop that has a converter to convert from VB.net to C# and C# to VB.net.

Beatles1692
  • 5,214
  • 34
  • 65
1

The amount of required patience is proportional to the size of the project.

GEOCHET
  • 21,119
  • 15
  • 74
  • 98
victor hugo
  • 35,514
  • 12
  • 68
  • 79