When I use VSTS debugger to see the properties of instance of class Process
, many of the properties are marked with InvalidOperationException
. Why? Am I doing anything wrong?
I am using VSTS 2008 + C# + .Net 2.0 to develop a console application.
Here is my code:
System.Diagnostics.Process myProcess = new System.Diagnostics.Process(); myProcess.StartInfo.FileName = "IExplore.exe"; myProcess.StartInfo.Arguments = @"www.google.com"; myProcess.StartInfo.Verb = "runas"; myProcess.Start();
And a screenshot of the debugger:
The InvalidOperationException exception should not be thrown for errors caused by invalid arguments. For invalid argument errors, throw ArgumentException or one of its derived types, such as ArgumentNullException or ArgumentOutOfRangeException. The ldflda CIL instruction throws InvalidOperationException.
An exception is defined as an event that occurs during the execution of a program that is unexpected by the program code. The actions to be performed in case of occurrence of an exception is not known to the program. In such a case, we create an exception object and call the exception handler code.
In . NET, an exception is an object that inherits from the System. Exception class. An exception is thrown from an area of code where a problem has occurred. The exception is passed up the stack until the application handles it or the program terminates.
Had you actually started the process when the debugger picture was taken? That's the screenshot I'd expect to see before the Start()
method is called.
Note that the common pattern is to create a ProcessStartInfo
, populate it, and then call the static Process.Start(startInfo)
method. That makes it conceptually simpler: you don't see the Process
object until it's been started.
Many of the properties are marked with InvalidOperationException because until you start the process . The object 'myProcess' is not associated with any running process and hence it cannot get the information.
Try adding these statements, after the code to start the process
if (myProcess != null) { myProcess.WaitForExit(); //or any other statements for that matter }
Now, when you are inside the if statement, the VSTS debugger will be able to show most of the properties associated with the object myProcess. This happens because, myProcess object is now associated with a running process "IExplore.exe".
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With