You can of course patch together the FileName and the Extension and hope for the best. Or test whether a file Extension has a predefined Opener, an entry in the Registry that associates an Extension with an application that can hadle that file format. The System provides an API – AssocQueryString – that provides this … Read more
Depending on what the 3rd party process is doing exactly you could try polling its threads’ states: foreach(ProcessThread thread in process.Threads) if (thread.ThreadState == ThreadState.Wait && thread.WaitReason == ThreadWaitReason.UserRequest) process.Kill(); Failing that… you can try to process.StandardInput.Close(); after calling Start(), I conjecture that an exception will be raised in the child process if it’s trying … Read more
What you need to do is capture the Standard Output stream: p.StartInfo.RedirectStandardOutput = true; p.StartInfo.UseShellExecute = false; // instead of p.WaitForExit(), do string q = “”; while ( ! p.HasExited ) { q += p.StandardOutput.ReadToEnd(); } You may also need to do something similar with StandardError. You can then do what you wish with q. … Read more
For per process data: Process p = /*get the desired process here*/; PerformanceCounter ramCounter = new PerformanceCounter(“Process”, “Working Set”, p.ProcessName); PerformanceCounter cpuCounter = new PerformanceCounter(“Process”, “% Processor Time”, p.ProcessName); while (true) { Thread.Sleep(500); double ram = ramCounter.NextValue(); double cpu = cpuCounter.NextValue(); Console.WriteLine(“RAM: “+(ram/1024/1024)+” MB; CPU: “+(cpu)+” %”); } Performance counter also has other counters than … Read more
This thread is over four years old, and it still annoys me that the accepted answer criticizes the question rather than answering it. There are many valid reasons you would want to limit the CPU time taken by your program, I can list a few off the top of my head. It might seem like … Read more
Can can use PsExec from http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx Or WMI: object theProcessToRun() = { “YourFileHere” }; ManagementClass theClass = new ManagementClass(@”\\server\root\cimv2:Win32_Process”); theClass.InvokeMethod(“Create”, theProcessToRun);
I ended up opening a case with Microsoft, and this is the information I was given: Process.Start internally calls CreateProcessWithLogonW(CPLW) when credentials are specified. CreateProcessWithLogonW cannot be called from a Windows Service Environment (such as an IIS WCF service). It can only be called from an Interactive Process (an application launched by a user who … Read more
Try this: using System.Diagnostics; // Get call stack StackTrace stackTrace = new StackTrace(); // Get calling method name Console.WriteLine(stackTrace.GetFrame(1).GetMethod().Name); one-liner: (new System.Diagnostics.StackTrace()).GetFrame(1).GetMethod().Name It is from Get Calling Method using Reflection [C#].