VSTS

Connecting VS2008 to any TFS2010 Project Collection

Martin Hinshelwood — Wed, 27 May 2009 04:05:07 GMT

Easy peasy, all you need is the full URL from the project collection and you will be able to connect directly to it as if it was a different Team Server. This functionality was added with Visual Studio 2008 Service Pack 1, so if you don’t have SP1 installed yet you had better get it:

Microsoft Visual Studio 2008 Service Pack 1

You need to use the following in the connection box “http://[tfsserver]:[port]/[vdir]/[projectCollection]

Although this looks complicated, it makes some sense at least, but is nowhere as nice as using the 2010 connection box:

One of the new things in TFS 2010 is that you can specify a virtual directory that it will run under, the default being “tfs” so you can have everything on the same ports.

So, if your tfs server name is “tfs01.domainname.com” and you take the default vdir of “tfs”, all you need is the collection name. So you could end up with “http://tfs01.domainname.com:80/tfs/MyNewCollection”

Backward compatibility +1

Connecting from Visual Studio 2005 Service Pack 1 is a different story, there is currently no way to connect VS2005 to TFS2010. There has been some discussion around this and its importance to Business Intelligence teams. If you are just opening VS2005/VS2003 occasionally then you could probably get away with using 2010 to control TFS and working in 2005, but many BI developers are still spending a considerable amount of there time in 2005 :(

Technorati Tags: Visual Studio 2005,Visual Studio 2008,Visual Studo 2010,Visual Studio 2010 Team Foundation Server,Team Foundation Server,TFS,VS2005,VS2010,TFS2010

Upgrading to TFS 2010 Beta 1 and SQL Collation

Martin Hinshelwood — Wed, 27 May 2009 03:04:55 GMT

I have just finished installing TFS 2010 beta 1 and doing an upgrade of out TFS 2008 data. This did not go well…

Due to a collation mismatch between my original SQL Server 2005 and my new SQL Server 2008 I received an error when upgrading…

[Error @13:57:23.665] TF255184: An error occurred during operation. Message=Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.. Exception=.
[Error @13:57:23.681] TF254026: An error occurred during the following operation: Upgrade. The error occurred during the following step group: Upgrade.TfsTeamBuild. It occurred on the following step: Check In Build Process Templates. The following message was returned: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1..
[Info @13:57:23.681] CollectionServicingMonitor - [5/25/2009 2:56:55 PM] Servicing step Check In Build Process Templates failed. (ServicingOperation: Upgrade; Step group: Upgrade.TfsTeamBuild)

And then the roll back of the transaction did not quite work as expected, so although the TFS Administration does not know about my OldTfs2008Test1 project collection.

My client has it listed but with a TF31001 error.…

Solution? Suck it up and reinstall everything, including SQL and change the collation to the same on both servers. :(

Technorati Tags: TFS2010,Team Foundation Server,Team Foundation Server 2010,Team Foundation Server 2010 Beta 1,Upgrade

Solution to connecting to TFS using HTTPS over the Internet from behind ISA

Martin Hinshelwood — Wed, 20 May 2009 22:18:35 GMT

This problem it seams is to do with the way Visual Studio 2010 connects to your TFS server over HTTPS. The default value for “BypassProxyOnLocal” in Visual Studio 2008 was “False”, but it has been changed to “True” for Visual Studio 2010 Beta 1. It should be noted that this is currently a Beta 1 workaround and this behaviour may be updated for Beta 2 and RTM.

You can fix this by adding the following registry keys and restarting Visual Studio 2010:

You need to add a “RequestSettings” key to both of the following location that contains a string value pair of “BypassProxyOnLocal=’False’”.

32bit OS Key Locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TeamFoundationServer\10.0\RequestSettings

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings

64bit key locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\TeamFoundationServer\10.0\RequestSettings

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings

You can find out more on the “How to: Change the BypassProxyOnLocal Configuration” documentation on MSDN.

Technorati Tags: Visual Studio 2010 Beta 1,Visual Studio 2010,Codeplex

Unable to connect to TFS using HTTPS over the Internet from behind ISA

Martin Hinshelwood — Wed, 20 May 2009 01:00:37 GMT

I have a number of CodePlex projects that I connect to from work and I have had a problem since 2008 that it does not always send my authentication to the proxy server (ISA). What this manifests as is that I get a popup telling me that “Proxy authentication is required”. The workaround was to connect in offline and then click the connect button and everything invariable works with no additional problems.

With Visual Studio 2010 the mater is slightly different. It pops up with a vague error that I had not seen before, but a little searching seamed to indicate that it may be the proxy problem rearing its ugly head in a killer way.

So the “ServicePointManager does not support proxies with the https scheme” error has been seen before when connecting to Windows Communication Foundation services through a proxies. The fix is code based, so that is not something that I can achieve, so I have raised a bug on Connect.

If you are experiencing this problem, then please add your support to the work item:

BUG: Unable to connect to TFS using HTTPS over the Internet from behind ISA

Technorati Tags: Visual Studio 2010 Beta 1,Visual Studio 2010,Codeplex

Why is the VS2010 iso so small?

Martin Hinshelwood — Tue, 19 May 2009 23:14:09 GMT

The reason is simple, it has no MSDN documentation in it. I for one never install the MSDN documentation and just use the online version and have always found it a pain to have it inside the same installation, but may people find it useful.

And, why is there no Offline MSDN documentation? The answer is simple, it is not ready yet…

Technorati Tags: VSTS,Visual Studio 2010 Beta 1,Visual Studio 2010,MSDN

Uninstalling Visual Studio 2010 Beta 1

Martin Hinshelwood — Tue, 19 May 2009 23:10:18 GMT

You may think, why is he uninstalling VS2010? Well, apart from proving that it works…And that it plays well with VS2008 I need to remove the pre-beta beta that I have installed.

This is in fact the second time I have uninstalled VS2010 on this computer, and I had no problems last time, but the difference is that I will be installing a slightly different build :) of Beta 1.

I am hoping that I do not have any problems, but my scenario is largely unsupported.

I have removed visual studio, but it probably left a few trainer that I will need to remove manually. The easiest way is to see what was installed in the last month and check it all… Gruelling I know, but what can you do…

There is a nice little feature in Vista when you are in the programs list that lets you filter the list… coz it can be realy big

Here is he list of software I have installed in the last month:

I have highlighted all of the 2010 bits and it at first seams like there are rather a lot of them, but as you go through the list (I will finish with the .NET 4.0 bits) you find that it is just a cleanup issue..

So I then had some fun uninstalling .NET 4.0…

I know that this was unsupported, and that we were warned us not to do it, but we are developers and we like to push the big red buttons, but I installed the pre-beta beta on my production computer…

During the uninstall there was an infinite number of runtime errors.

And after cancelling and rebooting received lots of .net 4.0 errors for all sorts of applications upon boot.

The same thing happened during my second attempt at uninstalling. The plan now is to try a repair and then an uninstall...

Well, the repair failed, so I am going strait to installing from the new .NET 4.0 Beta 1 release and everything seams to be working ok so far. I realise that my computer will be in an unknown state afterwards, but I can always reinstall when I get the chance.

And after a restart, no problems… Wohooo….

Now to VS2010… And if my infrastructure team get me my VPC there will be TFS fun as Well.

So the end result is that although I have not uninstalled .NET 4.0, I do have the latest version which is what I wanted…

Technorati Tags: Uninstall,.NET Framework 4.0 Beta 1,Visual Studio 2010 Beta 1

Visual Studio 2010 Supports UML

Martin Hinshelwood — Tue, 19 May 2009 04:49:26 GMT

Just in case you have been living in a shed at the bottom of the garden, Visual Studio 2010 is to support UML. As you can see from my diagram, my UML skills are a little, erm, crude. But I think you will get the picture and if you want to do better then just download Visual Studio 2010 on Wednesday if you are not an MSDN subscribe, and if you are… well you can get it today :)

As I have not used UML since university so I do not know if this feature will meet the needs of those that use UML extensively, but I would expect that a lot of time and investment has gone into this area, and if it is lacking in some minor but crucial feature, there is still time to get some changes made…maybe...

Technorati Tags: UML,Visual Studio 2010,Visual Studio 2010 Beta 1

Multi-Targeting in Visual Studio 2010

Martin Hinshelwood — Tue, 19 May 2009 04:46:57 GMT

We thought that we had it good in Visual Studio 2008, being able to target .NET 2.0, 3.0 and 3.5, but in reality they were all running on the .NET 2.0 Runtime, just with a different set of available libraries. Well Visual Studio 2010 take it that little bit further by being able to target .NET 2.0, 3.0, 3.5 and 4.0.

This will be an invaluable feature as, if it turns out to be stable enough, you will be able to build or work on your existing 2.0 Runtime application and websites in Visual Studio 2010. One feature that I was disappointed to see missing is the ability to open project files in both Visual Studio 2008 and Visual Studio 2010 simultaneously, that way you could move some of your developers over to 2010 and have the rest on 2008 on the same project…

But I guess we can’t have everything, and some features will be dropped for the sake of actually getting a product finished…

Well done to the Product teams for this mammoth feet…

Technorati Tags: Visual Studio 2010 Beta 1,Visual Studio 2010,Multi-Targeting,.NET Framework,2.0 Runtime,.NET 3.0,.NET 3.5,.NET 4.0,4.0 Runtime,VSTS,Visual Studio Team System

Connecting VS2010 to TFS 2008

Martin Hinshelwood — Tue, 19 May 2009 04:40:56 GMT

Connecting Visual Studio 2010 to Team Foundation Server 2008 is a snitch… If you have done it from VS200x to TFS200x then you will have no problems understanding what is going on…

Unlike previous versions of Team Suit there is not need to install Team Explorer separately as it comes preinstalled.

As you can see, when connecting to a TFS 2008 server you can see a single Team Projects collection called “Legacy server”, and a list of your projects. For more information about Project Collections try Brian Harry’s blog. Once Connected you have all the usual suspects, but just a little prettier…

Technorati Tags: Visual Studio 2010 Beta 1,Visual Studio 2010,TFS,VSTS,Visual Studio Team System

Installing Visual Studio 2010 Team Suit Beta 1

Martin Hinshelwood — Tue, 19 May 2009 04:39:06 GMT

It’s here, Visual Studio 2010 Beta 1. This is probably the most exciting product to come out of Microsoft since…well… Visual Studio 2008 ;).

The install will be totally familiar to those of you that have installed Visual Studio before, but you will note that there are no options like we had before where we could choose which components we want installed.

What we do get is the option to install for Managed or Native or both, this makes it easier for the those of us who just want all of the bits for the “thing” that we do.

You can, however click “Customize” at the bottom of the page to see the usual bits that, lets be honest, hardly any of us will use :)

I will be doing a full install by ticking both “Managed” and “Native” to get the works…Once you kick off the install you get a much nicer progress tracker.

The install took around 30 minutes, also a big improvement over previous versions, And you are done.

And what does the new welcome page look like?

Mmmmmm…

Technorati Tags: Visual Studio,Visual Studio 2010,VS2010,VSTS2010