I have that problem and I haven't ever thought of a "good" way around it -- I previously didn't package it with the DLL at all and then just manually uploaded the DLL to the bin folder. 

One thing I saw suggested is actually creating a completely separate module that has no view or edit controls and doesn't do jack but contains DLLs and only DLLs.  You provide it as a module package to install the shared DLLs and only uninstall it when/if you want to uninstall everything.  That method actually sounded really cool and a great idea.

Otherwise, just like you said, if you have the same DLL actually packaged with more than one module package and end up uninstalling one, you are screwed because the dependency is deleted and your module no longer can work.

If you ever used the original Smart-Thinker modules you'll know I've had this problem for years now. The best solution I had (I used to have a seperate Module Framework project) was to copy all the classes into each project... a pain, I know, but I never have versionining issues at least. It's a real pit the DNN installer is not smarter!

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players