Vb.Net to C# Conversion

  • Thread starter Thread starter Rajesh
  • Start date Start date
R

Rajesh

Hi guys,

It wil be very helpful if sumone could give me the pros and cons,Guidelines
or links for converting Vb.net projects to c#.

Regards
Rajesh
 
Rajesh said:
It wil be very helpful if sumone could give me the pros and cons,Guidelines
or links for converting Vb.net projects to c#.

Well, I've had some success with Instant C# from Tangible Software.

Disclaimer: I've been given a free licence for it, so I'm biased in
terms of gratitude. I've also only used it on a single project.
However, it did well on that (and has got better at doing it as the
converter has improved; I've converted the same project a few times).

See http://www.instantcsharp.com

Jon
 
Thanks Jon

What additional work you had to do after converting the vb.net project to
c#.Actually the project was converted from asp 3.0 to vb.net.The code looks
very sloppy , complicated , confusing and dirty. Im just trying to figure
out the major components that can be redesigned in C# since im new to the
project and Im given the responsbility to redesign the entire project( Any
suggestion?).Im the Tech lead out here

Regards

Rajesh
 
Rajesh said:
What additional work you had to do after converting the vb.net project to
c#.Actually the project was converted from asp 3.0 to vb.net.The code looks
very sloppy , complicated , confusing and dirty. Im just trying to figure
out the major components that can be redesigned in C# since im new to the
project and Im given the responsbility to redesign the entire project( Any
suggestion?).Im the Tech lead out here

I had very little to do after converting the project, but it was a
fairly small project. However, after converting it I went about
refactoring the code, and that let me get rid of a few VB-isms that
remained anyway.

Jon
 
Thanks peter So if i had to convert from classic Asp or vb.net to C# do you
have any kind of checklist?
 
What kind of a "Checklist" would you need? What you probably need to do is
outline exactly what the original application does and carefully rewrite it
for the .NET Platform, taking advantage of what it has to offer with
best-practices coding techniques. I think a good outline of exactly what
each section of the app does is a good place to start.
Good luck!
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
 
Hi,

Rajesh said:
Thanks Jon

What additional work you had to do after converting the vb.net project to
c#.Actually the project was converted from asp 3.0 to vb.net

You better rewrite the entire thing, you could use the components in case
they use a VB6 dll or have some business logic well delimited.

The experience I have with ASP sites is that it's a big spaghetti with code
inside the html portion and one page doing several things depending of one
or more parameters
 
Instant C# will provide some ToDo comments, but the rest of the adjustments
you'll have to make are mandated by the compiler. In other words, once you
take care of the ToDo's and get the final project to compile, that should be
the end of your adjustments. Naturally, you should ensure that your own
internal testing is satisfied.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C# to C++ converter & VB to C++ converter
Instant J#: VB to J# converter
 
Back
Top