Page 1 of 1

PACKAGE LOAD FAILURE

Posted: Thu 30 Aug 2007 17:25
by woolf2k
I have VS2005 Pro

The error occurs the momment i start up VS.

This started after I uninstalled the Trial version and installed the full version of mysqldirect .net v 4.2 team.

I've tried uninstalling and reinstalling numereous times checking and unchecking boxes but i still get the error.

How do i fix this?

and my collegue is having the same exact issue on her computer.

Posted: Fri 31 Aug 2007 07:40
by Alexey
Please create a text file called fix.reg with the following content:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\{56ECB50E-9170-472e-8EED-67E016185FAB}]
@="CoreLab.MySql.Vs.MySqlDataProviderPackage"
"Class"="CoreLab.MySql.Vs.MySqlDataProviderPackage"
"CodeBase"="C:\Program Files\CoreLab\MyDirect.NET2\CoreLab.MySql.Vs.dll"
"InprocServer32"="C:\WINDOWS\system32\mscoree.dll"
"Assembly"="CoreLab.MySql.Vs, Version=4.20.17.0, Culture=neutral, PublicKeyToken=09af7300eec23701"
"CompanyName"="Core Lab Software Development"
"ProductName"="MySQLDirect .NET"
"ProductVersion"="4.00"
"MinEdition"="Standard"
"ID"=dword:000003ee
Execute it. Then fire "devenv /resetskippkgs" from the command line.

Did this solve the package load issue?

Posted: Sat 01 Sep 2007 19:03
by cglock
I have VS 2005 Standard installed with 4.20.17.0 and get the same error message, applied the suggested fix above but did not seem to help.

Watch the drive letters in suggested fix.

Posted: Sat 01 Sep 2007 19:15
by cglock
Trying to get this nuisance taken care of I forgot to check the drive letters listed in the fix.

Re: PACKAGE LOAD FAILURE

Posted: Mon 03 Sep 2007 07:57
by capt_henry
Hi,

I get the same problem after upgrading from v4.0.13 Pro to 4.20.17 Pro with VS2005 Pro.

Checked the registry and the settings are as per reg example (with exception of drive paths).

Tried the suggested fix (with drive changes) and devenv /resetskippkgs but same problem.

For now I have uninstalled 420.17.0 and went back to 4.0.13.0 and all is OK.

Posted: Mon 03 Sep 2007 08:01
by Alexey
cglock wrote:Trying to get this nuisance taken care of I forgot to check the drive letters listed in the fix.
So the problem doesn't persist anymore?

Posted: Mon 03 Sep 2007 09:44
by Vic D'Elfant
The above registry patch fixed the problem for me as well - thanks! :)

Posted: Mon 03 Sep 2007 15:54
by BobMc
The Patch Worked for me also!!

Thank you for the prompt reply.

PACKAGE LOAD FAILURE

Posted: Tue 04 Sep 2007 15:13
by woolf2k
thank you. It appears like that patch worked.

Posted: Thu 06 Sep 2007 11:23
by Alexey
You are welcome.