1

I want to convert my old vb6 project to a vb.Net solution, when I open do: File->Open->Convert this is what I get:

enter image description here

And I can't find a way to show the available converters...

I have try:

  • Installing framework 1.0 since I read somewhere that it's needed
  • Tried to install framework 2.0 but it's says "I have it" but it's not showing in the uninstall programs list
  • Tried to install framework 3.0, same as before.
  • I even try to add the Microsoft.VisualBasic.UpgradeWizard.dll via regasm but I can't open a console command in VS2008, only in VS2010 and I have read that VS2010 can't handle the conversion from vb6 to vb.net, it has to pass over VS2008 first.

Thanks in advance!

Luis
  • 5,786
  • 8
  • 43
  • 62
  • @JimmyPena I don't think so, I just checked it in other browsers, try refreshing the page... – Luis Jul 17 '12 at 18:46
  • @JimmyPena it's ok, same here – Luis Jul 17 '12 at 18:51
  • possible duplicate of [Best Strategy for moving from VB6 to .NET](http://stackoverflow.com/questions/683918/best-strategy-for-moving-from-vb6-to-net) – C-Pound Guru Jul 17 '12 at 19:05
  • @C-PoundGuru This question is about the converter not working in VS2008 on one user's computer. It is absolutely **not** a duplicate of questions about which is the best conversion strategy. – MarkJ Jul 17 '12 at 19:23
  • 1
    @C-PoundGuru as you can see in the full description of the question, I can't choose a best strategy since **I can't even convert for the first time...** – Luis Jul 17 '12 at 19:54
  • @LuisSánchez: You're looking for a silver bullet (or an easy button). There really isn't one. You gotta do the work. – C-Pound Guru Jul 18 '12 at 00:54
  • My guess is that VS2010 has uninstalled it? Try completely uninstalling VS2010 and re-installing VS2008. However even if you get this working I doubt it will convert it for you in a meaningful way – Matt Wilko Jul 18 '12 at 11:14

2 Answers2

2

Well, the solution was to install Visual Studio 2005, then the converters were available:

I suppose I needed Framework 1.0.

Image showing the upgrade wizard

It's not perfect, it has some errors, but its a step forward for a complete solution.

Of course I've found some other 3rd party conversion programs, but they are expensive:

Hope it helps someone else!

Luis
  • 5,786
  • 8
  • 43
  • 62
0

No clue what that Convert dialog is for--there's nothing in the help on it.

According to this Forum Post, you can open the vbp in Visual Studio and it should ask to convert the project (no option to open a .vbp file in VS 2010). However, even if it still did that in VS 2010, it's a tremendously bad idea.

See also this post on converting VB6 to VB.NET.

Also, check these duplicated SO questions:

Edit: According to this MSDN Page, the conversion wizard only goes up to Visual Studio 2005

Edit Edit: Per MarkJ's comment, Visual Studio 2008 includes the upgrade wizard. It's gone in VS 2010.

Community
  • 1
  • 1
C-Pound Guru
  • 15,967
  • 6
  • 46
  • 67
  • Yes, i've seen all those posts, including this one which gives you the best step to step process http://www.codeproject.com/Articles/8004/On-Migrating-a-VB-Project-to-VB-NET now the problem is that i can't find a way to show those converters – Luis Jul 17 '12 at 19:53
  • @LuisSánchez: The most likely reason you can't see the converters is that Microsoft doesn't support VB6 to VB.NET conversion anymore. Perhaps an older version of Visual Studio (2003) would do it. Even if you can click the magic button, you will still have a huge mess on your hands--perhaps even bigger than just doing the work and writing the code. That's what I've had to do. – C-Pound Guru Jul 18 '12 at 00:56
  • Visual Studio 2008 [includes the upgrade wizard](http://msdn.microsoft.com/en-us/library/47s4twtx(v=vs.90).aspx). It was removed in VS 2010. The MSDN page you linked says the tool existed in VS2005. It **does not** say it was removed in any version. – MarkJ Jul 19 '12 at 20:22
  • @MarkJ: Thanks for pointing that out--didn't read more after finding the first article. – C-Pound Guru Jul 20 '12 at 13:40