Since this sounds like custom development any of the other offered solutions, while perhaps not your ideal, will work correctly and are a safer way to go. It sounds like you may have stepped too far outside the Win32 box. NET developed service, you could create n copies of the executable on your file system, and have each automatically get the parameters from the appropriate app.config file. Learn how to perform a clean boot in Windows (10, 8. As you can see customizing the command line is a bit more painful than it should be. Clean boot is one of the troubleshooting techniques to identify the issue causing application/service. Really though, a better way is to store your configuration somewhere the service knows about, like perhaps the registry or file system, and read whatever values you need. Hit the OK button to save the change and quit. You can then find the ‘Startup Type‘ and change it to Manual, Automatic (Delayed Start), Automatic, or Disabled. "ImagePath":C:\Projects\MyService\bin\MyService.exe Parameter1 Parameter2 To change startup type of a service, double click the service to open its Properties window. Assuming your custom service is called MyService: NET START won't allow you to pass arbitrary parameters as far as I know (it appears they have to be prefixed with a /), I believe the correct way is to modify the appropriate registry key and stop/start the service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |