Service Pack 1 (SP1) Beta Release Notes

How to get Visual Studio 2005 SP1 Beta

You can apply for the VS 2005 SP1 Beta by filling out the nomination survey or by signing up on the Visual Studio and .NET Framework "Available Connections" page of the Microsoft Connect (https://connect.microsoft.com/VisualStudio) web site.

After you have been approved, you will receive a link to a Microsoft Connect page where you can download the beta for your licensed copy of Visual Studio 2005.

Supported Languages, Operating System, and Install Requirements

Supported Languages

VS 2005 SP1 Beta provides updates for Visual Studio 2005 English and Japanese language products. All other VS supported languages will be added for the final Service Pack release.

Supported Operating Systems

Microsoft® Windows® 2000 Professional SP4

Microsoft® Windows® 2000 Server SP4

Microsoft® Windows® 2000 Advanced Server SP4

Microsoft® Windows® 2000 Datacenter Server SP4

Microsoft® Windows® XP Professional x64 Edition (WOW)

Microsoft® Windows® XP Professional SP2

Microsoft® Windows® XP Home Edition SP2

Microsoft® Windows® XP Media Center Edition 2002 SP2

Microsoft® Windows® XP Media Center Edition 2004 SP2

Microsoft® Windows® XP Media Center Edition 2005

Microsoft® Windows® XP Tablet PC Edition SP2

Microsoft® Windows ServerT 2003, Standard Edition SP1

Microsoft® Windows ServerT 2003, Enterprise Edition SP1

Microsoft® Windows ServerT 2003, Datacenter Edition SP1

Microsoft® Windows ServerT 2003, Web Edition SP1

Microsoft® Windows ServerT 2003, Standard x64 Edition SP1 (WOW)

Microsoft® Windows ServerT 2003, Enterprise x64 Edition SP1 (WOW)

Microsoft® Windows ServerT 2003, Datacenter x64 Edition SP1 (WOW)

Microsoft® Windows ServerT 2003 R2, Standard Edition

Microsoft® Windows ServerT 2003 R2, Standard x64 Edition (WOW)

Microsoft® Windows ServerT 2003 R2, Enterprise Edition

Microsoft® Windows ServerT 2003 R2, Enterprise x64 Edition (WOW)

Microsoft® Windows ServerT 2003 R2, Datacenter Edition

Microsoft® Windows ServerT 2003 R2, Datacenter x64 Edition (WOW)

Microsoft® Windows VistaT

Patch Installation requirements

• Customers must have a licensed copy of one or more supported Visual Studio 2005 products installed to install the corresponding VS 2005 SP1 Beta.
• Customers must have MSI 3.1 installed on their target machines.
• RAM requirements
• minimum 192MB
• recommended 256Mb or greater.

Service Pack 1 Beta - Deployment License & Support

Scope

No Go Live license is provided for this Service Pack Beta release. Deployment in customer production scenarios is unsupported and solely at the customers discretion.

Service Pack support is provided through Microsoft Connect and other forums
Formal Service Pack customer feedback is supported through Microsoft Connect resources.

Informal community support is also available through online MSDN forums and similar resources.

Even if you have a support contract in place with Microsoft, we will not be able to offer formal support before the final release of the Service Pack.

Fixes included in Service Pack 1 Beta

Please refer to the Visual Studio 2005 SP1 Beta Download on Microsoft Connect (https://connect.microsoft.com/VisualStudio) for details of the fixes included in Service Pack 1.

Related Products

Microsoft SQL Server 2005 Everywhere Edition

Microsoft SQL Server 2005 Everywhere Edition Tools for Visual Studio 2005 SP1 Beta software updates the Smart Device Development components in Visual Studio 2005 SP1 Beta with the latest Microsoft SQL Server 2005 Everywhere Edition design time UI/Dialogs and device CAB files, and includes new features like |DataDirectory| and ClickOnce support for ease of deployment. The download is available at: https://www.microsoft.com/downloads/details.aspx?FamilyID=61289b5d-af86-45dd-8962-e7dcc5221796&displaylang=en

SP1 Beta Known Issues and Workarounds

Note: Heath Stewart, a developer with Developer Division Customer Product-lifecycle Experience (DDCPX), has blogged about the following four issues in response to customer feedback through Microsoft Connect:

Custom Actions under UAC in Windows Vista

Please refer to Heath's blog entry, Custom Actions under UAC in Windows Vista, for more details.

Visual Studio 2005 Service Pack 1 takes a while to install

Please refer to Heath's blog entry, VS 2005 SP1 Takes a While to Install, for more details.

Visual Studio 2005 Service Pack 1 requires a lot of disk space

Please refer to Heath's blog entry, VS 2005 SP1 Requires a lot of Disk Space, for more details.

Visual Studio 2005 Service Pack 1 tries to install multiple times

Please refer to Heath's blog entry, VS 2005 SP1 Tries to Install Multiple Times, for more details.

Uninstall of Visual Studio 2005 Web Application Projects required

Installing VS 2005 SP1 Beta:

Before installing SP1, you should uninstall the Visual Studio 2005 Web Application Projects. After installing SP1, you must run this command:

"c:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe /Setup".

This will flush the assembly cache in ASP.NET and ensure Web Application Projects function correctly.

For customers who missed running the command:

If you get the following error-

"Error: this template attempted to load an untrusted component 'Microsoft.VisualStudio.Web.Application, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. for more information on this problem and how to enable this template, please see documentation on Customizing Project Templates."

-please run this command:

"c:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe /Setup".

Error 1718. Install fails because of digital signature policy violation

Please refer to: https://go.microsoft.com/fwlink/?LinkId=73863 for details.

Visual Web Developer Express SP1 fails to uninstall

Scenario:

Install Visual Web Developer Express.

Install the Web Developer Express SP1.

Uninstall Visual Web Developer Express.

Install Visual Web Developer Express.

Install the Web Developer Express SP1.

Uninstall Visual Web Developer Express.

An error will be encountered.

To get back to a known system state:

Uninstall Visual Web Developer Express.

Install Visual Web Developer Express.

Install the Web Developer Express SP1.

DbgClr debugging 64-bit applications

After installing Service Pack 1 on a machine where DbgClr is installed, DbgClr will be unable to debug 64-bit applications.

Debugging on 64-Bit Installations

When VS SP1 Beta is installed on a 64-bit platform, the vast majority of bugs addressed by the patch will be fixed in Visual Studio but debugger bugs are not fixed when debugging 64-bit applications. In addition, no files in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Remote Debugger will be patched. This includes both the 32-bit and 64-bit components.

There is also a known bug relating to launching 64-bit applications. The following error message may be displayed:

"The Debugger cannot continue running the process.  Unable to start program '<your app>'.  Either the application has not called WSAStartup, or WSAStartup failed."

You can work around this problem by displaying the Start Page in Visual Studio. Click on Tools->Options->Environment and change the "At startup:" option to "Show Start Page".

Installing multiple Windows Embedded CE 6.0 SDKs

When you install multiple Windows Embedded CE 6.0 SDK's based on same OS design, you will see only one SDK in the Visual Studio 2005 SP1 native projects creation wizard.

Scenario:

Install Visual Studio 2005 SP1

Install multiple WINCE6.0 SDKs based on the same OS design

Create new native projects; Click on platforms to select the platform SDKs. Only one SDK will be listed here.

Managed Resource Editor

Trying to add a new Image, Icon or Text File, or an existing file that is not within the project folder or one of its folders will cause Visual Studio to display this error message:

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

Workaround:

Manually move or copy the bitmap or other file into the destination folder in the project (usually the "Resources" folder), and the drag and drop the file from there into the managed resource editor.

Missing MFC lib files

This build of the VS 2005 SP1 Beta is not updating MFC import and static libraries.  As a temporary workaround, applications that link dynamically to MFC may build against VS 2005 released versions of MFC import libraries that are already installed on the computer by VS 2005. Applications that link statically to MFC may switch to link dynamically before a next release of VS 2005 SP1. Upcoming versions of VS 2005 SP1 are going to update both import and static MFC libraries with the newer versions. Applications that link either statically or dynamically to MFC are going to be able to use new SP1 versions of MFC libraries.

Project Properties for Visual Basic Project

Clicking on the "View Application Events" button in the Application property page in a VB project will cause Visual Studio to crash if the ApplicationEvents.vb file does not already exist.

Workaround:

Manually create a file called "ApplicationEvents.vb" in the root of the VB project, and insert the following text:

Namespace My

' The follow events are available for MyApplication:

' Startup: Raised when the application starts, before

' the startup form is created.

' Shutdown: Raised after all application forms are closed.

' This event is not raised if the application terminals

' abnormally.

' UnhandledException: Raised if the application encounters

' an unhandled exception.

' StartupNextInstance: Raised when launching a single-

' instance application and the application is already

' active.

' NetworkAvailabilityChanged: Raised when the network

' connection is connected or disconnected.

Partial Friend Class MyApplication

End Class

End Namespace

Refactoring Performance in ASP.NET Website Projects

A performance optimization has been introduced to improve the performance of invoking a refactoring operation in a solution that contains an ASP.NET website.

Before determining if a .aspx page should be loaded, the refactoring operation will:

Perform a lexical search on the element being refactored to determine if it exists in an .aspx page

Determine if a reference is accessible from the current scope

In Web Application Projects, rename refactoring and find all references are not supported from within .aspx files

Remote Debugging

VS 2005 SP1 Beta cannot be applied on a system that does not contain an installation of Visual Studio. Therefore, machines containing only remote debugging components cannot be serviced by the patch.  To apply the debugger the service pack fixes to these target machines, please replace the remote debugging components installed on each machine with those patched in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Remote Debugger\x86. 

Alternatively, this directory can be shared on your network.  Remote target machines can run msvsmon.exe directly from that share.

Smart Device Data Programming

Installing SQL Server Everywhere 2005 CTP will not allow you to do smart device data programming with Whidbey SP1 Beta.

Scenario:

Install Visual Studio 2005 RTM

Install Visual Studio 2005 SP1

Install SQL Server Everywhere 2005 CTP

Workaround:

Use SQL Mobile that ships with VS 2005 to do smart device data programming. Don't install SQL Serve Everywhere 2005 CTP

Team Foundation Server Readme and Known Issues

This service pack corrects several known issues in Team Foundation Server.

See Visual Studio 2005 Team Foundation Server Readme for more information about Team Foundation Server setup related issue.

See Visual Studio 2005 Team Foundation Server Known Issues for more information about Team Foundation Server non-setup related issues.

Web Application Project Conversion Issues

Conversion of a mixed solution with both C# and J# projects may fail and produce an empty project. Workaround is to only convert each project individually starting with a new instance of Visual Studio.

Canceling the conversion of a project to Web app project may cause an error and leave the project in a half converted state.

The upgrade of a 2003 VB6 WebClass project may fail to complete. The workaround is to close the project, reopen it and rerun the upgrade.

In Web Application projects, when converting VB files or .aspx files, the designer file may not be updated correctly. Workaround is to manually correct the files.

Website Pojects and Web Application Projects General Issues

Web Applications Project system does not detect missing web.config files. Adding a control that requires configuration information will cause a false folder to appear the solution explorer. Workaround is to add a web.config file manually before adding any controls to a Web Application Project.

Web application projects with subprojects that reference controls in the root project may hang the IDE.

PDB and XML files in a website solutions added to TFS source control may not be added source control correctly.

Visual studio will leak memory when operating a Wizard inside a View inside a Multiview. Workaround is to save the solution and restart Visual Studio.

Changes to bin in website and web applications projects can cause Visual Studio to create a shadow copy of the entire bin folder. This copy operation can slow down the performance of Visual Studio and consume a lot of disk space.

If your page and user control exist in different namespaces that are under the same root namespace, the generated code will not compile because the namespace the designer creates for the declaration of the user control inside the page is wrong. The workaround is to delete the declaration from the designer file and put it in the codebehind file. Once moved to the codebehind file it will remain there unaltered -- even if you change the page. This will allow you to work-around the issue.

Installing and uninstalling third party browsers may cause running from F5 and View in Browser to stop working for Web Application Projects. User should check to see if the following registry key is still available:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\IEXPLORE.EXE]
@=""C:\\Program Files\\Internet Explorer\\iexplore.exe""
""Path""=""C:\\Program Files\\Internet Explorer;"""

VS 2005 SP1 Beta Web Application Projects on Windows 2000 may fail to connect to the client side ASP.NET development server. This may cause the build to fail and may hang Visual Studio. This is caused by a race condition between the project system and the development server. The workaround is to configure the project to use the IIS on Windows 2000 avoiding the development server.

When using the Web Application Projects the creation of an event handler by double-clicking the event in the designer may fail when the page class contains one or more overloaded methods. This behavior does not happen when using the Website projects

Publishing a Web Application Project to a read only share will cause Visual Studio to crash. The workaround is to make sure the share is writable.

Third party firewalls may cause Visual Studio to crash.

In Web Application projects, Ctrl-F5 and View in Browser will cause a new instance of IE to be launch instead of using the previous instance.

Website projects fail to nest properly within Web Application projects.

Edit and Continue does not work for Service Pack 1 Beta Web Applications projects.

Adding an image through the properties resource page may cause the display of a false error message.

WSE 3.0 tracing does not work with projects created using the Visual Studio 2005 Web Application Project. Tracing does work as expected in WSE 3.0 for WebSite projects.

Unspecified error when checking in Visual Studio 2003 Web Application after conversion in Visual Studio 2005

Scenario:

Through VS 2003, Create a solution, add a web application and add to source control.

Through VS 2005, Open from source control and choose the solution created in VS 2003 above.

Migration dialog will appear, click Finish button to migrate 2003 solution/project to 2005 solution/project.

Get warning dialog during migration:

Title = "Microsoft Visual Studio"

Message = "One or more projects in the solution could not be loaded for the following reason(s): The project file or web has been moved, rename or is not on your computer. These projects will be labeled as unavailable in Solution Explorer. Expand the project node to show the reason the project could not be loaded"

Buttons = <OK>

The solution is migrated successfully; however, the project is not migrated and becomes unavailable in the Solution Explorer.

Workaround:

Install Visual Studio 2003, Create solution(s).

Install Visual Studio 2005 RTM, Load previous solutions(s) and save them.

Install Visual Studio 2005 SP1 Beta, Load solutions saved in previous step.

CComBSTR change of behavior

This pre-release service pack includes a change of behavior for CComBSTR which impacts some scenarios comparing NULL and "" values in BSTRs. This change is not correct and will not be present in the Release to Market version of the Service Pack.

CFormView memory leak

This pre-release service pack includes changes to CFormView designed to prevent memory leaks in some scenarios. Unfortunately, these changes have also caused crashes in other unrelated scenarios, and will be removed before

Customers working with ARMV4i and ARMV4T board types

Customers working with ARMV4i and ARMV4T board types with instruction set id's

84017153 and 84082689 will not be able to do application deployment, debugging, testing on device through Visual studio.

Workaround:

Make a backup copy of Microsoft.TypeMaps.8.0.xsl located at C:\Documents and Settings\All Users\Application Data\Microsoft\corecon\1.0\addons

In Microsoft.TypeMaps.8.0.xsl after <QISCONTAINER>  (line 6), add the following lines:

<QIS ID="84017153">

<PROPERTYCONTAINER>

   <PROPERTY ID="default" Protected="true">ARMV4I</PROPERTY>

</PROPERTYCONTAINER>

</QIS>

<QIS ID="84082689">

<PROPERTYCONTAINER>

   <PROPERTY ID="default" Protected="true">ARMV4I</PROPERTY>

  </PROPERTYCONTAINER>

</QIS>

Save the file.