<?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>Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx</link><description>Setup projects (.vdproj) do not have a project system format that can be understood by MSBuild. Hence MSBuild cannot build these projects directly and consequently neither can Team Build. What we can do however is use the devenv /build command to build</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Building MSIs on the TFS Build Server</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#540959</link><pubDate>Wed, 01 Mar 2006 04:23:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:540959</guid><dc:creator>Eric Matz</dc:creator><description /></item><item><title>VSTS Links - 03/01/2006</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#541332</link><pubDate>Wed, 01 Mar 2006 19:24:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:541332</guid><dc:creator>Team System News</dc:creator><description>Rob Caron points us to a process guidance print tool. He also talks about TDD in Agitator and Team System....</description></item><item><title>How to Have Team Foundation Server Build and Deploy Setup Projects</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#602119</link><pubDate>Fri, 19 May 2006 23:32:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:602119</guid><dc:creator>Technical Weblog of Eric Charran</dc:creator><description>&lt;br&gt;This article describes how to have &lt;br&gt;TFS's build functionality accomodate and build setup and deploy...</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#602141</link><pubDate>Fri, 19 May 2006 23:57:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:602141</guid><dc:creator>WixFan</dc:creator><description>Better even, just use Wix (&lt;a rel="nofollow" target="_new" href="http://wix.sourceforge.net"&gt;http://wix.sourceforge.net&lt;/a&gt;) that has native support for MSBuild ;).</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#739225</link><pubDate>Mon, 04 Sep 2006 13:18:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:739225</guid><dc:creator>C.Anbarasu</dc:creator><description>Hi ,
When using BuildTypes ,I am not getting the DeploymentPackage (.msi)file in Release mode,instead it is always creating the deployment package in Debug mode .

