Support Forums

So OCD :D ? Jokes aside, the .config files are necessary if you mix assemblies compiled against different runtimes. You can go to the vendor of the module or assembly and ask them to update their stuff, but then you will have to distribute those along with your app. Put all you executables in a sing...

As far as I know, .config files which contain startup information to support different .NET runtime versions must be outside.
Microsoft arranged for it this way. Any particular reason why this is a problem? Most .NET applications have these files.

My assumption was that he packages the GUI application as an exe. So there is no console.
I will see what I can come up with. Maybe we can even bake something into the host itself.

Jim, he posted about a GUI application. So there is a window. Posting simple messages should work with some C# code.

You posted your subscription number in this forum, please refer to the notice on top:
Forum rules
Do not post any licensing information in this forum.

We have disabled your subscription number as a result. Please contact sales@sapien.com to obtain a new subscription number.

Generally this is done by finding the Window of the already running instance. When one exists, send it a message. I am not sure if that could be done in PowerShell. You would have to insert some C# code I presume. https://stackoverflow.com/questions/1214638/how-to-send-a-message-from-one-instance-of...

I am not sure how you got the idea we have anything to do with that. It is a PowerShell error message and we cannot fix anything in PowerShell. A simple google search for the error retrieves plenty of documentation regarding the issue. https://www.google.com/search?q=The+ampersand+(%26)+character+is...

I have an idea about that. Please ping back in a month or so.

Yes, it is stored encrypted (AES). The functionality was never meant to add a layer of security to your systems or environment. These concerns are for you to decide based on your needs.It works to keep a casual observer away but it will not keep a determined person with a system level debugger away ...

We had that in a fashion and it went away. Basically the feedback was that users already have File Explorer. Right click -> Edit with PowerShell Studio. Removing unwanted or unneeded UI elements is a constant concern for us in order to keep the clutter to a minimum. Things are always changing though...