Hey mediapyre,

There are really only a few things you need to do to avoid the types of module collisions that you mentioned - and they each have a pretty similiar theme - incorporate your unique name into as much of your module's naming as possible.

• Make sure you give your module's folder a unique name (e.g. c:\inetpub\wwwroot\MyDnnSite\DestkopModules\EngageModule)
• Use a "module qualifier" for database objects. (e.g. EngageModuleName_ObjectName)
• Use a unique (and consistant) name for your assembly / namespace (e.g. EngageModule.dll and Engage.Dnn.Modules.ModuleName)

Also, from a big picture standpoint, in order to maintain a clean upgrade path, it is essential for you to avoid making modifications directly to the core DotNetNuke application and only enhance it with extensions (Skins, Modules, Providers, etc...)

Hope that helps & welcome back!

Take care,

Ian