The following content is my TFSBuild.proj 

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;Project DefaultTargets="DesktopBuild" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt;
&lt;!-- TO EDIT BUILD TYPE DEFINITION

  To edit the build type, you will need to edit this file which was generated
  by the Create New Build Type wizard.  This file is under source control and
  needs to be checked out before making any changes.

  The file is available at -
      $/{TeamProjectName}/TeamBuildTypes/{BuildTypeName}
  where you will need to replace TeamProjectName and BuildTypeName with your
  Team Project and Build Type name that you created

  Checkout the file
    1. Open Source Control Explorer by selecting View -&gt; Other Windows -&gt; Source Control Explorer
    2. Ensure that your current workspace has a mapping for the $/{TeamProjectName}/TeamBuildTypes folder and 
       that you have done a "Get Latest Version" on that folder
    3. Browse through the folders to {TeamProjectName}-&gt;TeamBuildTypes-&gt;{BuildTypeName} folder
    4. From the list of files available in this folder, right click on TfsBuild.Proj. Select 'Check Out For Edit...'


  Make the required changes to the file and save

  Checkin the file
    1. Right click on the TfsBuild.Proj file selected in Step 3 above and select 'Checkin Pending Changes'
    2. Use the pending checkin dialog to save your changes to the source control

  Once the file is checked in with the modifications, all future builds using
  this build type will use the modified settings
  --&gt;
  &lt;!-- Do not edit this --&gt;
  &lt;Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets" /&gt;
  &lt;ProjectExtensions&gt;
    &lt;!--  DESCRIPTION
     The description is associated with a build type. Edit the value for making changes.
    --&gt;
    &lt;Description&gt;test build&lt;/Description&gt;
    &lt;!--  BUILD MACHINE
     Name of the machine which will be used to build the solutions selected.
    --&gt;
    &lt;BuildMachine&gt;tmserver&lt;/BuildMachine&gt;
  &lt;/ProjectExtensions&gt;
  &lt;PropertyGroup&gt;
    &lt;!--  TEAM PROJECT
     The team project which will be built using this build type.
    --&gt;
    &lt;TeamProject&gt;Test&lt;/TeamProject&gt;
    &lt;!--  BUILD DIRECTORY
     The directory on the build machine that will be used to build the
     selected solutions. The directory must be a local path on the build
     machine (e.g. c:\build).
    --&gt;
    &lt;BuildDirectoryPath&gt;D:\BuildSample&lt;/BuildDirectoryPath&gt;
    &lt;!--  DROP LOCATION
      The location to drop (copy) the built binaries and the log files after
     the build is complete. This location has to be a valid UNC path of the
     form \\Server\Share. The build machine service account and application
     tier account need to have read write permission on this share.
    --&gt;
    &lt;DropLocation&gt;\\prog_126\Build&lt;/DropLocation&gt;
    &lt;!--  TESTING
     Set this flag to enable/disable running tests as a post build step.
    --&gt;
    &lt;RunTest&gt;false&lt;/RunTest&gt;
    &lt;!--  WorkItemFieldValues
      Add/edit key value pairs to set values for fields in the work item created
      during the build process. Please make sure the field names are valid 
      for the work item type being used.
    --&gt;
    &lt;WorkItemFieldValues&gt;Symptom=build break;Steps To Reproduce=Start the build using Team Build&lt;/WorkItemFieldValues&gt;
    &lt;!--  CODE ANALYSIS
       To change CodeAnalysis behavior edit this value. Valid values for this
       can be Default,Always or Never.

     Default - To perform code analysis as per the individual project settings
     Always  - To always perform code analysis irrespective of project settings
     Never   - To never perform code analysis irrespective of project settings
     --&gt;
    &lt;RunCodeAnalysis&gt;Never&lt;/RunCodeAnalysis&gt;
    &lt;!--  UPDATE ASSOCIATED WORK ITEMS
     Set this flag to enable/disable updating associated workitems on a successful build
    --&gt;
    &lt;UpdateAssociatedWorkItems&gt;true&lt;/UpdateAssociatedWorkItems&gt;
    &lt;!-- Title for the work item created on build failure --&gt;
    &lt;WorkItemTitle&gt;Build failure in build:&lt;/WorkItemTitle&gt;
    &lt;!-- Description for the work item created on build failure --&gt;
    &lt;DescriptionText&gt;This work item was created by Team Build on a build failure.&lt;/DescriptionText&gt;
    &lt;!-- Text pointing to log file location on build failure --&gt;
    &lt;BuildlogText&gt;The build log file is at:&lt;/BuildlogText&gt;
    &lt;!-- Text pointing to error/warnings file location on build failure --&gt;
    &lt;ErrorWarningLogText&gt;The errors/warnings log file is at:&lt;/ErrorWarningLogText&gt;
  &lt;/PropertyGroup&gt;
  &lt;ItemGroup&gt;
    &lt;!--  SOLUTIONS
     The path of the solutions to build. To add/delete solutions, edit this
     value. For example, to add a solution MySolution.sln, add following line -
         &lt;SolutionToBuild Include="$(SolutionRoot)\path\MySolution.sln" /&gt;

     To change the order in which the solutions are build, modify the order in
     which the solutions appear below.
    --&gt;
	  
    &lt;SolutionToBuild Include="$(SolutionRoot)\TT1\SRB.TT1.sln" /&gt;
  &lt;/ItemGroup&gt;
  &lt;ItemGroup&gt;
    &lt;!--  CONFIGURATIONS
     The list of configurations to build. To add/delete configurations, edit
     this value. For example, to add a new configuration, add following lines -
         &lt;ConfigurationToBuild Include="Debug|x86"&gt;
             &lt;FlavorToBuild&gt;Debug&lt;/FlavorToBuild&gt;
             &lt;PlatformToBuild&gt;x86&lt;/PlatformToBuild&gt;
         &lt;/ConfigurationToBuild&gt;

     The Include attribute value should be unique for each ConfigurationToBuild node.
    --&gt;
    &lt;ConfigurationToBuild Include="Release|Any CPU"&gt;
      &lt;FlavorToBuild&gt;Release&lt;/FlavorToBuild&gt;
      &lt;PlatformToBuild&gt;Any CPU&lt;/PlatformToBuild&gt;
	
    &lt;/ConfigurationToBuild&gt;
  &lt;/ItemGroup&gt;
  &lt;ItemGroup&gt;
    &lt;!--  TEST ARGUMENTS
     If the RunTest is set to true then the following test arguments will be
     used to run tests.

     To add/delete new testlist or to choose a metadata file (.vsmdi) file, edit this value.
     For e.g. to run BVT1 and BVT2 type tests mentioned in the Helloworld.vsmdi file, add the following -

     &lt;MetaDataFile Include="$(SolutionRoot)\HelloWorld\HelloWorld.vsmdi"&gt;
         &lt;TestList&gt;BVT1;BVT2&lt;/TestList&gt;
     &lt;/MetaDataFile&gt;

     Where BVT1 and BVT2 are valid test types defined in the HelloWorld.vsmdi file.
     MetaDataFile - Full path to test metadata file.
     TestList - The test list in the selected metadata file to run.

     Please note that you need to specify the vsmdi file relative to $(SolutionRoot)
    --&gt;
    &lt;MetaDataFile Include=" "&gt;
      &lt;TestList&gt; &lt;/TestList&gt;
    &lt;/MetaDataFile&gt;
  &lt;/ItemGroup&gt;
  &lt;ItemGroup&gt;
    &lt;!--  ADDITIONAL REFERENCE PATH
     The list of additional reference paths to use while resolving references.
     For example,
         &lt;AdditionalReferencePath Include="C:\MyFolder\" /&gt;
         &lt;AdditionalReferencePath Include="C:\MyFolder2\" /&gt;
    --&gt;
  &lt;/ItemGroup&gt;

    &lt;Target Name="AfterCompile"&gt;
		
		&lt;Exec  Command='"C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.com" "$(SolutionRoot)\TT1\WebSetup\WebSetup.vdproj" /ReBuild /ProjectConfig ' /&gt;
		&lt;Copy SourceFiles="$(SolutionRoot)\TT1\WebSetup\Release\WebSetup.msi" DestinationFolder="$(DropLocation)\$(BuildNumber)\" /&gt;
		
    &lt;/Target&gt;
