Visual Studio Configuration Properties [closed]

Closed. This question is off-topic. It is not currently accepting answers.

---

开发者_StackOverflow社区

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 11 years ago.

Improve this question

Why are certain properties not dependent on the current configuration?

For example, why can't I specify a different startup project based on the current configuration?

---

Configuration is meant to be all about how your project is built: x86 or amd64, ret or debug, etc ... The Visual Studio UI is geared around this experience and hence only presents the ability to configure build related tasks.

This is not to say that actions like StartAction can't be tied to configuration: they actually can. The project file format, at least for C#, VB.Net and F#, is just an MSBuild file. You can hand edit it to bind certain items to configuration properties

For example:

<StartProgram Condition="$(pick your msbuild prop)">Some\Path\app.exe</StartProgram>

---

While this may make sense to YOUR specific needs, the actual build configurations are tied to different Project based values (Debug flags, output folder, Target platform, etc).

The Startup Project is defined per Solution, so this makes sense to me that it is not tied to any specific build configuration.

Raise this on Microsoft Connect. While it is not assured that your issue will be solved, they are very responsive and willing to assist very quickly.