This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 5 years and 6 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
It is a .NET problem. It can easily be demonstrated with two C# applications created with Visual Studio.
Microsoft has of course been informed.
If you switch the packager to a different PowerShell engine, which changes the .NET requirements, it will still use whatever framework you have installed.
Including the parts that cause this problem. That is just how .NET works.
"A VBA can't be the solution." I am not sure what that means. The solution is to use a starter that is not a .NET application. Our packager can make a VBScript into an exe, which happens to be C++ based.
You can of course use whatever else you like, but the general solution is to use anything that calls ShellExecute as shown in the VBS example.
I thought at first I have to provide the credentials inside the VBA/VBS so it is in plaintext == no solution for me.
How can I Package the vbs so it suits my case?
When I open a vbs with the code you provided in the other thread. I cant Package the File to an .exe.
Maybe you can explain a bit further. How to proceed exactly.
This topic is 5 years and 6 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
