With all dlls for dotnetnuke in the bin folder and EntitySpaces moving so fast up the version numbers, is there a recommended approach to protecting existing modules using older versions form being killed by placing newer version of ES in the bin folder?

Is there some way of referencing ES dlls in a DesktopModules\MyModule\Bin folder? Or can the ES dlls be renamed - mymod.ES.Core.dll or packaged within mymod.dll?

What is recommended best practice?

Thats a very tricky question liffey. As you know this really is not ES specific, all component assembly manufacturers face the same challenges. You could try referencing your specifically desired versions from /SomeFolder in your module project. I am honestly not sure how assembly probing will handle this. One could also use an assembly redirect to point older versions of our dlls to the new desired ones, however if a business object regeneration is required then you will still have issues. Give it a whirl, and report your results back. If there is anything we can do to help make this situation work for all parties then we would love to.

---

Regards,

Scott Schecter
EntitySpaces | My Site