All Orcas Beta1 downloads now available

I'm happy to announce that all of the Visual Studio Team System "Orcas" Beta1 downloads are now available.  The VPC images were available a couple weeks ago but last night we finally got the self extracting installer images available for folks that want to install the product themselves on their own machines.  As I've said in previous posts, Orcas Beta1 is the best first beta release we've issued in a long time...we're using parts of it internally and I have no complaints so far. 

So, please take it for a spin and let us know what you think.  We're currently in the process of testing early Beta2 builds and fixing the bugs we've found so your timely feedback will certainly help us ensure that Beta2 is even better.  Please let us know what you think through Connect or leave a comment here...we're really eager to hear from you.

Comments

• Anonymous
  May 03, 2007
  Our good pal Jeff Beehler wrote a good post announcing Beta1 downloads being available. Want to see what

• Anonymous
  May 03, 2007
  Wanted to make sure you all were staying up with the latest events happening with Visual Studio itself.

• Anonymous
  May 10, 2007
  Brian's asking folks about their reaction to Team System "Orcas" Beta1 : We released Orcas Beta 1 a few

• Anonymous
  May 19, 2007
  Orcas Beta1 seems to have a file vssym32.h missing. I have a clean install of Longhorn Beta3 x64 and Orcas. The problem occurs with a new or existing MFC application. Anyway thought I'd let you know. Otherwise it all looks exciting.

• Anonymous
  May 21, 2007
  I asked my friends on the Visual C++ team about this and they suggested the following:   The problem here is that the registry key that references the Windows SDK include path is not populated in the WOW registry hive and hence you get this error. The possible solutions are documented here http://download.microsoft.com/download/9/F/7/9F79D1D8-72FD-407C-88F7-D2254EB4E0AD/VSNETSDKcontents.htm under 1.3.42 and I have also copy + pasted them below: To resolve this issue: The following solution options are available: • Each time after you run vcvars.bat manually, add the appropriate directories from "%systemdrive%Program FilesMicrosoft SDKsWindowsv6.0" to the beginning of your LIB, PATH and INCLUDE environment variables. • Modify "Program Files (x86)Microsoft Visual Studio 9.0Common7Toolsvsvars32.bat" in the following way: Change: :GetWinSDKFolder @call :GetWinSDKFolderHelper HKLM > nul 2>&1 @if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1 @if errorlevel 1 set WinSDKFolder=%VCINSTALLDIR%PlatformSDK @exit /B 0 To: :GetWinSDKFolder @call :GetWinSDKFolderHelper HKLM > nul 2>&1 @if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1 @if errorlevel 1 set WinSDKFolder=%systemdrive%Program FilesMicrosoft SDKsWindowsv6.0 @exit /B 0 This will cause vcvars32.bat to give the correct values each time it is run. • From the IDE, for each platform and directory type, Replace $(WindowsSDKDir) with "%systemdrive%Program FilesMicrosoft SDKsWindowsv6.0" (For example, replace $(WindowsSdkDir)bin with C:Program FilesMicrosoft SDKsWindowsv6.0) • Registry key:

1. Add this registry key: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SDKs
2. Set the value of the key to: "%systemdrive%Program filesMicrosoft SDKswindowsv6.0"