Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to create new build configuration

Here's an annoying one.

I have a solution in Visual Studio 2012 that contains a .Net 4.5 class library, a .NET 4.5 web application and a .NET 4.5 website.

I want to create a new build configuration, let's call it Publish or Live, mainly so that I can select it when publishing the web application and use a web.config transform.

So I click my Solution, go to Build then Configuration Manager. In the configuration dropdown, I choose , and I get the little popup asking me for the name of the new configuration etc. I fill this in, click OK, and......nothing. Nada.

No matter what I call the new configuration, whether I choose to copy from an existing configuration etc, no new configuration is created. Am I missing something blindingly obvious?

Thanks,

Matt

like image 611
MattW Avatar asked Sep 26 '12 08:09

MattW


People also ask

How do I create a new configuration in Visual Studio?

In the Configuration drop-down list for that project, choose New. The New Project Configuration dialog box opens. In the Name box, enter a name for the new configuration. To use the property settings from an existing project configuration, in the Copy settings from drop-down list, choose a configuration.

How do I get build options in Visual Studio?

If you want to build multiple configurations and platforms in one action, you can use the Build > Batch Build option in Visual Studio. To access this feature, press Ctrl+Q to open the search box, and enter Batch build .

How do I find TeamCity build configuration?

To find the build configuration creation wizard: Go to Administration | Projects and open the required project. Alternatively, open the project using the Projects pop-up menu and click Edit Project Settings. The Project Settings page will open.


2 Answers

I had the same issue, but when I deselected 'create new project configurations', I was able to create a new solution configuration.

like image 70
Hoppe Avatar answered Oct 07 '22 05:10

Hoppe


I recently had the same problem. I figured out that VS 2019 doesn't like it to have projects grouped in an project folder (virtual folder) which is named the same way as the project is. Or where the "virtual" folder name has the same name as an actual project

Example:

(virtual) project folder name: CompanyName.Webservice Content: CompanyName.Webservice (from CompanyName.Webservice.csproj)

In that case I couldn't neither add or rename project configurations nor execute transformation of web.config files of that project

Hope that helps someone after so many years...

like image 22
Gerrit Horeis Avatar answered Oct 07 '22 05:10

Gerrit Horeis