Upgrading to Orcas Beta 2

re: Upgrading to Orcas Beta 2

Ned Hamilton — Fri, 27 Jul 2007 18:07:46 GMT

Does Beta 1 have to be uninstalled first?

re: Upgrading to Orcas Beta 2

bharry — Fri, 27 Jul 2007 18:39:47 GMT

Yes, Beta 1 needs to be uninstalled first (if you have it installed).

Brian

re: Upgrading to Orcas Beta 2

Alex Black — Fri, 27 Jul 2007 18:55:58 GMT

Hi Brian, I've uninstalled Beta 1, and installed Beta 2, and installed Team Explorer, but I can't connected to source control, which I think is running on TFS 2005.

In the team explorer tab in VS2008, there is no longer a tree node for 'Source Control'.

In Tools->Options when I go to the source control section, the 'current source control plug-in:' says 'none' and if I pick 'Visual Studio Team Foundation Server', it immediately reverts to None!

Any ideas? I tried uninstalling Team explorer and reinstalling it.

Thanks!

- Alex

re: Upgrading to Orcas Beta 2

David Martin — Fri, 27 Jul 2007 18:57:16 GMT

I have installed the VS 2008 Team Suite Beta 2, and now I'm looking to install the Team Explorer 2008 client. I'm not sure where to download that from. Do I need to download the entire TFS Beta 2 image? Is it included in the VS 2008 Team Suite Beta 2 image?

re: Upgrading to Orcas Beta 2

Alex Black — Fri, 27 Jul 2007 18:59:08 GMT

Hi David, I downloaded the entire VS 2008 Team Foundation Server image and installed the Team Explorer 2008 client from there, though I'm not yet able to connect to source control with it :(

- Alex

Team Build Compatibility between 2005 and 2008

Buck Hodges — Fri, 27 Jul 2007 19:22:13 GMT

The following question came up today, and I thought it would be useful to post. One thing I didn't mention

Team Build Compatibility between 2005 and 2008

Noticias externas — Fri, 27 Jul 2007 19:43:14 GMT

The following question came up today, and I thought it would be useful to post. One thing I didn't

Visual Studio 2008 Beta2 Downloads

Javier G. Lozano — Fri, 27 Jul 2007 20:47:24 GMT

Visual Studio 2008 Beta2 Downloads

Visual Studio 2008 Beta 2, Silverlight, Rosario, and more!

Brain Matter — Sat, 28 Jul 2007 03:42:00 GMT

Visual Studio 2008 Beta 2, Silverlight, Rosario, and more!

re: Upgrading to Orcas Beta 2

bharry — Sat, 28 Jul 2007 14:19:37 GMT

Alex, we connected in email and I've hooked you up with someone on the version control team that should be able to help you. Let me know if that doesn't resolve itself quickly.

David, yes. Team Explorer 2008 comes on the TFS image. You need to download that.

Brian

re: Upgrading to Orcas Beta 2

aelij — Mon, 30 Jul 2007 11:21:57 GMT

Hi Brian,

Can you give some details about upgrading WSS 2 to 3? It is like a normal WSS upgrade?

Thanks,

Aelij.

re: Upgrading to Orcas Beta 2

Harry M — Mon, 30 Jul 2007 12:02:09 GMT

Hi Brian,

any ideas how to move projects frmo a beta 1 server to a beta 2? is there an export/import wizard somewhere?

cheers,

Harry

re: Upgrading to Orcas Beta 2

bharry — Mon, 30 Jul 2007 15:07:15 GMT

Officially migrating data from Beta 1 is not supported. However, the upgrade code was written to support it and it was lightly tested. So, you can try treating a Beta 1 upgrade just like a TFS 2005 upgrade - just un install the Beta 1 and install the Beta 2 and point it at your TFS databases from Beta 1. The install utility should take it from there. Again I can't promise your experience will be seamless but I think it will work.

Yes, WSS2 -> WSS3 is like a normal WSS upgrade. Nothing we do to the WSS site should interfere with that.

Brian

Moving to VSTS 2008 Beta 2

Jeff Beehler's Blog — Wed, 01 Aug 2007 16:34:56 GMT

