I'm creating a new Installscript project that fails to install an EXE as a service. I have a component created for it and the file properly gets copied, but it fails to register it as a service. I assume that InstallShield would use InstallUtil from the .NET folder to register, but it never works. I have verified that the proper paths to .NET are in the Options dialog. I have also verified that I can also install this EXE as a service by manually using InstallUtil through a command prompt. I keep thinking there should be something, within the IS interface, to identify this as a service, but don't see anything. What's funny, is that I have access to another InstallScript project (someone else created) which does properly install this EXE as a service. But, the only difference I can find between these two projects, regarding installing this EXE, is the version of INstallshield. How are services installed for a InstallScript type project?
In an InstallScript project, you would need to use the Objects view to add the NT Service object to your project.
If it is working in the previous version, you can copy merge module to your new version if the NT Service object not available in the latest version you are building.
There are no merge modules in this old project. The service, that it's installing, is a .NET assembly (EXE file) that is simply setup as a component. I don't even see any use of ServiceAddService() in the InstallScripts. What other methods are there for installing a service and why is not clear on how this old project is registering this EXE as a service?
For my new InstallScript project, I'm currently examining the use of ServiceAddService() function to install this EXE as a service. Is this a viable solution?
