Visual Studio 2008 Service Pack 1 Beta Readme

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
  • Microsoft Windows Server 2008
  • Windows Vista

    • 1.3. Hardware Requirements

  • 3.8GB of space on the system drive, with an additional 600 MB available on the drive which Visual Studio is installed on.
        Note: You can use the Disk Cleanup utility available in Start -> Programs -> Accessories -> System Tools to remove temporary files.  
  • Minimum: 1.6 GHz CPU, 1024x768 display, 5400 RPM hard disk
  • Recommended: 2.2 GHz or higher CPU, 1280x1024 display, 7200 RPM or higher hard disk 
  • On Windows Vista: 2.4 GHz CPU

    • 2. Known Issues

    2.1. Installing

    2.1.1.SQL Server Compact 3.5 SP1 Beta for Devices is not installed with Visual Studio 2008 SP1 Beta. It is available as a Web download

    The Windows installer (.msi) file for SQL Server Compact for Devices contains the mobile device runtime files that are required for installing SQL Server Compact on mobile devices. Installing Visual Studio 2008 SP1 Beta on the released version of Visual Studio 2008 does not update the SQL Server Compact 3.5 for Devices .msi file to the SP1 version.

    To resolve this issue:

    Download the .msi file for SQL Server Compact 3.5 for Devices SP1 Beta from the Microsoft Download Center Web site.

    2.1.2. Visual Studio 2008 SP1 Beta is not installed if .NET Framework 3.5 Client Beta 1 is already installed on the computer

    Installation of Visual Studio 2008 SP1 Beta fails when .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".

    2.1.3. During Visual Studio 2008 SP1 Beta installation or uninstallation, a message box asks the user to close Setup

    During installation or uninstallation of .Net Framework 3.5 SP1 Beta, .Net Framework 3.0 SP2 Beta, and .Net Framework 2.0 SP2 Beta, this message appears: "The following application should be closed before continuing with setup:"
    The list of applications shown contains the setup itself, as follows:
    Microsoft .NET Framework 3.5 SP1 Beta Setup
    setup

    To resolve this issue:

    Click "Ignore" and continue with setup.

    2.1.4.Visual Studio 2008 SP1 cannot be installed when SilverLight Tools is installed on the computer

    Microsoft Visual Studio 2008 Service Pack 1 (Beta) will not install if you have Silverlight Tools already installed on your system. The following error message will show up if you attempt the installation:
    "Microsoft Visual Studio 2008 SP1 (Beta) does not apply, or is blocked by another condition on your system. Please click the link below for more details."
    If you wish to apply Visual Studio 2008 Service Pack 1 to your Visual Studio 2008 installation, you must first uninstall Silverlight Tools.

    To resolve this issue:

    Uninstall steps for Silverlight Tools are as follows:

    For Vista or newer:
    1. Open the Remove Programs dialog from the Control Panel
    2. Uninstall Silverlight Tools Beta for VS2008
    3. Click 'View installed updates' in the task bar on the left
    4. Remove KB949325 (it will be listed under your version of VS2008)
    For pre-Vista systems:
    1. Open the Add/Remove Programs dialog from the Control Panel
    2. Uninstall Silverlight Tools Beta for VS2008
    3. Click 'Show updates' at the top of the window
    4. Remove KB 949325 (it will be listed under your version of VS)
    Optional addendum to both:
           5.   Uninstall Silverlight 2 SDK (this will also uninstall the ASP.NET server controls used for hosting Silverlight applications). Uninstalling is not required.
     
    Important: if you don't perform step 4 - Remove KB 949325 - the Service pack installation will proceed but several Service Pack files won't be installed in your machine, leaving Visual Studio 2008 on an inconsistent state. Should you reach this point in the installation process, take the following steps to fix it:
    1. Uninstall Visual Studio (only the product to which KB 949325 applies; this will only affect core VS components)
    2. Re-install Visual Studio (this will replace the core components uninstalled by the previous step)
    3. Run the SP1 beta installer again

    2.1.5. Visual Studio 2008 SP1 is incompatible with Silverlight 2 Beta 1 Visual Studio Tools

    Silverlight Tools Beta 1 for Visual Studio 2008 is incompatible with Visual Studio 2008 SP1 Beta. Also, you cannot install Silverlight Tools Beta 1 for Visual Studio 2008 on a computer that is running Visual Studio 2008 SP1 Beta.

    To resolve this issue:

    You must uninstall Silverlight Tools Beta 1 for Visual Studio 2008 before you install Visual Studio 2008 SP1 Beta.

    2.1.6 SQLPubWiz 1.2 fails to be installed on Visual Studio 2008 SP1

    SQL Publishing Wizard cannot be installed in Visual Studio side-by-side installations.
    SQL Publishing Wizard installation fails when you try to install a version of Visual Studio 2008 or Visual Web Developer Express 2008 on a computer where the service pack of these products is already installed. This is because Visual Studio 2008 SP1 installs a later version of SQL Publishing Wizard than the one that is included in Visual Studio 2008 or Visual Web Developer Express 2008, and SQL Publishing Wizard will not be installed if a later version is detected.

    Existing scenarios include:
    Attempting to install Visual Studio 2008 English on a computer that has Visual Web Developer SP1 English already installed.
    Attempting to install Visual Studio 2008 Japanese on a computer that has Visual Studio 2008 SP1 English or Visual Web Developer SP1 English already installed.
    The Setup program will finish and display this error message: "The following component failed to install: Microsoft SQL Publishing Wizard." However, both products will work with no loss of functionality.

    To resolve this issue:

    There is no known workaround.

    2.1.7 .NET Framework Setup Failure in SP1 Beta

    The .NET Framework Setup 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.8 It takes a long time for the Visual Studio 2008 SP1 Installation Log to be displayed after blocked content is permitted in Internet Explorer

    After blocked content is permitted in Internet Explorer, it may take a long time for the Visual Studio 2008 SP1 Beta Installation Log to be displayed.

    To resolve this issue:

    There is no known workaround.

    2.1.9 Visual Studio 2008 SP1 progress window reports "Install failed - rolling back" and then reports success on a finish page

    The Visual Studio 2008 SP1 Beta progress window may report "Install failed - rolling back" during upgrade, but the finish page reports that Setup has been completed successfully. This is caused by incorrect progress reporting for one of the Setup packages, and does not represent the result of an operation.

    To resolve this issue:

    You can disregard this message in the progress window. If the finish page reports success, all updates have been installed successfully.

    2.1.10 All instances of Visual Studio 2008 must be upgraded to SP1

    On the computers that have multiple instances of Visual Studio 2008 products, all instances should be upgraded to SP1. Visual Studio 2008 products rely on shared resources. Therefore, upgrading just one instance may bring other Visual Studio 2008 products into an unsupported state.

    To resolve this issue:

    Upgrade all editions of Visual Studio 2008 on a computer to SP1.

    2.1.11 Admin Deployment of Visual Studio 2008 SP1

    The Visual Studio 2008 SP1 uses a conditional download manager/patch installer, which detects and installs only patches that are applicable on the computer where it is running. For admin deployment, a full package layout should be created on the server computer.

    To resolve this issue:

    To create full layout of Visual Studio 2008 SP1:
    1. Download the VS90sp1_KB945140.exe SP1 installer to a temp folder of your choice, for example, C:\VS90SP1.
    2. Open a Command Prompt window (on Windows Vista, use administrator mode).
    3. Execute the following command to download all Visual Studio 2008 SP1 packages:
      VS90sp1-KB945140-ENU.exe /createlayout <full target folder path> /passive
      For example:
      VS90sp1-KB945140-ENU.exe /createlayout C:\VS90SP1\Layout /passive
      This will download the complete Visual Studio 2008 SP1 payload, including the SP1 setup program (SPInstaller.exe), and to the specified folder (for example, C:\VS90SP1\Layout), but it will not install it.
    4. Download the full .NET Framewor 3.5 SP1 redistributable from http://go.microsoft.com/fwlink/?LinkId=115068 into previously created C:\VS90SP1\Layout folder, and save it as dotnetfx35setup.exe, overwriting the existing file.

    To deploy the package on your network:
    1. Copy the created Layout folder to a shared network location.
    2. Execute SPInstaller.exe from client computer by using the following command:
      <full network path>SPInstaller.exe /q /log %temp%\VS90SP1.htm /promptrestart
      For example: \\server\VS90SP1\Layout\SPInstaller.exe /q /log %temp%\VS90SP1.htm /promptrestart

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

    Windows Automatic Update notification to restart computer may appear when Visual Studio 2008 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 Service Pack 1 installation completes.

    2.1.13 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.14 Visual Studio SP1 Hotfix KB944899 must be uninstalled prior to installing Visual Studio 2008 SP1

    Hotfix KB944899 must be uninstalled before Visual Studio 2008 SP1 is installed. The KB944899 hotfix addresses performance issues when stepping through downloaded source code, most likely the .NET Framework Source Library. The performance enhancements that are included in the KB944899 hotfix are also included in Visual Studio 2008 SP1.

    The patch authoring for other hotfixes is also incorrect. Any other Visual Studio Hotfix can also write the registry entry for this hotfix. After uninstalling KB944899 from the Installed Updates, the registry entries must be removed from under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\ for KB944899 as well.

    To resolve this issue:

    Remove KB944899 before installing Visual Studio 2008 SP1.

    For Vista or later:
    1. Open Control Panel
    2. Click on "Programs"
    3. Click on "View installed updates"
    4. Remove KB944899 listed under any versions of Visual Studio 2008
    For earlier operating systems:
    1. Open Control Panel
    2. Click on "Add / Remove Programs"
    3. Check "Show updates"
    4. Remove KB944899 listed under any versions of Visual Studio 2008
    If any other patches are installed on Visual Studio 2008 that you see in the list of updates, please open an elevated command prompt and run the following:
    1. Check for other references to KB944899:
      reg.exe query HKLM\Software\Microsoft\Updates /f KB944899 /k /s
    2. For each search result returned, copy the full key name (including spaces) and run the following command to delete them, replacing {key} with the search result: reg.exe delete "{key}" /f

    2.1.15 SQL Publishing Wizard in rare occasions causes SP1 install to fail

    If Visual Studio 2008 SP1 Installation fails and rolls back, install SQL Publishing Wizard separately and attempt the installation again.

    To resolve this issue:

    1. Download SqlPubWiz.msi from http://go.microsoft.com/fwlink/?LinkId=108983
    2. Open a Command Prompt (in Vista OS, Run as Administrator)
    3. Change the path in the Command Prompt to the folder where SqlPubWiz.msi was downloaded
    4. Type: msiexec /i sqlpubwiz.msi IsInvokedFromVs=1
    5. Then install VS2008 Sp1 Beta

    2.1.16 Visual Studio 2008 SP1 cannot be installed because of a file with an invalid signature

    When installing Visual Studio 2008, you might run into an error dialog that reads:
    "Error 1330.A file that is required cannot be installed because the cabinet file D:\msdn\cab2.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt."
    The path and name of the cabinet may be different, but might often be D:\msdn\cab2.cab, where D: refers to your DVD drive.

    To resolve this issue:

    The cause can vary from machine to machine. Therefore, there are several possible workaround you should try. If the following workarounds do not resolve the issue, please contact Microsoft Customer Support Services at http://support.microsoft.com.

    Install KB925336 on Windows Server 2003
    If you're attempting to install Visual Studio 2008 SP1 on Windows Server 2003, please install KB925336 from http://support.microsoft.com/kb/925336, reboot your machine when prompted, and try installing Visual Studio 2008 SP1 again.

    Install KB938759 on Windows Server 2003
    If you're attempting to install Visual Studio 2008 SP1 on Windows Server 2003, please install KB938759 from http://support.microsoft.com/kb/938759, reboot your machine when prompted, and try installing Visual Studio 2008 SP1 again.

    Defragment your hard drive
    Run Scan Disk and then defragment your hard drive and trying installing Visual Studio 2008 SP1 again.
    On Vista:
    1. Click on Start
    2. Click on Computer
    3. Right click on the drive Windows is installed on (you will see a Windows icon on it; typically C:)
    4. Select Properties
    5. Click on the Tools tab
    6. Click on the Check Now button under the Error-checking group
    7. Check "Automatically fix file system errors"
    8. Click the Start button
    9. After the scan is complete, close Close to return to the drive properties
    10. Click on the Defragment now button under the Defragmentation group
    11. Click on the Defragment now button
    On Windows XP and Server 2003:
    1. Click on Start
    2. Click on My Computer
    3. Right click the drive Windows is installed on (typically C:)
    4. Select Properties
    5. Click on the Tools tab
    6. Click on the Check Now button under the Error-checking group
    7. Check "Automatically fix file system errors"
    8. Click the Start button
    9. After the scan is complete, close Close to return to the drive properties
    10. Click on the Defragment now button under the Defragmentation group
    11. Click on the Defragment button

    Copy installation to the hard drive
    Copy the entire contents of your Visual Studio 2008 DVD or ISO to your hard drive or a network share and install from that location. If you receive this error while attempting to install Visual Studio 2008 SP1, please try installing Visual Studio 2008 SP1 again and when prompted to insert your DVD, browse to the location where you copied your DVD to your hard drive and select the .msi file for which you're being prompted.

    Close all running applications
    Verifying a digital signature can require a lot of memory. Try shutting down all unnecessary running applications to free memory.

    Change how Windows optimizes performance
    Having Windows optimize for the active application may eliminate this problem.
    On Vista:
    1. Click on Start
    2. Click on Control Panel
    3. Click on System and Maintenance
    4. Click on Settings
    5. Click on Advanced system settings
    6. Click on the Settings button under Performance
    7. Click on the Advanced tab
    8. Select Programs under Processor scheduling
    9. Click OK
    10. Click OK again
    If asked to reboot, please reboot your machine and try installing Visual Studio 2008 SP1 again.
    On Windows XP and Server 2003:
    1. Click on Start
    2. Click on Control Panel
    3. Double click on System
    4. Click on the Advanced tab
    5. Click on the Settings button under Performance
    6. Click on the Advanced tab
    7. Select Programs under Processor scheduling
    8. Click OK
    9. Click OK again
    If asked to reboot, please reboot your machine and try installing Visual Studio 2008 SP1 again.

    2.2 Uninstalling

    2.2.1 Uninstalling Visual Studio 2008 SP1 updates

    The Visual Studio 2008 SP1 is a set of patches and upgrades that should be uninstalled individually.
    After a complete uninstall of all Visual Studio 2008 SP1 updates, the remaining Visual Studio 2008 editions must be repaired to restore features that may have been replaced during the SP1 update. Microsoft .NET Framework 3.5 SP1 is not uninstalled, and we recommend that you leave it on the computer because it is backwards compatible with earlier versions of Visual Studio.

    To resolve this issue:

    To uninstall SP1 components:
    To restore Visual Studio 2008 to a supported RTM state:
    1. If any SP1 Express editions were installed, uninstall them by using the instructions above.
    2. If SP1 was applied to any Visual Studio 2008 non-Express edition, uninstall SP1 updates by using instructions above.
    3. For every instance of Visual Studio 2008 in Add or Remove Programs:
      1. Click Change/Uninstall to open Visual Studio Setup in maintenance mode.
      2. Click Repair/Reinstall on the maintenance mode screen to cause Setup to repair existing features.
    4. For every instance of Visual Studio 2008 in Add or Remove Programs:
      1. Click Change/Uninstall to open Visual Studio Setup in maintenance mode.
      2. Select Add or Remove Features on the maintenance mode screen.
      3. Clear and then select one of the features in the product feature tree, or add or remove any components you want to modify.
      4. Click Update to cause Setup to refresh the installed Visual Studio components.

    2.3. Product Issues

    2.3.1. General Issues

    2.3.1.1. Stand-Alone Profiler not updated by Visual Studio 2008 SP1 Beta.

    Stand-Alone Profiler is not updated by Visual Studio 2008 SP1 Beta.

    To resolve this issue:

    You can update the Stand-Alone Profiler manually by copying the required files from a computer that has the updated Visual Studio Profiler installed (Team Suite or Team Developer Edition).

    x86 Stand-Alone Profiler: From an x86 computer that has Visual Studio 2008 Profiler installed and updated by Visual Studio 2008 Beta SP1, copy the files in %SystemDrive%\Program Files\Microsoft Visual Studio 9\Team Tools\Performance Tools\ and paste them in the corresponding location on the computer you want to update. Also, copy %SystemDrive%\windows\system32\vsperf90.dll and paste it in the system32 directory on the computer you want to update.

    x64 Stand-Alone Profiler: From an x64 computer that has Visual Studio 2008 Profiler installed and updated by Visual Studio 2008 Beta SP1, copy the files in %SystemDrive%\Program Files (x86)\Microsoft Visual Studio 9\Team Tools\Performance Tools\ and paste them in the corresponding location on the computer you want to update. Also, copy %SystemDrive%\windows\system32\vsperf90.dll and %SystemDrive%\windows\sysWow64\vsperf90.dll and paste them in the corresponding directories on the computer you want to update.

    2.3.1.2.Remote Debugger is not patched by Visual Studio 2008 SP1 Beta

    If the Remote Debugger is installed on a computer that does not also have Visual Studio installed (Professional or Team Editions), the Remote Debugger is not updated by the Visual Studio SP1 installation.

    To resolve this issue:

    To update the Remote debugger components, manually copy the Remote Debugger files from a computer that has a patched Visual Studio 2008 SP1 Professional Edition or Team Edition installed. The corresponding SP1 Beta compiler must be installed on the computer you are copying from. For example, to upgrade the x64 Remote Debugger to SP1 Beta, the x64 SP1 Beta compiler must be installed on the computer you are copying from.

    x86 Remote Debugger: From an x86 computer, copy the files in %SystemDrive%\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86\ and paste them in the corresponding location on the computer you want to update.

    x64 Remote Debugger: From an x86 or x64 computer, copy the files in %SystemDrive%\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x64\ and paste them in the corresponding location on the computer you want to upgrade.

    IA64 Remote Debugger: Copy the files in %SystemDrive%\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\ia64\ from an x86 computer that has a Visual Studio SP1 Team Edition and paste them in the corresponding location on the computer you want to upgrade.

    2.3.1.3.After the Visual Studio 2008 SP1 Beta is installed, WCF debugging may be disabled

    After the Visual Studio SP1 Beta is installed, WCF debugging may be disabled. The debugger may not be able to do the following tasks:
    1. Step into or out of WCF functions.
    2. Automatically attach to projects that contain WCF services.
    3. Display a logical callstack that shows the client and server.

    To resolve this issue:

    1. On the Start menu, click Run.
    2. Execute the following command: "%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\vsdiag_regwcf.exe" -i
    3. Restart the application. If the application is in IIS, IIS must also be restarted.

    2.3.1.4. Visual Studio 2008 SP1 Beta does not create a Setup program to install the .NET Framework 3.5 SP1 Beta

    By default, .NET Framework 3.5 SP1 Beta is not included in deployment packages. Visual Studio 2008 SP1 Beta does not find the correct location to download and install the .NET Framework 3.5 SP1 Beta.

    To resolve this issue:

    For the English version:
    Note: We recommend that you do not deploy applications that you create using SP1 Beta for use in production environments.
    If you want to do a test deployment of your application with the .NET Framework 3.5 SP1 Beta, edit the XML file that stores the version of the .NET Framework and the download location.

    1. Open the package.xml file from the following location:
      a. On a 32-bit computer:
      %ProgramFiles%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35\en
      b. On a 64-bit computer:
      %ProgramFiles (x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35\en

    2. Update the element by using the following code.
    3. Change the name of the package to the following. .NET Framework 3.5 SP1 Beta
    4. Change the link for the download site to the following. http://go.microsoft.com/fwlink/?LinkId=110173
    5. The new Microsoft Pre-Release Software License Terms for the .Net Framework 3.5 SP1 Beta can be found at the following location:
      a. For a 32-bit computer:
      %windir%\Microsoft.NET\Framework\v3.5\Microsoft .NET Framework 3.5 SP1 (Beta)\
      b. For a 64-bit computer:
      %windir%\Microsoft.NET\Framework64\v3.5\Microsoft .NET Framework 3.5 SP1 (Beta)\
    6. For the English language version of the Microsoft Pre-Release Software License Terms, copy the eula.1033.rtf file to the same location as the package.xml file. Delete the existing eula.rtf file found at that location, and then rename eula.1033.rtf to eula.rtf.
    7. Open the Prerequisites dialog box:

      a. If you are using ClickOnce:
      i. On the Project menu, click ProjectName Properties.
      ii. Click the Publish tab of the Project Designer, and then click Prerequisites.

      b. If you are using Setup Projects:
      i. In Solution Explorer, click the setup project.
      ii. On the Project menu, click Properties.
      iii. Click the Prerequisites button.

    8. Select Download from the component vendor Web site.
      Note: You must select the option to download from component vendor Web site. Selecting any other option will revert the package back to .Net Framework 3.5.
    For the Japanese version:
    Note: We recommend that you do not deploy applications that you create using SP1 Beta for use in production environments.
    If you want to do a test deployment of your application with the .NET Framework 3.5 SP1 Beta, edit the XML file that stores the version of the .NET Framework and the download location.

    1. Open the package.xml file from the following location:
      a. On a 32-bit computer:
      %ProgramFiles%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35\ja
      b. On a 64-bit computer:
      %ProgramFiles (x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35\ja

    2. Update the element by using the following code.
    3. Change the name of the package to the following. .NET Framework 3.5 SP1 Beta
    4. Change the link for the download site to the following. http://go.microsoft.com/fwlink/?LinkId=110173
    5. The new Microsoft Pre-Release Software License Terms for the .Net Framework 3.5 SP1 Beta can be found at the following location:
      a. For a 32-bit computer:
      %windir%\Microsoft.NET\Framework\v3.5\Microsoft .NET Framework 3.5 SP1 (Beta)\
      b. For a 64-bit computer:
      %windir%\Microsoft.NET\Framework64\v3.5\Microsoft .NET Framework 3.5 SP1 (Beta)\
    6. For the Japanese language version of the Microsoft Pre-Release Software License Terms, copy the eula.1041.rtf file to the same location as the package.xml file. Delete the existing eula.rtf file found at that location, and then rename eula.1041.rtf to eula.rtf.
    7. Open the Prerequisites dialog box:

      a. If you are using ClickOnce:
      i. On the Project menu, click ProjectName Properties.
      ii. Click the Publish tab of the Project Designer, and then click Prerequisites.

      b. If you are using Setup Projects:
      i. In Solution Explorer, click the setup project.
      ii. On the Project menu, click Properties.
      iii. Click the Prerequisites button.

    8. Select Download from the component vendor Web site.
      Note: You must select the option to download from component vendor Web site. Selecting any other option will revert the package back to .Net Framework 3.5.

    2.3.1.5 The EntityDataSource control does not appear in Toolbox

    After upgrading Visual Studio 2008 with SP1 beta, the EntityDataSource control will not appear in Toolbox.

    To resolve this issue:

    To add the control:
    1. Create a Web Application
    2. Right click on the Toolbox over the "Data" group and select the "Choose Items…" option
    3. Scroll down in the list of components under ".NET Framework Components" until you find "EntityDataSource"
    4. If "EntityDataSource" is not in the list, click on the "Browse" button and add the assembly "System.Web.Entity.dll" from "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5" (or equivalent)
    5. Ensure the checkbox next to the component is marked and click on the OK button

    2.3.1.6 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.3.2. ADO.NET

    2.3.2.1. 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 name, and then save and close the file.

    2.3.2.2. 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 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.2.3. 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 contains several hundred tables.

    To resolve this issue:

    There is no known workaround .

    2.3.2.4. Undo operations are slow for models that contain more than 100 entity 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.2.5 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.3. Languages

    There are no known issues.

    2.3.4. LINQ

    There are no known issues.

    2.3.5. Visual Studio Tools for Office

    There are no known issues.

    2.3.6. Web Development

    There are no known issues.

    2.3.7. Windows Communication Foundation (WCF) Tools

    There are no known issues.

    2.3.8. Windows Presentation Foundation (WPF) Designer for Visual Studio

    There are no known issues.

    2.3.9. Windows Workflow Foundation (WF) Tools

    There are no known issues.

    2.3.10. Windows SDK Integration

    2.3.10.1. Uninstalling the Windows SDK can affect Visual Studio 2008

    If you install either the Windows SDK for Windows Vista or the Windows SDK Update for Windows Vista, and then uninstall the Windows SDK, registry keys that are required by Visual Studio to find Windows headers, libraries, and tools are removed.

    To resolve this issue:

    Do one of the following things:

    2.3.10.2. Running a custom installation of the Windows SDK may change file link paths to point to non-existent files

    Running a custom installation of the Windows SDK may change file link paths to point to non-existent files. If you have Visual Studio 2008 installed and then install the Windows SDK, an important registry key is changed. That key points to the SDK tools and also to Windows headers and libraries. However, if you run a custom installation of the Windows SDK that includes neither tools nor headers and libraries, the link to those files will be broken and some Visual Studio functionality will be broken.

    To resolve this issue:

    SEither repair Visual Studio 2008 or use the Windows SDK Configuration Tool, which is installed together with the Windows SDK for Windows Server 2008 and .NET Framework 3.5., to point to the expected version of either the Windows Headers and Libraries and/or the tools installed by the Windows SDK.

    2.3.10.3. Installing Windows SDK for Server 2008 after Visual Studio 2008 breaks the Visual Studio command-line build environment

    After you install the Windows SDK for Windows Server 2008, you are no longer able to build at the Visual Studio 2008 command prompt. You receive an error that csc, vbc, and/or msbuild commands are not recognized. You can build without problems in the Visual Studio IDE.

    To resolve this issue:

    The VC++ compilers that are installed with the Windows SDK are overwriting vcvars32.bat incorrectly.

    To resolve this issue:

    Repair the Visual Studio 2008 command-line build environment by editing c:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat manually.
    Close all instances of Visual Studio.
     Use Notepad to edit the file %\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat.
    Change the top few lines where the variables are set.

    To set the correct path of the FrameworkDir, change these lines:

    @SET VSINSTALLDIR=C:\Program Files\Microsoft Visual Studio 9.0
    @SET VCINSTALLDIR=C:\Program Files\Microsoft Visual Studio 9.0\VC
    @SET FrameworkDir=Framework32
    @SET FrameworkVersion=v2.0.50727
    @if "%VSINSTALLDIR%"=="" goto error_no_VSINSTALLDIR
    @if "%VCINSTALLDIR%"=="" goto error_no_VCINSTALLDIR

    To the following lines:

    @SET VSINSTALLDIR=c:\Program Files\Microsoft Visual Studio 9.0
    @SET VCINSTALLDIR=c:\Program Files\Microsoft Visual Studio 9.0\VC
    @SET FrameworkDir=c:\Windows\Microsoft.NET\Framework
    @SET FrameworkVersion=v2.0.50727
    @SET Framework35Version=v3.5
    @if "%VSINSTALLDIR%"=="" goto error_no_VSINSTALLDIR
    @if "%VCINSTALLDIR%"=="" goto error_no_VCINSTALLDIR
    Open the Visual Studio command-line build environment and verify that you can build successfully.

    3. Related Links

    3.1. Visual Studio Express Edition Readme:  http://go.microsoft.com/fwlink/?LinkID=111607

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

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