Process.start is not working in IIS

Question

5.00/5 (1 vote)

See more:

64 Points
224 Posts
Process.start is not working in IIS
Jun 20, 2012 08:48 AM|LINK

Hi,

can any1 help me on this. while running in VS ,process.start is working fine.but,after deploying in IIS,i am not able to invoke that , Process.start is not working.

Here is my code,

Process.Start("IExplore.exe", "www.northwindtraders.com");

Plz help me on this

Posted 21-Dec-12 20:47pm

Narra sreenu

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2012-12-21T21:15:00

Yes it is.

Trust me on this.

It's just that you don't understand what is happening.
C# code is executed on the server, not the client. So when you execute

C#

Process.Start("IExplore.exe", "www.northwindtraders.com");

You are executing it on the server, so the server is where the instance of internet explorer is run - not the client. When you were in development, both the server and the client were the same machine, so it looked like it worked - but when you deployed to the web server, suddenly you can't see Internet Explorer open because it is open on the server (which may be round the other side of the world) and is probably annoying the heck out of the Web server administration guy. Assuming the server has IE installed which is not a given - it is very unlikely that anything unnecessary is installed and that would exclude IE.

You cannot do what you want, except under very specific circumstances. Security will not allow you to execute applications (and certianly not specific applications which may or may not be installed) on a cline machine from the server. And the specific circumstances do not occur in 99% of circumstances.