New Team System Stuff - 2004-11-11
UML, DSL & Software Factories
Alan Cameron Wills has a post in which he responds to a comment to his previous post on the DSL tools release (DSL tools available):
Why not base domain specific languages on UML?
Firstly, just to reiterate – we do believe in UML’s usefulness for a variety of tasks. I sketch in UML for analysis purposes and for helping to think about the detailed design of code; I’ve written a book about it, developed some nice techniques, and given numerous courses over the years, and signing up with MS hasn’t changed my views; and my group colleagues have comparable histories, some of them making substantial contributions to where UML is today.
Team System - the Halo 2 of life-cycle tools?
Geoff Appleby is looking forward to Visual Studio Team System in a blog post that reminds me of some of the posts people have made about Halo 2:
Making the Connection in Las Vegas
TheServerSide.net has a series of articles that cover the DevConnections conferences in Las Vegas this week:
Whidbey Ascend Training
Rob Cecil has posted some coverage of the training provided through Whidbey Ascend.
- "Welcome to the Visual Studio 2005 Ascend program"
- Coverage from Whidbey Ascend - Day One <- Team System stuff
- Coverage from Whidbey Ascend - Day One (Continued)
- Whidbey Ascend Coverage : for (int dayIndex=1; dayIndex<days.Count; ++dayIndex)
From the other side of the podium, Chris Menegay has the following post:
Make Your Apps Fly
I received the December 2004 issue of MSDN Magazine today. In it, John Robbins of Wintellect has an extensive article on the Team System performance tools. Not a subscriber? Visit your local newsstand or check for an online version of the article early next week. I'll post a link when it goes live.
Software Architecture Guidelines
Dan Agonistes took a break from his love of baseball statistics to blog about guidelines for software architecture after reading a post from Steve Cohen:
Guidelines for Software Architecture
Recently, I've been thinking more about what a software architect does and trying to formulate some basic axioms or guidelines to keep in the front of my mind. To that end I thought Steve Cohen's thoughts on what " Enterprise Ready " means are useful.
Anyway, here are a few guidelines (not original of course) that I came up with for a course I teach on patterns and architecture in .NET that apply to a typical layered architecture (presentation, business, data).
SQL Server Reporting Services
Reporting in Visual Studio Team System is provided by SQL Server 2005 Reporting Services. If you want to master the whole enchilada, you should take a look into some of the other products on which Team System is built. Eric Nelson posted a link to his blog for a SQL Server Reporting Services Webcast:
SQL Server 2005 Reporting Services Webcast available on demand from Technet
I completely missed this - whoops! Haven't had time to check it out yet but it is apparently very useful https://msevents.microsoft.com/cui/r.aspx?r=5068262&c=en-US&t=4 Enjoy.
Restaurants at the End of the Web
Michael Lehman has posted the third installment in this series of posts about Software Factories:
If you missed the previous posts...
Ask Burton FAQ
Some new posts for the FAQ:
- Q: What's new with merging and branching? Why is it better? Can you associate criteria with a merge?
- Q: Will there be an easy way to write your own utility to migrate source code to Team Foundation version control?
- Q: Can a developer have their work items when they are disconnected (i.e., some form of caching?)
- Q: Does Team Foundation support automated workflow for work items?
- Q: How do you know which methodology template was chosen once the portfolio project is created?