A
Alex Moskalyuk
I have a variety of console application (written with C++ 6) that I
decided to unite under 1 GUI written in C#. On the press of the button
the app collects the information from the textboxes and then passes that
to what I thought would be a system() call, except that there's
apparently no system() equivalent in .NET.
Somewhere in the docs I dig up the information on
System.Diagnostics.Process.Start(), which supposedly performs similar
things, except I cannot get the console apps to stay - they die off as
soon as they are launched, even though some of them require user input
and print error messages on the way.
The WaitForExit() method, according to the documentation, waits for
exit, but in reality it doesn't, and the app dies off whether or not
this method is called.
Ready to scrap the whole thing and move back to Perl+Tk development where
system ("MyApp.exe arg1 arg2 arg3");
behaves exactly as I expect it.
Anyone have any suggestions on doing system calls with .NET? Or is this
going to be another Longhorn-only feature?
decided to unite under 1 GUI written in C#. On the press of the button
the app collects the information from the textboxes and then passes that
to what I thought would be a system() call, except that there's
apparently no system() equivalent in .NET.
Somewhere in the docs I dig up the information on
System.Diagnostics.Process.Start(), which supposedly performs similar
things, except I cannot get the console apps to stay - they die off as
soon as they are launched, even though some of them require user input
and print error messages on the way.
The WaitForExit() method, according to the documentation, waits for
exit, but in reality it doesn't, and the app dies off whether or not
this method is called.
Ready to scrap the whole thing and move back to Perl+Tk development where
system ("MyApp.exe arg1 arg2 arg3");
behaves exactly as I expect it.
Anyone have any suggestions on doing system calls with .NET? Or is this
going to be another Longhorn-only feature?