If you want to start small with your team project you might consider the "Basic Process Template" instead of the built-in MSF Agile and MSF CMMI process templates. It can find on MSDN. From the description:
The basic process template includes:
- one work item type: bug,
- three queries: AllWorkItems, MyWorkItems, and MyWorkItemsAllTeamProjects,
- a basic Windows SharePoint Services team portal (created from the default site template),
- and a SQL Server 2005 Reporting Services site that has the following reports on it: Builds, Bug Rates, Quality Indicators, Tests Failing Without Active Bugs and Load Test Summary.
Use this process template as a basic starting point and an alternative to the MSF for Agile Software Development or the MSF for CMMI Process Improvement templates.
Step 1: Upload the process template to your TFS
Step 2: Create a new team project (using the new process template)
Step 3: Discover what's been created
Link: http://msdn.microsoft.com/en-us/library/ms194993(VS.80).aspx
A: Two possible ways:
Step 1: Get the URL of the document saved in a SharePoint document library
From the project portal:
Right-click the file and select Copy Shortcut. Done.
From the Team Explorer window in Visual Studio:
Right-click the file under the Documents folder and select Properties.
The quickest way is to double-click on "Url", then right-click the blue-marked URL on the right side and select Copy (or press Ctrl+C respectively).
Step 2: Add the link to the work item
Select Add on the work item's Links tab:
Select the a link type of "Hyperlink":
Paste the URL and enter a comment optionally:
Confirm with "OK".
Done.
Beginning with TFS 2008 SP1 you can specify that only the necessary part of the Work Item meta data will be transferred to the client caches, e.g. not the meta data for project you have no permission on. This is not done by default.
You can read all the glory details in Martin Woodward's blog. Short excerpt:
Enabling WIT Meta-data filtering
Now that we have been through all the gory details, let's finally see how to switch on the feature.
In the appSettings section of the %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\WorkItemTracking\web.config file add the following keys
1: <add key ="filterClientMetadata" value="true"/>
2: <add key ="excludedUserAgents" value="WebAccess:w3wp:witfields:witimport:witexport:witadmin"/>
The filterClientMetadata switch determines whether to filter client metadata based on the calling user's access rights (true) or not (false). If not provided the setting will default to false.
The excludedUserAgents switch is a colon delimitated list of strings that may appear in the requested clients HttpRequest UserAgent header. You can take a look at your IIS logs or your TFS Activity logs to determine what user agents are used, but a handy feature of the TFS .NET API is that the executable name using the API is recorded in the user agent string, meaning that you can easily find your specific utility and exclude it if necessary. As far as I am aware, the only publically accessible application that makes use of shared meta-data is Team System Web Access, so we put "WebAccess" in our excluded user agents setting. We also put in the names of the utilities in Team System that need to see all the metadata to report back correct information to the TFS administrators.
Pick your favorite tool for your task/job:
From Visual Studio:
From the command line:
From the web browser:
From Microsoft Office products:
From other platforms or IDEs:
From Windows Explorer:
From other products:
Footnotes
(*) requires Team Explorer to be installed.
($) means the product is a commercial third party solution.
To shut down all services used by TFS you can use the following batch file:
Using Team Foundation Server to Develop Custom SharePoint Products and Technologies Applications
Summary: Use Microsoft Visual Studio 2008 Team Foundation Server to support SharePoint application development, and provide an integrated development environment and single source code repository for process activities, integrated progress reporting, and team roles. (12 printed pages)
Author: Microsoft Corporation, September 2008
Link: http://msdn.microsoft.com/en-us/library/cc948982.aspx
If you try to set the minimum size for a control you now need to specify a SizeType like "(50,100)" instead of "50,100".
Error message (from witimport.exe):
The 'MinimumSize' attribute is invalid - The value '50,100' is invalid according to its datatype 'SizeType' - The Pattern constraint failed.
Using a minimum size you can create multiple large text boxes on the work item form layout:
If this is the case...
Try...
- Make sure Visual Studio is closed (and devenv.exe not in memory anymore)
- Run: devenv /setup
- Check if it's fixed already. If not, close down VS again.
- Run: devenv /resetuserdata
The Team Explorer window should now look like expected again.
(Thanks to Sven Hubert for the screenshot and workaround verification.)
A good read:
About the technical side:
Name des Updates und Nummer:
- Security Update for SQL Server 2005 Service Pack 2 (KB948109)
version 9.00.3068.00 released on 7/8/2008
Applies to:
- SQL Server 2005 Service Pack 2 with Reporting Services installed
Symptoms & Result:
- After installation the SQL Server 2005 Reporting Services service might not start. Therefore the Reporting Services cannot be used anymore.
Distribution:
- The Update is distributed via Windows Update.
Workaround:
- Uninstall the update (requires a restart).
My recommendation:
(for your internal SQL server you use for TFS)
- Do not install the update and wait for the next service pack release.
Related Links:
Service Packs for VSTS/TFS do not only contain bug fixes, but quite a few nice new features as you can read here (more general) and here (TFS-specific).
Download links:
If you have trouble installing SP1 look here and here.
Tip #1: Uninstall Visual Studio Hotfixes first
If you previously installed a Visual Studio 2008 Hotfix, you must run the Hotfix Cleanup Utility before installing Visual Studio 2008 SP1. For more information, see Visual Studio 2008 Hotfix Cleanup Utility for Installing Visual Studio 2008 SP1.
Tip #2: Have enough disk space available on your primary hard drive:
You can read here why.
Tip #3: If you have Team Explorer or TSWA on your TFS you need to install... (Thanks to Hakan Eskici)
... Visual Studio 2008 Service Pack 1 and TFS 2008 Service Pack 1 (in that order!).
Tip #4: Integrate installation of TFS and SP1 ("Slipstream")
The steps to produce a so-called "slipstream" installation package are documented in the TFS Installation Guide in the chapter "How to: Integrate the Installation of Team Foundation Server and Service Pack 1".
There are a few reasons why you must do that (e.g. upgrading to SQL Server 2008) you can read in Brian Harry's blog post.
Tip #5: Ignore Windows Update reboot prompt (Thanks to Brian Harry)
If you get a Windows Update prompt to reboot during SP1 installation, ignore it (don't reboot). Wait until after the SP1 installation completes and then reboot.
Tip #6: Uninstall and reinstall Team System for Database Development GDR (Thanks to Brian Harry)
If you have a prerelease of the Team System for Database Development GDR (that supports SQL 2008) installed, you will need to reinstall it after upgrading to SP1.
Screenshots from applying TFS 2008 SP1:
Screenshots from applying VS 2008 SP1 (online installer) on at TFS with only Team Explorer installed:
Requires:
- The use of HTML description fields in stead of the default description field.
- Team System Web Access (TSWA) to insert the pictures.
Steps:
- Use a HTML fields for your descriptions instead of plan text fields
(might need to copy the old descriptions programmatically).
- Add the image you want to use to the work item's attachments:
- Save the Work Item.
- Double-click your attachment. IE opens. Copy the URL to the attachment to the clipboard.
- Open the Work Item in Team System Web Access and use the "Insert Images" bottom (from the toolbar within the HTML field):
- Paste the attachment-URL from clipboard:
- Save the Work Item.
- Done. You can see your picture in the HTML description field.
TSWA:
Team Explorer:
- Make sure all team project members are added to the appropriate groups (Project Administrators, Contributors and Readers).
- For every team project remove the "[Server]\Team Foundation Valid Users" group from the team project settings (Team Project Settings » Securty).
- Done. Regular members now should only see team projects where they have permissions.
Enjoy!
Question:
Can I define a file name, not only a file type (extension), if multiple checkout is allowed for the whole Team Foundation Server?
Answer:
Yes, that is possible, although the UI shows "file extensions" and displays it in a way that you might think that it's not supported.
As a result you can specify that *.cs files in general do support multiple checkout but a certain file called "specific.cs" follows exclusive-checkout logic.
Enjoy!
-Neno
From their website:
"Timely Migration currently provides modules that support migration from CVS and Borland StarTeam. Support for additional products will be added in the future."
Link to website: Timlely Migration
TeamBuild
- can build one build definition from a single Team Project at a time.
- can build multiple build definitions from different Team Project.
MSBuild
Thanks Grant for pointing out those facts.
Are you concerned about performance?
You can scale out by...
Or scale up by...
If one of the following action are planned you should ready the appropriate documentation:
More Posts
Next page »