| Groups | Blog | Home |
dotnet interop : my service stops when a user logs off
It loads and runs fine when windows starts. All is well when the user logs on. However, when the user logs off the app unloads from memory and is no longer running (but the service appears to be running). From what I've been able to determine to date, I need to handle the CTRL_LOGOFF_EVENT so that my program doesn't unload when the user logs off. I just can't seem to get it working: Here are some code snippets I am working with modeled after a good article found at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemgcclasskeepalivetopic.asp Any help would be appreciated! With thanks, Rob Public Class MyWin32 ' Declare the SetConsoleCtrlHandler function as external ' and receiving a delegate. <DllImport("Kernel32")> _ Public Shared Function SetConsoleCtrlHandler(ByVal Handler As HandlerRoutine, _ ByVal Add As Boolean) As Boolean End Function ' A delegate type to be used as the handler routine ' for SetConsoleCtrlHandler. Delegate Function HandlerRoutine(ByVal CtrlType As CtrlTypes) As [Boolean] ' An enumerated type for the control messages ' sent to the handler routine. Public Enum CtrlTypes CTRL_C_EVENT = 0 CTRL_BREAK_EVENT = 1 CTRL_CLOSE_EVENT = 2 CTRL_LOGOFF_EVENT = 5 CTRL_SHUTDOWN_EVENT = 6 End Enum End Class **************************** the handler routine Shared Function ConsoleCtrlCheck(ByVal dwctrltype As MyWin32.CtrlTypes) As Boolean Select Case dwctrltype Case MyWin32.CtrlTypes.CTRL_C_EVENT Debughandler("CTRL+C received!") Return True Case MyWin32.CtrlTypes.CTRL_BREAK_EVENT Debughandler("CTRL+BREAK received!") Return True Case MyWin32.CtrlTypes.CTRL_CLOSE_EVENT Debughandler("CLOSE received!") Return True Case MyWin32.CtrlTypes.CTRL_LOGOFF_EVENT Debughandler("LOGOFF received!") Beep() Beep() Beep() Return True Case MyWin32.CtrlTypes.CTRL_SHUTDOWN_EVENT Debughandler("SHUTDOWN received!") Return True End Select End Function *********************** in my main program (vb.net vs 2005) .... Dim hr As New MyWin32.HandlerRoutine(AddressOf ConsoleCtrlCheck) MyWin32.SetConsoleCtrlHandler(hr, True) System.Windows.Forms.Application.Run()
Rob,
[quoted text, click to view] >I am trying to run my app as a service using srvany. I'm not familiar with Srvany, but it seems like a bit of a hack. Why not make a proper service? Mattias -- Mattias Sjögren [C# MVP] mattias @ mvps.org http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
If the computer is member of a domain, or configured for CTRL+ALT+DELETE log
on all progams but Windows will be closed at Log off. Skjoldmø [quoted text, click to view] "Rob Latour" <roblatour@rogers.com> wrote in message news:OJd$NFeJGHA.1088@tk2msftngp13.phx.gbl... >I am trying to run my app as a service using srvany. > > It loads and runs fine when windows starts. All is well when the user > logs on. However, when the user logs off the app unloads from memory and > is no longer running (but the service appears to be running). > > From what I've been able to determine to date, I need to handle the > CTRL_LOGOFF_EVENT so that my program doesn't unload when the user logs > off. I just can't seem to get it working: > > Here are some code snippets I am working with modeled after a good article > found at: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemgcclasskeepalivetopic.asp > > Any help would be appreciated! > > With thanks, Rob > > Public Class MyWin32 > > ' Declare the SetConsoleCtrlHandler function as external > > ' and receiving a delegate. > > <DllImport("Kernel32")> _ > > Public Shared Function SetConsoleCtrlHandler(ByVal Handler As > HandlerRoutine, _ > > ByVal Add As Boolean) As Boolean > > End Function > > > > ' A delegate type to be used as the handler routine > > ' for SetConsoleCtrlHandler. > > Delegate Function HandlerRoutine(ByVal CtrlType As CtrlTypes) As [Boolean] > > ' An enumerated type for the control messages > > ' sent to the handler routine. > > Public Enum CtrlTypes > > CTRL_C_EVENT = 0 > > CTRL_BREAK_EVENT = 1 > > CTRL_CLOSE_EVENT = 2 > > CTRL_LOGOFF_EVENT = 5 > > CTRL_SHUTDOWN_EVENT = 6 > > End Enum > > End Class > > > > > > > **************************** > the handler routine > > Shared Function ConsoleCtrlCheck(ByVal dwctrltype As MyWin32.CtrlTypes) As > Boolean > > Select Case dwctrltype > > Case MyWin32.CtrlTypes.CTRL_C_EVENT > > Debughandler("CTRL+C received!") > > Return True > > Case MyWin32.CtrlTypes.CTRL_BREAK_EVENT > > Debughandler("CTRL+BREAK received!") > > Return True > > Case MyWin32.CtrlTypes.CTRL_CLOSE_EVENT > > Debughandler("CLOSE received!") > > Return True > > Case MyWin32.CtrlTypes.CTRL_LOGOFF_EVENT > > Debughandler("LOGOFF received!") > > Beep() > > Beep() > > Beep() > > Return True > > Case MyWin32.CtrlTypes.CTRL_SHUTDOWN_EVENT > > Debughandler("SHUTDOWN received!") > > Return True > > End Select > > End Function > > > > > > *********************** > > in my main program (vb.net vs 2005) .... > > > > Dim hr As New MyWin32.HandlerRoutine(AddressOf ConsoleCtrlCheck) > > MyWin32.SetConsoleCtrlHandler(hr, True) > > System.Windows.Forms.Application.Run() > >
two reasons:
1. the program was not written as an service - so if I can get this to work it would be easier 2. I am using vs 2005 standard which doesn't support writing service (so it would also be less expensive then upgrading) [quoted text, click to view] "Mattias Sjögren" <mattias.dont.want.spam@mvps.org> wrote in message news:O42QnWfJGHA.1124@TK2MSFTNGP10.phx.gbl... > Rob, > >>I am trying to run my app as a service using srvany. > > I'm not familiar with Srvany, but it seems like a bit of a hack. Why > not make a proper service? > > > Mattias > > -- > Mattias Sjögren [C# MVP] mattias @ mvps.org > http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com > Please reply only to the newsgroup.
I have other service that run, for example real vnc, that don't shut down
when a user logs off? [quoted text, click to view] "Skjoldmø" <IkkeMig@NN.com> wrote in message news:OHKA%23yoJGHA.3176@TK2MSFTNGP12.phx.gbl... > If the computer is member of a domain, or configured for CTRL+ALT+DELETE > log on all progams but Windows will be closed at Log off. > > Skjoldmø > > > "Rob Latour" <roblatour@rogers.com> wrote in message > news:OJd$NFeJGHA.1088@tk2msftngp13.phx.gbl... >>I am trying to run my app as a service using srvany. >> >> It loads and runs fine when windows starts. All is well when the user >> logs on. However, when the user logs off the app unloads from memory and >> is no longer running (but the service appears to be running). >> >> From what I've been able to determine to date, I need to handle the >> CTRL_LOGOFF_EVENT so that my program doesn't unload when the user logs >> off. I just can't seem to get it working: >> >> Here are some code snippets I am working with modeled after a good >> article found at: >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemgcclasskeepalivetopic.asp >> >> Any help would be appreciated! >> >> With thanks, Rob >> >> Public Class MyWin32 >> >> ' Declare the SetConsoleCtrlHandler function as external >> >> ' and receiving a delegate. >> >> <DllImport("Kernel32")> _ >> >> Public Shared Function SetConsoleCtrlHandler(ByVal Handler As >> HandlerRoutine, _ >> >> ByVal Add As Boolean) As Boolean >> >> End Function >> >> >> >> ' A delegate type to be used as the handler routine >> >> ' for SetConsoleCtrlHandler. >> >> Delegate Function HandlerRoutine(ByVal CtrlType As CtrlTypes) As >> [Boolean] >> >> ' An enumerated type for the control messages >> >> ' sent to the handler routine. >> >> Public Enum CtrlTypes >> >> CTRL_C_EVENT = 0 >> >> CTRL_BREAK_EVENT = 1 >> >> CTRL_CLOSE_EVENT = 2 >> >> CTRL_LOGOFF_EVENT = 5 >> >> CTRL_SHUTDOWN_EVENT = 6 >> >> End Enum >> >> End Class >> >> >> >> >> >> >> **************************** >> the handler routine >> >> Shared Function ConsoleCtrlCheck(ByVal dwctrltype As MyWin32.CtrlTypes) >> As Boolean >> >> Select Case dwctrltype >> >> Case MyWin32.CtrlTypes.CTRL_C_EVENT >> >> Debughandler("CTRL+C received!") >> >> Return True >> >> Case MyWin32.CtrlTypes.CTRL_BREAK_EVENT >> >> Debughandler("CTRL+BREAK received!") >> >> Return True >> >> Case MyWin32.CtrlTypes.CTRL_CLOSE_EVENT >> >> Debughandler("CLOSE received!") >> >> Return True >> >> Case MyWin32.CtrlTypes.CTRL_LOGOFF_EVENT >> >> Debughandler("LOGOFF received!") >> >> Beep() >> >> Beep() >> >> Beep() >> >> Return True >> >> Case MyWin32.CtrlTypes.CTRL_SHUTDOWN_EVENT >> >> Debughandler("SHUTDOWN received!") >> >> Return True >> >> End Select >> >> End Function >> >> >> >> >> >> *********************** >> >> in my main program (vb.net vs 2005) .... >> >> >> >> Dim hr As New MyWin32.HandlerRoutine(AddressOf ConsoleCtrlCheck) >> >> MyWin32.SetConsoleCtrlHandler(hr, True) >> >> System.Windows.Forms.Application.Run() >> >> > >
While I agree he should write this as a Service, I'd like to comment on
this: "More, you are using Windows forms in your application, and you expect it to keep runing when the user logs off? Well, that's not possible" He used this code: System.Windows.Forms.Application.Run() This just sets up a message pump on the current thread. This can be done just fine within a service. I didn't see any place else in his code where he was creating any forms, etc. Tom
If it's not written as a service it won't behave as a service.
More, you are using Windows forms in your application, and you expect it to keep runing when the user logs off? Well, that's not possible, windows services can/should not have a UI ( unless you set the service to interact with the desktop, something you should do only for debugging), windows services do not survive a logoff when they are attached to the interactive desktop. Willy. [quoted text, click to view] "Rob Latour" <roblatour@rogers.com> wrote in message | two reasons:news:%23M0MqNtJGHA.312@TK2MSFTNGP09.phx.gbl... | 1. the program was not written as an service - so if I can get this to | work it would be easier | 2. I am using vs 2005 standard which doesn't support writing service (so | it would also be less expensive then upgrading) | | [quoted text, click to view] | "Mattias Sjögren" <mattias.dont.want.spam@mvps.org> wrote in message | > Rob,| news:O42QnWfJGHA.1124@TK2MSFTNGP10.phx.gbl... | > | >>I am trying to run my app as a service using srvany. | > | > I'm not familiar with Srvany, but it seems like a bit of a hack. Why | > not make a proper service? | > | > | > Mattias | > | > -- | > Mattias Sjögren [C# MVP] mattias @ mvps.org | > http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com | > Please reply only to the newsgroup. | |
There is a windows ui portion to my app, I had checked Interact with the
desktop as a services option and it works well - except for the log off thing. From your responses however it would appear there is no way to survive a windows log off using vb.net however I am left wondering how other apps that interact with my desktop - such as my UPS monitoring application and Real VNC seem to be able to survive the logoff just fine. Thanks, Rob [quoted text, click to view] "Willy Denoyette [MVP]" <willy.denoyette@telenet.be> wrote in message news:eDUJ9P3JGHA.3912@TK2MSFTNGP10.phx.gbl... > As far as I can see this is not a complete program, so I can't tell if no > UI > elements are created and also I don't see a reason why he needs a message > pump. > Note that the OP also registers a console control handler, which is also > not > usable from a service. So I have the impression he's trying to run a > windows/console application as a service and thinks he can solve the > logoff > issue with a console handler. > > Willy. > > > "TDC" <NOtcarvinSPAM@lycos.com> wrote in message > news:1138805652.398520.185160@g47g2000cwa.googlegroups.com... > | While I agree he should write this as a Service, I'd like to comment on > | this: > | > | "More, you are using Windows forms in your application, and you expect > | it to keep runing when the user logs off? Well, that's not possible" > | > | He used this code: > | > | System.Windows.Forms.Application.Run() > | > | This just sets up a message pump on the current thread. This can be > | done just fine within a service. I didn't see any place else in his > | code where he was creating any forms, etc. > | > | Tom > | > >
As far as I can see this is not a complete program, so I can't tell if no UI
elements are created and also I don't see a reason why he needs a message pump. Note that the OP also registers a console control handler, which is also not usable from a service. So I have the impression he's trying to run a windows/console application as a service and thinks he can solve the logoff issue with a console handler. Willy. [quoted text, click to view] "TDC" <NOtcarvinSPAM@lycos.com> wrote in message | While I agree he should write this as a Service, I'd like to comment onnews:1138805652.398520.185160@g47g2000cwa.googlegroups.com... | this: | | "More, you are using Windows forms in your application, and you expect | it to keep runing when the user logs off? Well, that's not possible" | | He used this code: | | System.Windows.Forms.Application.Run() | | This just sets up a message pump on the current thread. This can be | done just fine within a service. I didn't see any place else in his | code where he was creating any forms, etc. | | Tom |
Agreed. The graphical portion of the application must be seperated
from that which you intend to be used as a service. I have written services in VB.NET that work just fine, including one that basically wraps what used to be an ActiveX Exe (and that works fine too). There are any number of IPC methods you can use to communicate from your UI to your service, but obviously if your application access the UI alot then this will require a major restructuring to seperate your business logic from your user presentation. Tom
Because they (the UI part) are separate applications that use some form of
IPC mechanism to 'talk' to the service. Such applications are configured as 'autoruns', that is they start when a user logons on and they stop when a user logs off. Services that directly interact with the desktop (as SYSTEM) handle the logon/logoff events and do migrate the service desktop to the active desktop using Win32 API's, such services are really insecure and they will fail on Vista. Willy. [quoted text, click to view] "Rob Latour" <roblatour@rogers.com> wrote in message | There is a windows ui portion to my app, I had checked Interact with thenews:%23wM37z3JGHA.3100@tk2msftngp13.phx.gbl... | desktop as a services option and it works well - except for the log off | thing. From your responses however it would appear there is no way to | survive a windows log off using vb.net however I am left wondering how other | apps that interact with my desktop - such as my UPS monitoring application | and Real VNC seem to be able to survive the logoff just fine. | | Thanks, Rob | | [quoted text, click to view] | "Willy Denoyette [MVP]" <willy.denoyette@telenet.be> wrote in message | > As far as I can see this is not a complete program, so I can't tell if | news:eDUJ9P3JGHA.3912@TK2MSFTNGP10.phx.gbl... no | > UI | > elements are created and also I don't see a reason why he needs a message | > pump. | > Note that the OP also registers a console control handler, which is also | > not | > usable from a service. So I have the impression he's trying to run a | > windows/console application as a service and thinks he can solve the | > logoff | > issue with a console handler. | > | > Willy. | > | > [quoted text, click to view] | > "TDC" <NOtcarvinSPAM@lycos.com> wrote in message | > | While I agree he should write this as a Service, I'd like to comment | > news:1138805652.398520.185160@g47g2000cwa.googlegroups.com... on | > | this: | > | | > | "More, you are using Windows forms in your application, and you expect | > | it to keep runing when the user logs off? Well, that's not possible" | > | | > | He used this code: | > | | > | System.Windows.Forms.Application.Run() | > | | > | This just sets up a message pump on the current thread. This can be | > | done just fine within a service. I didn't see any place else in his | > | code where he was creating any forms, etc. | > | | > | Tom | > | | > | > | |
[quoted text, click to view] "TDC" <NOtcarvinSPAM@lycos.com> wrote in message | Agreed. The graphical portion of the application must be seperatednews:1138895550.059642.235690@g44g2000cwa.googlegroups.com... | from that which you intend to be used as a service. | | I have written services in VB.NET that work just fine, including one | that basically wraps what used to be an ActiveX Exe (and that works | fine too). | | There are any number of IPC methods you can use to communicate from | your UI to your service, but obviously if your application access the | UI alot then this will require a major restructuring to seperate your | business logic from your user presentation. | True, but Services that interact 'heavily' with a UI front-end shouldn't be written as services in the first place, as they are mainly 'driven' by the presence of an interactive user, they aren't of great use at all when no such user is present. The most obvious problem with services today is that they aren't used for what they were originally designed for (NT Services, designed back in 1990), that is run as a 'daemon' in a security constrained context, that is, running in a 'sandboxed and secured desktop' as a 'non-interactive' user with elevated 'local security' privileges. If you understand all these constraints, it should be clear that instantiating full ActiveX COM components (OCX96) is a big NO and a "not supported" scenario. Another problem, introduced with .NET, is that everyone seems to need a bunch of Services running on their boxes, but most don't know that the number of services on a (Win32) system is restricted by the size of the non-pooled memory available, add to that, the size of the non-pooled memory and the handles taken by the GDI when interact with the desktop is enabled and you know why some systems behave so badly. Willy.
Thanks for all of this.
I guess its back to the drawing board for me :-) Cheers, Rob [quoted text, click to view] "Willy Denoyette [MVP]" <willy.denoyette@telenet.be> wrote in message news:u8fEvzBKGHA.1424@TK2MSFTNGP12.phx.gbl... > > "TDC" <NOtcarvinSPAM@lycos.com> wrote in message > news:1138895550.059642.235690@g44g2000cwa.googlegroups.com... > | Agreed. The graphical portion of the application must be seperated > | from that which you intend to be used as a service. > | > | I have written services in VB.NET that work just fine, including one > | that basically wraps what used to be an ActiveX Exe (and that works > | fine too). > | > | There are any number of IPC methods you can use to communicate from > | your UI to your service, but obviously if your application access the > | UI alot then this will require a major restructuring to seperate your > | business logic from your user presentation. > | > > True, but Services that interact 'heavily' with a UI front-end shouldn't > be > written as services in the first place, as they are mainly 'driven' by the > presence of an interactive user, they aren't of great use at all when no > such user is present. > The most obvious problem with services today is that they aren't used for > what they were originally designed for (NT Services, designed back in > 1990), > that is run as a 'daemon' in a security constrained context, that is, > running in a 'sandboxed and secured desktop' as a 'non-interactive' user > with elevated 'local security' privileges. If you understand all these > constraints, it should be clear that instantiating full ActiveX COM > components (OCX96) is a big NO and a "not supported" scenario. > Another problem, introduced with .NET, is that everyone seems to need a > bunch of Services running on their boxes, but most don't know that the > number of services on a (Win32) system is restricted by the size of the > non-pooled memory available, add to that, the size of the non-pooled > memory > and the handles taken by the GDI when interact with the desktop is enabled > and you know why some systems behave so badly. > > Willy. > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |