CODEWITHSUNDEEP
visual-studiovisual-studio-2013msbuildbuildconfigurationprojects-and-solutions
Hoppe
Hoppe

Reputation: 6805

Possible to store build configuration in a file other than solution file?

I work with a solution that has a lot of projects in it. I created a new build configuration to speed up working with it.

To speed up compiling, I set most of the projects not to build in my new build configuration. To speed up debugging, I set most of the projects to build for release in my new build configuration.

This is great, until I have to check in a change to the project file, or get the latest from someone else's changes to the project file. It is painful to merge the changes, or shelve and unshelve them constantly.

Is it possible to store my build configuration in a separate file? Ideas for workarounds welcome.

Upvotes: 0

Views: 609

Answers (1)

stijn
stijn

Reputation: 35901

To answer the question directly: no you cannot store your config in a seperate file. Unless that seperate files is also a solution file of course. But there are some workarounds, all stored locally on your machine (too long for a comment so I'm posting an answer anyway):

I set most of the projects not to build in my new build configuration

  • just build them once, then unload the projects so they will not be built again. These settings are stored in the .suo file.
  • if you insist on keeping a seperate build configuration: ask the team if it's ok to push it into the source control, maybe others can benefit from it as well?
  • or write a script to transfrom the original solution file into one having our build config. That can be as simple as applying a patch, which you should keep up-to-date

To speed up debugging, I set most of the projects to build for release

  • write a script to delete the pdb files of those projects
  • for C++: add all namespaces of those projects to the natstepfilter file

Upvotes: 2

Related Questions