I wanted to create a separate configuration in order to get a separate assembly with my own config (so that the SQL Server connection string was different). That is, in the configuration manager I created a new one ( Deploy ) and in the context menu of the Web.config (in the solution explorer) I made the “ Add configuration conversion ”. And I got a Web.Deploy.config . If you click " View changes for Web.Deploy.config " in the context menu of Web.Deploy.config , then they are there, it is different from the root Web.config . While all the way through. But when you start (via Visual Studio) applications, these changes are not applied, the root Web.config remains the config file (an attempt is made to use the wrong connection string, which in Web.Deploy.config , but generally some ... default is visible (on the Web .config connection string not specified)). In the folder with the project is \ bin and \ obj . In \ bin simply lie dll, in \ obj there is a folder for each configuration in which there is ProjectName.csproj.App.config , which is identical to the root Web.config .

Question: how to achieve the appearance of assemblies for each project configuration? Where should they be stored?

    1 answer 1

    It turns out that Visual Studio uses only the root Web.config at startup, regardless of the selected configuration. When publishing a project, the already converted Web.config is used , depending on the configuration selected during publication. Thus, using Visual Studio, this cannot be achieved. Perhaps by configuring MSBuild ($ (ProjectName) .csproj), this can be achieved.