I installed my windows service via (name of the service: Testing Service)
InstallUtil.exe present in .NET Framework (:\Windows\Microsoft.NET\FrameWork64\v4) in a windows 7 computer.
I can see my service under services console.
However, i went to programs and features of control panel to manually uninstall the same service, i didn't see my services under programs and features?
Any thoughts why a service will not be shown, so that, user can uninstall it?
I checked the show hidden files too, but still service not shown?
InstallUtil.exe: As others have stated, InstallUtil.exe is intended for development use only, not for final distribution of your service.
MSI: The normal way to deploy services in the fashion you describe (with a proper entry in add/remove programs) would be to use an MSI installer created using a tool designed to help you do so (it is not advisable to "roll your own" tool to do this).
Ad-Hoc: The ad-hoc description of deployment tools below was written in a hurry, and has sort of been re-purposed as a general description of such tools. Not too relevant for the question asked, but it sort of "happened" and here it is.
How can I compare the content of two (or more) MSI files? (towards bottom) - (most of) these are not full-featured tools to make setups, but great to inspect MSI files and to create transforms.
There are many tools you can use for MSI-creation, for example (arbitrary order - links to Stefan Kruger's installsite.org below will show further tools, these are just the most common ones):
WiX
- quick download
Free, open source framework - excellent, but with a learning curve, hence a few more links.
WiX quick-start tips
(a bit chaotic, strangely upvoted, must be helpful).FireGiant
has a WiX expansion pack (which costs money).IsWiX
- quick download
IsWiX
The various ways used (and abused) to install Windows Services.
Advanced Installer
- quick download
InstallShield
- quick download
PACE suite
- quick download
Visual Studio Installer project type
Auto-Update?: Various ways to create auto-updating packages.
What are the above tools like in actual use? Here are some pragmatic observations and summaries:
There are many further tools available to create create installers / setup.exe files of various kinds (not just MSI tools, but general purpose, legacy tools, multi-platform tools, etc...):
Stefan Kruger's Comprehensive Lists:
Other Links:
Cross-Platform Installers: Does an universal cross-platform installer exists? (non-MSI tools).
dotNetInstaller: There is also the dotNetInstaller Setup Bootstrapper - which I have never used.
Here it is on github.com (source).
Just a bootstrapper (runs things in sequence for you, and then some), not a development tool as such. I find this tool "a bit weird".
Some General Links: And there are various other ways to deploy - for example with self-extracting zip archives and stuff like that. Not recommended, but some links:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With