VB.net - C# converter

[Tana]

Hi,

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do the rest

I am using VS 2005.

thanks

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do
the rest

I am using VS 2005.

Several such tools exist.

Local apps and web apps.

I do not use VS.

SharpDevelop has a little tool to do it.

You can find a lot of alternatives via Google.

90-95% does not sound unrealistic, but you may still
want a person to go over the code anyway.

Arne

 

[Cor Ligthert [MVP]]

Tana,

http://dotnet.mvps.org/dotnet/faqs/?id=languageconverters&lang=en

Be aware that converting from C# to VB.Net is much easier than visa versa and therefore there are much more good C#->VB.Net converters than good VB.Net -> C# converters.

I hope this helps,

Cor
"Tana" <[email protected]> schreef in bericht Hi,

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do the rest

I am using VS 2005.

thanks

 

[Guest]

You can expect much better than 90-95%.
Try the various demo/trial editions of the available converters (including
ours), and pick the best one.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C#/VB to C++ converter
C# Code Metrics: Quick metrics for C#

 

[Guest]

I don't think that's true. We make both VB to C# and C# to VB converters and
they each have major challenges:

VB to C#:
The main challenge is to sort out the extremely high level of ambiguity and
diverse syntax alternatives. In addition, there are syntax alternatives from
*many* years back that are still supported in VB.NET.

C# to VB:
One main challenge is parsing - since there is no one-to-one correspondence
of line to statement you have to be able to parse possibly fragmented or
combined C# lines into sensible C# statements. Another challenge is that C#
doesn't spell out everything in agonizing detail like VB, so you need to work
harder to identify things (e.g., is the entity after the colon in a class
header a class or interface?, e.g., which methods will need "Implements" tags
- you need to have logic to accurately determine that).
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C#/VB to C++ converter
C# Code Metrics: Quick metrics for C#

 

[Cor Ligthert [MVP]]

David,

I don't think that's true. We make both VB to C# and C# to VB converters
and
they each have major challenges:

You mean that Tana can take any VB.Net -> C# Sharp converter and it should
not be precisely your product?

While writing my text I was thinking about your product because I know how
attentionful you are. I am not sure anymore if I have expirience with your
product. However, I have seen much more C# -> VB.Net converters than visa
versa.

I have not the idea that it is because there are more people converting from
C# to VB.Net (I have in fact lately only seen one in the language.vb
newsgroup who did that completely).



Cor

 

[Brian Gideon]

David,

I'm just curious. Does your C# to VB.NET converter handle anonymous
methods well?

Brian

 

[Guest]

It converts some cases of anonymous methods, but not all.
For example, anonymous methods referencing local variables in the scope of
the anonymous method call ('captured variables') are not converted.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C#/VB to C++ converter
C# Code Metrics: Quick metrics for C#

 

[Brian Gideon]

David,

Yeah, I figured captured variables would be difficult to convert. In
fact, I'm not sure how you would do it without implementing part of the
C# specification. There are some intricate rules regarding the
lifetime of the captured variables. It would be cool if you could
somehow accomplish that without too much effort.

Brian

 

[Tana]

Thank you everybody for your help, you people rule

David, I will definitely try your software.


Hi,

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do the rest

I am using VS 2005.

thanks

 

[chanmm]

One of the purpose of .Net framework is lighten the cross language calling. If you have existing VB.NET code in place then I believe you can just leave it. For your new application you can develop in C# or build it using class library perhaps so that your existing VB.NET can utilize the C# portion of it.

When you check the Microsoft patterns: http://msdn.microsoft.com/practices/ I don't think they specified which language you must use as well.

Good luck

chanmm
Thank you everybody for your help, you people rule

David, I will definitely try your software.

If
Hi,

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do the rest

I am using VS 2005.

thanks

 

[Tana]

Thank you everybody or your help.

Dave, I will definitely try your software.

chanmm, I also have a framework that is written in vb.net. That's why I better convert all my code.
Good news is it seams like these conversion tools actually do a good job, 95% of code gets converted and does not need any intervention. So, I am willing to do the rest, at this point we don't have to mach of code written.

regards
tana


Hi,

My company wants to migrate all our apps from vb.net to c#.
Can someone recommend a good migrate/convert tool?
I am hoping that such a tool can do a 90-95% work for me, and I will do the rest

I am using VS 2005.

thanks

 

[Tana]

David,

I must say that I am very pleased with your "instant C#" software.
I did convert much more than 95% of my code.

I reported the minor bug to your company and they fixed it the same day and provided me with a updated executable.
Excellent customer service.

I would recommend this software to anyone who needs to migrate VB.net code to C#.

Tana