.Net 1.1 and 2.0 don't play well together!

April 4, 2006 2:59 AM

How can I use a .Net 1.1 assembly in my .Net 2.0 application?

Here's my scenario: I have a .Net 1.1 assembly, provided by our Denmark-based development office. My application has been written entirely in .Net 2.0, referencing other internal .Net 2.0 assemblies and using nice new 2.0-specific features. In theory, we could get the .Net 1.1 assembly migrated over to 2.0, but is there any way to just use it in my application without having to go through all that hassle? I don't really understand how things like assemblybinding in the config file works, so if there's some way to do it with that I'd be glad to use it. The reason that I want to make sure that this .Net 1.1 assembly uses the 1.1 Framework is because, well, it accesses protected memory if I try to use it in the 2.0 Framework (and it's confirmed to work in 1.1 :)) It would be great if I could just get it up and running without having to worry about getting it recompiled into 2.0 - we'd prefer to not have to worry about all that hassle.

posted by antifuse to computers & internet (3 comments total)

Upon further discussion with one of my real-smart-with-.Net-friends, it seems as though the only way to do this is to spawn a separate .Net 1.1 process to encapsulate the functionality of this control, and access it via remoting or something... Ooog.
posted by antifuse at 3:51 AM on April 4, 2006

That sounds a little suspicious. I have several 1.1 assemblies linked into a number of different 2.0 projects right now, and the process of doing so wasn't any different in either nant or Visual Studio from the same process in 1.1. Provide a little more info, such as what exactly this assembly does, and maybe we can get you sorted out.

I'm not even sure what "spawn a separate .Net 1.1 process" means...
posted by feloniousmonk at 7:57 AM on April 4, 2006

Solution: force the Danish guys to actually look at their code, where they can see that the problem was the result of a bug in their code, rather than dismissing my problem as being a result of linking to 2.0. Man, do I ever hate "it can't possibly be my problem" coders.

(and by "spawn a separate .Net 1.1 process" I mean "write a whole new .Net 1.1 app that encapsulates all the functionality of the control, and exposes it via remoting, and then launch that app from within my 2.0 app and have my head explode with the ugliness of it all :))
posted by antifuse at 8:52 AM on April 4, 2006