Where is configuration manager in visual studio

Imagine you are developing a Visual Studio extension which requires you to prompt users to modify their project build configurations. The ideal way to do that is to open default configuration manager window of Visual Studio and let users configure. The method has no parameters and it is as easy as calling a MessageBox. Show in windows forms. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Configuration Assembly: System. Provides access to configuration files for client applications. This class cannot be inherited. Note The name and location of the application configuration file depend on the application's host. Is this page helpful? Yes No. Any additional feedback? Skip Submit. GetSection String.

Retrieves a specified configuration section for the current application's default configuration. OpenExeConfiguration String. RefreshSection String. The active solution configuration also provides context to the IDE. For example, if you're working on a project and the configuration specifies that it will be built for a mobile device, the Toolbox displays only items that can be used in a mobile device project. The configuration and platform that a project targets are used together to specify the build settings and compiler options to use when it's built.

A project can have different settings for each combination of configuration and platform. To modify the properties of a project, open the shortcut menu for the project in Solution Explorer , and then choose Properties. At the top of the Build tab of the project designer, choose an active configuration to edit its build settings. All projects that are specified in that solution configuration are built, and the only project configuration that's built is that one specified in the active solution configuration and active solution platform, which is shown in the toolbar in Visual Studio.

For example, Debug and x Other defined configurations and platforms are not built. Batch build is not available for all project types. See How to: Build multiple configurations simultaneously.

When you define a new solution configuration and don't copy settings from an existing one, Visual Studio uses the following criteria to assign default project configurations. The criteria are evaluated in the order shown. Configuration names are not case-sensitive. If the project has a configuration name in which the configuration-name part matches the new solution configuration, that configuration is assigned, whether the platform portion matches or not.

Hello Thanks Parjwal, the solution works for me. But if I want to update the build version. Thank you for the response, Prajwal. I tried that, but the updates never completed. My guess is because the clients do not report as needing the updates. I know this is not reality, because I have about 14 computers all in need of VS updates. Do you know if a reason why the clients would be reporting to the server that there are 0 required?

By the way, I have been following this blog for a long time and used it countless times to help me with various SCCM challenges over the years. Thank you. I have been trying to deploy these updates without an ADR. The problem is, I think, that it appears that all of my clients which have VS installed show as 0 required. Di you know why my clients would report that the update is not required? You might need to wait until the updates are ready. Initially it may show updates not required but later the updates will be applied.

I think there are multiple things going on here. First, you probably need to create a configuration baseline to detect if Visual Studio is installed or not. Then, use the link that David provided to set the opt in parameter. If this is not set, you will not get updates. This is something I am working on with the Visual Studio team at Microsoft. It makes sense from a programming perspective not to get updates automatically, but from an Admins perspective it just causes more work.