Hopefully by now you've downloaded Visual Studio Team System 2008 Beta 2 , read Brian's blog on upgrading

VSTS Links - 08/02/2007

Team System News — Thu, 02 Aug 2007 17:59:06 GMT

Jeff Beehler on Watch out Tech Ed 2007 sessions. Rob Caron on Visual Studio Team System 2008 Team Foundation...

re: Upgrading to Orcas Beta 2

Ken — Sat, 04 Aug 2007 00:42:48 GMT

Brian,

Looks like we're having the same problem that Alex reported earlier; we've installed VS2008 B2 on a couple machines [never had B1 there] and VS2008 is unlable to connect to our TFS2005. In fact, no source management providers show up on the list at all.

Thanks.

Ken

re: Upgrading to Orcas Beta 2

bharry — Mon, 06 Aug 2007 17:36:47 GMT

I suspect Alex's solution was different than yours. He had openned a bound solution while Team Explorer was uninstalled and disabled the loading of the TFS package when prompted. His problem was fixed by running

devenv /resetskippkgs

You can try that. Your problem does seem to indicate some kind of a package load failure.

Let me know if that doesn't work and we'll have someone help you diagnose it.

Brian

re: Upgrading to Orcas Beta 2

Brandon — Tue, 07 Aug 2007 22:02:32 GMT

Brian,

Just some feedback on the upgrade process of TFS from TFS v1 to Orcas Beta2. The upgrade process was very smooth this go around. Congratulations. One thing that almost threw me was the lack of progress made while upgrading the .NET Framework to 3.5. The installion sat there for at least 5 to 10 minutes without progressing or giving any indication of progress. It was so long that I almost cancelled the install because I thought it was hung. Anyway, that is my only criticism of the upgrade. By just being patient it successfully upgraded everything and ran the first time.

Brandon

re: Upgrading to Orcas Beta 2

bharry — Tue, 07 Aug 2007 22:49:33 GMT

That's fantastic to hear. I'll pass on the comment about progress and see if there is anything we can do about that. Unfortunately, some of those kinds of things are buried too deep in the installer technologies and are out of our control but I'll check into this one.

Brian

re: Upgrading to Orcas Beta 2

CAB — Thu, 16 Aug 2007 16:27:09 GMT

Run into same problem as Ken, TFS 2005 provider not present in Plug-in Selection...

re: Upgrading to Orcas Beta 2

bharry — Thu, 16 Aug 2007 18:04:57 GMT

Have you tried running...

devenv /ResetSkipPkgs

Brian

re: Upgrading to Orcas Beta 2

CAB — Thu, 16 Aug 2007 18:40:29 GMT

Tried that before, still not present...

re: Upgrading to Orcas Beta 2

hippietim — Thu, 16 Aug 2007 22:55:52 GMT

CAB, please contact me via my blog:

http://blogs.msdn.com/hippietim/contact.aspx

Be sure to include your email address.

Thanks!

re: Upgrading to Orcas Beta 2

bharry — Mon, 20 Aug 2007 16:26:20 GMT

Here some question that may help us determine what is happening:

1. Can you run any of the tf commands from the command line? For example, tf workspaces /s:http://your_server_name:8080

2. Do you have the following registry keys:

a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\SourceControlProviders\{4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}

b. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{D79B7E0A-F994-4D4D-8FAE-CAE147279E21}

3. What is the value of HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\CurrentSourceControlProvider.

a. Do you have write access to this key?

b. Is there any text in the output toolwindow after you attempt to change the Source Control plugin

4. Do you have the file TfsProviderStub.dll in the installation directory? If you installed on C, it would be here: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\VS SCC\TfsProviderStub.dll

5. Verify you have the following files in C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies

a. Microsoft.VisualStudio.TeamFoundation.VersionControl.dll

b. Microsoft.TeamFoundation.VersionControl.Controls.dll

6. What OS?

re: Upgrading to Orcas Beta 2

mbelding — Mon, 20 Aug 2007 23:33:06 GMT

Hi Brian,

I installed VS 2008 Beta 2 over an existing VS 2005. I did not install the beta 1. I do not have any of the registry settings, nor the files in the private assemblies folder. I did install the team system version of the beta. I am using Windows XP SP2. The source control plug in remains my VS 2005 IDE but not in the VS 2008 IDE.

