This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Using VSTS/TFS on Existing Conference Development Projects Part 1
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
So with the release of VSTS Beta 2, there is now the opportunity to stop the VPC stuff and do some real work with it/on it for existing projects. In particular for me, to investigate the use of it, and the MSF-Agile methodology guidelines for my real projects: DevTeach 2005 consisting of three deliverables and VSLive! Boston conisting of two deliverables and VTdotNet consisting of one deliverable. In each case, the deliverables consist of PPT decks and lots of Whidbey code projects.
So to that end, I spent a bit of time on the weekend setting up my physical machine for Win2K3 Standard and then installing Yukon and then VSTS on it. The only issue (again) I had was with Sharepoint causing project creation to fail on a plugin initialization which was fixed by this. So, I created a new Team Project for DevTeach 2005 and I used the MSF-Agile template, well it was the only one available. So, the question for me that I will look to address is how agile is it really? I don't think I'm ready to answer that yet but the template does come up with a nice Project Guidance web site. After creating the Team project, I had a whole list of Work Items. While that's all well and good, the immediate disconnect I had is how do I get my existing stuff into TFS? I would double-click on Hatteras, whoops now its called “Version Control” and I would have this great Source Code Control window but I couldn't see how to get anything into source control. It was not until I opened up an existing Whidbey solution file and added that to source control, that I started to get the button for adding files to source control. There actually is a Work Item set up by the Process Guidance that says “SETUP: Migration of Source Code“. When I check-in source which is different than adding files, I have several tabs in the check-in, one of which is what Work Item to associate or close out with the check-in. Very useful! Then, it's important to remember that TFS is a real source system unlike its predecessor so that nothing happens until you check-in which commits the changes. I kept adding files and directories and nothing was showing up! Doh! I forgot that I had to commit the add with check-in. So that's it so far. I'll do this: I'll set this up as Part 1 and write up my experiences of doing this so stay tuned!!
Previous Topic
