Signature Based Licensing

All current versions of our products, include a means to licence “bulk copies” of the toolkits (DicomObjects or XdsObjects) - e.g. when used by trusted customers for use on CDs etc.  This is a replacement for the previous “strong name” based licencing, which had multiple drawbacks.

To use this facility, which we call “applicaiton signing”, developers develop as normal (using a developer key), then get a “signature” for the executable by submitting it, alongside their special “signing key” (of the form wwww-xxxx-yyyy-zzzz)  using a small local signing program, which sends the hash of the executable to our servers, where the licence information is added, the whole thing is “signed”.

This program will place a licence file (executablename.exe.lic) in the same directory as the executable, which you must distribute (hidden if you wish!) also in the same directory as the executable.  When DicomObjects needs to obtain a licence, it will check this file first, and if a suitable signature is found and if it matches the hash of the program, it will obtain the licence details from that without offering a pop-up or needing any other licencing.  This process is used for both .NET and COM versions, but the licence key you are given is specific to a particular product (DicomObjects.NET - DIcomObjects for COM or XdsObjects) - so please ensure that you use the right one, as the signing program does not know which product will be used, and so will not give an error if the wrong key is used at signing time!

To Sign your exe:

  1. Fetch a copy of our Signing tool from here. 
    This downloaded zip contains both GUI and command line tool (useful in automated situations such as a post-build event).

  2. Note your standard licence key (if you have any) is NOT valid for application signing.
    The format for a signing key is SK-xxxx-xxxx-xxxx , you may contact us at accounts@medicalconnections.co.uk  to obtain your function specific signing key.

  3. Sign by command line:

    ApplicationSignerConsole.exe [Expiry]

  4. Alternatively you can use the GUI to generate licence file.

    A licence file (executablename.exe.lic) will placed in the same directory as the executable

* Note - every new build of your assembly has to be re-signed because it won’t match the previous hash so your existing .lic file would be invalid.

For instructions on doing a ClickOnce deployment of your executable click here


We use cookies to give you the best possible experience on our website. By continuing to use this website, you agree with our use of cookies. for more information please click HERE