Team System Requirements
Aaargh. After installing Visual Studio 2005, the december release, my first thought was to try out Team System. Of course I need a server installation for that, so I was looking to install it. Read the manual.chm and found out it needs 1GB ram. Not only that, it also needs Windows 2003 Server with AD to work properly. And ofcourse if you really want to get going, MS Project, SharePoint, the works.
Too bad my Pentium 2 with 512MB memory can’t handle those requirements. Maybe at work we can arrange something over an internet connection.
I would love to test Team System, also over internet. See if source control works well, create unit tests and do performance tests. But also everything from start to end of a project. Analysis, design, development, testing, etc. All with bug tracking, etc, etc.
For now, I guess all I can do is watch those presentations…
Dennis is an independent consultant and software architect who loves building distributed systems and the challenges they bring. What he learns he tries to share via numerous articles, blogposts, presentations and workshops.
Well although Team System is a Nice Idea, it isn’t that great at all.
If you are using serious stuff like BizTalk there is NO support at all..
I think VS.NET alone is pretty serious already. And isn’t BizTalk integrated into VS.NET? So for everything you coded, there must be source control, bug tracking, unit tests, etc.
Of course BizTalk is a little different and a lot of things probably work a little different then the usual source code. So that’s probably why some stuff isn’t integrated.
If you did read any futher in the installation manual you will see that you need different machines, with both the same requirement.
The Data Tier (DT) can not be installed on the same machines as the Application Tier (AT).
The Client Tier (CT) (readL visual studio 2005) can be installed on either the DT or AT.