Page Comparison

...

As you can extend antony’s desktop client and administator with custom modules, you usally will ship some assemblies with it. If you want to integrate into Zoom you might ship a special zoom assembly. This is no problem as long as no other also module ships this dll too. This will also raise problems, if you ship assemblies antony already provides.

...

For example antony ships the Newtonsoft.Json assembly like nearly every other application in the world. The version we provides in provide at this moment has the version 12.0.3. So if your module uses this assembly in version 13.0.1, you can develop and compile against this. You will also shop deploy the version 13 with within your setup.

If you start antony with your shipped version 13.0.1 antony will detect your assembly and automatically create an assemblyRedirect from 13.0.1 to 12.0.3. If you relay on a new method within this assembly, you will get a MethodNotFoundException.

...

The assemblies and the dependent modules will be checked on every startup of the antony Client. If we detect changes we’ll generate a special SCOM.Groupware.exe.config file containing the redirection. In the example above this will contain the entry below

    <dependentAssembly>
 
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
      <bindingRedirect oldVersion="13.0.1.0" newVersion="12.0.3.0" />
   
</dependentAssembly>

You might find more than this entry for the Newtonsoft.Json assembly, if other modules than yours ship some other versions.

...