Visual Studio 2008 Express Editions Service Pack 1 Beta Readme

This document contains readme notes for the following products:

Table of Contents

1. System Requirements

1.1 Supported Architectures

  • x86
  • x64 (WOW)

    • 1.2. Supported Operating Systems

  • Microsoft Windows XP
  • Microsoft Windows Server 2003 Service Pack 2
  • Microsoft Windows Server 2008
  • Windows Vista

    • 1.3. Hardware Requirements

  • Minimum: 1.6 GHz CPU, 192 MB RAM, 1024x768 display, 5400 RPM hard disk
  • Recommended: 2.2 GHz or higher CPU, 384 MB or more RAM, 1280x1024 display, 7200 RPM or higher hard disk
  • On Windows Vista: 2.4 GHz CPU, 768 MB RAM
  • 1.3 GB of available disk space for the full installation

    2. Known Issues

    2.1. Installing

    2.1.1. General Issues

    2.1.1.1. Visual Studio 2008 Express edition with SP1 Beta is not installed if .NET Framework 3.5 Client Beta 1 is already installed on the computer

    Visual Studio 2008 Express edition with SP1 Beta installation fails to if .NET Framework 3.5 Client Beta 1 is already installed on the computer.

    • To resolve this issue:

    1. Open Add or Remove Programs.
    2. Uninstall "Microsoft .NET Framework 3.5 Client Beta 1".
    3. Uninstall "Microsoft .NET Framework 3.0 Client Beta 1".
    4. Uninstall "Microsoft .NET Framework 2.0 Client Beta 1".

    2.1.1.2 64-bit debugger components are not updated on computers that have the original release versions of 2008 Express Editions installed

    The Remote Debugger Light lets you debug 64-bit applications from the Visual Studio Express editions. If the original release version of a Visual Studio 2008 Express Edition is already present on the computer, installing the 2008 SP1 Beta version does not upgrade the Remote Debugger Light component to the 2008 SP1 level. As a result, some of the new features in 2008 SP1 Beta do not function correctly or are not available when 64-bit applications are debugged. Also, repairing the Visual Studio Express Edition fails at the step that tries to repair the Remote Debugger Light; and repairing any subsequent components fails.

    To resolve this issue:

    1. Before you install the SP1 Beta version of a Visual Studio 2008 Express Edition on a 64-bit version of Windows, open Add or Remove Programs.
    2. Uninstall the Visual Studio 2008 Remote Debugger Light.
    3. Install the SP1 Beta version of the Visual Studio 2008 Express Edition of your choice.

    2.1.1.3 Visual Studio 2008 Express SP1 Beta may fail to upgrade SQL Server to the 2008 February CTP release

    Installing Visual Stuido 2008 Express SP1 Beta on a computer that has earlier versions of SQL Server does not upgrade SQL Server to the 2008 February CTP release (CTP6). SQL Server 2008 CTP6 supports upgrades from the following earlier versions:

    2.1.1.4 Both SQL Server 2005 and SQL Server 2008 appear on a computer after upgrade to Visual Studio 2008 Express SP1 Beta

    After installing a Visual Studio 2008 Express Edition SP1 Beta on a computer that has SQL 2005 Express installed, there are references to 2005 and 2008 versions of SQL on the Start menu and also in Add or Remove Programs.
    SQL Server Express has been upgraded to the 2008 version. The additional references represent SQL Server 2005 Express support files that were not uninstalled. These files do not affect Visual Studio 2008 Express Edition SP1 or SQL 2008 editions.

    To resolve this issue:

    If there are no other named instances SQL 2005, uninstall SQL 2005:
    1. Open Add or Remove Programs.
    2. Remove SQL Server 2005.

    2.1.1.5 Visual Studio 2008 Express Edition with SP1 Beta does not install SQL Server 2008 on Windows XP 64-bit Gold

    SQL Server 2008 will not be installed with Visual Studio 2008 Express Edition with SP1 on computers that are running the Windows XP 64-bit Gold version. SQL Server 2008 has the following minimum operating-system version requirements: For more information about the SQL Server 2008 February CTP release, consult the readme file for SQL Server 2008 CTP at http://go.microsoft.com/fwlink/?LinkId=100093

    To resolve this issue:

    If your operating system is earlier than the minimum operating-system versions that are required for SQL Server 2008, visit Windows Update to upgrade the operating system.

    2.1.1.6 .NET Framework Setup failure in SP1 Beta

    The .NET Framework setup program fails on Windows XP computers that do not have the .NET Framework installed, or that have the .NET Framework version 2.0 or earlier. The reason for this failure is that is an IIS metabase lock is held longer than is required.

    To resolve this issue:

    2.1.1.7 Visual Studio 2008 Express Edition SP1 Beta Setup will not run when a non-Express edition of Visual Studio 2008 is installed on a computer

    Visual Studio 2008 Express Edition SP1 Beta Setup will not run when a non-Express edition of Visual Studio 2008 is installed on a computer. Express Edition Setup reports a Visual Studio servicing issue, and does not continue. Visual Studio 2008 Express Edition SP1 Beta is not supported when it is installed on a computer that has a non-Express edition of Visual Studio 2008.

    To resolve this issue:

    Uninstall the non-Express edition of Visual Studio 2008, before you install an SP1 Beta Express Edition, or upgrade to the SP1 release.

    2.1.1.8 Windows Automatic Update notification appears during Visual Studio Express 2008 Service Pack 1 installation on Windows Vista

    Windows Automatic Update notification to restart computer may appear when Visual Studio Express 2008 with SP1 is being installed on a Windows Vista computer, that does not have .NET Framework 2.0 SP2 and .NET Framework 3.0 SP2 installed. Allowing Windows Update to reboot immediately will fail Visual Studio setup.

    To resolve this issue:

    Postpone the restart until the Visual Studio Express with SP1 installation completes, or Visual Studio Express setup prompts to restart computer.

    2.1.1.9 Visual Studio 2008 SP1 installation fails when .NET Framework 2.0 SP2 unable to upgrade .NET Framework 2.0 or 2.0 SP1

    .NET Framework 2.0 SP2 installation fails on a computer that has the .NET Framework 2.0 or 2.0 SP1 installed and that is running Windows XP, Windows Server 2003, or Windows 2000.

    The .NET Framework 2.0 SP2 setup is a major upgrade that uninstalls earlier versions of the .NET Framework 2.0 and 2.0 SP1. When Windows Installer uninstalls previous versions, it relies on using the cached installation database and all updates. If Windows Installer cannot find the install packages for the earlier installed updates during the uninstall operation in its cache, or original source location, the installation fails. If an incomplete rollback occurs, this failure to install may also cause applications that use the .NET Framework to fail.

    This problem may occur for one of the following two reasons:

    The Windows Installer cache is missing necessary files

    The Windows Installer cache is critical for repairing, for updating, and for uninstalling products. Therefore, you should not remove or modify the contents of the cache. If you change the contents of the cache, you may be prompted for a source when you try to update or to repair Windows Installer-based products.

    Sometimes a Windows Installer Patch (.msp) file that Windows Installer expects to find in the cache may not exist. The following are two common reasons why the .msp file may be missing:

    If this issue occurs, you see the following in the Windows Installer log for the failing installation:

    MSI (s) (D0:B0) [19:05:57:843]: Couldn't find local patch 'C:\WINDOWS\Installer\a4784a.msp'. Looking for it at its source. MSI (s) (D0:B0) [19:05:57:843]: Resolving Patch source.

    You can use the Microsoft .NET Framework Registration Correction Tool to resolve this issue when it occurs when you install the .NET Framework 2.0 SP2. The tool fixes this issue by deleting all hotfix or update registrations that are specific to this update so that maintenance installations do not try to load the specific .msp file.

    You can also try to fix this issue by rebuilding the installer cache. You can typically find the Knowledge Base number for the hotfix or for the update in the lines that follow "Resolving Patch source," as shown in the following example:
    MSI (s) (D0:B0) [19:05:57:859]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (D0:B0) [19:05:57:859]: Note: 1: 1706 2: -2147483647 3: NDP20-KB917283-X86.msp

    To fix the Windows Installer Cache for this example, follow these steps:
    1. Visit the following Microsoft Web site: http://support.microsoft.com/kb/917283 (http://support.microsoft.com/kb/917283) Note You can replace the Knowledge Base article number in the URL with the Knowledge Base article number of the hotfix or the update for which you want to fix the Windows Installer cache.
    2. Download the update.
    3. Extract the .msp file that is inside the hotfix or the update by using the /x command-line switch or the /extract command-line switch.
    4. Copy the extracted .msp file to the location for the missing file. In this example, the location is %windir%\Installer\a4784a.msp.

    The hotfix registration or the update registration is corrupted

    After a hotfix or an update is installed on a Windows Installer-based product, the hotfix registration or the update registration may become corrupted. This problem can occur because of third-party registry cleaner utilities that remove certain registry keys. These keys include the keys that are meant for internal use by Windows Installer. In this case, the "Resolving Patch source" message in the log reads as follows:
    MSI (s) (CC:5C) [03:02:56:181]: Couldn't find local patch ''. Looking for it at its source.
    MSI (s) (CC:5C) [03:02:56:181]: Resolving Patch source.

    Note The location of the hotfix or the update is missing in the log message because of the missing hotfix or upate registration information. In this case, a hotfix or an update is still registered to a product. However, location information for the hotfix or update is missing. Although the file may exist, Windows Installer does not know the path of the file that Windows Installer needs in order to load.
    You can use the Microsoft .NET Framework Registration Correction Tool to resolve this issue when it occurs when you install the .NET Framework 2.0 SP2. The tool fixes this issue by deleting all hotfix or update registration that is specific to this service pack so that maintenance installations do not try to load the hotfix or the update package.

    To resolve this issue:

    If you cannot successfully install the .NET Framework 2.0 SP2 and find the "Resolving Patch source" text in the installation log file as described in the “Cause” section, you can download the Microsoft .NET Framework Registration Correction Tool to resolve this issue.
    The Microsoft .NET Framework Registration Correction Tool resolves both of the issues that the "Cause" section describes.

    The following file is available for download from the Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?FamilyID=0BA6038C-061E-4B4A-9BE9-96A323701260

    The Microsoft Download Center has one version of the tool for each processor architecture that the .NET Framework 2.0 supports (x86, x64, and IA-64). Most customers run a 32-bit version of the operating system. Therefore, these customers need to download and to install the x86 version of the tool.

    Administrators may also use this utility in scripts by passing either the /q command-line switch or the /quiet command-line switch. In this way, you can run the application in silent mode without using a user interface and without using block scripts.

    The tool writes a running log under the %TEMP%\dd_clwireg.txt folder. You can view this log for more information about what the tool is doing.

    Notes

    2.1.1.10 Visual Studio 2008 SP1 Beta Resets Settings to Defaults

    When installing Visual Studio 2008 SP1 Beta on top of Visual Studio 2008, VS user settings are reset to default VS settings. This bug is caused by code originally put in place to reset settings when upgrading minor version of VS, for example from VS Beta1 to VS Beta2 so that VS would have the latest default profile settings. VS does migrate settings from VS 2005 to VS 2008. VS certainly should keep user settings when upgrading to a service pack, which will be fixed for SP1.

    To resolve this issue:

    Backup your VS settings before upgrading to SP1.
    1. Use the "Export Settings" wizard ("Tools" menu, "Import and Export Settings…") to save your current settings
    2. Install SP1 Beta
    3. Use the wizard to import your settings back into VS

    2.1.2. Visual C++ Express Edition

    There are no known issues.

    2.1.3. Visual C# Express Edition

    There are no known issues.

    2.1.4. Visual Basic Express Edition

    There are no known issues.

    2.1.5. Visual Web Developer Express Edition

    There are no known issues.

    2.2. Uninstalling

    2.2.1 General Issues

    2.2.1.1 Uninstalling Visual Studio 2008 Express Edition SP1

    Every Visual Studio 2008 Express Edition SP1 is a complete refresh of the 2008 original release version, and includes its own Setup.

    To resolve this issue:

    To remove an Express Edition from a computer:

    2.2.2 Visual C++ Express Edition

    There are no known issues.

    2.2.3 Visual C# Express Edition

    There are no known issues.

    2.2.4 Visual Basic Express Edition

    There are no known issues.

    2.2.5 Visual Web Developer Express Edition

    There are no known issues.

    2.3. Product Issues

    2.3.1. General Issues

    2.3.1.1. Visual Studio 2005 Express Editions are not compatible with SQL Server 2008 Express Edition and users will be unable to connect to SQL databases after they have upgraded their databases.

    Because SQL Server 2008 Express Edition is not compatible with the Visual Studio 2005 Express Editions, upgrading to SQL Server 2008 Express Edition will overwrite the named instance of the database, and any of the Visual Studio 2005 Express Editions will no longer be able to target the default SQL Server Express instance.

    To resolve this issue:

    Visual Studio 2005 Express Editions are not compatible with SQL Server 2008 Express Edition. Users must upgrade to the Visual Studio 2008 Express Editions to develop SQL database-driven applications.

    2.3.1.2. ClickOnce defaults to SQL Server Express 2005 as a prerequisite package

    When you use ClickOnce to deploy applications that require SQL Server Express 2008, Visual Studio 2008 SP1 Beta Express Editions select the SQL Server Express 2005 prerequisite by default.

    To resolve this issue:

    To deploy SQL Server Express 2008 with your application, you must manually change the prerequisite from SQL Server Express 2005 to SQL Server Express 2008.

    2.3.1.3 Renaming the conceptual model namespace may cause the Entity Designer to display the safe mode watermark

    If the conceptual model contains a type that has the same name as the last part of the storage model, renaming the conceptual model namespace will cause the Entity Designer to display its safe mode watermark. This makes the .edmx file editable only in the XML Editor. For example, if the Entity Data Model contains a type named ‘Store’ and the namespace of the storage model is ‘AdventureWorksModel.Store’, renaming the namespace of the conceptual model will cause this issue.

    To resolve this issue:

    Double-click the related error in the error list. The error number for this error is 34. For example:
    Error 34: Unknown namespace or alias (AdventureWorksModel)
    This will open the model in the XML editor. Rename the namespace to the new namespace name, and then save and close the file.

    2.3.1.4 The Entity Designer displays the safe mode watermark when parameters of a stored procedure that is mapped to a Function Import are modified

    If parameters of a stored procedure that has a corresponding Function Import are added, removed, or changed, then the Entity Designer will display its safe mode watermark. This makes the .edmx file editable only in the XML Editor.

    To resolve this issue:

    Open the EDMX file in the XML editor and either delete the FunctionImport and corresponding FunctionImportMapping (these are in two places in the EDMX file), or change its parameters to correctly map, by count, order, and type, those in the corresponding stored procedure, which will appear as a Function element in the SSDL section.

    2.3.1.5 Code generation throws a System.OutofMemoryException on models that have several hundred tables

    Code generation can fail with a System.OutofMemoryException when code is generated for an Entity Data Model that contans several hundred tables.

    To resolve this issue:

    There is no known workaround.

    2.3.1.6 Undo operations are slow for models that contain more than 100 types

    Undo operations take a long time to complete for Entity Data Models that contain more than approximately 100 entity types.

    To resolve this issue:

    There is no known workaround.

    2.3.1.7 Important Requirement for Windows Vista

    To run Windows Presentation Foundation (WPF) Applications with this package you will need to have installed Windows Vista SP1 or install the Microsoft Visual C++ 2005 SP1 Redistributable Package:

    2.3.2. Visual C++ Express Edition

    2.3.2.1 Debug build of TR1 in VC++ Express creates error when linked to CRT

    If you run a debug build of an application that uses TR1 (new feature) in VC Express SP1 and dynamically links to CRT, you may see an error "Procedure entry point ... could not be located in …msvcp90d.dll".

    To resolve this issue:

    Use applocal or static linking.

    2.3.3. Visual C# Express Edition

    2.3.3.1. "Package Load Failure" in C# Express 2008 SP1 Beta when opening an XML file

    There is a known bug in C# Express 2008 SP1 Beta where adding/opening an XML file in a project after running a WinForms project that includes a data source will result in a "Package Load Failure" error. This bug will be addressed for the SP1 RTM release.

    Repro Steps:
    1. Create a WinForms project
    2. Add a .mdf file as a local data source
    3. Drag a table from the data source wizard on to the WinForm designer
    4. Run the project
    5. Create a new WinForms project
    6. Add a new XML file to the project
    Result:

    The following error message will be displayed:

    Package 'Visual Studio XML Editor Package' has failed to load properly ( GUID = {87569308-4813-40A0-9CD0-D7A30838CA3F} ). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'VCSExpress /resetskippkgs' to re-enable package loading.

    To resolve this issue:

    Select "No" for disabling the package in the future and continue adding the XML file to the project.

    2.3.4. Visual Basic Express Edition

    2.3.4.1 Models that have identical SSDL schema names will cause errors in Website projects

    If a Website project contains Entity Data Models that have the same SSDL namespace (for example, "dbo"), an error that indicates that the project contains conflicting storage namespace names will occur at run time.

    To resolve this issue:

    Change the metadata portion of the connection string in the web.config file from this:
    res://*

    to this:

    res://*/<virtual_root>.<path-to-file>.<filename>.csdl|res://*/<virtual_root>.<path-to-file>.<filename>.ssdl|res://*/<virtual_root>.<path-to-file>.<filename>.msl
    For example, if you have a model in the App_Code folder (App_Code/Model.edmx) in WebSite1, the connection string should look like this:
    res://*/WebSite1.App_Code.Model.csdl| res://*/WebSite1.App_Code.Model.ssdl|res://*/WebSite1.App_Code.Model.msl

    2.3.5. Visual Web Developer Express Edition

    There are no known issues.

    3. Related Links

    3.1. Visual Studio Readme:  http://go.microsoft.com/fwlink/?LinkID=110456

    3.2. .NET Framework Readme:http://go.microsoft.com/fwlink/?LinkId=112154

    © 2008 Microsoft Corporation. All rights reserved. Terms of Use  | Trademarks  | Privacy Statement