...

You need to provide the path to the file of your assembly. antony checks all available modules at startup, compares with the available licences and calls your registry. Congratulations, you are in

Specific Implementation for specific versions

The ExtensionInterfaces will change over time, as we add or extends the possibility to integrate into antony. Therefore we might add more interfaces for theses extension points. You as an module developer can use these interfaces to extend your module too. As you update the ExtensionInterfaces you are able to do so.

As we described in Modules and dependent assemblies we the assemblies of antony itself are preferred to load, including the ExtensionInterfaces.Therefore you will get a TypeNotFoundException, if you try to load your band new module within an old antony installation. To get around this, we provide the possibility to declare a minimal version of antony your registry runs on.

So if you create a new version with new interfaces of your module you need to create a new registry defining the version you want to add. In this case the old registry works as usual, and the new registry registered the new interfaces and implementations within the DI-container.

Conclusion

It is quite simple to provide a module which is loaded by antony. You only need to specify a registry and let antony know where to search for it. You should be able to use the classes within nearly every project.

...