Any ideas would be great

Mike

mbelding@ethicspoint.com

re: Upgrading to Orcas Beta 2

James — Tue, 21 Aug 2007 02:30:06 GMT

I have the same problem as Ken, CAB, and mbelding. Here are the answers to your questions:

1. No, and I noticed that the VS command prompt batch script failed to execute (!) due to my PATH containing the entry "C:\Program Files\Microsoft DirectX SDK (February 2006)\Utilities\Bin\x86" with the quotes; I had to remove the quotes before I could get a VS command prompt.

a. No

b. No

3. (Default): {00000000-0000-0000-0000-000000000000}

ProviderRegKey: Software\Microsoft\SourceSafe

4. No.

a. No

b. No

6. XP SP2. I have VS 2005 installed but have not installed any previous Orcas or .NET Framework 3+ beta.

Sounds to me like the installer just forgot to install TFS source control. I looked in the installer's "Custom" install page for a TFS source control feature, but couldn't find any entries for it (I selected every feature available).

I did have trouble during the install; the first time it failed. I uninstalled and tried again and it finished installing the second time. But I can't find any entries in the installer's "Custom" page relating to TFS source control.

Here's the abridged contents of my about box if it's any help:

Microsoft Visual Studio 2008

Version 9.0.20706.1 Beta2

Microsoft .NET Framework

Version 3.5

Installed Edition: Enterprise

Microsoft Visual Basic 2008

Microsoft Visual C# 2008

Microsoft Visual C++ 2008

Microsoft Visual Studio 2008 Tools for Office

Microsoft Visual Studio Team System 2008 Beta 2 Architecture Edition

Microsoft Visual Studio Team System 2008 Beta 2 Test Edition

Microsoft Visual Web Developer 2008

Microsoft Web Application Projects 2005

Version 9.0.20706.1

Microsoft Visual Studio Team Edition for Database Professionals Version 9.0.20706.1

Visual Studio Team System 2008 Beta 2 Development Edition

re: Upgrading to Orcas Beta 2

Andre — Tue, 21 Aug 2007 18:27:10 GMT

I've recently installed VS2008 Beta 2 and Team Explorer. When trying to check in items, I get the following error:

internal error in Changeset Comments Policy

(Note that using VS2005 on the same machine does not exhibit this error.)

I can override the policy, but this is obviously less than ideal. I understand this may be related to our use of the TFS Power Tools under VS2005, and that they are not yet compatible with VS2008.

Does this make sense? Is there any current workaround, and is it likely that this error will "go away" once the Power Tools are released for VS2008?

Thanks,

Andre

re: Upgrading to Orcas Beta 2

bharry — Tue, 21 Aug 2007 20:52:55 GMT

James,

It looks like (based on the about box and the install logs) you have not installed the Team Explorer yet. This is what allows you to connect to Team Foundation Server. If you are using VS 2008, tt's in the TFS download link you'll find here: http://blogs.msdn.com/bharry/archive/2007/07/26/orcas-beta-2-download-urls.aspx

If you are using VS 2005, you will need to find your TFS 2005 install disk.

I think it's in a folder called TFC (for Team Foundation Client).

Brian

re: Upgrading to Orcas Beta 2

bharry — Tue, 21 Aug 2007 21:12:19 GMT

Andre,

I think you've nailed it. The problem is that the Checkin policy power tools are compiled against the TFS 2005 assemblies but are loaded in VS2008 which uses the TFS 2008 assemblies.

We'll be releasing updated Power Tools for VS 2008 in the next few months. You can either wait until then or you can try to muck around with setting assembly binding policies in your devenv.exe.config file to cause the older TFS assemblies to be redirected to the newer ones.

Brian

re: Upgrading to Orcas Beta 2

James — Wed, 22 Aug 2007 01:28:58 GMT

Why is the TFS plugin not included on the "Team System" "Team Suite" DVD? The nomenclature is highly confusing.

re: Upgrading to Orcas Beta 2

bharry — Wed, 22 Aug 2007 03:04:30 GMT

