I'm having an issue that I have not encountered before where App.configs for Windows Services that are installed under the "Program Files (x86)" directory are locked for editing even when the Windows Services are not running. I get a message that the file is in use, even when it should not be.
- Is this something specific about putting a .config file for a Windows Service under the Program Files directory?
- How can I allow a user that knows the location of the .config file to edit it in Notepad or another editor without receiving the file is "in use" message.
I have tried the install of the Windows Service on three different machines and ensured the service is not actually started/running. I'm hoping to gain some knowledge on why this is not working as in the past I have had app.configs editable for .exes that happen to live in a directory.