Content Preview: rss
5 days ago
Sayed Ibrahim Hashimi covers some tasks in the MSBuild Extension Pack in this dnrTV show. Watch now
15 days ago
I work a lot with MSBuild files, mostly to automate numerous processes in the development lifecycle. I wrote a tool to help me work with MSBuild and today I’ve uploaded it to the web in the hope that it will make the lives of those who use MSBuild every day a little bit easier. The tool is called MSBuild Explorer and it provides the following features: Explore the makeup of your MSBuild files. Save Favourites to quickly execute your pre-configured MSBuild Scripts. Quickly run a snippet of MSBuild. Quickly create a new MSBuild file. The quickest way to see what the tool really does is to spend a minute or two reading the Example Usage Walkthrough . You can download Version 1 of MSBuild Explorer here. You will need .Net 3.5. Version 2 will Require .Net 4.0 and will be available in H1 2010. Mike
16 days ago
For those using TFS 2010, take a read of John Robbins new post TFS 2010 Build Number and Assembly File Versions: Completely In Sync with Only MSBuild 4.0
18 days ago
This is a revised and combined post covering the two previous posts, Versioning Code in TFS Part 1 & Part 2. If you haven’t read those two posts, then this revised post is all you need to read. If you have read the two previous posts, then although similar, I recommend you read this revised post as it contains important corrections, updates and clarifications. Note that this post mostly relates to TFS 2008, though the concepts implied are not tied to a specific version of TFS. ____________________________________________________________________________________ The Problem I’ve lost count of the number of blog posts, forum questions and internal emails that I have seen regarding problems with versioning assemblies in TFS. I believe the root cause of the problem is that many users have tried to migrate their existing versioning logic and code to work with TFS, blinded by the wealth of functionality that TFS has brought to the development process. The Truth ...
22 days ago
Moving to VS2010 felt like a step backwards in some respects as it doesn’t implement many of the great productivity enhancements that the Power Commands for Visual Studio 2008 offered. The good news is that the PowerCommands for Visual Studio 2010 are are now available here. One thing to note is that after installing the Visual Studio extension, you will probably need to enable it for administrators. To do this, Go to Tools > Options > Environment - Extension Manager and check ‘Load per user extensions when running as administrator.’ Restart Visual Studio Be sure to check out the Gallery for other useful extensions:
