Step 1: Install the .Net 4.0 Framework Beta 2 on your build server (or just put VS2010 beta 2 on it)

Step 2: Change the Team Build config as follows

• Stop the Team Build service
• Go to C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies and open up TfsBuildService.exe.config in the text editor of your choice.
• Find the MSBuildPath setting and set the value as follows
  <add key=”MSBuildPath” value=”c:\windows\microsoft.net\Framework\v4.0.21006\” />
• Restart the Team Build service and check that your builds work.

Step 3: You’re done.  Go and ask your boss for a pay rise for being so efficient.

Taken from: http://richardsbraindump.blogspot.com/2009/11/how-to-build-vs2010-solutions-using.html

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Initializing IIS Web Server...
Successfully created virtual directory 'ycmbuild'.
Granting IIS read access to the folder 'C:\Projects\YourClubMatters\Trunk\YCM\WebSite_deploy\Release'.
C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.targets(676,5): error : Some or all identity references could not be translated.
Warning: Unable to grant IIS access to folder 'C:\Projects\YourClubMatters\Trunk\YCM\WebSite_deploy\Release'.
Done building project "WebSite_deploy.wdproj".
========== Rebuild All: 7 succeeded, 0 failed, 0 skipped ==========

The solution for me was to stop the web deployment project from creating the iis virtual directory, make a virtual directory pointing at say “c:\inetpub\vdir”, give the application pool it belongs to the same rights as the tfservice, edit team build project file adding a task that shuts down the parent website of the virtual directory, deletes all subdirectories and files in “c:\inetpub\vdir”, copies the published website that the deployment project creates to “c:\inetpub\vdir” and starts the parent website of the virtual directory.

I’m sure there are other solutions, I found that to be the simplest. Also, I used SDC Tasks to do all of this, very simple stuff.

What you add the the .proj file looks like this:

Related posts:

1. Redirecting using strong types in an asp.net web application project Update, I recommend also reading the following post after you...
2. Handling Relative Paths and debug mode with Jquery in ASP.Net Web Forms I had a problem where I wanted to use the...

Related posts brought to you by Yet Another Related Posts Plugin.

It does all this by integrating with Sharepoint Services and SQL Server 2005+ (& Reporting Services). So everything including source control is stored on your SQL server, and all your permissions are Windows Auth, so it works really well with active directory.

One of the nicest features of the system is the source control, it took a bit of getting used to but there is something really awesome about being able create a Task inside Visual Studio, do the work required to complete that task, hit check in and associate the changeset with the task all without switching windows.

As with trac you can create views on the bugs/tasks that need to be resolved, but being able to define the area the bug happened in gets easier as you can create a tree that defines the application and pick any point in that tree to assign the bug to.

With team build you can set up builds to go off when checkins are made or they can be triggered by users you give the priviledges to do so. Its ridiculously easy to set up and it uses MSBuild to build and MSTest to Unit Test. In your visual studio window it gives you the result of the build, including any unit tests passed and failed.

TFS exposes web services through the IIS site it creates which you connect to using team suite using Visual Studio or for that matter any other application (of which there are quite a few) allowing you to connect behind the vast majority of firewalls and allowing you freedom to write an application specific to your needs when developing. Personally I only use the Team System Web Access tool to allow people who don’t use Visual Studio to add tasks to the project so far but when I get some more time I’ll go digging through them.

The one major problem I found with it is that configuring Active Directory and Sharepoint are a pain in the ass if you’ve never done it before, specifically when trying to make it accessible from outside your network. The advantage is of course that everything works with IIS and all the technology that is already in place in most Microsoft project and product houses. Its also easier to configure active directory than it is to set up all the things that TFS provides using open source software but I still wonder what I’ll be doing in a few years when the Microsoft Biz Spark program runs out and we have to start paying for software.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.