VS 2003 to VS 2008 - Can not load type library
-
I successfully converted a project from VB6 to VS2003 as VS2003 is what I had originally. Everything was working as expected. I just got VS 2008 and upgraded (opened) the project and now I get an error with one of the DLLs I wrote (I have a couple and the others worked fine) the error is type 'MyXXX.XXX' is not defined, so I go to add a reference and I get the error: A Reference to 'C:\mypath\MyXXX.dll' could not be added. Could not load the type library, Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY) Googled it but did not seem to find much directly related any idea where I should be looking? (or doing?) Thanks in advance, No-e
-
I successfully converted a project from VB6 to VS2003 as VS2003 is what I had originally. Everything was working as expected. I just got VS 2008 and upgraded (opened) the project and now I get an error with one of the DLLs I wrote (I have a couple and the others worked fine) the error is type 'MyXXX.XXX' is not defined, so I go to add a reference and I get the error: A Reference to 'C:\mypath\MyXXX.dll' could not be added. Could not load the type library, Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY) Googled it but did not seem to find much directly related any idea where I should be looking? (or doing?) Thanks in advance, No-e
Has that type library been upgraded as it's own project and recompiled??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
Has that type library been upgraded as it's own project and recompiled??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
Nope, have not touched it in years.... I have a couple, this one does not work, the others do. No-e
The next thing I'd do is recompile that component under the new compiler and try it. It could be that the component is encounter a breaking change from .NET 1.1 to running under .NET 2.0.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...