Target the Framework version from 2.0 to 1.1

[b6s]

Dear all,
I have encountered a problem of "DragDrop registration failed"
problem in my .NET 1.1 dll because of the assembly binding is always
going to .NET 2.0. Therefore I tried to specifiy the runtime version
and redirect those bindings in MyModule.dll.config.

The binded assemblies, however, are still in .NET 2.0, according to
both VS.NET 2003's output log and VS.NET 2005's fuslogvw. Meanwhile,
they also logged compiling and linking processes. At that stage, linked
assemblies are in version 1.1 correctly.

My question is, does it means that configurations of runtime version
and assembly binding redirection do not work backward from 2.0 to 1.1?

Thank you for your precious time.

Best Regards,
Mike

 

[Carl Daniel [VC++ MVP]]

Dear all,
I have encountered a problem of "DragDrop registration failed"
problem in my .NET 1.1 dll because of the assembly binding is always
going to .NET 2.0. Therefore I tried to specifiy the runtime version
and redirect those bindings in MyModule.dll.config.

The binded assemblies, however, are still in .NET 2.0, according to
both VS.NET 2003's output log and VS.NET 2005's fuslogvw. Meanwhile,
they also logged compiling and linking processes. At that stage,
linked assemblies are in version 1.1 correctly.

My question is, does it means that configurations of runtime version
and assembly binding redirection do not work backward from 2.0 to 1.1?

A single process can host only a single version of the CLR, so if the EXE
that launched the process is a 2.0 assembly (or isn't forced to run under
1.1), then the entire process will run under 2.0.

-cd

 

[b6s]

Oh, actually all my assemblies were compiled in 1.1 (VS.NET 2003);
however, since my develop environment also has 2.0 (VS.NET 2005), the
system usually load "system assemblies" in some of 2.0 (such as
System.Xml.dll) and some of 1.1 (such as System.Drawing).