How to run an executable file

  • Thread starter Thread starter wannabe geek
  • Start date Start date
W

wannabe geek

This has to be easy. I want to run an .exe file from within my code, but
search in VCE 2008 Help turns up nothing. A quick google turns up the
Process.Start() way of doing it. Is this a good way? It should basically
start the application, and then all links to the calling app should
disappear, leaving two independently running.
Thanks in advance!
 
This has to be easy. I want to run an .exe file from within my code, but
search in VCE 2008 Help turns up nothing. A quick google turns up the
Process.Start() way of doing it. Is this a good way? It should basically
start the application, and then all links to the calling app should
disappear, leaving two independently running.
Click to expand...

Process.Start is fine.

Arne
 
Why would you think he hadn't? In what non-trivial way is his reply
different from yours?
Click to expand...

Q: Is Process.Start good?
A1: Yes
A2: Process.Start

What do you think ?

Arne
 
Arne said:
[...]
Why would you think he hadn't? In what non-trivial way is his reply
different from yours?
Click to expand...

Q: Is Process.Start good?
A1: Yes
A2: Process.Start

What do you think ?
Click to expand...

I find the two equivalent. You haven't explained why they are not.
Your reply was a simple "yes", while Scott's could be construed as
providing a specific usage example (i.e. an elaboration on "yes").

Quit giving him a hard time. Your reply to him added zero to this
thread (yes, the irony of my own reply to you is not lost on me).
 
Arne said:
[...]
Did you read the entire post you replied to?

Why would you think he hadn't? In what non-trivial way is his reply
different from yours?
Click to expand...

Q: Is Process.Start good?
A1: Yes
A2: Process.Start

What do you think ?
Click to expand...

I find the two equivalent.
Click to expand...

A1 answers the question.

A2 repeats what is in the question.

Difference.
You haven't explained why they are not.
Click to expand...

No. I considered that rather obvious.
Your
reply was a simple "yes", while Scott's could be construed as providing
a specific usage example (i.e. an elaboration on "yes").
Click to expand...

It could be construed as a lot of things, but the text posted
did not answer the question.
Quit giving him a hard time.
Click to expand...

I assume that he is an adult and can take criticism.
Your reply to him added zero to this thread
Click to expand...

It happens on usenet that posts content get discussed.

Arne
 
Neither the OP or your reply gave the full namespace for the Process type.
I simply provided a more complete answer. Not that big of a deal, I think.

-Scott
 
I find the two equivalent.  You haven't explained why they are not.
Your reply was a simple "yes", while Scott's could be construed as
providing a specific usage example (i.e. an elaboration on "yes").

Quit giving him a hard time.  Your reply to him added zero to this
thread (yes, the irony of my own reply to you is not lost on me).
Click to expand...

Shuttup you net bully.

Arne is more helpful in this forum that pedantic you.

RL
 
Neither the OP or your reply gave the full namespace for the Process type.
I simply provided a more complete answer. Not that big of a deal, I
Click to expand...
think.

Ah - it was System.Diagnostics that was the point - I did assume
that at least some of OP's google results showed that.

Arne
 
Arne Vajhøj said:
think.

Ah - it was System.Diagnostics that was the point - I did assume
that at least some of OP's google results showed that.

Arne
.
Click to expand...

Shut up, all of you! I think I did see the System.Diagnostics part, but I
did not see the Start(filename) version. Scott's post answered my question
and then some. Thanks Scott!
 
Jeff Johnson said:
That's my point: we shouldn't have to guess. People shouldn't make up
abbreviations.
Click to expand...

But since these NG's usually get a lot of messages from newbies, it's
unrealistic to expect that they know every acronym or are correct in the
ones they use. Since the question was in a C# group and clearly about a
standard .NET type (process), it's not a stretch to figue out what the OP
means by VCE.

You could have just as easily posted a message explaining what the correct
terminology was, rather than draw this out.

-Scott
 
Jeff Johnson said:
That's my point: we shouldn't have to guess. People shouldn't make up
Click to expand...

Make up???????????????????? Wasn't me!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you want to blame someone, blame the authors of Beginning Microsoft
Visual C# 2008. Wiley Publishing, Inc. Any term used in a book that fat ought
to be standard terminology. Here are similar ones:
VS
VBE
VB
VBA
 
Back
Top