Hi there!

There is no way to check, but we hope is alright because there is no downside in re-registering an application that is already registered. If registration is that same as before, it's not disruptive and not going to change anything.

Could you please let us know why do you think the check would be helpful?

Best regards,
UltiDev Team.

Hello,

We would be happy to clarify what happens when applications are registered and unregistered. Re-registering an application does not disrupt users in most cases: sessions are kept as host processes stay loaded. The first request sent to an application that has been re-registered will be slow, but should not kick users out. We consider this to be a pretty small price to pay for the simplicity of the command-line registration, where multiple registrations and unregistration have small effect. When application is unregistered, some of its settings are stored for later, and in case the application is registered again, previous ports can be used if they
are still available. Registering an application that is already registered does not fail - it replaces previous registration. Unregistering non-existing application does not produce failures either.

The solution that you may want to consider is using UWS configuration API. It can be used from .NET and COM, and has methods that let you examine whether the application is installed, and then use one of the RegisterApplication() overloads to register it.

Please let us know if we you have questions.

Best regards,
UltiDev Team.

Hi!

When your installer/updater upgrade your app code base, application will be reloaded by ASP.NET, causing brief downtime event if re-registration is not involved. Roughly same delay is introduced by re-registering an existing application. If in some cases your installer does not change application files, then same logic should prevent UWS application registration from happening. Are we missing anything here: it looks to us that if you upgrade files, you have go through short downtime and re-registering won't hurt, and if you don't change file, then don't re-register either.

Even when using UWS config API, you probably won't have to do much of manual work of figuring out system configuration - you could use InstallShield custom actions, which can pass parameters to your code with target folder, etc.

Finally, when you re-register a previously-registered application, and you specified port 0 (system assigned) among endpoints, UWS will register it on the same port as before, so you won't need to first check which port its on and then re-register - it's done automatically. That's why we suggest so loudly to always use system-assigned port on at least one application endpoint.

Best regards,
UltiDev Team.