|
Posted by
Paschal
on
|
|
I came across a problem where I wanted to launch Internet Explorer from my windows application. Once again, a good search from
and I found my answer.
System.Diagnostics.ProcessStartInfo start =
new
System.Diagnostics.ProcessStartInfo("IExplore.exe");
start.WindowStyle = System.Diagnostics.ProcessWindowStyle.Normal;
start.Arguments = “www.bernardstudios.com“;
System.Diagnostics.Process.Start(start);
|
|
|
|
Posted by
fergal
on
|
You can also use the static method and have windows use the default browser (for all those firefox fans) by just using
System.Diagnostics.Process.Start("
http://www.ryarc.com/SC/SC.asp
")
|
|
|
|
Posted by
akidd8
on
12-15-2004 11:06
|
| just asking, do i understand something wrong, that Diagnostics means designed for diagnostic purposes, and NOT for regular usage? means it works technically, but it is not recommended practice. |
|
|
|
Posted by
fergal
on
|
AFAIK this is the documented, reccomended way to start a process from within a .net application.
The Diagnostics namespace is just the namespace under which the set of functionality comes. The formal definition is "provides classes that allow you to interact with system processes, event logs, and performance counters"
providing performance coutners and interacting with the event log are normal aspects to a program. Starting a web browser, or any other program is just another process.
HTH
-fergal
|
|