eScrum is a Scrum process template with a strong web management interface. It is developed by Microsoft and was released some times after Team Foundation Server 2005 as a separate download on their website.
It took some time, but now they released version 1.1 which supports TFS 2008 without doing the known work-around.
Go and download the new version 1.1 .
Being the first is not always the best, especially if you want to be the first on a new software release ;-). So if you already want to install the Service Pack 1 for your Team System environment, I want to give you some hints to not getting troubles.
- Before installing SP1 make sure you run the Hotfix Cleanup Utility for Visual Studio to cleanup your current installation
- If you have Express Edition and normal Visual Studio installed, you can't update Express before upgrading normal Visual Studio
- When upgrading your TFS with an installation of Visual Studio make sure that you first install SP for Visual Studio and then the one for TFS. If you first install TFS SP1, then you can't update Visual Studio anymore...
- Update all your tiers with SP1 (this includes Build Server, Load Controller, TFS and Client) to avoid unpredictable errors
- If you working with ASP.NET Ajax you should wait to upgrade, because there could be a bug in the SP. This was reported by Thomas Schissler in his blog post (German).
- If you make a new installation of TFS and want to include installing SP1, then look for the updated TFS Installation Guide to integrate SP1 in the installation (there is currently no TFS2008 ISO incl. SP1).
- Look for the Readme listing the known issues
As good practice I advice my customers (Production environments) to wait for the next 2 weeks to make sure no big problems will be found.
Hi, if you don't know it already, Microsoft has released Service Pack 1 for Visual Studio and Team Foundation Server 2008 and also the .NET Framework 3.5 SP1 (Just a week after the release of SQL Server 2008).
To get more info and links to the download page go to Brian Harry's blog post.
Currently I'm looking at the Rosario CTP's, what's new and hot. So this post will hopefully be the first of a series about small enhancements which helps you in the daily work.
Work Item Queries
It's now possible to group your queries in folders.
In VSTS 2008, I created/changed the queries with a prefix for example the "RE - User Stories" or "DEV - My Tasks". Because if you have many queries, it's nice to have some sorting. In Rosario you could make folders by process role. Nice!
As I normally blog about Team System and especially Team Foundation Server, maybe the question comes up, why am I posting about Sharepoint updates? The answer is quite easy. Because with each TFS installation, you also need at least a WSS installation. I'd like to inform the TFS admins out there, to also look for maintaining the rest of the system or inform their system admins to look for it.
This updates corrects some problems with workflows and improvements to scalability and performance, for details look at Knowledge Base article KB951695.
Download: Infrastructure Update for Windows Sharepoint Services 3.0 (KB951695)
Deploy software updates for Windows Sharepoint Services 3.0
As I'm posting information about updates, I always tested them on my TFS test machine. But for sure, I do not guaranty that the updates works on all environment configurations.
The new release (Juli) of the Team Foundation Server Power Tools has been released this night.
The new features are:
- UI for subscribing to TFS alerts!
- TFS Best Practices Analyzer support for SQL-Server 2008
- Support for changing user's names
- Some improvements of the tfpt.exe
You can download it here.
For more details see the post from Brian Harry and his preview post. He does an outstanding job to deliver us with all this great feature extensions!
Unfortunately the TFS Web Access Update and SCOM management pack is still in work, but will be released soon.
And what's hot: Brian said, there will be an eScrum 2008 release soon! How long do we waited for that?
Are you interested in the Application Lifecyle Management topic combined with the Microsoft development products?
Software development has changed over the past years. Many companies tried to implement their development processes with more or less success. The biggest problem is not the definition, but the control of the work produced each day according to that process. Only with the integration of the complete product lifecycle and the ability to adopt the process, will help us, to make the quality of the software and organization better.
Microsoft has announced the Application Lifecycle Management (ALM) Day with 7 speeches about how ALM can be implemented with the Team System product suite.
We from Trivadis will be there with a speech about the theory and practice of agile development with VSTS and SCRUM. So come and join us!
Monday, August 25th at Microsoft Switzerland, Wallisellen
for more details, check out the offical event infos on MSDN Switzerland: Application Lifecycle Management Day
I already posted about the PowerCommands for Visual Studio 2008 here.
Last Saturday, they released a new version which includes some good additions:
- Enable / disable PowerCommands in options dialog
- Format document & Remove and Sort Usings on save
- Clear all panes
- Copy path
- Email CodeSnippet
- Insert Guid attribute
- Show all files
- Undo close
Have a look on the MSDN code gallery.
Have you ever created a branch in the wrong directory and noticed it too late (after check-in)?
For example, you create a branch under "$/Project/Main/" instead of "$/Project/Dev/". After you have realized your mistake, you go for a delete on the branch (checking in) and create a new one under "Dev".
Now go to the branches tab on the source control folder properties and look what you've got:
Your deleted branch will appear in the tree without any information that it was deleted. It's right that the branch wasn't removed because TFS handles deletes only with a status change. But I don't want to see the deleted files, right? Or at least they should be marked as deleted. Because I think this is really confusing, I posted a bug at connect:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=336734
How can I really remove the branch?
To really remove your branch, go for a destroy with the tf command line util.
To remove an item out off source control (not only mark as deleted), run the destroy command:
>tf destroy {BRANCHNAME}
Because you already have deleted the branch, the command will throw an exception that the branch wasn't found. This is because deleted items will get renamed with a deletion-id suffix. To get the deletion-id, go and run the properties command:
>tf properties {BRANCH_NAME}
Now, after you have the deletion-id, go and run the destroy command again (don't forget the x!):
>tf destroy {BRANCHNAME};x{DELETION-ID}
The properties window of your source control folder will show only the existing branches :-).
The new version of the Teamprise add-in for Eclipse has released.
Teamprise Explorer enables you to connect to the Team Foundation Server from within the Eclipse IDE. You can use source control, work item tracking, project reports and Ant / CruiseControl integration.
Now in version 3.0 you can also use Team Build & Check-in policies. It's getting better and better!
Have you heard from the Visual Studio Extension "PowerCommands for Visual Studio 2008"?
Microsoft has released some really cool extensions to the solution explorer:
- Collapse projects
- Copy/Paste Class
- Copy/Paste Reference
- Open containing folder
- Open command prompt
- Unload/Reload projects
- Remove and sort usings
- Extract constant
- Clear recent lists
- and some more...
Download it from the Visual Studio Gallery here.
If you're already there, also watch out the "Source Code Outliner Power Toy". It's like a "Class View" only for the current file. Normally you need to work with the combo boxes at the top of your current opened source file to browse to methods. Not any more...
And if you have ever worked with the Eclipse IDE, then you won't work without it!
This is my second post about errors which can occur while installing Team Foundation Server.
If you find errors like this in your event log:
| Source: |
MSSQLSERVER |
| Event ID: |
18456 |
| Description: |
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>] |
| Source: |
Report Server Windows |
| Event ID: |
107 |
| Description: |
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. |
and/or for example the TFSSchedulerService does not start after reboot, your SQL services might start to slow. This happens mostly if you install TFS in Single-Server mode.
Other services trying to connect to databases in the SQL Server but this is not completely up and running. To avoid this problem you need to delay loading this specific services.
Go to the registry editor and add a Multi-String Value to the corresponding service entry:
Key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReportServer
Right click "New Multi-String Value"
Name: DependOnService
Value: MSSQLSERVER
Do this for all services like ReportServer and TFSSchedulerService. There is also a Knowledge-Base article here.
Creating a new Team Project within Visual Studio / Team Explorer 2005 connected with a Team Foundation Server 2008 can cause in an error:
Error:
TF30170: The plugin Microsoft.ProjectCreationWizard.Portal failed during task SharePointPortal from group Portal.
Message:
The language id specified in the process template does not exist on the WSS server.
This happens because the 2005 edition does not understand the WSS 3.0 services. Microsoft has released a patch for the Team Explorer 2005 which solves the problem here.
Do you want to checkin your files from the Windows Explorer (Shell Integration) like with Subversion add-ins?
Some people don't want or need a Visual Studio Team Explorer, because they are none Microsoft-based developers like Oracle DBA's. But you want to use Team Foundation Server as your source control repository by default, because you like the integration of work items or the main development of your project is in .NET.
Unfortunately, this is by default not available from TFS. But there are two tools around which are closing this gap!
I hope Microsoft will implement this in a future release by it's own. But there's now no excuse anymore to say you need a Subversion repository because of the shell integration.
I decided to write a short post about licensing of Team Build Server environments because I was asked several times in the past. There's a good chapter in the Team System Licensing Guide which explains it in detail.
If you want to run Static Code Analysis or automated Tests you need to install Visual Studio Team System on the build server. For this Team System installation you don't need any additional licenses as far as your developers have an appropriate license to do the specific task (extract from Licensing Guide):
| Team Member Actions | Licensing Implications |
| Developer checks-in source code. | Team Foundation Sever CAL required. |
Developer defines a team build type to include any of:
- Unit Testing
- Code Coverage
- Code Analysis | Team Edition for Developers or Team Suite is required. |
Tester defines a team build type to include any of:
- Generic Testing
- Web Testing
- Load Testing
- Manual Testing | Team Edition for Testers or Team Suite is required. |
| Team member initiates a build. | Team Foundation Sever CAL required. |
Conclusion:
If you (=developer) only have a Developer Edition installed and queue a new Team Build, you don't need any additional licenses. Only if you want to modify or create such a build definition.
The build server do not need any licenses (included in Team Foundation License), only the developers who working on it!
Mehr Beiträge
Nächste Seite »