Calling from .Net 1.1 to .Net 2.0/3.0

  • Thread starter Thread starter Jim1400
  • Start date Start date
Hello Jim1400,
What are the options for calling from .Net 1.1 to .Net 2.0/3.0 besides
COM? Thanks.
Click to expand...

Service level seperation is really the only way I know of ....

COM doesn't really cut it since a single process can only load 1 version
of the framework at once.

ie an initial app which loads framework 1.1 cannot interact with 2.0 code
directly even through COM as it would require 2 versions of the framework
to be loaded to cope.

Unless you force the app to load the latest version of the frameowrk in the
first place.
 
Rory,
Thanks for your reply. I really mean COM+ when I said COM. You mentioned
"Unless you force the app to load the latest version of the frameowrk in the
first place.". Could you give me some direction how to make it work this
way? Thanks!
Jim
 
Hello Jim1400,
Rory,
Thanks for your reply. I really mean COM+ when I said COM. You
mentioned
"Unless you force the app to load the latest version of the frameowrk
in the
first place.". Could you give me some direction how to make it work
this
way? Thanks!
Click to expand...


I thought that there was a way to redirect the Assembly bindings in an App.config
so that a 1.1 exe would run under 2.0 even if 1.1 was installed.
I cannot now remember the specifics but you should be able to find something
relating to this in google.
 
Back
Top