I developed a protocol between PCs. Here a special process receives data packet from a remote node and checks the header. It can pass the packet to
other applications that registered with it or handle it depending on packet
address. This process is now part of dll and when a application registers
using dll api, this process is invoked and will be alive as long as atleast
one application is using dll.
Sounds like something similar is done with a "Windows service". I want to
know what is advantage of making this process as windows service ? What is
advantage of not making a Windows service.
Please refer a good book that will help me understand windows services,
processes, threads etc. I have Jeffrey Richter book, great to understand some
of these concepts, but it does not talk about windows services.
Re: Stuck in stream.read ... plz help. ... in the windows service when it detects that the data ...listener thread which accepts connections from clients. ... After every packet read it starts a timer. ... (microsoft.public.dotnet.general)
Re: Application, dll and driver design ... How big can semaphore "lMaximumCount" can be. ... > But there is one problem with replacing window messages with packet reading... I have 15 processes all talking to each other and Dll process.... (microsoft.public.win32.programmer.ui)
Re: Sharing code between ASP.NET application and Windows service app in the same solution ... and I managed to use that DLL into my project (Web ... I already set the project dependences in Solution properties,... Even if I copy myself the new DLL from library project to Web app bin... >> project, those files are actually copied to Windows service folder, So ... (microsoft.public.dotnet.framework)
Re: Sharing code between ASP.NET application and Windows service app in the same solution ... and I managed to use that DLL into my project (Web ... I already set the project dependences in Solution properties,... Even if I copy myself the new DLL from library project to Web app bin... >> project, those files are actually copied to Windows service folder, So ... (microsoft.public.dotnet.framework.aspnet)
Re: Sharing code between ASP.NET application and Windows service app in the same solution ... and I managed to use that DLL into my project (Web ... I already set the project dependences in Solution properties,... Even if I copy myself the new DLL from library project to Web app bin... >> project, those files are actually copied to Windows service folder, So ... (microsoft.public.dotnet.general)
