I have an icon that points at a server application written in dotNet.

I wish to allow the users on distributed pc's to be able to close the
application and walk away but I have to ensure that this does not shut down
the actual application on the server.

In this way the application on the server acts kind of like a service but it
can never be closed down on the server.

Has anybody any idea how to implement this or indeed can it be done?

Hi,

The way I would do it is to create a web service which handles all
my business logic. Then I would create a windows forms application that uses
the web service. That way the web service is always available and the client
can shut down the application on his pc. I hope this helps

Ken
--------------------------

"marcmc" wrote:

>
> I have an icon that points at a server application written in dotNet.
>
> I wish to allow the users on distributed pc's to be able to close the
> application and walk away but I have to ensure that this does not shut down
> the actual application on the server.
>
> In this way the application on the server acts kind of like a service but it
> can never be closed down on the server.
>
> Has anybody any idea how to implement this or indeed can it be done?
>
>

thankyou,

Unfortunately I have no (and I mean that literally) experience of web
services and xml. Is there another simpler(to me) means of achieveing this
task.



"Ken Tucker [MVP]" wrote:

> Hi,
>
> The way I would do it is to create a web service which handles all
> my business logic. Then I would create a windows forms application that uses
> the web service. That way the web service is always available and the client
> can shut down the application on his pc. I hope this helps
>
> Ken
> --------------------------
>
> "marcmc" wrote:
>
> >
> > I have an icon that points at a server application written in dotNet.
> >
> > I wish to allow the users on distributed pc's to be able to close the
> > application and walk away but I have to ensure that this does not shut down
> > the actual application on the server.
> >
> > In this way the application on the server acts kind of like a service but it
> > can never be closed down on the server.
> >
> > Has anybody any idea how to implement this or indeed can it be done?
> >
> >

Of course Time is of the essence here and reading my book on xml web services
is merely a lost dream at this stage.

Could I use API calls to get the computer name and implement some logic
around the Application.Exit when it's event is fired that ensures the Exit
button on a non-server machine cannot close the server application. Does that
sound mad?

"marcmc" <(E-Mail Removed)> wrote in message
news:0D374A73-1592-4BD0-BBB9-(E-Mail Removed)...
>
> I have an icon that points at a server application written in dotNet.
>
> I wish to allow the users on distributed pc's to be able to close the
> application and walk away but I have to ensure that this does not shut
> down
> the actual application on the server.
>
> In this way the application on the server acts kind of like a service but
> it
> can never be closed down on the server.
>
> Has anybody any idea how to implement this or indeed can it be done?
>

if the application is going to "act kind of like a service", why not make it
an actual service?

I don't have that option due to my reliability on Sophisticated logging and
sms tools within .net. For that I need a working interface.

"Rick Mogstad" wrote:

>
> "marcmc" <(E-Mail Removed)> wrote in message
> news:0D374A73-1592-4BD0-BBB9-(E-Mail Removed)...
> >
> > I have an icon that points at a server application written in dotNet.
> >
> > I wish to allow the users on distributed pc's to be able to close the
> > application and walk away but I have to ensure that this does not shut
> > down
> > the actual application on the server.
> >
> > In this way the application on the server acts kind of like a service but
> > it
> > can never be closed down on the server.
> >
> > Has anybody any idea how to implement this or indeed can it be done?
> >
>
> if the application is going to "act kind of like a service", why not make it
> an actual service?
>
>
>
>

Hi,

What does you application do?

Ken
-------------
"marcmc" <(E-Mail Removed)> wrote in message
news:8A5BD816-1385-480F-A660-(E-Mail Removed)...
Of course Time is of the essence here and reading my book on xml web
services
is merely a lost dream at this stage.

Could I use API calls to get the computer name and implement some logic
around the Application.Exit when it's event is fired that ensures the Exit
button on a non-server machine cannot close the server application. Does
that
sound mad?