Migrating VS2003 to VS2005

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Boni - 01 Feb 2006 15:04 GMT

Dear all,
I get following error, when I try to call dll compiled in VS2003 inside
addin in VS2005 environment:
System.InvalidCastException: Unable to cast COM object of type
'System.__ComObject' to interface type
'Microsoft.VisualStudio.VCProjectEngine.VCProject'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{70B6C8E7-5B3E-49C7-9937-C5F0B3168AF3}' failed due to the following
error:
(Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
May be somebody already had this?
Thanks a lot,
Boni

Reply to this Message

Carlos J. Quintero [VB MVP] - 01 Feb 2006 17:07 GMT

Hi Boni,

> I get following error, when I try to call dll compiled in VS2003 inside
> addin in VS2005 environment:

Which compiled dll? Your own? Do you have the code and the line that is
crashing?

> System.InvalidCastException: Unable to cast COM object of type
> 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.VCProjectEngine.VCProject'. This operation failed

You can use

Typeof obj Is Microsoft.VisualStudio.VCProjectEngine.VCProject

to test if the cast is valid.

Also, you can use Microsoft.VisualBasic.Information.TypeName(obj) to get the
underlying class behind a System.__ComObject. Maybe it is not a VCProject
after all...

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com

Reply to this Message

Boni - 03 Feb 2006 12:19 GMT

Hi Carlos,
I found the reason VCCompilertool , pchOption has changed there is no more
"Auto" option.
Thanks,
Boni

> Hi Boni,
>
[quoted text clipped - 17 lines]
> the underlying class behind a System.__ComObject. Maybe it is not a
> VCProject after all...

Reply to this Message

Migrating VS2003 to VS2005

Free Magazines