Eh, you have thought about the security implications if a http-launched
app *could* launch an arbitrary process? I.e., Process.Start("cmd.exe -k
rmdir c:/winnt")?

For the issue with full-trust, look back in the archives for items by
Chris Sells on "Yahoo". That should provide a pretty good overview of
the current security challenges for an http-deployed WinForm.

John

John St. Clair
Prosjekt- og teamleder
Reaktor AS


> -----Original Message-----
> From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED]] On Behalf Of Dave Adair
> Sent: Saturday, October 05, 2002 11:08 PM
> To: [EMAIL PROTECTED]
> Subject: [ADVANCED-DOTNET] Can't use Process.Start from a WinForms
app.
> launched via http??
>
> I have a WinForms .exe.  When I click on a LinkLabel to go to a web
site
> (for example,
System.Diagnostics.Process.Start("http://www.Microsoft.com";)
> it works fine if I'm running the app. locally, but when it's launched
from
> http it fails.  The site I'm launching it from has "full trust"
permissions.
>
> This is the error that occurs:
>
> System.ComponentModel.Win32Exception: The requested section was not
present
> in the activation context
>
> Any ideas?  Can a WinForms app. launched from http not start a
process, even
> if it has full trust?   That doesn't make much sense to me.  What else
could
> be the problem?  How else could I launch a web page from my
http-launched
> exe?
>
> You can read messages from the Advanced DOTNET archive, unsubscribe
from
> Advanced DOTNET, or
> subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to