Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Saving Visual Studio's Configuration Manager Settings Locally

would like to add my own configuration settings in Visual Studio 2010. I opened the configuration manager, created the profile I wanted and noticed that the settings are stored in the .csproj file. I would like to keep these settings local to my own box. Our source control currently checks in .csproj files and so if I checked these changes in, my entire team would be affected. Does anyone know if it's possible to create configuration settings that are local to your own dev box?

Edit: Adding a screenshot of the configuration manager. It's these settings I want to save locally.

Configuration Manager

like image 868
Halcyon Avatar asked Apr 12 '12 16:04

Halcyon


People also ask

Where are Visual Studio settings stored?

settings is located in the My Project folder for Visual Basic projects and in the Properties folder for Visual C# projects. The Project Designer then searches for other settings files in the project's root folder.

Where are solution configurations stored?

This is stored in the user's . suo file, next to the . sln (solution) file.

How do I access the Configuration Manager in Visual Studio?

The project configuration determines what build settings and compiler options are used when you build the project. To create, select, modify, or delete a configuration, you can use the Configuration Manager. To open it, on the menu bar, choose Build > Configuration Manager, or just type Configuration in the search box.

How do I add active solution configuration in Visual Studio?

Open the Configuration Manager dialog box. In the Active solution configuration drop-down list, choose Edit. The Edit Solution Configurations dialog box opens. Select the solution configuration name you want to change.


2 Answers

Why not just save all this to a diffrenet solution file and use it, while others will use old one?

like image 165
cookieMonster Avatar answered Oct 06 '22 05:10

cookieMonster


You've got a csproj file and a csproj.user file.

Visual Studio places settings in the user file that can be different per user without affecting the entire team's development (like whether the Show All Files button is clicked). You wouldn't check this file in, and deleting it might be an inconvenience but it won't affect the program.

Visual Studio places settings in the csproj file itself that will affect your team's development (such as which classes are part of the project, references to DLLs, and the targeted framework version). You have to check this file in when changes are made, and deleting it would definitely affect your program.

This is based on my own understanding and experience. Maybe if you list which settings you'd like kept out of the csproj file, someone else on here will be able to list a workaround...

like image 33
Grant Winney Avatar answered Oct 06 '22 05:10

Grant Winney