Yes, was using Visual Studio .NET to compile it and all, as I went from Visual C++ 4.00 to 6.00, then to .NET over time. The code was initially written under Visual C++ 6.00; and the .NET took care of the code ugprades.
I know the WinExec function is rather old, but I did not remember how to use the CreateProcess and previously, used I believe ShellExec -- another old one. Seeing how WinExec did it's job, it shouldn't really pose any problem.
I have a few ideas that I wanted to experiment with, but my programming skills are not up to par -- like they use to be, and not saying I am a professional programmer either. Just had some good points and some bad points; but don't everyone?
Quote:
|
Originally Posted by curtdept
If you are using .Net just add the .NET Framework "Process" component. You can then set it properties, stuff like working directory and executable location, and execute the program from an object such as a button using <Processcontrolname>.Start(); Then you wont need all this thrid party software. PatchMe launcher from start to finish in C# is 1 line of code, 4.5 kb, and 2 minutes ;p As for touching base with installers. Being that the .NET Framework is the "end of DLL hell." Unless you use some hemped up third party libraries, DLL, or external applications you can just distribute the executable and tell them to grab the Framework off of WindowsUpdate, if they dont already have it.
To extend this you could do a compare of the EQHost and replace it for either EQEmu or EQLive upon launch, using an object like radio buttons. Store the working directory path in an ini or XML and hardcode a keep alive in a relatively short period of time ;p Could even take it that much farther and add things like an autoupdate for it. All depends how far you want it to go Just some ideas.
WinExec is somewhat legacy now as well. They currently recommend and most major institutions tend to teach CreateProcess in VC6+ for the degree of control it offers.
-Curtis |
Hybrid Mode
