«

Yes, I want to run a Windows app on client-side...

I have created a test web site consists of one page and here is its code :
protected void Page_Load(object sender, EventArgs e)

{

System.Diagnostics.Process p = new System.Diagnostics.Process();

p = System.Diagnostics.Process.Start("IExplore.exe");


}

It is not working and no exception appears ..!!


"Mark Rae [MVP]" <> wrote in message
news:...
> "Juan T. Llibre" <> wrote in message
> news:ui$%...
>
>> Use System.Diagnostics.Process.Start()
>>
>> The executable will run as the ASP.NET account,
>> so the ASP.NET account will need whichever permissions the process needs.
>
> I interpreted the OP as wanting to run a Windows app client-side...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"Tamer Ibrahim" <> wrote in message
news:...

> Yes, I want to run a Windows app on client-side...

That's what I thought, though you didn't specify that in your original
post...

> It is not working and no exception appears ..!!

It won't work, because it is trying to run Internet Explorer on your
webserver...

Can you please explain *precisely* what you're trying to do here...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Here is what I'm trying to do. Calling this windows application,
Archiving.exe, on the client side ....

protected void Page_Load(object sender, EventArgs e)

{

System.Diagnostics.Process p = new System.Diagnostics.Process();

p = System.Diagnostics.Process.Start(@"C:\Program Files\The Pen IT\Archiving
System\Archiving.exe");


}



"Mark Rae [MVP]" <> wrote in message
news:%...
> "Tamer Ibrahim" <> wrote in message
> news:...
>
>> Yes, I want to run a Windows app on client-side...
>
> That's what I thought, though you didn't specify that in your original
> post...
>
>> It is not working and no exception appears ..!!
>
> It won't work, because it is trying to run Internet Explorer on your
> webserver...
>
> Can you please explain *precisely* what you're trying to do here...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"Tamer Ibrahim" <> wrote in message
news:%...

> Here is what I'm trying to do. Calling this windows application,
> Archiving.exe, on the client side ....

> System.Diagnostics.Process p = new System.Diagnostics.Process();

I already told you that won't work - that is server-side code, not
client-side code.

I've already provided you with a link showing you how to do this
client-side - here it is again:
http://www.faqts.com/knowledge_base/.../31646/fid/124


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

re:
!> I interpreted the OP as wanting to run a Windows app client-side...

I wish him good luck with that chore if that what he wants.

An ActiveX object would be the first thing to try but I,
like you, discourage their use given the security issues.

Users have to approve the installation of any ActiveX object
....and that is enough to cause problems.

The whole idea of the .Net Framework is *not* to do client-side processing,
except for UI actions and notifications which use Javascript, for which Ajax
is the ideal vehicle, although it will *not* run executables client-side either.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"Mark Rae [MVP]" <> wrote in message news:...
> "Juan T. Llibre" <> wrote in message news:ui$%...
>
>> Use System.Diagnostics.Process.Start()
>>
>> The executable will run as the ASP.NET account,
>> so the ASP.NET account will need whichever permissions the process needs.
>
> I interpreted the OP as wanting to run a Windows app client-side...
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

"Juan T. Llibre" <> wrote in message
news:...

> re:
> !> I interpreted the OP as wanting to run a Windows app client-side...
>
> I wish him good luck with that chore if that what he wants.
>
> An ActiveX object would be the first thing to try but I,
> like you, discourage their use given the security issues.
>
> Users have to approve the installation of any ActiveX object
> ...and that is enough to cause problems.
>
> The whole idea of the .Net Framework is *not* to do client-side
> processing,
> except for UI actions and notifications which use Javascript, for which
> Ajax
> is the ideal vehicle, although it will *not* run executables client-side
> either.

Indeed - I've already advised him twice not to do this...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net