...

To register you need to specify the assembly attribute AntonyModule to your assembly. Within this attribute you need to point to a class, containing the Register Callregistry. Every module need to have an own Id, you need to specify. It is not used directly, but will in the future. Please provide the same Guid for all registries your module belongs to. At the end you might specify a RegistryGroup. This Group is used for the licence system. In this example we’ll define “Zoom” as a group. This registry will only be loaded, if you have a valid module-licence with this group defined. You can get these licences from our shop. If you cant to create a package for the customer please contact the supportregistry need to be part of a module for licencing. Every module needs to be licencened - even if its free. To define a module you need to register as a Module-Developer within out shop.

The Register call needs to be annotated with the AntonyServiceRegistry attribute to be loaded. You can optional define an application you want to be loaded in . You are loaded in every application on default. The signature of this method is provided in the snipped below. In this method you can finally provide your types at the ExtensionPoints you want to integrate to.

[assembly: AntonyModule(typeof(ZoomModuleAntonyRegistry), RegistryGroupModuleKey = "de.die_groupware.zoom")]
namespace antony.Groupware.AddinX.Zoom
{
    public class ZoomModuleAntonyRegistry
    {
        [AntonyServiceRegistry()]
        public void Register(IServiceCollection services)
        {
           // ...
        }
    }
}

...

As we defined the registry itself we also need to tell antony where to find your assembly. We’ll do this by using the windows registry. You need to add a value into the following key

HKEY_CURRENT_USER\SOFTWARE\SCOM\antony\modules

There you can place the path to your module in the value. As the name you can use the name of your module, but it is not relevant.

...

You need to provide a folder. antony will autodetect all AntonyRegistries automatically and load, if the conditions are met.

...

\<application>\<your_module_key>\

You need to replace the values within the bracets with appropriate values as shown within the screenshot below. The application might be

• AntonyGroupware: To integrate within Antonys Administator or Groupwareclient

• AntonyHubClient: To integrate within the antonyHub to provide dialogs and logic for a custom server. You need to to so, if you want to deploy a service via the antonyHub.

...

You need to provide the path to the file of your assembly. antony will check all available modules at startup, compares with the available licences and call the registry. You are in

Conclusion

As you saw it is 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.

So open up a VisualStudio, Create a Project and go for it. You can do it right now.🇳 🅾 🇼