1
I am running a command of an executable by the CMD of the Blue Prism software, I tested local and it worked, but I have a question for when I go up in production, because the IIS server will have the executable but the client will not have, there is the possibility to run the CMD on the server of a client who does not have access to that server.
si.StartInfo.WorkingDirectory = "C:\\Program Files\\Blue Prism Limited\\Blue Prism Automate\\";
si.StartInfo.UseShellExecute = false;
si.StartInfo.FileName = "cmd.exe";
si.StartInfo.Arguments = "/c AutomateC.exe /user 123 123 /run Processo_teste
si.StartInfo.CreateNoWindow = true;
si.StartInfo.RedirectStandardInput = true;
si.StartInfo.RedirectStandardOutput = true;
si.StartInfo.RedirectStandardError = true;
si.Start();
string output = si.StandardOutput.ReadToEnd();
si.Close();
In case this code will try to locate the Blue Prism directory and run Automatec.exe, but in 99% of the cases the user will not have this executable, someone has already gone through something like?
It will run on the server, as long as the application account has privilege for this... But as I said will run on the SERVER, do not expect this to have any result on the machine of the user who is accessing the site
– Leandro Angelo
Leandro I’ll take a look I hope you’re right but I haven’t heard back from the staff below, thanks for the comment
– Voltz
It is that here there is no magic, you need to understand the scopes of Client and Server Side... Unless you build a specific framework for this, you will not get this program on the user’s machine, let alone if it is accessing your application through the browser
– Leandro Angelo
And the architecture of this solution is not so trivial.
– Leandro Angelo