Re: Launching an application from ASP.NET
From: Ten (nick.bartolotti@tentechnologies.com)
Date: 11/22/02
- Next message: Tim Greenfield: "Programmtically invoke the login prompt"
- Previous message: george d lake: "Re: How to retrive List of Roles (Win auth) HELP"
- In reply to: Nick Holmes: "Re: Launching an application from ASP.NET"
- Next in thread: Willy Denoyette [MVP]: "Re: Launching an application from ASP.NET"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Ten" <nick.bartolotti@tentechnologies.com> Date: Fri, 22 Nov 2002 19:37:53 GMT
Nick,
Thanks for the information. I have a few questions WRT your response.
Where can I find documentation about the further restrictions you mentioned.
This was my initial guess at the problem, because it makes sense, but I
can't find anything in the MSDN to this respect. I'd like to document the
changes so future designs can be aware of the limitation.
Also, I can't launch the application on the client side because it modifies
configuration settings for the web application and interfaces with things
like TWAIN, ISIS, Acrobat's automation interface, and other custom entities
on the web server that provide access to our custom hardware.
Thanks,
Nick.
"Nick Holmes" <nicknews.removeXs@coyXote-softXware.com> wrote in message
news:#i2cPULkCHA.2432@tkmsftngp10...
> Winstations are like an abstraction of the screen, keyboard and mouse.
> Clearly, only one such Winstation is connected to the real screen and
> keyboard, either the currently logged on (interactive) user, or the logon
> handler, if no one is logged on.
>
> Each Win32 Service has its own winstation, which it will share with any
> other processes it creates. If you launch a process from ASP.NET, you wont
> see the UI, even though the process will list as running.
>
> I once wrote some code that allowed to Service to run a process on the
> interactive desktop, WinSta0, but there were a couple of serious issues;
the
> Service had to run with really high privileges, and it didnt work if
no-one
> was logged on. The code was non-trivial C++. Not only do I think you
> couldn't do the same thing from managed code, but also I seem remember
that
> further restrictions have been introduced into what can be done here (and,
> quite rightly so).
>
> Anyway, you dont need to worry about this, all you need to do is launch
the
> application from the client side. You can still put you server side code
in
> place, to determine whether to render the client scripting into the page
or
> not.
>
> Nick Holmes.
>
>
> "Ten" <nick.bartolotti@tentechnologies.com> wrote in message
> news:tPOC9.152460$c51.44935337@twister.nyroc.rr.com...
> > Willy,
> >
> > This is Nick from TenTechnologies writing.
> >
> > I have a reason to do this. We configure our web pages to know if they
> are
> > running on the server itself rather than a client machine. When the
page
> > detects that is is running on the server, we allow the user to launch
> Win32
> > applications because they will interact with the application
immediately.
> > Among the things the apps do are configure some aspects of our custom
> > hardware and create new system resources that are then immediately
> available
> > for use to all client connections.
> >
> > In ASP on IIS5 we accomplished this by writing a COM object that
launched
> > the application. In ASP.NET we want to use the system.process.whatever
to
> > launch the app. When using the system.process.whatever, we can launch
the
> > app but the UI never is displayed. We tried many combinations of
> parameters
> > to the method call but nothing worked.
> >
> > My guess is that MS has tightened it's hold on what can and cannot be
> > displayed. Allowing an app to run with a window (invoked from an aspnet
> > user login) could be a huge security risk if the app being run was a
clone
> > of the login screen. All the client would have to do is launch the app
> and
> > wait for the user to enter his login credentials then write the
> information
> > to an FTP site, http, or file on the system for later retreival.
> >
> > In any event, we'd still like to do this because our web application,
> > although capable of working across the internet is really one used on an
> > intranet.
> >
> > Any information on what a winstation is will be helpful. Of course, I
> will
> > research this on this end.
> >
> > Thanks,
> > Nick.
> >
> >
> > "Willy Denoyette [MVP]" <willy.denoyette@pandora.be> wrote in message
> > news:eMc$FiUjCHA.1368@tkmsftngp09...
> > > This is not possible as the process launched from asp.net (or IIS for
> that
> > matter) has no visible Winstation associated. Why would
> > > you do this in the first place, your application with UI would run
> server
> > side where there's noone to look at it.
> > >
> > > Willy.
> > >
> > > "The Viper" <jrocketz300@yahoo.com> wrote in message
> > news:43d2ad4a.0211151749.6e7e6951@posting.google.com...
> > > > I"m having trouble launching application with UI within the .net
> > > > framework as web services. I can only see the process running but
> > > > with no UI. Does anyone know how to configure it so that the UI is
> > > > visible???
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Tim Greenfield: "Programmtically invoke the login prompt"
- Previous message: george d lake: "Re: How to retrive List of Roles (Win auth) HELP"
- In reply to: Nick Holmes: "Re: Launching an application from ASP.NET"
- Next in thread: Willy Denoyette [MVP]: "Re: Launching an application from ASP.NET"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
