Converting VB 6.0 application to C#

[David C]

My client has talked to me about taking over their VB 6.0 project,
which I really don't want to do. I did VB seven years ago.

I told them that I would do so only if they are willing to migrate
over to C# winforms, which I think is the best way to go in the long
run.

So has anyone done this? I do not picture myself doing this by hand
and a quick google search shows some conversion tools in the market.
What is the viability of using one and migrating to C# winforms?

 

[Michael C]

My client has talked to me about taking over their VB 6.0 project,
which I really don't want to do. I did VB seven years ago.

I told them that I would do so only if they are willing to migrate
over to C# winforms, which I think is the best way to go in the long
run.

So has anyone done this? I do not picture myself doing this by hand
and a quick google search shows some conversion tools in the market.
What is the viability of using one and migrating to C# winforms?

I haven't seen these products but anything you do will require a significant
amount of work.

Michael

 

[Petar Atanasov]

My client has talked to me about taking over their VB 6.0 project,
which I really don't want to do. I did VB seven years ago.

I told them that I would do so only if they are willing to migrate
over to C# winforms, which I think is the best way to go in the long
run.

So has anyone done this? I do not picture myself doing this by hand
and a quick google search shows some conversion tools in the market.
What is the viability of using one and migrating to C# winforms?

Even VISTA supports Classic VB Runtime, as you can see in
http://channel9.msdn.com/ShowPost.aspx?PostID=241076

....

And I agree with Michael - there's no tool, that replaces dev effort
completely...

Regards,
Petar Atanasov
http://a-wake.net

 

[Guest]

Most of the tools (including ours) convert VB.NET (or VB 2005) to C#, not VB6
to C#.
Upgrade to VB.NET/2005 first and then use a tool to convert to C#. The bulk
of your work will be going to .NET, not the VB to C# part - all of the
converters will handle this part better than the upgrade wizard handles VB6
to VB.NET/2005.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
C++ to C# Converter: converts C++ to C#
Instant C++: converts C# or VB to C++/CLI

 

[Brian Schwartz]

There are so many important differences between VB6 and the .NET Framework
(VB or C#) that you'll almost certainly be better off doing the conversion
to .NET manually.

 

[David C]

Upgrade to VB.NET/2005 first and then use a tool to convert to C#. The bulk
of your work will be going to .NET, not the VB to C# part - all of the
converters will handle this part better than the upgrade wizard handles VB6
to VB.NET/2005.

When you say "upgrade to VB.NET/2005 first" is this all manual?

 

[Guest]

Use the upgrade wizard with VS 2005 (or 2003). It does most of the grunt
work, but you'll have to make numerous adjustments to get it to compile.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
C++ to C# Converter: converts C++ to C#
Instant C++: converts C# or VB to C++/CLI