January 2008 - Posts
Using check-in policies has become a common need, especially if it concerns to code analysis.
There are important differences between VS 2005 to VS 2008 when using this policy:
It appears that you need to be aware of these differences when using different versions of VS and Team Explorer to modify this type of check-in policies.
Microsoft has a detailed explanation here.
This is the forth post in eScrum series.To read to previous posts:
- Introduction to eScrum.
- Synchronization between VSTS and eScrum web client.
- The product issue in eScrum.
After creating new project you should do few things to see it in eScrum web client: (http://localhost/escrum)
Update RegisterGroups.xml file with your project:
In IIS Manager right click on eScrum website, open.
open “RegisterGroups.xml” file and Add this:
<Server Name="server name" Uri="server uri">
<Group Name="team project name" />
</Server>
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, "Courier New", courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
still don’t see your new projects in eScrum?, try this:
- In IIS, “Application pools”, right click on eScrumAppPool, recycle.
- Delete eScrum cache.(c:\windows\temp\eScrumCache).
This is the third post and part of 4 posts about escrum.
Read the previous posts:
In eScrum, a product made up of product backlog which is a single prioritized feature with a baseline cost estimate, is prioritized work to be done.
A Product is a combination of a Product Backlog, a Product Owner, and a list of Team Members who will participate in the Sprints.
If you want to create a new product through the VSTS Team Explorer you will need to add new work item type “eScrum product details “. Note that VSTS relates to new product as new area, that is why you will need to define new area and only then create new product which is related to this area.
To define new area:
1. Right click on your project in team explorer.
2. Select “Team project settings” and “Areas and iterations…”
3. Areas and Iteration window will open, view the “Area” tab and click the icon “Add a child node”.
4. Give name to your area and close the window.
To create new product related to your area:
1. Right click on “Work Items” in team explorer.
2. Select “Add work item” and “eScrum product details “.
3. New eScrum product details window will open, in the classification area select your area from the drop down list.
4. In the status area select product owner, fill in other details that you want and Save.
You should be aware to the fact that you can create more than one ” eScrum product details” for the same area.
eScrum web client shows the list of products with the same name (area) while actually displaying just the first one that was created, no meter which product you select.
TFS 2008 has many advantages which incourage companies to use it.
The main issue is how to perform the move - you must be smart about deciding what is the right method for you:
If you're just starting to use TFS for the first time and don't have any history with TFS than you just need to perform a clean installation of TFS 2008 - that's simple.
If you're working with TFS 2005 and just want to upgrade than you just need to perform a TFS 2008 upgrade on your current TFS server - that's simple too.
BUT:
What if you have an upgraded TFS 2008 server and must (due to various reasons) perform a clean installation of TFS?
Here is my recommendation according to my experience:
It appears that it's not that simple to move to TFS 2008 if you started working with TFS 2005, upgraded to TFS 2008 and must perform a clean installation.
I discovered that it's wrong to make a clean installation of TFS 2008 and then restore the upraded databases, especially if you're using customised webservices, VS add-ins etc' on the server.
I encountered several problems regarding DLL's versions, registry, permissions and more... Of course, if you know how, you might be able to fix all these problems with time (however, a long time!), but it's not the right solution - you can never know what will be the consequences of your manual fixing.
The right way to do it is to install TFS 2005 (with SP1 of course) and only then perform an upgrade to TFS 2008 (and at the end restore the databases, verify that all your webservices, VS add-ins and other additions are working fine).