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 Harray)
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 Harray)
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:
Since you can only deploy one master TFS server and replication mechanisms are not supported you might consider using a TFS Proxy server, which caches the downloads from the Team Foudation Version Control.
Functionality / What it does:
Cache downloads from Version Control only. Control Messages and other artifacts like work items are still transferred directly between client (Visual Studio) and server (TFS).
Read more about how the proxy works.
Licensing:
From a licensing perspective the TFS Proxy costs you one (additional) TFS license.
See also: Licensing whitepaper.
Installation
You find the installation files on your TFS CD under Proxy\setup.exe.
After the installation is complete you need to modify the configuration file.
See also: hardware requirements.
More Information (including all links mentioned above):
Well if you asked me a year ago if Microsoft is going to deliver UML tools the answer would not been to positive.
As you can read in Cameron Skinner's blog Microsoft changed it's views a bit. It's not anymore about "DSL vs. UML", but a combination of both: "the right tool for the right job".
There will be a clean separation between the two approaches:
- UML will be used at the high-level modeling ("logical" layer")
- DSL at the "physical layer"
As a result Microsoft will introduce five UML 2.1 compliant UML diagrams with the next version of VSTS and a few new DSLs. The UML diagrams are:
- Class Diagram
- Use Case Diagram
- Component Diagram
- Sequence Diagram
- Activity Diagram
You can have a look at those on these screenshots by MVP colleague Willi.
So Microsoft is not at all moving away from DSL, but recognized the value of UML as an addition and now clearly propagates the value in using a combination of both.
The future is: UML + DSL. The "programmatic approach" as Cameron puts it.
Screenshots from a successful team project creation.
You updated to TFS 2008, but since the upgrade process doesn't touch your already installed WSS you are responsible for upgrading it yourself.
Official Guidance:
Step 1: Run Prescan.EXE
Resulting log file:
Resulting XML file:
Step 2: Install WSS 3.0
Step 3a: Upgrade (invoked automatically by setup)
(Be aware: if you do not use the same port as your TFS is configured to talk to today you need to change the TFS registration using TFSAdminUtil afterwards!)
Step 3b: Still Upgrade (not in the web browser)
Step 4: Finalization (manual step)
Step 5: Uninstall WSS 2.0 (manual step)
Step 6: Install & configure TFS Extensions for WSS (located on the TFS media)
Step 7: Verify success by creating a new team project
Screenshots from a successful Power Tools installation
Step 1: Installing Windows PowerShell
Step 2: Installing TFS Power Tools
Screenshots of a successful Team System Web Access (TSWA) installation.
Requires: Team Explorer 2008 to be installed.
Open TSWA to verify it's working:
Screenshots from a successful Team Build installation
More Posts
Next page »