I have two assemblies (one dependent on another) that need to be loaded dynamically. I also have a certain version of the two assemblies referenced in the project, but a different version than this version should be executed depending on the assemblies loaded. How can I make sure that the executed code comes from the dynamically loaded assemblies and not from the static references in the project?
Here's some pseudo-code of what I'm trying to do:
Assembly assembly1 = Assembly.LoadFile( @"c:\assembly1.dll" );
Assembly assembly2 = Assembly.LoadFile( @"c:\assembly2.dll" );
Assembly2Type a2 = (Assembly2Type)assembly1.C
CreateInstance does seem to create the right type, but Assembly2Type seems to used the project-referenced version of the assembly instead of the dynamically loaded assembly.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Do you have a specific reason why you need to load Assembly1 again as you already have it in the reference. If you refer the different version of .NET assembly you need to be careful as you might run into DLL hell. Second, you should use Assembly.Load instead of Assembly.LoadFrom since if the assembly with the same identity has been loaded already, it will not be loaded again via .LoadFrom
I would consider a factory pattern, to make sure all your code goes through the proper assembly.
If you want to implement stuff differently based on configuration, you might have a look at the provider model.
But I need to guess the purpose you have for these assemblies.
If for e.g. Assembly1 handles communication via sockets, Assembly2 via pigeons, the provider model would be good for you.
you can find a fully working sample on:
http://www.cloudsamples.ne
The idea is: Have a common interface for your assemblies, and then instantiate the proper assembly instance depending on the configured provider.
Steps:
- Create custom configuration section
- Use System.Configuration.Provi
- Create common base class/interface for your 2 classes.
- Create factory to create the instance based on your config.
good luck!
Business Accounts
Answer for Membership
by: gromulPosted on 2008-01-04 at 17:35:13ID: 20587388
Btw, Assembly2Type is an interface for Assembly1Type.