• State Verified Answer
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 10 subscribers
  • Views 96 views
  • Users 0 members are here
Options
Related

Order of events when plugins are initializing

Robert Nash

I am seeing that 

Events_BeforeUpdate(UserBeforeUpdateEventArgs e)
is being called before 
SetController(ISqlServerConnectedPlugionController controller)
The event is being setup in the main plugin and the ISqlServerConnectedPlugin is a child of this plugin.

  • 0

    I'm not sure I follow the question. IUsers.Events.BeforeUpdate is unrelated to plugin initialization.

  • 0 in reply to Michael Monteleone

    within the Initialize() method of the core plugin an event handler is setup IUsers.Events.BeforeUpdate, the main plugin is receiving these events before the related child plugins have been initialized.  Therefore, the plugin group has not completed setup and things go wrong. The events should not be sent to a half-initialized set of plugins.

  • +1 in reply to Robert Nash

    This is unchanged. The order of plugin initialization has never been deterministic, including whether or not plugins are child plugins. 

    One option in this case is to use the AfterInitialization event. 

  • 0 in reply to Michael Monteleone

    It is unchanged but because the SQL is now initialized in a plugin this becomes a problem as the code that is initialized in the core plugin is started to be active before the database information has been setup. I will do as you advise but this is something that will catch others out, so worth flagging. 

  • 0 in reply to Robert Nash

    What I usually do, myself, is to implement all "infrastructural" components of a plugin tree on the parent, itself. So, IConfigurable, ISqlServerConnectedPlugin, IInstallablePlugin, ISocket, etc all on a root plugin and then manage the state of their controllers explicitly, wrapping and/or making their controllers available elsewhere in my plugin. Then child plugins and plugin-defined services and apis can focus on specifics.

  • 0 in reply to Robert Nash

    I have just tried it and it doens't work 

        PluginManager.AfterInitialization += (sender, args) =>{
                    Injector.Get<IMfaLogic>().Initialize(....)

    still being called before the SetController(ISqlServerConnectedPlugionController controller)
  • 0 in reply to Michael Monteleone

    that's great for simple plugins, but ones that are complex and need separation of concern or need to use common libraries such as a common SQL installer class this will not work.  Ideally we need an event on IPluginGroup so that the system knows that this particular set of plugins is completely initialized. 

  • 0 in reply to Robert Nash

    or always initialize the ISqlServerConnectedPlugins first?

  • 0 in reply to Robert Nash
    Robert Nash said:
    that's great for simple plugins, but ones that are complex and need separation of concern

    I can assure you I've used this pattern on highly complicated plugins (including many components of the platform, itself) with clear separations of concerns, DI, etc. It's in service of that, not orthogonal to it. That said, it's just one of many possible approaches.

    Robert Nash said:
    or always initialize the ISqlServerConnectedPlugins first?

    This actually is the case. Let's back up for a moment:

    For any given set of plugins, their controllers are injected before they're initialized. This includes ISqlServerConnectedPlugin, IConfigurablePlugin, etc. 

    The order is:

    1. ISqlServerConnectedPlugin.SetController (called on all plugins of this type, in a non-deterministic order)
    2. IPlugin.Initialize (called on all plugins, but the order is non-deterministic)
    3. PluginManager.AfterInitialize (after all plugins have initialized)
  • 0 in reply to Michael Monteleone
    Just to confirm the above, here's an unrealistic example of a parent plugin with 2 child plugins, where all 3 implement ISqlServerConnectedPlugin and IConfigurablePlugin.
    using Telligent.Evolution.Extensibility.Configuration.Version1;
using Telligent.Evolution.Extensibility.Version1;
using Telligent.Evolution.Extensibility.Version2;

namespace TestPlugins;

public class TestChildPluginB : IPlugin, ISqlServerConnectedPlugin, IConfigurablePlugin
{
	public string Name => "Test Child Plugin B";

	public string Description => Name;

	public void Initialize()
	{
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginB.Initialize");

		PluginManager.AfterInitialization += (sender, args) =>
			System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginB.AfterInitialization");
	}

	public void SetController(ISqlServerConnectedPlugionController controller) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginB.SetController");

	public void Update(IPluginConfiguration configuration) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginB.Update");

	public Version Version => new(1, 0, 0, 0);
	public PropertyGroup[] ConfigurationOptions => [ new() { LabelText = "" } ];
	public void Install(Version lastInstalledVersion) { }
	public Task InstallAsync(Version lastInstalledVersion, CancellationToken cancellationToken) => Task.CompletedTask;
	public void Uninstall() { }
	public Task UninstallAsync(CancellationToken cancellationToken) => Task.CompletedTask;
}


public class TestParentPlugin : IPlugin, IPluginGroup, ISqlServerConnectedPlugin, IConfigurablePlugin
{
	public string Name => "Test Parent Plugin";

	public string Description => Name;

	public IEnumerable<Type> Plugins => [typeof(TestChildPluginA), typeof(TestChildPluginB)];

	public void Initialize()
	{
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestParentPlugin.Initialize");

		PluginManager.AfterInitialization += (sender, args) =>
			System.Diagnostics.Debug.WriteLine("TestPlugins: TestParentPlugin.AfterInitialization");
	}

	public void SetController(ISqlServerConnectedPlugionController controller) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestParentPlugin.SetController");

	public void Update(IPluginConfiguration configuration) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestParentPlugin.Update");

	public Version Version => new(1, 0, 0, 0);
	public PropertyGroup[] ConfigurationOptions => [ new() { LabelText = "" } ];
	public void Install(Version lastInstalledVersion) { }
	public Task InstallAsync(Version lastInstalledVersion, CancellationToken cancellationToken) => Task.CompletedTask;
	public void Uninstall() { }
	public Task UninstallAsync(CancellationToken cancellationToken) => Task.CompletedTask;
}


public class TestChildPluginA : IPlugin, ISqlServerConnectedPlugin, IConfigurablePlugin
{
	public string Name => "Test Child Plugin A";

	public string Description => Name;

	public void Initialize()
	{
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginA.Initialize");

		PluginManager.AfterInitialization += (sender, args) =>
			System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginA.AfterInitialization");
	}

	public void SetController(ISqlServerConnectedPlugionController controller) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginA.SetController");

	public void Update(IPluginConfiguration configuration) =>
		System.Diagnostics.Debug.WriteLine("TestPlugins: TestChildPluginA.Update");

	public Version Version => new(1, 0, 0, 0);
	public PropertyGroup[] ConfigurationOptions => [ new() { LabelText = "" } ];
	public void Install(Version lastInstalledVersion) { }
	public Task InstallAsync(Version lastInstalledVersion, CancellationToken cancellationToken) => Task.CompletedTask;
	public void Uninstall() { }
	public Task UninstallAsync(CancellationToken cancellationToken) => Task.CompletedTask;
}
    When the parent plugin is enabled, a plugin initialization demonstrates that controllers and configuration are set/injected first on all 3, followed by Initialize() on all 3, followed by AfterInitialization on all 3.
    TestPlugins: TestParentPlugin.SetController
TestPlugins: TestParentPlugin.Update
TestPlugins: TestChildPluginA.SetController
TestPlugins: TestChildPluginA.Update
TestPlugins: TestChildPluginB.SetController
TestPlugins: TestChildPluginB.Update
TestPlugins: TestParentPlugin.Initialize
TestPlugins: TestChildPluginA.Initialize
TestPlugins: TestChildPluginB.Initialize
TestPlugins: TestParentPlugin.AfterInitialization
TestPlugins: TestChildPluginA.AfterInitialization
TestPlugins: TestChildPluginB.AfterInitialization

About
Privacy Policy
Terms of use
Copyright 2026 Verint, Inc.
Powered by Verint Community