Short

Add-in should start Openness Scripter as Process to import XML-Files; LinkDemand error,my guess; not enough trust in method to access System.Diagnostics.Process()

Question

Is there an option to run the add-in with enough trust to allow starting external processes (Openness Scripter)? Maybe elevate add-in process during runtime with user prompt?

Description

I wrote an add-in that imports a lot of data which an excel outputs into PLC & HMI objects. Recently I found out that there is a thing called OpenessScripter, which allowed me to write simple scripts to import a lot more of the data automatically. To streamline the process and make it easy for us, i tried to add that functionallity to my add-in. It worked awesome in Visual Studio with the Add-in Tester executer. But as I stopped debugging and was happy, exporteted and tried to run from within TIA:

System.Security.SecurityExeption: Request failed. at MyClass.MyMethod(args) The action that failed was: LinkDemand The type of the first permission that failed was: System.Security.Permissionset.

After searching I found that starting a process in my Add-In prompts this error:

Process process = new System.Diagnostics.Process();

Is there a way to [PermissionSet(SecurityAction.LinkDemand, Name = "FullTrust")] or edit a Manifest or something to circumvent that problem?
Only User with local Admin and knowlege of what they are doing are running that add-in.

What I want to do

string project = settings.ProjectPath;
string plc = settings.PLCName;
string hmi = settings.HMIName;
string pathToImportFiles = settings.PathToImportFiles;
string logFileName = "C:\\Temp\\logs\\" + itemName + ".log";

string args = "/silent /file:" + "\"" + pathScript + "\"" +" /log:" + "\"" +logFileName+ "\"" + " ImportFile=" + "\"" + pathToImportFiles + "\\" + itemName + "\"" + " ProjectFile=" + "\"" + project + "\"" + " plc=" + "\"" + plc + "\"" + " hmi=" + "\"" + hmi + "\"";

Process process = new System.Diagnostics.Process();

ProcessStartInfo startInfo = new System.Diagnostics.ProcessStartInfo();
startInfo.FileName = pathScripter;
startInfo.Arguments = args;
process.StartInfo = startInfo;
process.Start();
process.WaitForExit();

The solution that I see

I am thinking of implementing the import within the addin, letting openness Scripter slide,but it would be so much easier!
The other Idea that I have is making a seperate program that starts with admin privileges which starts the Scripter and communicates with the add-in process via inter-process communication but we would have to start that program each time too, a lot of wasted mouse clicks...
Is there an option that I don't see?

As I am not really adept at neighter TIA nor Openness API nor C# i would greatly appreciate your help!

Process process = new System.Diagnostics.Process();

string pathScripter: "C:\\PathTo\\OpenessScripter.exe"
string pathScripte: "C:\\PathTo\\Script.opns"
string args = "/silent /file:" + "\"" + pathScript + "someotherargs"
Process process = new System.Diagnostics.Process();

ProcessStartInfo startInfo = new System.Diagnostics.ProcessStartInfo();
startInfo.FileName = pathScripter;
startInfo.Arguments = args;
process.StartInfo = startInfo;
process.Start();
process.WaitForExit();

I am still hoping that I did something wrong and that it is possible, it worked fine with the TIA-Addin debugger right out of VS-Studio.

If you have any Idea or thought what I should test or try, please let me know.

Thank you & Have a nice evening

<Siemens.Engineering.AddIn.Permissions.ProcessStartPermission/>