10 years ago, I wrote Windows Service, and I do remember I had to use instalutil.exe to install the thing and that was a pain in the neck to install it, figure out what was wrong, deinstall it and go again... I remember having a batch file to do all this.
Turns out that there is a trick to do it easily - you use windows console app instead of windows service, and check in Main is this Environment.UserInteractive or not. That way you can attach to the process to debug it and iron out all the issues, and still have your windows service when deployed. In other words, have your cake and eat it.
And why Google failure? You can not search for this trick until you know it is possible. Many many people use installutil and forums and StackOverflow are full of answers to that, but to find out console app masquerading as service, you have to know about it, then you will find couple of nice blogs where this is explained.
So back to Stanislaw Lem story - to ask proper question, you have to know most of the answer already.
Turns out that there is a trick to do it easily - you use windows console app instead of windows service, and check in Main is this Environment.UserInteractive or not. That way you can attach to the process to debug it and iron out all the issues, and still have your windows service when deployed. In other words, have your cake and eat it.
And why Google failure? You can not search for this trick until you know it is possible. Many many people use installutil and forums and StackOverflow are full of answers to that, but to find out console app masquerading as service, you have to know about it, then you will find couple of nice blogs where this is explained.
So back to Stanislaw Lem story - to ask proper question, you have to know most of the answer already.
