Don't think its problem to have 2 dlls loaded.

 

You can open project in solution and rename dll name to ToolkitPro1200.dll,

 

We've been having a few problems with versioning, related to the version number and build-environment being hard-coded into the name of the DLLs.

 

What is the policy regards naming the DLLs if there is no API change?

 

For instance, if we ship 30 DLLs, which depend on ToolkitPro1200vc60.dll, then we need to patch one of the DLLs, but meanwhile you released v 12.1 with some bug-fixes, so when we build the new DLL it depends on ToolkitPro1201vc60.dll we have a problem.

 

This is because all of a sudden if we shipped the new CJ DLL as well, we'd have 2 CJ DLLs loaded in the space of our application.  Is this a real problem or can multiple CJ DLLs co-exist in the same process space?

 

Otherwise we need to rebuild all modules, and release all as a patch, and they need to be synchronised (i.e. client can't update some modules and not others).

 

We also don't like having the build environment coded into the DLL name.

 

Adrien