MSBuild Property Evaluation

re: MSBuild Property Evaluation

hass0002 — Tue, 17 Jul 2007 05:58:04 GMT

Hi,

I've created some related blog entries they may be helpful.

MSBuild CreateProperty bug workaround (http://www.sedodream.com/PermaLink,guid,44ef8e1e-735f-40c5-92e9-4d7e31590c5d.aspx)

MSBuild Property & Item Overide Problems (http://www.sedodream.com/PermaLink,guid,95544bf1-f5b9-48c4-994b-8581389c4996.aspx)

Sayed Ibrahim Hashimi

VSTS Links - 07/18/2007

Team System News — Wed, 18 Jul 2007 17:39:16 GMT

Dave McKinstry on (Launch != Release). Eugene Zakhareyev on .NET Update gets in the way of TFS. Martin...

Orcas SP1 TFS Build Changes, Part 2

Aaron Hallberg — Mon, 12 May 2008 16:18:22 GMT

As promised, here are some more details on other SP1 changes for TFS Build.  3. Detect test results.

Blogging again????

Clark Sell — Fri, 22 May 2009 17:02:13 GMT

You know sometimes it’s just sad how fast time can go by.  Looking back it’s been well over a year

re: MSBuild Property Evaluation

DarinHIggins — Fri, 24 Jul 2009 00:17:17 GMT

Great article, but i was wondering if you've noticed a peculiar behavior that I'm seeing with MSBuild for 3.5

Essentially, if I use a PROPERTYGROUP +within+ a target, then use CALLTARGET to call another target, the properties set within that group aren't visible in conditions on the called target.

However, if I so those SAME properties, within a propertygroup in a seperate target and refer to it via the DEPENDSONTARGETS attr, then those properties ARE visible in conditions on a called target.

Very strange and would appear to be a bug. I can't imagine that that is intended behavior.