G
Guest
I have a .net assembly (dll) that is com exposed and is build with 1.1
framework. My main application is in unmanaged c++ EXE. I make a cocreate and
create my .net assembly in it. After installing the .net 2.0 on the machine,
it seems that whenever my .net assembly dll is loaded, it loads the .net 2.0
dlls and not 1.1 dlls. My registry for the .net assembly has the Runtime
version as 'v1.1.4322'. But when my application creates an instance of my
..net assembly, it loads the .net 2.0 dlls. This is causing some problem in my
assembly. If i try to use the same from a managed C# application, it loads
the .net 1.1 dlls correctly. Why doesn't it do the same from an unmanaged c++
application? It seems to ignore the Runtime version flag and always load the
latest version available. Is this a bug? Any feedback would be appreciated.
framework. My main application is in unmanaged c++ EXE. I make a cocreate and
create my .net assembly in it. After installing the .net 2.0 on the machine,
it seems that whenever my .net assembly dll is loaded, it loads the .net 2.0
dlls and not 1.1 dlls. My registry for the .net assembly has the Runtime
version as 'v1.1.4322'. But when my application creates an instance of my
..net assembly, it loads the .net 2.0 dlls. This is causing some problem in my
assembly. If i try to use the same from a managed C# application, it loads
the .net 1.1 dlls correctly. Why doesn't it do the same from an unmanaged c++
application? It seems to ignore the Runtime version flag and always load the
latest version available. Is this a bug? Any feedback would be appreciated.