Wrong COM version for Interop Assembly

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rick Strahl [MVP] - 16 Jan 2005 03:16 GMT

HI all,

I have a COM Interop assembly I'm accessing through VB and VFP. I'm trying
to debug the thing in VS.NET and it turns out I can't because it's loading V
2.0 of the .NET framework. If I debug the component as soon as it is
accessed with the VS 2003 debugger attached VS closes the running
application and stops debugging. If I just run the component and return the
version number back (Environment.Version) it returns 2.0...

This component is CodeBase registered - not installed in the GAC and this
would have to be so for debugging I suppose. If I look in the registry I can
see that the RuntimeVersion is correctly compiled as 1.1.4 and the entry is
there in the InProcServer subkey.

Why is .NET firing up the wrong version?

Any ideas?

+++ Rick ---

Signature

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
http://www.west-wind.com/wwThreads/
----------------------------------
Making waves on the Web

Reply to this Message

Rick Strahl [MVP] - 16 Jan 2005 05:18 GMT

Ok, I foudn my own answer:

I need to create a config file with:

<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.0.3705"/>
<requiredRuntime version="v1.1.4322"/>
</startup>
</configuration>

and name it the same as the EXE that's running.

In this case VFP9.exe.config or MyApp.exe.Config.

Nothing to see here <g>...

+++ Rick ---

Signature

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
http://www.west-wind.com/wwThreads/
----------------------------------
Making waves on the Web

> HI all,
>
[quoted text clipped - 15 lines]
>
> +++ Rick ---

Reply to this Message

Rate this thread:

Wrong COM version for Interop Assembly

Free Magazines