Hi Wout, I see in the newer versions that you are requiring apps to be signed. Is that a requirement only for the directly linked assembly or for all assemblies in the application? We have avoided signing our complete app in the past because we load user plugins (which would also have to be signed if we signed the whole application) - is that something we'd have to change to continue to use these newer licenses? The assembly that we link CadLib to is already signed so that wouldn't be as much of an issue... Also we often use Linqpad to work with our tools (internally) but AFAIK there's no way to have linqpad sign the assemblies it builds - does that mean we wouldn't be able to use that tool going forward? Cheers, Chris

One other thought - is there a limit on how many applications we can sign? or we need to use the same signing key for all applications or... ?

Hi Chris, Just for the assembly that calls CadLib. Since .NET Core not all assemblies need to be signed if the exe is signed. You just get a compiler warning that can be safely ignored. You can create as many applications as you want and use the same signing key. - Wout