&lt;/Project&gt;

My objective is ,After building this build type ,i have to get the deployment package in Release mode 

Help me out with this issue
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#1439280</link><pubDate>Tue, 09 Jan 2007 16:58:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1439280</guid><dc:creator>FreeToDev</dc:creator><description>&lt;p&gt;You could also use the DevEnv build task to simplify it. You will still need VS installed.&lt;/p&gt;
&lt;p&gt;Tasks: &lt;a rel="nofollow" target="_new" href="http://www.gotdotnet.com/codegallery/codegallery.aspx?id=b4d6499f-0020-4771-a305-c156498db75e"&gt;http://www.gotdotnet.com/codegallery/codegallery.aspx?id=b4d6499f-0020-4771-a305-c156498db75e&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Sample:&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;&amp;lt;Tools.DevEnv VisualStudio=&amp;quot;8.0&amp;quot; Path=&amp;quot;MySetup.vdproj&amp;quot; Config=&amp;quot;Release&amp;quot; OutputFolder=&amp;quot;$(SolutionRoot)\..\BuildType&amp;quot; Clean=&amp;quot;true&amp;quot;/&amp;gt;&lt;/p&gt;
&lt;p&gt;Regards... FreeToDev&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#1914351</link><pubDate>Mon, 19 Mar 2007 22:58:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1914351</guid><dc:creator>TonyL</dc:creator><description>&lt;p&gt;Does this still work with the released bits? When I gave it a try the build service never returned so the build went on forever. I had to kill it via task manager and restart the build service.&lt;/p&gt;</description></item><item><title>re: Building setup projects without Team Build on the .Net 2.0</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#2988987</link><pubDate>Wed, 30 May 2007 17:31:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2988987</guid><dc:creator>Alex</dc:creator><description>&lt;P&gt;I whant to automate the proceses in our teem. But I can't build the msi project neither with msbuild.exe nor Nant nor through the command prompt. Even devenv.exe cann't build *.vdproj through the command prompt. I will aprisiate very much if &amp;nbsp;anutthara tell me how to do any of these steps correctly.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#3413579</link><pubDate>Wed, 20 Jun 2007 01:44:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3413579</guid><dc:creator>Jereme Watts</dc:creator><description>&lt;p&gt;Thanks for the tips it got my build server running. I forgot the whole installation permissions thing, I assumed that the configuration of the build server would have given the appropriate permissions to the TFS Service Account.&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#3593064</link><pubDate>Fri, 29 Jun 2007 01:15:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3593064</guid><dc:creator>Joey</dc:creator><description>&lt;p&gt;Alex, you should be able to build a .vdproj through the command line. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Instead of specifying the .vdproj file, I used the .sln and it seems to be working well for me.&lt;/p&gt;
&lt;p&gt;Good Luck,&lt;/p&gt;
&lt;p&gt; Joey&lt;/p&gt;</description></item><item><title>Team Build DevEnv Task</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#3836352</link><pubDate>Thu, 12 Jul 2007 23:35:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3836352</guid><dc:creator>Aaron Hallberg</dc:creator><description>&lt;p&gt;Because many Visual Studio project types are not supported in MSBuild, many Team Build users end up needing&lt;/p&gt;
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#4485763</link><pubDate>Tue, 21 Aug 2007 02:18:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4485763</guid><dc:creator>Jignesh Vyas</dc:creator><description>&lt;P&gt;I am able to build and install succesfully by following above mentioned step.&lt;/P&gt;
&lt;P&gt;Issue arises in scenario where i run the build for the second time. Since it has already installed the application during first build. It cannot install again. It runs in silence mode, actually its waiting for user intervention whether to reinstall or repair the application. Due this build process runs infinetly without ending.&lt;/P&gt;
&lt;P&gt;Any help on this scenario is appreciated.&lt;/P&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#4506124</link><pubDate>Wed, 22 Aug 2007 10:12:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4506124</guid><dc:creator>anutthara</dc:creator><description>&lt;p&gt;Hi Jignesh- You should probably include a task to uninstall the build in your tfsbuild proj file after tests are executed. HTH.&lt;/p&gt;
&lt;p&gt;Also, I am on a different team now and dont have the full context on the current scene on setup proj scenario with Team Build. :( &lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/buckh"&gt;http://blogs.msdn.com/buckh&lt;/a&gt; should be the best place to ask setup proj or Team Build related qs&lt;/p&gt;
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#4518231</link><pubDate>Thu, 23 Aug 2007 04:27:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4518231</guid><dc:creator>buckh</dc:creator><description>&lt;p&gt;Jignesh, if you are installing the application you would need to uninstall the application before installing it again. &amp;nbsp;The Build forum on MSDN is a good place to ask questions: &lt;a rel="nofollow" target="_new" href="http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=481&amp;amp;SiteID=1"&gt;http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=481&amp;amp;SiteID=1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Buck&lt;/p&gt;
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#5779277</link><pubDate>Tue, 30 Oct 2007 14:14:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5779277</guid><dc:creator>Shefeek Rahman</dc:creator><description>&lt;p&gt;The article is good... But I tried the thing suggested by you in my TFS build script. But Unfortunately it's keep on going...&lt;/p&gt;
&lt;p&gt;what went wrong here.Any idea?&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#6887913</link><pubDate>Fri, 28 Dec 2007 22:31:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6887913</guid><dc:creator>mehek</dc:creator><description>&lt;p&gt;hi,&lt;/p&gt;
&lt;p&gt;i have two configuration set up.&lt;/p&gt;
&lt;p&gt; &amp;lt;ConfigurationToBuild Include=&amp;quot;Development|Mixed Platforms&amp;quot;&amp;gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;lt;FlavorToBuild&amp;gt;Development&amp;lt;/FlavorToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;lt;PlatformToBuild&amp;gt;Mixed Platforms&amp;lt;/PlatformToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;&amp;lt;/ConfigurationToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt;	 &amp;nbsp;&amp;lt;ConfigurationToBuild Include=&amp;quot;Testing|Mixed Platforms&amp;quot;&amp;gt;&lt;/p&gt;
&lt;p&gt;		 &amp;nbsp;&amp;lt;FlavorToBuild&amp;gt;Testing&amp;lt;/FlavorToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt;		 &amp;nbsp;&amp;lt;PlatformToBuild&amp;gt;Mixed Platforms&amp;lt;/PlatformToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt;	 &amp;nbsp;&amp;lt;/ConfigurationToBuild&amp;gt;&lt;/p&gt;
&lt;p&gt; &amp;nbsp;&amp;lt;/ItemGroup&amp;gt;&lt;/p&gt;
&lt;p&gt;i can run one environment at one time .&lt;/p&gt;
&lt;p&gt;Can you help me how we can run both(development&amp;amp;testing) at one time.&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#7642901</link><pubDate>Tue, 12 Feb 2008 16:47:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7642901</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;For Shefeek:&lt;/p&gt;
&lt;p&gt;I presume the name of your TFS build and/or project path contains spaces.&lt;/p&gt;
&lt;p&gt;it is easy to work this around by adding a second quote after devenv and another one before the /build.&lt;/p&gt;
&lt;p&gt;This should do the trick&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8335988</link><pubDate>Tue, 25 Mar 2008 18:48:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8335988</guid><dc:creator>Mamatha</dc:creator><description>&lt;p&gt;How can I build a solution that has&lt;/p&gt;
&lt;p&gt;-asp.net webservice&lt;/p&gt;
&lt;p&gt;-VC++ DLL&lt;/p&gt;
&lt;p&gt;-C# DLL&lt;/p&gt;
&lt;p&gt;-setup project&lt;/p&gt;
&lt;p&gt;from Team build, using devenv command line for the vdproj file. I get &amp;quot;Unable to find dependencies error&amp;quot;. also in which flavor should I build - Release/Debug?&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8394166</link><pubDate>Mon, 14 Apr 2008 22:27:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8394166</guid><dc:creator>Tommy Norman</dc:creator><description>&lt;p&gt;I have been trying different flavors of this fix and still do not have it working. After several issues surrounding the fact we code with VSTS2008 but build on TFS2005 I finnaly got the build to run without an error, however the command line building the vdproj using devenv just rebuilds the solution and still skips the setup project. The line is :&lt;/p&gt;
&lt;p&gt;&amp;quot;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv&amp;quot; c:\tfs1\JurisSuite\MpMainDev\BuildType\..\Sources\Main\Services\Configuration\ConfigurationServiceSetup\ConfigurationServiceSetup.vdproj /Build &amp;quot;Debug|x86&amp;quot;&lt;/p&gt;
&lt;p&gt;Any ideas from those who have this working?&lt;/p&gt;</description></item><item><title>Способы сборки инсталляционных пакетов с помощью Team Build</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8661323</link><pubDate>Fri, 27 Jun 2008 14:45:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8661323</guid><dc:creator>Дмитрий Лапшин</dc:creator><description>&lt;p&gt;В идеале, при гибкой (Agile) разработке процесс сборки решения и его развертывания в среде тестирования&lt;/p&gt;
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8921301</link><pubDate>Wed, 03 Sep 2008 08:26:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8921301</guid><dc:creator>pradana</dc:creator><description>&lt;p&gt;Is it possible to build a setup project without installing VS on the build server? Because I'm required not to install VS there&lt;/p&gt;</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8944160</link><pubDate>Thu, 11 Sep 2008 12:40:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8944160</guid><dc:creator>Craig</dc:creator><description>&lt;p&gt;Thanks for the assistence - you answered my questions perfectly.&lt;/p&gt;</description></item><item><title>TFS/MSBuild caveats &amp;laquo; Andrzej&amp;#8217;s Weblog</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#8946633</link><pubDate>Fri, 12 Sep 2008 16:15:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8946633</guid><dc:creator>TFS/MSBuild caveats &amp;laquo; Andrzej&amp;#8217;s Weblog</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://alipka.wordpress.com/2006/03/19/tfsmsbuild-caveats/"&gt;http://alipka.wordpress.com/2006/03/19/tfsmsbuild-caveats/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Building setup projects with Team Build and running tests on product install</title><link>http://blogs.msdn.com/anutthara/archive/2006/01/05/509606.aspx#9553143</link><pubDate>Thu, 16 Apr 2009 19:46:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9553143</guid><dc:creator>Snehal</dc:creator><description>&lt;p&gt;This post is almost 2 years old. Are we still not able to build Set project (vdproj) via MSBuild???&lt;/p&gt;</description></item></channel></rss>