System.Diagnostics.Process.Start() (6 overloads)
http://msdn.microsoft.com/en-us/library/system.diagnostics.process.start.aspx
By default, ASP.NET runs its worker process with a weak account.You
will need to grant "run executable" rights to this account.
In the past, I have created a .bat file on the server and linked to it as a
download file. Let them download it and get them to click run instead of
save. Will this be a suitable compromise?
Alternatively, research how some of these trojan horse writers exploit
loopholes in IE, but expect that method to be blocked in the future.
--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available
"Raghupathi K" <raghu...@gmail.com> wrote in message
news:bf9213ef-9f2c-4d9c...@y28g2000prd.googlegroups.com...
>> I need to be able to start an application on a client machine from a web
>> page.
>
> System.Diagnostics.Process.Start() (6 overloads)
>
> http://msdn.microsoft.com/en-us/library/system.diagnostics.process.start.aspx
>
> By default, ASP.NET runs its worker process with a weak account.You
> will need to grant "run executable" rights to this account.
This won't work at all. The OP wants to run a client-side process, not a
server-side process...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
>> System.Diagnostics.Process.Start() (6 overloads)
> I can't see how that will run an application on the client side.
It won't.
> In the past, I have created a .bat file on the server and linked to it as
> a download file. Let them download it and get them to click run instead of
> save. Will this be a suitable compromise?
That's a far better solution, and neatly side-steps the browser security.
Kostya
"Greg55305" <Greg...@discussions.microsoft.com> wrote in message
news:62780B06-80D3-4E14...@microsoft.com...