I have a complex WCF service that uses for example TCP, WindowsLogin, CustomLogin and transactions.
This have been hosted in IIS7 with WAS but to get better performance I will now try to move this in to a selfhosting environment as a Windows Service.
But I got som questions before I start this project :
-
Will I be able to install multiple instances of the same service without building several installation packages?
-
Will the WindowsLogin and CustomLogin work as before?
-
The startup time when hosted in IIS can sometimes be as long as 1 minute, I saw something about a 30 sek limit when hosted in a Windows Service? How do I handle this?
-
Is there something else I should consider before starting this project?
- Do you got article to recommend on this subject?
Yes, make your service name configurable in the installer. The port should also be configurable too so it does not conflict with other instances.
Yes
Either start it async, or call
this.RequestAdditionalTimein yourOnStart()methodThis one is really broad, kinda hard to address
http://msdn.microsoft.com/en-us/library/ms733069.aspx