Comments for This blog has moved to www.freetodev.com

Comment on Versioning Code in TFS – Revised by You’re doing it wrong!!! Well some of it at least… | Well Technically... | ongoing adventures in nerdiness

Sat, 10 Mar 2012 13:07:09 +0000

[...] points are re-iterated in Versioning Code in TFS – Revised along with several solutions including the two detailed above. Moving to TFSVersion to update the [...]

Comment on MSBuild 4.0 BeforeTargets and AfterTargets by Doug Clutter

Doug Clutter — Mon, 27 Feb 2012 17:37:55 +0000

Just tested it…AfterTargets does NOT get called if there is an error in your Target. Bummer.

Comment on MSBuild 4.0 BeforeTargets and AfterTargets by Doug Clutter

Doug Clutter — Mon, 27 Feb 2012 17:26:50 +0000

How do AfterTargets behave if there is an error in a target? Does it still get called?

Comment on Debugging Outlook 2010 Add-ins with Visual Studio 2010 by Travis

Travis — Wed, 15 Feb 2012 18:41:10 +0000

Thank you for posting this. I’ve was seeing the same behavior — it was driving me nuts,.

Comment on MSBuild 4.0 BeforeTargets and AfterTargets by Arun

Arun — Tue, 31 Jan 2012 21:44:19 +0000

The BeforeTargets does have sense in the following situation:
(1) there are 2 projects, part of the build on them overlap – that is there are targets that both projects would use – essentially this results in creation of a third file for common targets in two
(2) in one project you need to perform an action Before executing a target; at the same time, you do not want that to be coded into the other project or (obviously) in the common targets file
(3) you would create a Before target in the project where you want the change to happen

This case is very much present when I had to make a change to the common “Microsoft.common.Targets” include.

Comment on Debugging Outlook 2010 Add-ins with Visual Studio 2010 by Sander van Haaff

Sander van Haaff — Fri, 07 Oct 2011 13:28:58 +0000

wow, had the same problem, googled “outlook debug visual studio”, your blog came first up and it indeed solved my problem. First time I “could” have hit the google ‘I feel lukcy’ button… (but off course didnot)

Thanx!

Sander

Comment on Versioning Code in TFS – Revised by Hugo Häggmark » Stuck on “Cannot create unknown type {clr-namespace:” in TFS Build?

Thu, 08 Sep 2011 13:52:46 +0000

[...] I took a moment of thought to see what I could do to improve this MSBuild task. I read this great post by Mike Fourie’s and yet another great post by John Robbins that I really encourage anyone [...]

Comment on Versioning Code in TFS – Revised by Ivan Pavlović

Ivan Pavlović — Mon, 18 Apr 2011 09:43:20 +0000

I want to use something like 1.2.123.1 as build number, label for source code and as a part of installer filename (final result of build process). What do you think, is it ok to use output of GetVersion to change the $(BuildNumber) in that particular case?

Comment on Versioning Code in TFS – Part 2 by Uldis Karlovs-Karlovskis

Uldis Karlovs-Karlovskis — Thu, 10 Mar 2011 10:37:12 +0000

Since I`m to lazy to write special MSBuild task this fitted my needs. Thank you!

However, having DateTime as version indicator in Enterprise is totally unacceptable and now I need to develop my own versioning policy which is not supported by TFS 2008. I hope things in TFS 2010 are a bit better.

Comment on Display Custom Build Steps in the Team Build IDE by Uldis Karlovs-Karlovskis

Uldis Karlovs-Karlovskis — Tue, 08 Mar 2011 09:34:20 +0000

Hi,

after 4 years I need this feature again
Seems assembly works only on TFS 2005. Got the same exception as user “unknown”. Mike, can you send me those sources again so I`ll can recompile them for TFS 2008?