<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx</link><description>Issue : - 
 I would like to invoke a specific target just after each solution is compiled. Unfortunately, team build performs a build including all solution in an atomic MSBuild call. I don’t want to make changes in my sln or csproj files but I am OK</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title> Manish Agarwal How to call a custom target after building each | Weak Bladder</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#9705771</link><pubDate>Mon, 08 Jun 2009 04:40:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9705771</guid><dc:creator> Manish Agarwal How to call a custom target after building each | Weak Bladder</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://weakbladder.info/story.php?id=5108"&gt;http://weakbladder.info/story.php?id=5108&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9705771" width="1" height="1"&gt;</description></item><item><title>Don't override CoreCompile</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#694949</link><pubDate>Fri, 11 Aug 2006 04:52:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:694949</guid><dc:creator>Buck Hodges</dc:creator><description>There have been several times when folks have needed to run a custom target prior to building each solution...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=694949" width="1" height="1"&gt;</description></item><item><title>re: How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#694938</link><pubDate>Fri, 11 Aug 2006 04:31:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:694938</guid><dc:creator>Buck Hodges</dc:creator><description>For those who try this, note that you'll need to copy the TeamBuildMessage task invocations as well, otherwise the logger will crash (Steve points this out in his blog post &lt;a rel="nofollow" target="_new" href="http://sstjean.blogspot.com/2006/06/tfs-team-build-problems-with-calling.html"&gt;http://sstjean.blogspot.com/2006/06/tfs-team-build-problems-with-calling.html&lt;/a&gt;). &amp;nbsp;The v1 logger depends on those messages to determine what's being built.&lt;br&gt;&lt;br&gt;Regardless, it's not a good idea to override any of the Core* targets, especially CoreCompile, as they will definitely be changing in future releases.&lt;br&gt;&lt;br&gt;Buck&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=694938" width="1" height="1"&gt;</description></item><item><title>re: How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#621319</link><pubDate>Thu, 08 Jun 2006 02:36:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:621319</guid><dc:creator>Steven St Jean</dc:creator><description>Your override of the CoreCompile target does fewer tasks than the original version in Microsoft.TeamFoundation.Build.targets. &amp;nbsp;Do you believe that this will materially change the behavior of the overridden build vs. the behavior of the original?&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=621319" width="1" height="1"&gt;</description></item><item><title>re: How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#621316</link><pubDate>Thu, 08 Jun 2006 02:32:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:621316</guid><dc:creator>Steven St Jean</dc:creator><description>At the end of your article, you mention that the logger will crash under certain circumstances. &amp;nbsp;Can you elaborate further on why this occurs? &amp;nbsp;I am using your pattern to perform code generation prior to compilation and it looks like the logger is crashing during the run. &amp;nbsp;My build is failing and I have a truncated build log.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=621316" width="1" height="1"&gt;</description></item><item><title>re: How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#601980</link><pubDate>Fri, 19 May 2006 20:07:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:601980</guid><dc:creator>Jan Bergstrom</dc:creator><description>I think I have answered my own question:&lt;br&gt;&lt;br&gt;When calling the target for MSBuild to do the CoreCompile, pass the original $(SolutionRoot) with &lt;br&gt;&lt;br&gt;Properties=&amp;quot;SolutionRoot=$(SolutionRoot)&amp;quot;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=601980" width="1" height="1"&gt;</description></item><item><title>re: How to call a custom target after building each individual solution (sln) in Team Build?</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#598318</link><pubDate>Mon, 15 May 2006 23:58:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:598318</guid><dc:creator>Jan Bergstrom</dc:creator><description>I have tried to do something like this on the main Microsoft.TeamFoundation.Build.targets file on CoreCompile. &amp;nbsp;I would like to insert a target that is executed for each configuration immediately before that configuration.&lt;br&gt;&lt;br&gt;If I use $(SolutionRoot)\TeamBuildTypes\$(BuildType)\tfsbuild.proj as the reference for the recursive call to the project file, it can't find my solutions (because it now searches relative to this file rather than relative to $(SolutionRoot)\..\BuildType\tfsbuild.proj. &amp;nbsp;If I use $(SolutionRoot)\..\BuildType\tfsbuild.proj, the build crashes on the server claiming that it can't find the working directory.&lt;br&gt;&lt;br&gt;How do I insert a target into the CoreBuild step that is executed once for each configuration, and not mess up all the other stuff that the Microsoft.TeamFoundation.Build.targets CoreBuild is doing?&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=598318" width="1" height="1"&gt;</description></item><item><title>VSTS Links - 05/10/2006</title><link>http://blogs.msdn.com/b/manishagarwal/archive/2006/05/09/593510.aspx#594530</link><pubDate>Wed, 10 May 2006 16:51:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:594530</guid><dc:creator>Team System News</dc:creator><description>Manish Agarwal tells us how to call a custom target after building each individual solution in Team Build....&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=594530" width="1" height="1"&gt;</description></item></channel></rss>