Wednesday, February 23, 2005

Catastrophic Computer Failure....

Sorry for not posting in the last week, but as I went to update my blog last night, Windows decided to go all corrupted on me. So I've spent the past 24 hours rebuilding my machine. Good news is I was able to save all my VPC hard drives. But, of course, now I have to get my laptop back in working order. Look for new posts really soon!

Wednesday, February 09, 2005

Move on folks. Nothing to see here...

This is a test.  This is only a test.  In the event of a real blog post, there would actually be something interesting to read here.

Tuesday, February 08, 2005

Check This Out

Jon Box, a friend of mine, is talking about Team System at TechExpo 2005 in Little Rock, AR. Billy Hollis will also be talking on Smart Clients, and there is a SQL Server 2005 track as well. All in all, it looks like a great day of information, and I really wish I could go.

Did I mention the event is FREE? And there will be PRIZES?

If you live in or around the area, you should head over and check it out. You won't be disappointed, especially with Team System!

On a side note, I am laid up with the "creeping crud", as my Dad used to call it, so my foray into VSTS may slow down this week. I'll do my best to get a couple of more posts up though.

EDIT: Change the state to be AR instead of AK (it is supposed to be Little Rock, Arkansas (AR), not Little Rock, Alaska (AK). And I'm born and raised in the South!) Sorry for the confusion, and my thanks to Rob for catching that for me.

This And That...

Peter Varhol - Microsoft Team System Combines Established With New

I find this to be an interesting post. I do disagree with him on a couple of things.

First, the bulk of these features work only with code developed in Visual Studio 2005

Not trying to sound too flippant, but I think that is pretty obvious. I agree that for some teams, it may take them a while to move to VS2005. For my department (which is a small department, I admit), we are already making plans to move to it as soon as it is released.

Second, as a first release, the Team System will lack the reliability and breadth of features that will make it truly useful

I completely disagree with this statement. I have only scratched the surface in my testing of the December CTP, but from what I have seen, and what I have read on blogs and other sources, I feel VSTS will make an impact out of the box. Heck, just the version control aspect has me all excited, because it is SOOOOOOO much easier than what we are currently using. And all the task and project management tasks are going to allow my little developer shop to be more productive, without an excessive overhead. (at least, that is the plan!)

I think that development groups will be able to take the pieces that they like of VSTS, and make them work for them. And I don't think that Microsoft is abandoning the individual or small group developers. Obviously, as an individual developer, there is a lot of VSTS that you probably would not use. But then again, it is there if you want to use it (and I am geeky enough that I probably would). I don't believe MS is going to leave anyone in its community behind, because lately they are making a big push to include the community.

Let's keep the excitement about VSTS up. Its going to be a great product!

Thursday, February 03, 2005

Creating A Project And Adding It To Source Control

In VS2005, I selected File->New->Project. Under Project Types I chose Visual C#, and Windows Application. I entered "HelloGumbi" as the project name, and did NOT check the "Add to Source Control" checkbox. I clicked the OK button to create the project:

Figure 1 - New Project Window

The new project was created and displayed in the Solution Explorer. I right-clicked on the solution, and selected "Add To Source Control". This opened the "Add Solution To Hatteras" window:

Figure 2 - Add Solution To Hatteras Window

It defaults to the Team Project I have already created. The folder name defaults to the solution name of my project. I took the defaults and clicked the Next button. This opens the next page of the wizard:

Figure 3 - Add Solution To Hatteras Step 2

On this windows you can change the name of the repository folders, if you want to. I took the defaults and clicked Finish. A progress window opens, showing the progess of adding the project into the version control system. Once the project has been added, the progess window closes, and the IDE looks as follows:

Figure 4 - IDE After Adding Project To Source Control

Notice all the files have + signs beside them in the solution explorer. They are waiting to be checked in. In the Pending Checkin window at the bottom of the IDE, I click the Checkin button. I recieve a message telling me to add a value to the Code Reviewer, so I did this and clicked the Checkin button again. My files were checked into Hatteras, and the IDE now looks like this:

Figure 5 - IDE State After Check In

Notice the little blue locks by the files in the Solution Explorer, showing they are currently checked into Hatteras.

Up Next: I start trying to check out files.

Wednesday, February 02, 2005

Why change a good thing...

Sometimes change is a good thing. And sometimes you should just leave well enough alone. I adhere to the latter statement concerning creating a new project in VS 2005, specifically, creating a new web project.

To recap my adventure so far, I have Team System up and running using VPCs, and I have created a Team Project. My next step is to create an actual project to do some work in. So I click the New Project button, and the New Project window opens.

Figure 1 - New Project window

I click the + sign beside Visual C#, and begin looking through my template options, looking for ASP.NET. After going through the list twice, I realize its not there. "Oh my", I think to myself (at least, that's the G-rated version of what I think), "did I install something wrong? Where are the ASP.NET templates?".

I cancel out of the window, and then select File->New->Project. The same window opens as above. No ASP.NET option.

I go back to the File->New menu option. That's when I notice that under the New option, there is a choice for Project, and another choice for Website. Under the Website choice are what is needed to create an ASP.NET website.

I think I understand why they did it this way. Logically, in some respects, it makes sense. But at the same time, when I click the "NEW PROJECTS" button, or go File->New->Projects, I expected to be able to create any kind of C# project, as I could in VS2003. So while I understand logically why they split it out this way, I don't like it. I wish you would let me be able to select an ASP.NET project from the New Projects dialog window.

I decided to go ahead and create a Windows Form app, just for the heck of it. I have not built one before (I'm an ASP.NET kinda guy), so I figured it would be a learning experience in several ways.

Tune in next time to see me create this new project and add it to the source control.

Tuesday, February 01, 2005

A Quick Look At The Team Explorer Window

The following screen shots show the different folders and subfolders located in the Team Explorer window, after I finished creating the initial Team Project, discussed in my previous post:

I then decided to check out the Team Project website, to see what happened:

  • Figure 4 - IAmGumbi Project Website

  • Yikes! Look at all the Reporting Services errors! I don't know if those are because I have done something wrong, or that piece is not working. I'll put that on my list of things to investigate.

    Up next, I create my first VS2005 project (and for some reason, I make a Windows Form project instead of an ASP.NET project...)