Friday, May 18, 2012 6:05 PM
Many moons ago I was VB6 Pro based.
I then upgraded to VB Express 2008 and ported my applications.
After a while I uninstalled VB6 with no problems.
In VB2008 is used some of the included power pack extensions.
Then Upgraded for VB Express 2010 and imported my 2008 apps with no problem.
Today many months later I decided to uninstall VB2008.
This immediately broke my vB 2010 apps as the power pack coding/links failed.
Any idea how I can fully migrate to VB 2010 and fully remove VB2008 wihtout breaking my 2010 projects.
Thanks in advance.
Friday, May 18, 2012 11:26 PM
Since the powerpacks were installed when vb2008 was installed after uninstalling 2008 just reinstall the powerpacks into vb2010 and then goto your my project page then the references tab and make sure the VisualBasic PowerPacks is referenced.
At least that is what I had to do.
- Edited by Curtis UN Friday, May 18, 2012 11:30 PM
Sunday, May 20, 2012 5:34 PM
Actually it was more complicated than both of us thought.
My project which I have ported from VB6 ....... VB2010 was carrying a link to VB6? Power Packs V1.1. This library is squirelled away in a place (MS Common files?).
Anyway I uninstalled VB2008 again. Reinstalled VB2010/Stuidio 10 and the same problem happend.
Tried installing VB Pwwer Packs V2 and V3 and still no joy.
Following the error/warning trail I looked at Project Properties and References to see the link back to old Power Packs V1.1.
I solved the problem by doing a delete of the current Power Pack 1.1 Reference / Path and then added a new link to .NET Power Packs V10.0.0.0
Looks like (and I can understand why) porting / migrating between Visual Studio Versions is not a simple affair. What would be a nice migration feature/path would be to be able Export your project from one Studio Version (including powerpacks / addons) to a new Studio version as a NEW project with no legacy "links". As a staged progress you could then resolve the issues on the original migration (when your code / design is fresh in your head) and not be hit many months later after migrration when you delete an old Studio version.
Not looking forward to VB/Studio 2011/12/13... as no doubt a) I'll have fogotten the migration issues and b) I'll have to painfully go through a horrible process again.
Monday, May 21, 2012 11:50 PM
Wish I could have been more help but it has been several years since I upgraded and migrated all my apps. I remember having several problems but I don't remember now what I did to solve them lol.
I have found out that I don't really care for the power packs. They have some drawbacks that can cause problems between different versions of windows OS. One problem is the printing of the form client area, it will work on XP and not work on some of the Windows 7 systems. I ran into this just the other day and had to go back to using PrintDocument by making a copy of the client area to a bitmap then drawing the bitmap in printdocument in order to print it.
I am going to stay with VB2010 for a while because I have several apps that are extremly large and will have to support for a few more years . Besides a lot of the refinements in VB2011 I don't need.