Visual Studio 2010 Ultimate RC

16. February 2010

By now I’m sure everyone knows that the release candidate for Visual Studio 2010 has been launched into the wild and can now be downloaded form the Microsoft Visual Studio website.

I’ve spent some time tonight removing Beta 2 and installing the RC and I have to admit that I’m quite surprised at just how smoothly it’s all gone. The whole process was more or less identical to moving from Beta 1 to Beta 2 which is something I’ve covered in depth before.

First impressions are that the RC is significantly faster than the beta’s and just feels a little more polished. With a bit of luck I’ll get to try some of the latest MVC bits out over the next few days as I’ve fallen a little behind with the last few releases.

Currently rated 3.0 by 10 people

  • Currently 3/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Adding a Collection & Project to TFS 2010 Beta 2

8. January 2010

In my last post I covered how to install TFS 2010 Beta 2 so in this post I’m going to go through the process of adding a new project into TFS.

Apologies in advance for the length of this post but it’s mostly screenshots and the whole process from start to finish took no longer than 30 minutes. I’m really impressed with just how easy it all was.

Creating a new collection

TFS groups projects into collections and when you first install TFS it creates a default collection for you. Not wanting to be stuck with the default my first step was to create a new collection to house my projects in. To do this you will need to open the TFS Administration Console on the server, in this case the Windows 7 machine I had installed TFS onto.

At the top right of the screen you will see a link which says “Create Team Project Collection” and once you click on that link you will enter a wizard for creating a new collection.

1-1

The first step is to give your collection a name and description.

1-2 
Clicking “Next” will allow us to setup the collection database, in this case I'm creating a new database on the SQL Express instance installed on my virtual machine.

1-3

Clicking “Next” we are now asked whether we want to configure lab management for the collection. Because I didn’t enable lab management on my TFS server I just moved to the next step here.

1-4

Now you can review the settings for your new collection and if you’re happy click on the “Verify” button which check the configuration information is all ok.

1-5

1-6

Finally after the verification is finished you can click on the “Create” button and watch TFS create your new empty collection.

1-7

1-8

Now you have the default collection and your shiny new collection to put all of your projects in.

1-9

Connection to TFS 2010 in Visual Studio 2010

After creating the collection we have to connect Visual Studio to TFS so the first thing to do is open up Visual Studio and look for the “Connect to Team Foundation Server” option in the top left just under the Visual Studio 2010 logo.

3-1

The resulting pop up window has a drop down list which is filled with the servers currently registered with Visual Studio. When you pick one of those servers the collections available on that server will populate the left hand side of the dialog and on selecting a collection it’s projects will appear on the right hand side. At the moment we have no servers so we need to register a new one.

3-2 
When you click on the “Servers” button in the top right you are shown a list of servers currently registered.

3-3

As this list is currently empty we need to click on the “Add” button. If you have used the default setup all you should have to do now is enter the name of your TFS machine and click “OK”.

3-4 
Your server should now appear in the server list which you can close.

3-5
On closing the server list we are back to where we started but now our TFS instance is listed and we can see the collections on the server. Click on the collection you would like to connect to and the press the “Connect” button.

3-6

Adding a Project to a Collection

Now we have our empty collection and Visual Studio has been connected to TFS so the next step is to add a project into our collection so we can get to work. To do this we need to open up Team Explorer which you can find under the “View” menu in Visual Studio.

4-1
To add your project right click on the name of your server and collection, in this case sidebytetfs\Sidebytes and then select the “New Team Project” option. Up pops yet another wizard and the first step is to give your project a name and description.

4-2 
Next we select a process template, I’m going for Agile.

4-3
Next up source control options, I’m creating a new source control folder but you can also create a new branch from an existing repository.

4-4

Review all of your settings and finish the wizard.

4-5 4-6 4-7

In team explorer you should now see project you have just created.

4-8
Adding source code to a TFS project source control

Now we have our project in TFS we need to add our code to it’s source control repository. If you are adding existing code into source control then open up the solution and then right click on the solution in the solution explorer selecting the “Add Solution to Source Control” option. If you are adding a new project tick the “Add to source control” option at the bottom right of the new project dialog.

Up will pop a dialog which lists the projects inside the TFS collection you are currently connected to. Select the project you would like to associate the source with and then give it a folder name.

5-1
Your project will now be added to source control and you should see a list of pending changes which are still to be committed to the repository.

5-2

Select the “Check In” option and all of your files will be pushed back to the repository leaving your solution now under source control.

5-3 5-4
Web Access

As a quick aside TFS 2010 now comes with a full featured web interface where you can access your source control, work items etc.

6-1
6-2

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Installing TFS 2010 Beta 2 on a Windows 7 Virtual Machine

28. November 2009

I’ll start this post by saying that in the past I’ve always used Subversion for source control and Team City or Cruise Control as a continuous integration server. As such this is my first every experience with TFS but with the release of 2010 Beta 2 I thought it was time to take a look at Microsoft's latest offering.

