process.start

I have an .exe file that needs to be run after I create a file. The file is successfully created and I am using the following code to run the .exe file after that: ProcessStartInfo processInfo = new ProcessStartInfo(); processInfo.FileName = pathToMyExe; processInfo.ErrorDialog = true; processInfo.UseShellExecute = false; processInfo.RedirectStandardOutput = true; processInfo.RedirectStandardError = true; Process proc = Process.Start(processInfo); I also tried with a simple Process.Start(pathToMyExe); but the .exe file is not run. When I try pathToMyExe manually on my Windows Explorer the

Suppose I have a C# WinForms application and it is started by external program simply by using Process.Start(MyModule.exe) . I've tried to debug my code by using My project properties -> Debug -> Start Action -> Start external program (with setting proper Working directory of course). My enother attempt was Debug -> Attach to process UPDATE: Both my module and external program use one resource. So external program releases it, then calls Process.Start(), waits for my process to exit ans then capture the resource again. So I can't attach when your program is already running. Both of them failed

I'm successfully using System.Diagnostics.Process.Start() to start my external mono executable on windows. However it fails on mac. I'm not getting any error, simply nothing at all happens. I tried doing it the following way: System.Diagnostics.Process.Start("mono", "/path/program.exe"); Also I've tried opening terminal like the following (which also failed): System.Diagnostics.Process.Start("Terminal"); The only thing I was able to do is launch the Terminal in the following way: System.Diagnostics.Process.Start("open", "-a Terminal"); Any ideas? I would really appreciate any help. Thanks!

Background I have a Windows service that uses various third-party DLLs to perform work on PDF files. These operations can use quite a bit of system resources, and occasionally seem to suffer from memory leaks when errors occur. The DLLs are managed wrappers around other unmanaged DLLs. Current Solution I'm already mitigating this issue in one case by wrapping a call to one of the DLLs in a dedicated console app and calling that app via Process.Start(). If the operation fails and there are memory leaks or unreleased file handles, it doesn't really matter. The process will end and the OS will

I am using System.Diagnostics.Process.Start(ProcessInfo); to open a TEXT file in notepad from within my windows form application. Detailed code snippet is ProcessStartInfo PSI = new ProcessStartInfo("notepad.exe", LogFile); PSI.WindowStyle = ProcessWindowStyle.Normal; System.Diagnostics.Process p = System.Diagnostics.Process.Start(PSI); However, it opens notepad on the default desktop but not on the extended desktop on which the main application is running. Now, the question is, how to open notepad on the active desktop i.e. Window on which the current application is running? Other that

When I try to do Process.Start("echo", "%cd%") it raises a System.ComponentModel.Win32Exception: The system cannot find the file specified . When I do this manually in cmd it just works like it should. I never knew that there's a difference... Also, when I do File.Exists(logfile.txt) (w/o path) of a file that should definitely be there, it returns false. This is btw the reason for the echo above: debugging... This error doesn't occur on my developement machine, only on another one where I am testing on. The Path variable looks normal. Both are WinXP. Both are running .NET 3.5 Try Process.Start