If the plug-ins don't farm out to a separate process but reside within the service process than it should be as simple as that yeah.
If you run as a service, they'll run under that same space. Why is this a requirement btw?
If the plug-ins don't farm out to a separate process but reside within the service process than it should be as simple as that yeah.
Could you accomplish this by creating a C# script then running it as part of your scene? If you could do the lookup to get the PNRP address, then use the built-in InControl email function (look at existing scripts for the command), you could email yourself the address when you activate the scene.
If the plug-ins don't farm out to a separate process but reside within the service process than it should be as simple as that yeah.
If the plug-ins don't farm out to a separate process but reside within the service process than it should be as simple as that yeah.
same reason as if I ran it through netsh within a cmd.exe - if I kill the cmd the pipe is closed rather than allowing the pipe to be assigned to a "computer" for any instance of time.
So I imagined if it was associated tightly to the service that would be easier to keep maintaining or emailing something on the cloud side - per process. rather than farming out to some random process that may die and have to author around watching that process to keep the path alive and the db up to date.