You ask a good question and I wish I had a better answer. It starts with some history. TFS 2005 originally shipped at a different time than VSTS 2005 (it was about 3-4 months late). That's why it wasn't originally included in the VSTS client SKUs.

In VSTS 2008 TFS will be shipping at the same time and we originally intended to combine the setups. Unfortunately, when we costed all of the work we needed to do, it didn't fit so we had to cut it. At that time status quo kicked in and we left things the way they were.

The TFC setup has to be on the TFS disk because you can purchase TFS and CALs and use TFS without buying VSTS client SKUs. However, there's no reason we couldn't drop the TFS client onto the DVD with the VSTS role SKUs. The only problem might be the amount of space on the DVDs.

I've just kicked off a thread to discuss the possibility of including it on the disk. We'll see where that goes.

Thanks,

Brian

re: Upgrading to Orcas Beta 2

James — Wed, 22 Aug 2007 03:46:20 GMT

Ah, I figured it was something like that. I notice the TFC setup directory is 600 MB; ouch! I hope you can squeeze it on (and hopefully include a link in the autorun.exe so people realize it's there). Thanks for your reply and effort in improving this!

re: Upgrading to Orcas Beta 2

Rupak Ganguly — Mon, 22 Oct 2007 20:10:04 GMT

Brian,

We have a TFS 2005 which we connect via Team Explorer 2005 and VS 2005. Now, we have installed VS2008 Beta 2 on some machines to evaluate it. The VS2008 installed side-by-side with a hitch. Now, I want to connect to TFS 2005 from my VS 2008. Here is what I want to know:

1. Since I already have Team Explorer 2005 installed and can connect to my TFS 2005 via VS 2005 Team Suite, do I need to install Team Explorer 2008 to be able to connect to the same TFS 2005 via VS 2008 Team Suite?

2. Connecting to TFS 2005 with Team Explorer 2008 via VS 2008 will not chnage anything in the TFS 2005 that might jeopardize my development setup or source code in my real world of VS2005 environment?

Any help will be greatly appreciated.

re: Upgrading to Orcas Beta 2

bharry — Tue, 23 Oct 2007 08:41:20 GMT

1) Yes, you will need to install Team Explorer 2008. It is required to integrate with VS 2008. It will work with either a TFS 2005 or TFS 2008 server.

2) Generally, that's right. There's only two things to be mindful of. Don't use TE 2008 to edit your checkin policies because after you do, they won't be editable in TE 2005. And don't use TE 2008 and edit your build definitions because that will cause some limitations for TE 2005. Other than that, there should be no issues whatsoever.

Brian

re: Upgrading to Orcas Beta 2

Pam — Wed, 31 Oct 2007 20:33:00 GMT

Brian,

Our team is installing TFS Beta 2--mostly for the purpose of evaluating source control and process stuff. However, I'd like to be able to continue to use VS2005 as my development platform.

We've installed the server component, and I've installed the Client components on my development machine. Is there a way that I can access the TFS 2008 tool from within my VS2005 IDE? (I.e., How do I get the "Connect to team foundation server" item on my tools menu?)

Thanks,

Pam

re: Upgrading to Orcas Beta 2

bharry — Wed, 31 Oct 2007 20:36:31 GMT

You will need to install Team Explorer 2005 to get client integration with your VS 2005 IDE. Team Explorer 2005 will work with the TFS 2008 server just fine.

Brian

re: Upgrading to Orcas Beta 2

Pam — Wed, 31 Oct 2007 20:37:33 GMT

Wow! Thanks for the lightning fast response! Much appreciated...

re: Upgrading to Orcas Beta 2

Andy — Mon, 10 Mar 2008 17:23:23 GMT

Is there a list of known issues anywhere pertaining to the use of VSTS 2008 with TFS 2005? My team is trying to use these together and has run into some pretty serious problems. Thanks.

-Andy

re: Upgrading to Orcas Beta 2

bharry — Sun, 20 Apr 2008 23:15:35 GMT

I have blogged a few minor issues in my blog posts on TFS 2008 features and compatibility. However, none of them are serious (of course, that can always be in the eye of the beholder). If you could list some examples of issues you are seeing, I might be able to help you.

Brian