Planning A Team Project + More Thoughts On MSDN2 And Local Help Files
I just found what I thought was an interesting help file over at MSDN2. Its a post (document, information, who knows what to call it) entitled "Planning A Team Project". And its a bunch of different questions to ask yourself before you create your team project:
The questions are divided into four groups:
-
Questions about the current team project (if any) and your future work.
-
Questions about the capacity and performance of the Team Foundation server.
-
Questions about the preferred software development process.
-
Questions about the structure or hierarchy for organizing the team project
Mostly its questions to help you decide whether to create a new team project or use an existing one.
I found another cool doc, entitled New Team Project Wizard Warnings and Errors. Its a list of some of the possible error and warning messages you might recieve when trying to create a new project. I would swear this did not used to be there.
I love how MSDN2 is being (or seems to be at any rate) constantly updated with new information. I've posted previously about how I liked the changes that have been made to the local MSDN help file. But therein comes a problem. When I am not connected to the Internet, I used the local file. Unfortunately, my local file is already so out of date. So when I connect to the Internet, I try and use the Internet version, because it has the latest content.
I want an option in the local MSDN Help, to have automatically go out to the Internet and update itself with the latest information from MSDN2. Sure, I get updates to the MSDN Help through my MSDN subscription, but that is not good enough, especially with how quickly changes might be made to existing documentation or new documentation may be added. If new documentation is added to MSDN2, I want my local MSDN help to download and integrate those changes. That way, if I am going away for the weekend, I can make sure I have the latest documentation information before I go, as opposed to having to struggle with documentation that is months old, only find that the answer is on MSDN2 a couple of days later.
What do you think? Does anyone else want this? Or am I living in a dreamworld?