Home/ Questions/Q 4601694
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T23:51:56+00:00

I am trying to publish an internal application I have developed. I have done

  • 0

I am trying to publish an internal application I have developed. I have done this multiple times before with no issues, but never with this application.

In VS2010 I go to my TestManager project, hit publish, and set everything up correctly. I go to my folder and run the setup.exe. Installation then fails and gives me a log file stating that it cannot find the TestManager.exe.config.deploy file.

When I go into the Application Files directory, it’s true that it did not create a TestManager.exe.config.deploy file, but it instead created the config as App.config.deploy.

I have looked at my other ClickOnce installers (even installers for other projects in the same solution) and verified that it is correctly creating an <appname>.exe.config.deploy and not creating an app.config.deploy.

Why is Click-Once not creating the app.config file properly for deployment, and how can I fix it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not clear if this will work, but if you’re having ClickOnce file deploy issues with specific files, then the first thing I check is the build action property for those files.

    Using the Solution Explorer, check that the App.Config’s build action is still “None”.

    If it were listed as “Content”, this might lead to the file being deployed with it’s original name (rather than the prefixed name) as you mentioned.

    NOTE: Other config files should be marked as Content in order to ensure they end up in the deploy folder.

    • 0