Be sure to check out this post from J.D. Meier. It contains a LOT of new information and recommendations on how to get the best bang for your buck from Visual Studio Team System.
I just attended the 2007 Jolt Awards at the SD West Expo in Santa Clara.
In case you haven’t already seen it, Microsoft had quite a few nominations and received two “Productivity Awards” (honorable mentions), and one Jolt Award! See below:
Jolt Award Winner:
There were other tools that won or were mentioned that complement, integrate, or support either Visual Studio or the .NET platform.
For a complete list of nominees (and soon-to-be-posted winners): http://www.joltawards.com/2007/
In case you haven't seen this yet..
Team Foundation Server is happy to announce the release of version 1.2 of Team Foundation Power Tools (formerly known as Power Toys). In this release we’ve added 2 new command line tools for the developer and 3 non-command line tools. This version includes some bug fixes to previous Power Tools, support for Vista, and adds the following new functionality:
Please note that the Process Template Editor has some additional pre-requisites, they are identified on the download page.
You can locate the Team Foundation Power Tools V1.2 release here and you can get help on the forums for these tools here.
I get asked this question a lot. You download the latest and greatest version of the guide, open it, and you can't access any of the help items!
This is because the .chm file (the installation guide help file) is "blocked" for security reasons. To resolve this, simply right-click on the file and select Properties. You'll notice that there is an "Unblock" button at the bottom.
Click that button, and click Ok to close the Properties dialog. Lastly, re-open the installation guide and you should be set!
To download the TFS installation guide, go here: http://go.microsoft.com/fwlink/?linkid=40042
The TFS install guide is quite comprehensive. It covers walkthroughs & checklists for both single- and dual-server deployments, system requirements, security, and install guides for the Build Server, Proxy, and Team Explorer.
Are you kidding me? People are using blogging, this great communications medium, to play TAG? So let me get this straight: I mind my own business, don't over-blog because I try to only post meaningful stuff here, and now because I've been "tagged" I need to reveal 5 things about myself. All thanks to Grace Francisco.
In the interest of keeping my friends my friends, I’ll end the madness with me and not tag anyone else (at least for now).
I think the folks at Borland have finally removed my StarTeam blog. With the inception of CodeGear, CG seemed to take over the blog server, and removed me.
I honestly haven't touched it since leaving Borland, but several former colleagues and customers have emailed me wondering if the content is still available somewhere (I had a lot of how-to's and SDK samples posted). I honestly don't think it's archived anywhere, but I've asked the CodeGear folks via email, and will post the URL if it's still posted somewhere.
There’s not a huge amount of best practice info out there regarding areas and iterations. One interesting place to look at is a blog post that describes how the Visual Studio team uses them (http://blogs.msdn.com/ericlee/archive/2006/08/09/when-to-use-team-projects.aspx)
So here are my 2 cents (you can see how much that's worth these days!) on Areas and Iterations.
To me, areas are ways of tagging or organizing objects within a Team Project. Typically, areas are used to define either logical, physical, or functional boundaries. It’s a way to slice and dice a normally large project effort into more manageable, reportable, and easily identifiable pieces.
For example, let’s say we have a tiered web application managed in a single TFS project called “MySite”. There are 3 major components to this app: the web site, a web service, and a database. If this is a decent-sized application, you might have 1,200 tasks in the system for this project. But how do you know to which component a given task belongs? What if I only wanted to see tasks for the web service piece? Areas are a convenient way to handle this. Set up areas like this:
Now you can specify an area of assignment for each task (work item), making it easy to effectively filter what you want to look at/work on. You can use areas in both queries and reports as well.
You may optionally want to further dissect those major components to be even more specific:
\Layout & Design
One final aspect of Areas to consider is security. You can set security options on each Area node which can dictate not only who can change the areas, but also who can view or edit work items in a particular Area.
So if you think of Areas as slicing and dicing by “space”, think of Iterations as slicing and dicing by “time”. Iterations are like “phases” of a lifecycle, which can dissect the timeline of a project effort into more manageable time-based pieces.
So going back to the “MySite” example, say the project management team wants to split the entire project into 3 cycles, Phase 1, Phase 2, and Phase 3. Thus, your Iterations can mirror that:
These Iterations can be phases within the entire life of a project, or phases within a given release of a project. So if “MySite” is going to have multiple releases over time, my Iterations might look lik this
Now you have categorization options for both space and time (now if only we had a continuum..) for your project, allowing you to assign your tasks or other work items not only to the appropriate functional area (Area), but also to the phase (time cycle) of the project.
Take a look to find the closest of the 23 cities hosting a launch event!
I would like to invite you to a webcast designed specifically for our customers in the West Region. This event, presented by William Salazar – Microsoft will cover Microsoft Visual Studio Team System and will include technical and solution overviews.
Microsoft® Visual Studio® 2005 Team System is the best integrated software development platform to build the mission-critical applications that businesses depend on. It extends Visual Studio’s integrated and productive experience from the developer to the entire development team by delivering powerful new role-based tools for software architects, developers, testers and project managers. It also includes an integrated team server and customizable processes to help teams drive predictability, visibility, and control into their software development process.
Overview of ‘Data Dude’ aka Visual Studio Team Edition for Database Professionals11/29/06, Wednesday, 10:00 a.m. – 11:30 a.m., LiveMeetingVisual Studio Team Edition for Database Professionals delivers a market-shifting database development product designed to manage database change, improve software quality through database testing and bring the benefits of Visual Studio Team System and life cycle development to the database professional. This webcast will cover the main features of the Database Professionals product like:- Schema Management - Controlling Database Change- Data Generation for Tests- Database Unit Testing - Improving Collaboration and CommunicationPresented by: William Salazar, MicrosoftAudience: IT Managers and Professional Developers, DBAs, Architects and TestersPrerequisites: Previous experience with Microsoft Visual Studio Tools and technologiesRegistration URL: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032316244 Event ID: 1032316244
There isn't a lot of documentation out there that covers deploying Team Foundation Server across two non-trusted domains. This is not to say that TFS simply won't work this, but that there is simply not a lot of deployment documentation to support this scenario. There is an MSDN forum post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=177844&SiteID=1) that discusses it, but no formal guidance.
The below is a diagram outlines a deployment configuration that should support this scenario. Again, it's not formal documentation, but rather a visualization of a workable scenario.
The full-size image is attached to this post.