With Visual Studio 2010 you can now install TFS on Windows 7, Vista and XP so gone is the need to have a Windows Server box kicking about to host your TFS instance. My install was on a Windows 7 virtual machine hosted on VMware Workstation 6.5.

The install is separated into two sections. Install and Configuration, I’ll start with the Install. As always these steps worked for me but they may not work for you.

Install

The first step is to fire up the installer and to click through the first welcome screen and the license screen.

1

2-1 
Next you will be asked which of the components you would like to install. I selected both Team Foundation Server and the Build Service.

2-2 
Now sit back and watch it install.

2-3 
After a couple of minutes we’re all done, how easy was that? I should add that there was a reboot required after the install of the .NET Framework 4.0 but the whole install still came in under the 10 minute mark.

2-4
Configuration

After installing TFS you now need to configure it. When you click Finish on the TFS install up pops the TFS server configuration wizard.

3-1  
I’m not doing an advanced install so I’m just going to make my way through the basic configuration wizard. If you select the advanced install you have full control over the IIS settings, SQL settings etc.

3-2 

You can install to an existing SQL Server Instance or you can use SQL Express which is the option I’m going for. In this case the SQL Express Instance is running on the same machine as TFS.

3-3

Click through a few more screens to verify all of the details and the wizard will then start to configure TFS for you.

3-4

3-5

3-6 
Before you know it we’re done and up pops the administration console.

3-7

3-8

Both steps combined took 30 minutes at most. I’ll write up a post soon on my experience of setting up the first project in my new TFS instance.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

, , ,

TekPub

16. November 2009

I’ve been following Rob Conery’s blog for quite a while and a few weeks ago he and James Avery announced the launch of TekPub.

Without wanting to lift too much from their website the idea of TekPub is to produce top quality screencasts to help developers become better developers, something I’m all for. Currently there are five series running on the site, two free and three which require you to have a paid subscription. The paid subscriptions come in three varieties: yearly, monthly and series. The yearly and monthly subscriptions give you access to all of the content for the length of the subscription and with the yearly subscription you can download content in addition to streaming from the website.

I took the plunge over the weekend and worked my way through all of the content in the free series and I’ve got to say that it is fantastic!! I’ve never really been one for learning through screencasts but I’m now a paid up monthly subscriber and I’m really looking forward to getting started on the NHibernate series.

Their plans for the future look good as well and I’m quite excited to see they have planned series on iPhone applications, cloud computing and resharper.

I highly recommend that you go check out TekPub now even if it’s just to watch the free Concepts series, you might just end up a better developer for it.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Moving Code from .NET 4 Beta 1 to Beta 2

23. October 2009

My last post covered the removed of Visual Studio 2010 Beta 1 and the subsequent install of Beta 2. In this post I’ll follow on from that and cover the steps taken to upgrade my solution, created in Beta 1, to work with Beta 2.

As it turns out this was a pretty straight forward process but there were a couple of small glitches along the way which I'll cover below. These steps worked for me but they may not work for everyone.

The first job was to make sure the solution compiled in the new .NET framework so I fired up Visual Studio 2010 and opened up the solution I’d been working on. A quick build threw up a few errors all of which were related to ASP.NET MVC. When the solution had been created references to ASP.NET MVC 1.1 had been added to the Web, Tests and Controllers projects (the solution has multiple projects) so those were quickly replaced with references to ASP.NET MVC 2.0. Another build and the solution was compiling without any errors.

With the project compiling I opened up NUnit to make sure all of the business and data logic tests were still passing. All the tests executed successfully so it was time to check out the actual website to see if it was working properly. I know this should probably be done through some sort of unit test but at the moment we don’t have that in place.

I opened up the IIS Management Console and placed the website into the default .NET 4.0 integrated app pool. I normally like to run each application in it’s own app pool but I’ll cover that a bit later on in the post

To get the web site working three changes had to be made within the sites web.config. The first of these was the removal of the targetFrameworkMoniker attribute in the compilation tag.

Secondly the configSection entries added to the web.config by ASP.NET MVC 1.1 had to be removed. In .NET 4.0 Beta 2 these config sections are contained within the machine.config file which causes a duplication error when they are also present in the web.config of your project.

The third and final change to the web.config was to update any reference references for MVC 1.1 to 2.0. Remember to also change the web.config in the views folder.

At this point the result was a fully functioning website so job done right? Well not quite no. I normally like to have each of my applications running in it’s own app pool so I went back to the IIS Management Console and created a new app pool targeting v4.0.21006 of the .NET Framework (Beta 2) and assigned the website to the app pool.

I thought those changes would just work but every time I visited the site the app pool would stop and the browser would display a 503 service unavailable error. Investigating the event viewer yielded a couple of interesting error messages:

error1

