I would like to take advantage of this feature  available when loading a module - supportsprobingprivatepath -- I think ...

What I want to do is install two support assemblies that may colide with others installs..  Specifically ITextSharp and ZedGraph and  Report Module uses ZedGraph for example.   Both of these common libraries could be previously installed on a DNN site.   How can I ensure that I get access to my versions.   Can I place them in the /desktopmodules/mymodule directory or use the manifest option to place them in an subdirectory of /Bin.

If I place them into the subdirectory, I will need to load them explicitly via code-- correct?  But how does the module itself get loaded ... will DNN look for it in the sub-directory?

Any insight would be appreciated...  also since DNN V5.0 is enhancing the module definitions is there a better (different)  way in Version 5?

Thanks in advance,
Paul.

Basically it' not possible to do this. Whenever a dll is first accessed it loads into the application workspace, and cannot be unloaded from it - that's why changes to the bin folder/web.config etc. force an app recycle, it's to remove the contents to allow for refreshes. Whilst you could use a probingpath to put 2 different copies of the same type within your folder structure, it would mean that (depending on setup) ,either only one would ever load or the 2nd would load and cause a crash. There is no way for 2 copies of the same type with different versions to exist in the application workspace, unless they are strongly named i.e. if they are in the GAC, at the point at which they're loaded their name and version is known so they can coexist.

Cathal

Thanks for the feedback.   Do you have any suggestions ...

what I am concerned about is the use of ZedGraph -- my module might need one version and the report module needs another ... If installed in the /Bin directory, an upgrade could result in the failutre of some other module.

Paul.