Good day, I understand that a ww.license.dll file is needed for the application to be able to use the cad libraries. For our internal development, we normally package all dll files with the exe (using ilmerge), and obfuscate the resulting exe. Will this create a problem for the license dll? Thanks and regards, Jean

Hi, I've no idea to be honest, I give it a 87% chance that it will work OK. CadLib doesn't use any special Assembly loading mechanism to load WW.License.dll. - Wout

The license dll is used for the .NET 4.0 CadLib version by the way, for later versions the licensing changed to use a license string, and the calling assembly has to be signed with a strong name key. - Wout

We do not normally sign our assemblies, except when they are to be used outside. Not sure we still have a valid certificate. Are there alternatives to signing? Thanks! Jean

Hi, Signing with strong name key, not with certificate (they are different things). Creating a strong name key is free, it's just that the license can verify the signature of it. There's no alternative for CadLib 6.0. - Wout