On our current project we are using MSBuild to build our application. This is my first time using MSBuild other than just tinkering and I have found it.... challenging to say the least. A lot of my challenges are lack of knowledge but the other half is the language itself. The most recent challenge I wanted to write about was calling a target multiple times. Our scenario is this: We have to generate a batch file for each environment we are going to install in with environment specific settings. The issue I had was that for each environment we had that...

One common issue of team development is sharing configuration files. If a developer is testing something out and changes a value and then accidentally checks that file in it affects all developers. There are a few approaches to solving this issue: 1) Be very careful and disciplined. +Simple -SImple to forget 2) Have a web.config.template under source control that developers copy to web.config and not include in source control. +Prevents checkins of web.config files that affect other people -Developers need to manually update their config files if a new value is added/removed/or the default updated 3) Have a build script task to generate a config file...