![]() ![]() I’ve put everything I discuss into a sample project that shows how to set this up for both C#/VB projects as well as for native C++ projects. įor the rest of this article, I’m assuming you’ve read my original blog entry on. That and they wanted documentation on how I got it working. The client was kind enough to let me blog this so everyone could benefit. ![]() They asked me to get my pure MSBuild approach working inside Visual Studio projects so they could get the benefit of the build numbers, but not change how anyone builds the code on their development box. Additionally, there was good security and process on TFS build servers so adding the custom workflow activity was going to take a while to get installed. Working with a client, they like my approach, but didn’t care for the fact you had to initially create the assembly version files with a command line build. ![]() While you can use Jim Lamb’s excellent custom workflow activity, I liked doing the version numbers with MSBuild because you could have the same build for both the build server as well as the developer desktop. A while ago, I showed using MSBuild 4.0 to create build version files with the TFS build number so that build number could be included in your binaries. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |