Microsoft has announced the release of the first beta of the Visual Studio 2005 Service Pack 1. Currently it can only be downloaded via the Microsoft Connect site (registration required). It is currently available in English and Japanese. The final version is expected to be available in 3 to 4 months.
In order to release the service pack sooner, it will not contain updates required to ensure Vista capability. Also, it is confirmed that Vista will ship with .Net 3.0 pre-installed.
Visual Studio 2002 and 2003 will not be supported on Vista for development. Applications using those versions can be compiled using XP and run on Vista. For more information, see Somasegar's Web Log.
Finally, VB6 will be supported on Vista. For more information, see the Support Statement for Visual Basic 6.0 on Windows Vista.
For those of you still waiting for your Microsoft Connect registration to be approved, here is a partial list of fixes included in the service pack:
- Update to the Web Project Conversion Wizard in Visual Studio 2005
- You receive LNK2001 and LNK1120 error messages when you use the Vcbuild.exe command-line tool to build a Visual C++ solution
- The customized color code marker that is actually added may differ from the customized color code marker that you try to add in Visual Studio 2005
- The IDE stops responding when you work with nested generic types in C# in Visual Studio 2005
- A native application takes a long time to start when you try to debug the application by using Visual Studio 2005
- You may receive an error message when you rebuild a solution and try to view a Windows Form in Design view in Visual Studio 2005
- IntelliSense may stop working, and Visual Studio may crash, when you try to open a large Managed C++ project in Visual Studio 2005
- The IDE stops responding when you build a project that generates lots of text in the Output window in Visual Studio 2005
- An attributed ATL-based COM server unexpectedly exits in Visual Studio 2005
- The browser may stop responding when you scroll through a Visual J# 2005 Web page that contains a J# Browser Control
- Error message when you use the debugger in Visual Studio 2005 to debug an MFC class library application: "Managed Debugging Assistant 'Loader Lock' has detected a problem in '
'" - You may receive Visual Basic compiler error messages when you are developing a Visual Basic 2005 project in Visual Studio 2005
- Visual Studio 2005 may stop responding when you build a Web application project that is checked out of Visual SourceSafe
- Update to support Visual Studio 2005 Web Application Projects
- An access violation may occur when you try to run a Visual C++ 2005 application that contains OMG CORBA IDL code
- Error message when you use certain code patterns that involve the IDisposable interface in the Visual Studio 2005 C++ compiler: "Fatal error C1001"
- You may receive an incorrect error message when you open a Visual Studio 2005 Tools for Office document
- All the applications that use the C run-time library may not start after you install Visual Studio 2005 and then you uninstall Visual Studio 2005 without restarting the computer
- Error message when you try to use the Visual SourceSafe 2005 LAN booster service together with Visual Studio 2005 on a server that is running Windows 2000: "Unable to use SourceSafe LAN service"
- The Visual Studio 2005 IDE stops responding when you work with a large Visual C++ .NET solution in Visual Studio 2005
- The report does not print the first time that you click Print when you try to print the report from the Report Viewer control in Visual Studio 2005
- The Visual Studio 2005 IDE may corrupt the deployment files for a Web Setup Project and for a Setup Project
- The position of the Properties window may not be saved after you exit Visual Studio 2005 on a dual-monitor system
- The Cole Property Page object of a Visual C++ application may be deleted when the Bound Property Changed function is invoked, and Visual Studio 2005 may unexpectedly close (crash)
- Custom build steps may not run when you add the custom build steps to a Visual C++ 2005 Win32 static library project in Visual Studio 2005
Japanese, Chinese, or Korean characters in resource files may be overwritten by question marks after you convert a Visual C 6.0-based project to Visual Studio 2005 - You may experience performance issues when you use solutions that contain large Visual Basic projects in Visual Studio 2005
- The Atls.pdb file and the Atlsd.pdb file contain incomplete debugging information when you debug an ATL-based C++ application in Visual Studio 2005
- A floating-point exception may occur when an inline function in a C++ application returns an uninitialized floating-point variable in Visual Studio 2005
- You may experience slow performance and increased memory usage when you start the debugger for a Visual C++ project in Visual Studio 2005
- MS Project Work Item Publish Error
- How to rebuild the C++ STL library for Visual Studio 2005
- You may receive an error message when you try to build a Web project that references a .NET Compact Framework 2.0 assembly in Visual Basic 2005
- You may receive an error message when you consume an assembly that has an obfuscated generic type in Visual Studio 2005
- You may receive a "Fatal error C1902" error message and a solution build may fail when you try to use the AT command or a scheduled task to automate a build of a C or C++ project in Visual Studio 2005
- You may experience slow performance when you work with a Visual Basic solution that contains many projects in Visual Studio 2005
- Visual Studio 2005 exits unexpectedly when you try to edit an existing Data Table object or add a new Data Table object to the dataset that you are editing