Hi!
I need some structural advise here...
I'm developing something that requires a lot of assemblies, destributed as several projects. Most of the projects are independant (with no dependencies by eachother) because I use the basic of the plugin technology to detect and creat the assemblies I need at run-time.
Untill he everything ok, but, sudenlly, the few dependencies I must have, referenced directly to the dll, not a project dependency, started generating errors. Something so stupid like: Object A cannot be converted in Object A. I beleave this is a vertioning problem but I can't find a way to get around it!
My main question is:
In this kind of project structure, what's the best practice to store the compiled code and what's the best practice to reference assemblies?
Thanks!
Alex
I need some structural advise here...
I'm developing something that requires a lot of assemblies, destributed as several projects. Most of the projects are independant (with no dependencies by eachother) because I use the basic of the plugin technology to detect and creat the assemblies I need at run-time.
Untill he everything ok, but, sudenlly, the few dependencies I must have, referenced directly to the dll, not a project dependency, started generating errors. Something so stupid like: Object A cannot be converted in Object A. I beleave this is a vertioning problem but I can't find a way to get around it!
My main question is:
In this kind of project structure, what's the best practice to store the compiled code and what's the best practice to reference assemblies?
Thanks!
Alex