C# .net system.diagnostics.process

[rhitam30111985]

Hi all i am trying to compile a set of source files located in location In the following code sample i am trying to compile a visual c++ 6.0 (dsp) project from a c# application

 ProcessStartInfo procStartInfo = new System.Diagnostics.ProcessStartInfo("cmd", @"/c  set path=%programfiles%\Microsoft Visual Studio\Common\MSDev98\Bin");
            procStartInfo.RedirectStandardOutput = true;
            procStartInfo.UseShellExecute = false;
            System.Diagnostics.Process proc = new System.Diagnostics.Process();
            proc.StartInfo = procStartInfo;
            proc.Start();
 
            proc.WaitForExit();
 
            procStartInfo = new System.Diagnostics.ProcessStartInfo("cmd", @"/c  MSDEV C:\Shared\Source\Binaries\Project\Project.dsp /MAKE  /REBUILD >> compilerr.txt");
            proc.StartInfo = procStartInfo;
            procStartInfo.RedirectStandardOutput = true;
            procStartInfo.UseShellExecute =false;
 
            proc.Start();

But for the first process(set path) it gives error :

'proc.ExitCode' threw an exception of type 'System.InvalidOperationException'

and for the msdev command :

'proc.BasePriority' threw an exception of type 'System.InvalidOperationException'


Any idea where i could be going wrong ?

Thanks a lot ,

Rhitam

[Plater]

I don't think you can use the output operators >> << | inside the arguments of the process class can you?
The lines of code that threw the exceptions are not included in your sample source code?

[rhitam30111985]

I don't think you can use the output operators >> << | inside the arguments of the process class can you?
The lines of code that threw the exceptions are not included in your sample source code?

While stepping through the code ... the IDE (Visual c# express) is not throwing any exception .. but if i mouse over the process variable (proc) ... and see its members .. then i get this exception ... it is thrown at each proc.start() line in the sample code ..

as for the output operators .. thats secondary. . i am not even able to execute the set path command ..

[rhitam30111985]

I tried only the set path option like this :

 
 System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo(@"set path=%programfiles%\Microsoft Visual Studio\Common\MSDev98\Bin");
            psi.UseShellExecute = false;
            psi.RedirectStandardOutput = true;
            psi.RedirectStandardInput = true;
            psi.RedirectStandardError = true;
            System.Diagnostics.Process proc = System.Diagnostics.Process.Start(psi);
 

then it gives the error :

The system cannot find the file specified win32 exception was unhandled

stacktrace:


at System.Diagnostics.Process.StartWithCreateProcess( ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at GetBuildSource.Program.Main(String[] args) in C:\Shared\Test Environment\GetBuildSource\Program.cs:line 39
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[Plater]

While stepping through the code ... the IDE (Visual c# express) is not throwing any exception .. but if i mouse over the process variable (proc) ... and see its members .. then i get this exception ... it is thrown at each proc.start() line in the sample code ..

as for the output operators .. thats secondary. . i am not even able to execute the set path command ..

Haha, yeah of course they will. You cannot look at an exitcode if thr process has not exited yet, it just means the value is like null still.

As for why SET doesn't work, its because SET is not a command. There are other ways to set the environment variables for a program. And even if you could set that, it would only apply for the scope of that process, which would end after the set command was fired. So it would not be valid for the next Process object.

For your actual process object, look at .EnvironmentVariables on the ProcessStartObject

[rhitam30111985]

Haha, yeah of course they will. You cannot look at an exitcode if thr process has not exited yet, it just means the value is like null still.

As for why SET doesn't work, its because SET is not a command. There are other ways to set the environment variables for a program. And even if you could set that, it would only apply for the scope of that process, which would end after the set command was fired. So it would not be valid for the next Process object.

i see .... . will look into it.. thanks a lot :)

[Plater]

Something like this maybe? You might have to expand out the %programfiles% string with procStartInfo.EnvironmentVariables["%programfiles%"], but I don't think so

System.Diagnostics.ProcessStartInfo procStartInfo = new System.Diagnostics.ProcessStartInfo("cmd", @"/c  MSDEV C:\Shared\Source\Binaries\Project\Project.dsp /MAKE  /REBUILD >> compilerr.txt");
procStartInfo.EnvironmentVariables["path"]=procStartInfo.EnvironmentVariables["path"]+@";%programfiles%\Microsoft Visual Studio\Common\MSDev98\Bin;";
procStartInfo.UseShellExecute = false;
System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo = procStartInfo;
proc.Start();
 

[rhitam30111985]

Something like this maybe? You might have to expand out the %programfiles% string with procStartInfo.EnvironmentVariables["%programfiles%"], but I don't think so

System.Diagnostics.ProcessStartInfo procStartInfo = new System.Diagnostics.ProcessStartInfo("cmd", @"/c  MSDEV C:\Shared\Source\Binaries\Project\Project.dsp /MAKE  /REBUILD >> compilerr.txt");
procStartInfo.EnvironmentVariables["path"]=procStartInfo.EnvironmentVariables["path"]+@";%programfiles%\Microsoft Visual Studio\Common\MSDev98\Bin;";
procStartInfo.UseShellExecute = false;
System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo = procStartInfo;
proc.Start();
 

procStartInfo.EnvironmentVariables["%programfiles%"] returns blank value .. hence the path had to be hardcoded ..even %systemroot% is not working ... apart from that it works like a charm :-)