error2
It looks like IIS is trying to load the Beta 1 version of .NET 4.0 and is falling over because it’s not installed which is subsequently causing my app pool to stop running. Looking at the .NET Framework folder within the windows directory showed two folders for .NET 4.0, one for Beta 1 (v4.0.20506) and one for Beta 2 (v4.0.21006).

folder
Having already uninstalled Beta 1 I took a bit of a gamble and deleted the v4.0.20506 folder and then restarted my app pool. Problem solved and now we’re all done.

All told the migration took about 25minutes but most of that was spent head scratching on the app pool problem so I’m very impressed with how well it went. Just as a quick aside ASP.NET MVC now comes as a preinstalled part of Visual Studio so there is no need to download and install a separate add on.

Next up is my first ever install of TFS.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Installing Visual Studio 2010 Ultimate Beta 2

21. October 2009

Visual Studio 2010 Ultimate Beta 2 is now up and running on my machine and I thought I’d just write up a quick post about my experience of moving from Beta 1 to Beta 2.

The first step was to remove Beta 1 so I fired up the installer (below) and then went off to find the readme file to see if there was an order in which all the components had to be uninstalled.

1   
The readme says to first uninstall Visual Studio and then to mop up any extra bits and pieces which are left over so I selected the “Change or Remove Visual Studio 2010” and was shown another screen containing the uninstall option.

2   
After selecting to uninstall it was just a case of waiting and after a while the big green tick showed up to tell me the uninstall had completed successfully.

3

4

 

 

Now it was a case of tidying up any bits and pieces which hadn't been removed by the uninstall of Visual Studio. The Beta 1 readme gives you a specific order to remove these components in so one by one I removed:

  • Microsoft .NET Framework 4 Extended Beta 1
  • Microsoft .NET Framework 4 Client Profile Beta 1
  • Microsoft Visual C++ 2010 Beta 1 x64 Redistributable - 10.0.20506
  • Microsoft Visual C++ 2010 Beta 1 x86 Redistributable - 10.0.20506

I’d previously installed ASP.NET MVC 1.1 so at this point I realised that I should probably have removed that prior to removing Visual Studio but I didn't think it would be that big an issue. Unfortunately after removing “Microsoft Visual Studio 2010 Tools for ASP.NET MVC 1.1” I just couldn’t get ASP.NET MVC 1.1 to uninstall, it kept telling me to remove the tools first but I’d just done that! After a little bit of searching I found this post (http://forums.asp.net/p/1482699/3465455.aspx) on the ASP.NET forums and managed to find the correct registry key to remove.

With Beta 1 removed I did a quick reboot before firing up the installer for Beta 2. I know it’s a bit silly but the first thing to impress was the new logo, I really like it.

5_thumb

6   
After selecting “Install Visual Studio 2010” it’s a case of clicking through the usual screens and selecting which components you would like to install and then watching as it works it’s way through the list and after a while you will hopefully get the success screen.

7

8

Time to fire up Visual Studio.

9

10   
A  very straight forward and quick install.  My only issue after the install was trying to get Visual Studio and Visual SVN to play nicely together but it looks like this is a known issue. Thankfully the always brilliant stack overflow had the answer.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

,

Visual Studio 2010 & .NET Framework 4 Beta 2 Now Available

19. October 2009

Visual Studio 2010 & .NET Framework 4 Beta 2 have now been released to MSDN subscribers and will become generally available on Wednesday of this week (the 21st).

It looks like Microsoft is trying to simplify the number of versions available so at the moment I've got VS2010 Ultimate and Team Foundation Server downloading. Once they are done I'll put up a post about migrating from Beta 1 to Beta 2 and any changes required.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Introduction to Dependency Injection and Inversion of Control

17. October 2009

I've been doing some catching up on blog posts this morning and Rob Conery has published one of the best introductions to Dependency Injection and Inversion of Control that I've come across. If you're interested in DI & IoC I'd highly recommend giving it a read and if you don't know what I'm on about definitely give it a read. You'll be a better programmer for it.

http://blog.wekeroad.com/smackdown/200-page-manual-on-inversion-of-control-plus-or-minus-199/

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

,

VisualSVN & Visual Studio 2010 Beta 1

29. September 2009
Following on from my last post it looks like VisualSVN now includes support for Visual Studio 2010. The newest version can be downloaded from http://www.visualsvn.com/visualsvn/download/ and is well worth a look if you like SVN integration in Visual Studio.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

,

VisualSVN & Visual Studio 2010 Beta 1

11. July 2009

I've only just started to play about with the first beta of VS2010 and one of the first thing's I noticed was the lack of any VisualSVN menu. I've been using VisualSVN for a couple of years now and have been very very impressed by it and just how well it integrates with visual studio. Unfortunately it looks like there isn't a release which currently supports VS2010 but I guess that's one of the pains of using pre release software.

According to this post support will be coming in the next few months so for the moment I've installed the latest version of AnkhSVN which is doing the job so far.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

, ,