Hello.

Regarding your first post: Administering the UA application from a separate program is in the plans, but not supported yet.

If the issue is with placing the command onto the system menu, and not with running the form itself: There is nothing that forces you to place this command on the system menu. The reason why we "advertise" this method is because it can be used in any Windows desktop application in the same way.

But you can add a command to your application to invoke the OPC UA Administration dialog from anywhere you like - such as your own menus, icons etc. So this is the way I would go in this case. See: opclabs.doc-that.com/files/onlinedocs/OPCLabs-OpcStudio/Late...UA%20Application%20Dialog.html . Basically, just call EasyUAFormsApplication.Instance.UIAdministerApplication (opclabs.doc-that.com/files/onlinedocs/OPCLabs-OpcStudio/Late...2~UIAdministerApplication.html ) when you want the dialog to appear. Suggested arguments are:

- for 'owner': your parent form
- for 'clientSelector': New EasyUAClientSelector(EasyUAClient.SharedInstance)
- for 'allowPullCertificateManagement': True
- for 'allowChangePrivateKeyPassword': False

I hope this helps
Best regards

I cannot reproduce this either.

Hello.

I do not not want how to interpret the video. I do not know what to expect, therefore I do not see anything wrong. What is that you are trying to say?

Regards

Hello.

Cannot reproduce it. In my tests, the time to execute this statement is so short that is not noticeable.
Please provide a minimal project that exhibits the problem.

As a workaround, you can do this in a background (example below). That should work unless the user actually needs to execute that command from the system menu before it is added - in your case in first 6 seconds.
Regards