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]" wrote:
Tana,
http://dotnet.mvps.org/dotnet/faqs/?...erters&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" <ta**@verizon.n etschreef in bericht news:%2******** *********@TK2MS FTNGP06.phx.gbl ...
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