Visual Studio 2008 Service Pack 1 (SP1) Readme

Table of Contents

·     1.1. Supported Architectures

·     1.2. Supported Operating Systems

·     1.3. Hardware Requirements

·     2.1. Installing

·     2.2. Uninstalling

·     2.3. Product Issues

·             2.3.1. General Issues

·             2.3.2. ADO.Net

·             2.3.3. Languages

·             2.3.4. LINQ

·             2.3.5. Visual Studio Tools for Office

·             2.3.6. Web Development

·             2.3.7. Windows Communication Foundation (WCF) Tools

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

·             2.3.9. Windows Workflow Foundation (WF) Tools

·             2.3.10. Windows SDK Integration

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.8 GB available on the system drive, plus 600 MB on the drive on which Visual Studio is installed
    Note: You can use the Disk Cleanup utility 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 Microsoft Synchronization Services for ADO.NET 1.0 for Devices installation requirements

Microsoft Synchronization Services for ADO.NET 1.0 for Devices is not installed together with VS2008 SP1. Users must download the .msi file before Local Database Cache funtionality in Smart Device projects can be enabled.

To resolve this issue:

Download the Microsoft Synchronization Services for ADO.NET 1.0 for Devices .msi file from the Download center and install it.

http://www.microsoft.com/downloads/details.aspx?FamilyId=75FEF59F-1B5E-49BC-A21A-9EF4F34DE6FC&displaylang=en

2.1.2 Visual Studio 2008 SP1 installation fails and the message "A connection with the server could not be established" is displayed

Visual Studio 2008 SP1 installation fails and the message "A connection with the server could not be established" is displayed.
These are the possible causes for such a failure:

The most likely cause is a firewall on the target computer.

To resolve this issue:

Add an exception to the firewall for SPInstaller. This will stop the firewall from blocking communications required by SpInstaller. Then run the Visual Studio 2008 SP1 installation again.
On a Windows XP computer:

  1. Open the Control Panel.
  2. Click "Windows Firewall".
  3. Click the "Exceptions" tab.
  4. Click "Add programs".
  5. Add SPInstaller to the list of programs.
  6. Click "OK".
  7. Restart the computer.

On a Windows Vista computer:

  1. Open the Control Panel.
  2. Click "Windows Firewall".
  3. Click "Allow a program through Windows Firewall".
  4. Click the "Exceptions" tab.
  5. Click "Add programs".
  6. Add SPInstaller to the list of programs.
  7. Click "OK".
  8. Restart the computer.

2.1.2  Installation of SQL Server on Windows 7 RC generates a compatibility warning

When you try to install SQL Server 2008 RTM or SQL Server 2005 RTM/SP1/SP2 on Windows 7 RC, you may receive a warning that SQL Server has known compatibility issues with this version of Windows.  Because SQL Server is redistributed by Visual Studio, installations in which the user selects to install SQL Server together with Visual Studio may be affected.  The issues that trigger the compatibility warning have been fixed in SQL Server 2008 SP1 and SQL Server 2005 SP3.

To resolve this issue:

Install Visual Studio 2008 and select to install SQL Server 2005 Express Edition SP2 (selected by default). 

1.     During installation, click “Run Program” when you receive the compatibility warning. 

2.     After installation is completed, download and install SQL Server 2005 Express Edition SP3 here. (NOTE: The x64 version is located near the bottom of the page.)

3.     During SQL Server 2005 Express Edition SP3 setup, make sure to upgrade the already installed instance.

4.     You can verify your version of SQL Server 2005 Express Edition by following the instructions here.

As an alternative, you can install SQL Server 2005 Express Edition SP3 before you install Visual Studio 2008. 

More Information

·         Download SQL Server 2005 Express Edition SP3

·         Download SQL Server 2005 SP3 (non-Express)

·         Download SQL Server 2008 SP1

If you have to install SQL Server 2008 on Windows 7 RC and want to avoid the warning messages, you can create the SQL Server 2008 with Service Pack 1 package yourself.  Follow the steps described by Peter Saddow:   Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

2.1.3 Uninstalling a patch may downgrade files in other Visual Studio products

When Visual Studio 2008 SP1 is applied to multiple products on a computer, for example, to Visual Studio 2008 English and Visual Studio 2008 Spanish, uninstalling SP1 from either will downgrade files for the other Visual Studio 2008 products.

To resolve this issue:

Repair the products that still have Visual Studio 2008 SP1 installed, or uninstall SP1 from those products as well.

For Windows Vista or later:

1. Open Control Panel.
2. Click "Programs".
3. Click "Uninstall a program".
4. Select an edition of Visual Studio 2008 that still has SP1 installed.
5. Click "Uninstall/Change".
6. Click "Continue" to elevate if prompted.
7. Click "Next" when Setup components have been loaded.
8. Click "Repair/Reinstall".

For operating systems earlier than Windows Vista:

1. Open Control Panel.
2. Click "Add or Remove Programs".
3. Click "Uninstall/Change".
4. Click "Next" when Setup components have been loaded.
5. Click "Repair/Reinstall".

2.1.4 Visual Studio 2008 SP1 installation fails when the Windows Vista sidebar is enabled.

Visual Studio 2008 SP1 installation fails when the Windows Vista sidebar is on.

To resolve this issue:

1. Right-click the Sidebar icon in the notification area, at the far right of the taskbar.
2. Click "Exit".

2.1.5 Each language version of Visual Studio requires the matching language version of the service pack

Installing mismatched language versions of Visual Studio 2008 RTM and Visual Studio 2008 SP1 can result in broken features or mixed-language UI.
Supported scenarios:

To resolve this issue:

  1. Uninstall Visual Studio 2008 SP1.
  2. Perform a Maintenance Mode repair of Visual Studio 2008 RTM.
  3. Install the matching language version of Visual Studio 2008 SP1.

2.1.6 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:

Perform either of the following actions:

2.1.7 Visual Studio 2008 SP1 will not install MSDN Library for Visual Studio 2008 SP1 during Setup

During installation of Visual Studio 2008 SP1, MSDN Library for Visual Studio 2008 SP1 will not be installed on your computer.

To resolve this issue:

MSDN Library for Visual Studio 2008 SP1 is available as a separate download. See Microsoft Download Center.

2.1.8 SQL Server Compact 3.5 SP1 for Devices Windows installer (MSI) file is not installed with Visual Studio 2008 SP1, but it is available as a download

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

To resolve this issue:

SQL Server Compact 3.5 SP1 for Devices MSI is available as a download on the Microsoft Download Center.

2.1.9 Windows Automatic Update notification appears during Visual Studio 2008 SP1 installation on Windows Vista

Windows Automatic Update notification to restart the 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 restart immediately will cause Visual Studio Setup to fail.

To resolve this issue:

Postpone the restart until Visual Studio SP1 installation is finished.

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

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

The .NET Framework 2.0 SP2 Setup uninstalls earlier versions of the .NET Framework 2.0 and .NET Framework 2.0 SP1. When Windows Installer uninstalls earlier versions, it uses the cached installation database. During the uninstall operation, if Windows Installer cannot find the installation packages for the earlier updates in its cache, or the 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 either of these reasons:

The Windows Installer cache is missing required files.

The Windows Installer cache has been changed. The cache is critical for repairing, for updating, and for uninstalling products. Therefore, do 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:
- A tool that finds and deletes large files or rarely used files on the hard disk has been run.
- The owner of the %windir%\Installer directory is changed from SYSTEM or from Administrators.

If this issue occurs, the Windows Installer log for the failing installation will show something that resembles the following:
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. 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 in 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 may be 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 requires to load.

You can use the Microsoft .NET Framework Registration Correction Tool to resolve this issue when it occurs. 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 .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.

Microsoft .NET Framework 2.0 Registration Correction Tool

The Microsoft .NET Framework Registration Correction Tool resolves both of the issues that the “Cause” section describes.
The following file is available for download on the Microsoft Download Center:

Download the Microsoft .NET Framework 2.0 Registration Correction Tool package now.
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 should download and 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
- The Microsoft .NET Framework Registration Correction Tool is designed to be used with any current version of the .NET Framework.
- You must be an administrator to run this utility.

2.1.11 All instances of Visual Studio 2008 must be upgraded to Service Pack 1

On computers that have multiple editions of Visual Studio 2008 products, including language editions, all editions should be upgraded to Service Pack 1. Visual Studio 2008 products rely on shared resources and upgrading just one edition may bring other Visual Studio 2008 editions into an unsupported state.

To resolve this issue:

Upgrade all editions of Visual Studio 2008, including language editions, to Service Pack 1.

2.1.12 Uninstalling Visual Studio 2008 SP1 Beta may result in a report that a cabinet has an invalid digital signature

Uninstalling Visual Studio 2008 SP1 Beta or running the Visual Studio 2008 Patch Removal Tool may generate message 1330 (Cabinet has an invalid digital signature) and may prompt for the installation source.

This problem is most often caused by intermittent disk read errors or network transfer issues.

To resolve this issue:

Uninstall Visual Studio 2008 SP1 Beta or re-run the Visual Studio 2008 Patch Removal Tool.

If the problem persists,

1. If you use the Visual Studio 2008 Patch Removal Tool, save it to your local hard disk.
2. Copy Visual Studio 2008 RTM installation files from the original media, or network location, to a local directory (for example, %TEMP%\VS2008).
3. Remove the original installation media or disconnect the network cable.
4. Uninstall Visual Studio 2008 SP1 Beta again or re-run the Visual Studio 2008 Patch Removal Tool and specify the local path of the Visual Studio 2008 installation files when you are prompted for source.

2.1.13 Visual Studio Repair should not be run from media after SP1 installation

After you install Visual Studio SP1, do not run Visual Studio Repair from the original release (RTM) installation media.  Packages that are installed with Visual Studio 2008 SP1 are newer and can only be repaired by using Add or Remove Programs because they are not present on the original release installation media.

To resolve this issue:

To repair Visual Studio 2008 SP1:

1. Open Add or Remove Programs from the Control Panel.
2. Select Visual Studio 2008 and click Change.
3. Select Repair Visual Studio in the maintenance window.

The following components must be repaired separately by using Add or Remove Programs:

- Microsoft .NET Compact Framework
- Microsoft Remote Debugger
- Microsoft Visual Studio Tools for Office
- Microsoft SQL Server Compact Edition
- Microsoft Windows Mobile SDK

2.1.14 Repair of Visual Studio 2008 Standard Edition with Service Pack 1 on x64 computers fails

The detection logic for Visual Studio Repair is incorrect because a registry value is missing.  This occurs only on x64 computers that have Visual Studio Standard installed.

To resolve this issue:

1. Open Windows Explorer.

2. Navigate to ..Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x64.

3. Record the file version of msvsmon.exe.  (Right-click properties and examine them, or just hover over them and read the tool tips.

4. Open Regedit, and add two string registry values, both named "Version", that contain the current version string at:

      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Remote Debugger Lite Setup\9.0\1033

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Remote Debugger Lite Setup\9.0\1033

2.1.15 Microsoft SQL Server Database Publish Wizard 1.3 is not fully repaired from Add or Remove Programs

If you try to repair 'Microsoft Sql Server Database Publishing Wizard 1.3' (the version that gets installed with Visual Studio 2008 Service Pack 1 or Visual Web Developer 2008 with SP1) by using Add or Remove Programs, you might encounter one of the following problems:

a. Repair button is not available under 'Microsoft Sql Server Database Publishing Wizard 1.3' component.

b. Repair button is available, but performing a repair causes an older version of the wizard 'Microsoft Sql Server Database Publishing Wizard 1.2' to be installed.

c. Repair button is available, but performing a repair causes a prompt for the source of SqlPubWiz.msi.

 

To resolve this issue:

Windows XP / Vista

1. Open Control Panel and go to Add or Remove Programs.

2. Right-click the component 'Microsoft Sql Server Database Publishing Wizard 1.3' (or 'Microsoft Sql Server Database Publishing Wizard 1.2' if this older version was installed due to (b) above), and then click Uninstall. Wait for uninstallation to finish.

3. Run SqlPubWizInstaller.exe from http://go.microsoft.com/fwlink/?LinkId=119368  to re-install 'Microsoft Sql Server Database Publishing Wizard 1.3'. You can verify that it was installed by looking in Add or Remove Programs.

2.1.16 Visual Studio 2008 SP1 blocks installation when there are incompatible Beta components installed on the computer

Because the following pre-release programs and updates prevent Visual Studio 2008 SP1 from being installed successfully, they must be removed before Visual Studio 2008 SP1 is installed:
- Microsoft Silverlight Tools Beta 1
- Microsoft Visual Studio 2008 - KB949325
- Microsoft Visual Studio 2008 - KB944899 (v1)
- Microsoft Visual Studio 2008 - KB945140 (SP1 Beta)
To remove these programs, we recommended that you run the automated Visual Studio 2008 Service Pack Preparation Tool. This tool removes the specified updates and programs from your system and restores the integrity of any Visual Studio 2008 features that may have been compromised during manual removal of the Visual Studio 2008 SP1 Beta release.

To resolve this issue:

1. Visit the Visual Studio 2008 Service Pack Preparation Tool download page at http://go.microsoft.com/fwlink/?LinkID=121685&clcid=0x409.
2. Follow the instructions on the page to download and run the tool.

2.1.17 Visual Studio 2008 Service Pack 1 cannot be installed on a non-English VSTT computer because Visual Studio Tools for Office 3.0 language pack is present

When you install the update for Visual Studio 2008 SP1, you may see a Windows Installer 1638 error because the Visual Studio Tools for Office 3.0 language pack is already installed. This occurs if non-English Visual Studio Team Test 2008, and the VSTO 3.0 runtime and corresponding language pack, are installed. The VSTO 3.0 runtime may also be installed in other Visual Studio products such as Team Foundation Client.
"ERROR_PRODUCT_VERSION 1638 Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel."

To resolve this issue:

1. Uninstall the Visual Studio Tools for Office 3.0 Runtime Language Pack by using Add or Remove Programs (in Windows XP) or Programs and Features (in Windows Vista).
2. Re-run the Visual Studio 2008 SP1 setup (SPInstaller.exe).

2.1.18 Installing Visual Studio 2008 SP1 Breaks Windows SDK Configuration Tool

Installing Visual Studio 2008 SP1 breaks the Windows SDK Configuration tool in the Windows SDK for Windows Server 2008 and .NET Framework 3.5. This tool is used to set the version of Windows SDK headers, libraries and tools you wish to build with in Visual Studio. After installing VS 2008 SP1, the Configuration tool will crash with an unhandled exception on an X86 computer. The tool’s UI will be displayed with a blank dialog box on an X64 computer. This issue does not affect VS 2008 Express SKUs.

The Configuration tool depends on a registry key value that is overwritten with invalid content by the Service Pack patch. After the SP1 patch is installed, the HKLM\Software\Microsoft\Microsoft SDKs\Windows\v6.0a subkey ProductVersion is set to “v6.0A”. The tool expects this value to be a build number with the format 6.xxx.xxx.xxx. On an X64 computer, an additional registry key is overwritten with the invalid value: HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v6.0A@ProductVersion.

To resolve this issue:

Repair Visual Studio 2008 to reset the ProductVersion value.

  1. Open the Control Panel and select Products and Features (Add/Remove Programs on pre-Vista operating systems)
  2. Select Microsoft Visual Studio 2008 and click on Uninstall/Change. The Visual Studio 2008 Setup wizard will launch.
  3. When prompted, choose to Repair/Reinstall Visual Studio 2008. (This will not remove the Service Pack.)

Alternatively, advanced users can update the registry key(s) manually to set a ProductVersion value of “6.0.6001.17011”. Review the article, Windows registry information for advanced users before editing the registry.

An additional workaround is necessary to use the SDK Configuration in GUI mode on VS 2008. Refer to the Windows SDK Blog post, WinSDK bug notification: SDK Config Tool appears to work but fails.

2.1.19 Admin Deployment of Visual Studio 2008 SP1

This method allows deployment through Microsoft Systems Management Server (SMS) or other software distribution tools. The network administrator initially runs setup to create a full Visual Studio SP1 layout on a network share, which is then deployed by running setup in unattended mode. Creating a full layout is necessary to prevent setup from downloading payload packages from the Internet. When running in unattended mode, Service Pack 1 setup will silently update all detected Visual Studio 2008 instances in a given language. If errors occur, setup exits silently with a failure. Each SP1 layout targets a specific language, mulptiple layouts may need to be created in environments with different language versions of Visual Studio. Service Pack 1 setup will fail silently, if a system does not have targeted language installed.

To deploy the components using SMS, you must follow these steps:

  1. Create full SP1 layout
  2. Create the component package
  3. Create the component program
  4. Create the component distribution point
  5. Create the component advertisement


Step 1: Create full SP1 layout

  1. Create a folder on the server. For example, <drive>:\VS90SP1
  2. Download Microsoft Visual Studio 2008 Service Pack 1 (installer) and save it locally on a machine (i.e. %Temp%\VS90sp1-KB945140-ENU.exe)
  3. From the Start menu, choose Run
  4. Type the following command to initiate download of all SP1 payload components to created directory:
    %TEMP%\VS90sp1-KB945140-ENU.exe /createlayout <drive>:\VS90SP1 /q

    Note: The download (~850Mb) may take some time depending on your connection speed. The Service Pack 1 can then be installed by calling SPInstaller.exe from the created layout that includes complete set of SP1 updates in a given locale. For manual deployment, /q parameter can be replaced with /passive to display download/install progress.

Step 2: Create the component package

  1. Click Start, point to Programs, and then click Systems Management Server to open the SMS Administrator console.
  2. In the Site Database tree, right-click Packages, point to New, and then click Package.
  3. On the General tab of the Package Properties dialog box, add the following values to the appropriate fields.

Field

Value

Name

Microsoft Visual Studio 2008 Service Pack 1

Version

SP1

Publisher

Microsoft

Language

<Component Language>

 

  1. On the Data Source tab, click to select the check box for This package contains source files, and then click Always obtain files from source directory.
  2. Click Set.
  3. In the Set Source Directory dialog box, click Local drive on site server, and then click Browse.
  4. In the Browse for Folder dialog box, select the folder for the component that you are installing (e.g. <drive>:\VS90SP1).
  5. Click OK three times to close the dialog boxes.


Step 3: Create the component program
Each SMS package contains at least one SMS program. The SMS program is a command-line program that runs on each destination computer to control how the package runs.

  1. Under Packages in the Site Database tree of the SMS Administrator console, expand the appropriate node.
  2. Right-click Programs, point to New, and then click Program.
  3. On the General tab of the Program Properties dialog box, type Microsoft Visual Studio 2008 SP1 in the Name box. Then, type SPInstaller.exe /q /norestart value in the Command Line box.
  4. In the After running list, select the appropriate value that is based on the following list.
  5. On the Environment tab, click to clear the check box for User input required, and then click Run with administrative rights.
  6. Click OK to close the Program Properties dialog box.


Step 4: Create the component distribution point
SMS distribution points are shares on site systems. You copy the package source files to an SMS distribution point so that client computers can access the source files.

  1. Under the appropriate node in the Site Database tree of the SMS Administrator console, right-click Distribution Points, point to New, and then click Distribution Points.
  2. In the New Distribution Points Wizard, click Next.
  3. Select the distribution point to which you want to copy the package.
  4. Click Finish.


Step 5: Create the component advertisement
An advertisement specifies what program is available to the client computers, which computers receive the advertisement, and when the program is scheduled for installation.

  1. In the Site Database tree of the SMS Administrator console, right-click Advertisements, point to New, and then click Advertisement.
  2. On the General tab of the Advertisement Properties dialog box, type Microsoft Visual Studio 2008 SP1 in the Name box.
  3. In the Package list, select the appropriate component.
  4. In the Program list, select the appropriate component program.
  5. Click Browse, and then select the collection of computers to which you want to deploy the program.
  6. Click OK to close the Advertisement Properties dialog box.

2.2 Uninstalling

There are no known issues.

2.3 Product Issues

2.3.1 General Issues

2.3.1.1 Enable Samesite for the .NET Framework 3.5 SP1 bootstrapper package

If the .NET Framework 3.5 SP1 bootstrapper package is selected in the Prerequisite dialog box for a Setup project or in ClickOnce publishing, and also the "Download prerequisites from the same location as my application" option is selected, the following build error is shown: 

The install location for prerequisites has not been set to 'component vendor's web site' and the file 'dotNetFx35setup.exe' in item 'Microsoft.Net.Framework.3.5.SP1' cannot be located on disk.

To resolve this issue:

Update the Package Data

  1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
  2. Edit the Product.xml file in Notepad.
  3. Paste the following into the < PackageFiles > element:
    <PackageFile Name="TOOLS\clwireg.exe"/>
    <PackageFile Name="TOOLS\clwireg_x64.exe"/>
    <PackageFile Name="TOOLS\clwireg_ia64.exe"/>
  4. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001
  5. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above
  6. Save the product.xml file

 

Download and Extract the Core Installation Files

  1. Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
  2. Download the dotNetFx35.exe file to your local disk.
  3. Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
  4. At the command prompt, type:
    dotNetFx35.exe /x:.
    This will extract the Framework files to a folder named “WCU” in the current directory.
  5. Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
    o DotNetFx35SP1 (folder)



You may now delete the files and folders you downloaded and extracted in steps 2 and 4.

 

Download the Language Pack Support Files

  1. Refer to the Table below for the download locations.
  2. Navigate to the URL provided, and when prompted, download to the subdirectory of the dotNetFx35SP1 folder that is indicated in the table. Note: You must do this once for the x86, and also the x64 files, even if you do not have to support x64 with your package.

 

Language

Architecture

Source URL

Destination

Chinese (Simplified)

x86

http://go.microsoft.com/fwlink?LinkID=118146

zh-CHS\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118151

zh-CHS\DotNetFX35\x64

Chinese (Traditional)

x86

http://go.microsoft.com/fwlink?LinkID=118087

zh-CHT\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118050

zh-CHT\DotNetFX35\x64

English

x86

N/A

N/A

x64

N/A

N/A

French

x86

http://go.microsoft.com/fwlink?LinkID=118148

fr\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118153

fr\DotNetFX35\x64

German

x86

http://go.microsoft.com/fwlink?LinkID=118149

de\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118154

de\DotNetFX35\x64

Italian

x86

http://go.microsoft.com/fwlink?LinkID=118097

it\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118115

it\DotNetFX35\x64

Japanese

x86

http://go.microsoft.com/fwlink?LinkID=118096

ja\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118114

ja\DotNetFX35\x64

Korean

x86

http://go.microsoft.com/fwlink?LinkID=118147

ko\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118152

ko\DotNetFX35\x64

Portuguese – Brazil

x86

http://go.microsoft.com/fwlink?LinkID=118092

pt-BR\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118110

pt-BR\DotNetFX35\x64

Russian

x86

http://go.microsoft.com/fwlink?LinkID=118090

ru\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118108

ru\DotNetFX35\x64

Spanish

x86

http://go.microsoft.com/fwlink?LinkID=118101

es\DotNetFX35\x86

x64

http://go.microsoft.com/fwlink?LinkID=118119

es\DotNetFX35\x64

2.3.1.2 After Visual Studio 2008 RTM and Visual Studio 2008 SP1 RTM are installed, redist mfc90rus.dll is not updated

- There is no mfc90rus.dll in the redist folder after the Visual Studio 2008 SP1 RTM patch is installed.

- The user will not be able to use Russian resources to write a localized application and distribute it.

To resolve this issue:

The user can copy the MFC90RUS.DLL from the winsxs folder to the redist folder.

2.3.1.3 A request for the original installation media may occur during the installation of Visual Studio 2008 SP1 in some situations

The original installation media may be requested during the installation of Visual Studio 2008 SP1 if the following features have not been selected during the installation of Visual Studio 2008:

Under "Visual C++ Class & Template Libraries"

- ATL MFC Source Code

- ATL MFC Static Libraries ANSI

- ATL MFC Static Libraries Unicode

- ATL MFC Shared Libraries ANSI

- ATL MFC Shared Libraries Unicode

Under "Visual C++ Tools"

- MFC Trace Utility

- Visual C++ Error Lookup

- Win32 Tools

To resolve this issue:

Have the original media available.

2.3.1.4 The targeted .NET Framework version is not .NET Framework 3.5 SP1 even after a reference to System.Data.Entity is added to the project.

ClickOnce does not automatically check for SP1 if you selected the option to target the .NET Framework Client Profile at any time during development, even if you add a reference to System.Data.Entity (which requires SP1).

If you clear the "Client-only Framework subset" option in projects that contain a reference to System.Data.Entity, the application will incorrectly check for .NET Framework 3.5 without SP1.

To resolve this issue:

To force ClickOnce to check for .NET Framework 3.5 SP1:

For Visual Basic projects:

Open project properties (double-click 'My Project' in Solution Explorer).
Click the Compile tab.
Click Advanced Compile Options.
Clear the 'Client-only Framework subset' option.
Remove the reference to System.Data.Entity from the project.
Add a reference to System.Data.Entity to the project again.
 

For C# projects:

Open project properties (double-click 'Properties' in Solution Explorer).
Click the Application tab.
Clear the 'Client-only Framework subset' option.
Remove the reference to System.Data.Entity from the project.
Add a reference to System.Data.Entity to the project again.

2.3.1.5 The publish.htm page generated by ClickOnce tries to install the .NET Framework Client Profile even when it is already installed.

The publish.htm page is generated without the script that detects the presence of the .NET Framework Client Profile on target computers.

To resolve this issue:

1. Ensure that the application targets the Client-only Framework subset.

For Visual Basic projects:

Open project properties (double-click 'My Project' in Solution Explorer).
Click the Compile tab.
Click Advanced Compile Options.
Select the 'Client-only Framework subset' option.
 

For C# projects:

Open project properties (double-click 'Properties' in Solution Explorer).
Click the Application tab.
Select the 'Client-only Framework subset' option.
 

2. To get the correct script, select the .NET Framework 3.5 SP1 prerequisite and publish the application.

3. In the Publish properties of the project, change the prerequisite package back to the .NET Framework Client Profile and clear the option "Automatically generate deployment web page after every publish."

4. Publish the application again.

2.3.1.6 Association connectors do not appear, or appear incorrectly positioned, in the ADO.NET Entity Data Model Designer

This issue occurs in two scenarios:

1. After Update Model from Database is run, associations are created for new foreign keys in the database but do not appear in the diagram.

2. After undo/redo operations in the designer, association lines appear incorrectly placed in the diagram.

To resolve this issue:

There are several workarounds:

- Save the file. Close the designer. Open the file again.

- Right-click an empty area of the diagram and then click "Layout Diagram". This may alter any manual layout changes previously made to the diagram.

- Manually move related entities to refresh their rendering.

2.3.1.7 Default redirection link to the Microsoft Visual Studio 2008 SP1 ReportViewer is incorrect

The default redirection link to the Visual Studio 2008 ReportViewer (ReportViewer.exe) that is provided in the Setup and Deployment project incorrectly redirects to the language pack of the ReportViewer (ReportViewerLP.exe) on non-English operating systems.

To resolve this issue:

1. Open %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\ReportViewer\<locale>\package.xml

2. Replace the link http://go.microsoft.com/fwlink/?LinkID=98185 with http://go.microsoft.com/fwlink/?LinkID=98185&clcid=0x409 in package.xml.

3. Make sure that you do not change the link to the ReportViewerLP.exe http://go.microsoft.com/fwlink/?LinkID=98185&clcid=<CLID>.

2.3.1.8 Load tests fail to run with Visual Studio Team Server 2008 SP1 installation

If you install Visual Studio Team Server 2008 SP1 client and use this to run load tests, then you must use a Visual Studio Team Server 2008 SP1 controller to run the tests. All the agents that are online and connected to that controller must also be Visual Studio Team Server 2008 SP1 agents. If you install SP1 on the Visual Studio client only and run a load test by using a test rig that does not have the Visual Studio Team Server 2008 SP1 version installed, the load test fails immediately and "Not Executed" is displayed in the Test Results window. If you click on the link in the Test Results window, the error shown in the "Test Run Errors and Warnings" section will be similar to the following:

Failed to queue test run 'username@MYCONTROLLER 2008-06-13 11:17:28': Object of type 'Microsoft.VisualStudio.TestTools.LoadTesting.LoadTestConstantLoadProfile' cannot be converted to type 'Microsoft.VisualStudio.TestTools.WebStress.WebTestLoadProfile'. 

(The first type listed will depend on the type of load pattern used by your load test.)

The versions of the Visual Studio client, controller, and agents must match because API enhancements were made for Visual Studio Team Server 2008 SP1 to implement different load test patterns.

To resolve this issue:

Upgrade the clients, controller, and agent to Visual Studio 2008 SP1.

2.3.1.9 Running the Assembly Cache Viewer in Windows Vista

The Assembly Cache Viewer (Shfusion.dll) is a Windows shell extension that lets you view and manipulate the contents of the global assembly cache by using Windows Explorer. Shfusion.dll is located in the %windir%\Microsoft.NET\Framework\v2.0.50727 directory.

In Windows Vista, the Assembly Cache Viewer does not run with elevated permissions even if you open it from a Command Prompt window that has elevated permissions (for example, by using the START command with the path of the global assembly cache). This is because the Assembly Cache Viewer is a shell extension for Windows Explorer, which does not run with elevated permissions.

To resolve this issue:

Use Shfusion.dll only for viewing.

For updates, open a Command Prompt window that has administrative privileges and use the Gacutil.exe command-line tool from the .NET Framework SDK.

2.3.1.10 The 64-bit profiler SDK is not installed

The PerfSDK folder is missing from the x64 performance tools directory.  This folder contains vsperf.h and vsperf.lib, which are required to link in the profiling runtime APIs.

To resolve this issue:

The 64-bit Profiler SDK will be included in the 64-bit SP1 Stand-Alone Profiler installation, which will be available on the MSDN Download Center.  Install the 64-bit Stand-Alone Profiler on a 64-bit version of Windows and then copy the installed 64-bit PerfSDK directory into "%program files(x86)%\Microsoft Visual Studio 9.0\Team Tools\Performance Tools\x64".

2.3.1.11 Profiling a Web site fails if the web.config file is corrupt or does not exist

If the web.config file becomes corrupt from a previous profiling run or has been deleted, the profiler will display the message "The web site could not be configured correctly; getting ASP.NET process information failed. The server may not be running a version of Asp.Net version 2.0 or greater. Requesting 'Http://localhost/VSEnterpriseHelper.axd' returned an error: The remote server turned an error:  (500) Internal Server Error."

To resolve this issue:

Delete the web.config file.

Run the Web site under the debugger to regenerate a clean web.config file.

Run under the profiler.

2.3.1.12 CHT and JPN: Setup and Deploment project that has "Microsoft Visual Studio 2008 Report Viewer" as a prerequisite displays warning messages

Creating a CHT or JPN Setup and Deployment project that has "Microsoft Visual Studio 2008 Report Viewer" as a prerequisite results in several warning messages. However, these warning messages do not prevent the application deployment, including the ReportViewer control.

To resolve this issue:

No workaround is required.

2.3.1.13 AMD64 and IA64 ATL applocal assemblies are not updated by Visual Studio 2008 SP1

The AMD64 and IA64 ATL applocal assemblies under %VSINSTALLDIR%\vc\redist\amd64 and %VSINSTALLDIR%\vc\redist\ia64 are not updated by Visual Studio 2008 SP1. Therefore, both remain at the Visual Studio 2008 RTM level (9.0.21022.8) after the installation of SP1. As a result, the applocal deployment of AMD64 and IA64 ATL applications that bind to Visual Studio 2008 SP1 .dll files are affected.

To resolve this issue:

  1. Replace %VSINSTALLDIR%\vc\redist\amd64\atl90.dll and %VSINSTALLDIR%\vc\redist\ia64\atl90.dll with the corresponding SP1 AMD64 and IA64 files that are installed under %windir%\winsxs.

    Note: The SP1 AMD64 and IA64 files are installed in the following sub-folders under %windir%\winsxs

    SP1 AMD64 atl90.dll => amd64_microsoft.vc90.atl*9.0.30729.1*
    SP1 IA6464 atl90.dll => ia64_microsoft.vc90.atl*9.0.30729.1*
  2. Open %VSINSTALLDIR%\vc\redist\amd64\Microsoft.VC90.ATL.manifest in a text editor. Change
    version="9.0.21022.8"
    to
    version="9.0.30729.1"

    Repeat for %VSINSTALLDIR%\vc\redist\ia64\Microsoft.VC90.ATL.manifest.

 

  1. Save the file.

2.3.1.14 VC Redist (x86, x64 and ia64) packages contain the incorrect License Terms

The License Terms currently attached to the ENU VC Redist packages (VCRedist_x86.exe, VCRedist_x64.exe, and VCRedist_ia64.exe) does not allow you to redistribute the VC Redist. It specifies that you may only install and use ONE copy of the software. The correct License Terms permits installation and use of any number of copies of the VC Redist packages.

To resolve this issue:

There are two ways to work around this issue:

  1. Go to the Hotfix site and download the Hotfix for Visual Studio 2008 SP1 that replaces the VC Redist package files on disk with the new files containing the new License Terms.
  2. Download the SP1 vcredist packages and replace the three vcredist package files on disk.

2.3.2 ADO.NET

There are no known issues.

2.3.3 Languages

2.3.3.1 MFC application that has CRichEditView causes RC2151

If you use the MFC Application Wizard to create an MFC application that uses Ribbon UI, and change the base class from CView to CRichEditView, the application will fail to build with the following resource compiler error:

".\REdit.rc(565) : error RC2151 : cannot reuse string constants, 280(0x118) - "Insert Object...

o" already defined. Cannot add 280(0x118) - "Find/Replace

f"

This is caused by duplicate macro value definitions in resource.h for the following macros:

#define IDS_RIBBON_INSERT_OBJECT   280

#define IDS_RIBBON_FINDREPLACE       280

To resolve this issue:

1. Open the Resource.h file.

2. Locate the IDS_RIBBON_INSERT_OBJECT and IDS_RIBBON_FINDREPLACE macros.

3. Change one of their values to "307", or whatever value that is not used in the file.

4. Rebuild the application.

#define IDS_RIBBON_INSERT_OBJECT   280

#define IDS_RIBBON_FINDREPLACE       307

2.3.4 LINQ

There are no known issues.

2.3.5 Visual Studio Tools for Office

2.3.5.1 Office 2007 solutions created by using Visual Studio 2008 SP1 require the Visual Studio Tools for the Office system 3.0 Runtime SP1.

You might receive an error message if you install a solution by opening either the deployment manifest (a .vsto file), the Office application, the document, or the workbook. This is because the solution installer does not perform a check for prerequisites.

To resolve this issue:

There are two ways to resolve this issue:
- Install the SP1 patch for the Visual Studio Tools for the Office system 3.0 Runtime SP1.
- Install the solution by running the Setup program.
The Setup program checks for the correct version of prerequisites and installs them as required.

2.3.5.2 Office 2003 solutions cannot use the .Net Framework Client Profile as the target framework.

The properties page of the project lets you select .NET Framework Client Profile as the target framework even though it is not supported by the project.

To resolve this issue:

If your project uses Office 2003 as the target version, do not select Client-only Framework subset in the properties page of the project.

2.3.5.3 Warning message appears when you develop Office solutions for the .NET Framework Client Profile

When you develop Office solutions for the .NET Framework Client Profile runtime, you see these build warning messages: "The project has a reference to assembly <name>. This assembly is not part of the .NET Framework Client Profile.  By not having this reference, there may be compile or runtime errors."  or "The referenced assembly <name> has a dependency on <assembly> which is not listed as part of the .NET Framework Client Profile. If this dependent reference is required, you may get compilation errors."

If you ignore these warnings, you might get the following exception because of the missing assemblies: "Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly <assembly> or one of its dependencies. The system cannot find the file specified."

To resolve this issue:

If your application uses features that rely on assemblies not contained in the .NET Framework Client Profile, ensure that your project uses the full .NET Framework 3.5 as the target framework.

For Visual Basic projects:

  1. Open project properties (double-click 'My Project' in Solution Explorer).
  2. Click the Compile tab.
  3. Click Advanced Compile Options.
  4. Clear the 'Client-only Framework subset' option.
  5. Ensure that .NET Framework 3.5 appears as the target framework.

For C# projects:

  1. Open project properties (double-click 'Properties' in Solution Explorer).
  2. Click the Application tab.
  3. Clear the 'Client-only Framework subset' option.
  4. Ensure that .NET Framework 3.5 appears as the target framework.

2.3.5.4 When you publish a solution, the following warning message appears: "No 'HomeSite' attribute has been provided for Microsoft Office 2007 Primary Interop Assemblies"

By default, the solution bootstrapper is configured to download the primary interop assemblies package from the Web. However, this package cannot be downloaded; it must be installed from the same location as the application. 

To resolve this issue:

You can ignore this warning.

Even though the “Download prerequisites from the component vendor’s web site" is selected in the Prerequisites dialog box, the primary interop assemblies package will be automatically published to the same location as the application.

2.3.5.5 After Visual Studio 2008 SP1 is installed, Office projects that were created previously display a warning when published.

When you publish the solution, the following warning appears "Item '.NET Framework Client Profile' is required by 'Visual Studio Tools for Office system 3.0 Runtime Service Pack 1', but was not included."

This warning appears because Visual Studio Tools for Office system 3.0 Runtime Service Pack 1 is selected as an installation prerequisite.  However, neither the .NET Framework 3.5 Service Pack 1 nor the .NET Framework Client Profile package is selected.

To resolve this issue:

  1. Open the project properties:
  2. Click the Publish tab.
  3. Click Prerequisites to open the Prerequisites dialog box.
  4. Select either .NET Framework 3.5 Service Pack 1 or .NET Framework Client Profile.
  5. Publish the solution again.

2.3.5.6 Applications that use the ServerDocument class cannot target the .NET Framework Client Profile.

If your project targets the .NET Framework Client Profile, your application will throw a FileNotFound exception when you run the application. This happens because the ServerDocument class requires the complete .NET Framework 3.5. 

To resolve this issue:

For Visual Basic projects:

  1. Open project properties (double-click 'My Project' in Solution Explorer).
  2. Click the Compile tab. Click Advanced Compile Options.
  3. Clear the ‘Client-only Framework subset’ option.
  4. Ensure that .NET Framework 3.5 appears as the target framework.

For C# projects:

  1. Open project properties (double-click 'Properties' in Solution Explorer).
  2. Click the Application tab.
  3. Clear the ‘Client-only Framework subset’ option.
  4. Ensure that .NET Framework 3.5 appears as the target framework.

2.3.6 Web Development

2.3.6.1 Visual Studio 2008 SP1 Requires an Updated Installation of Silverlight Tools Beta 2

If Silverlight Tools Beta 2 is previously installed, after installation of Visual Studio 2008 SP1, Visual Studio will be unable to open Silverlight projects until the Silverlight Tools Beta 2 installation is updated.

To resolve this issue:

Download the updated Silverlight Tools Beta 2 for Visual Studio 2008 SP1 at http://go.microsoft.com/fwlink/?LinkID=120032.

2.3.7 Windows Communication Foundation (WCF) Tools

2.3.7.1 WCF Service Library project cannot be hosted by WCF Service Host when relative path is set to "Output Path" on the Properties page

When you create a WCF Service Library project, you can change the Output path from the default bin\debug\ to a relative path such as "." or ".." on the Build tab of the project Properties page. If you then try to debug the service, the service cannot be hosted by the WCF Service Host and this message is displayed: "A project with an Output Type of Class Library cannot be started directly."

To resolve this issue:

On the Build tab, input the fully qualified path instead of a relative path.

2.3.7.2 Error message when "Add New Item" is selected in a WCF Service Library project in Visual Studio with TFS plug-in

If you create a new WCF Service Library project in Visual Studio with the TFS plug-in, you may see an error displayed when you select Add New Item in this project. After clicking OK to close the error dialog box, the item service is added successfully and works as expected.

To resolve this issue:

Click OK to dismiss the error dialog box.

2.3.8 Windows Presentation Foundation (WPF) Designer for Visual Studio

2.3.8.1 The Properties window displays values, such as dates and numbers, by using the U.S. format.

The Properties window in the WPF Designer displays and edits values by using the U.S. format. This matches the XAML convention, which uses the en-US CultureInfo.  For example, dates and numbers are always in U.S. format. Dates are always displayed mm/dd/yy. If you enter a date value in the Properties window it will be converted to the mm/dd/yy format.

To resolve this issue:

No workaround is available.

2.3.8.2 Limitations when symbols in XAML files are code refactored

In Visual Studio 2008 SP1, if you use code Refactor to make type or member modifications, the refactoring will propagate to the XAML files.  For more information about this feature, see "How to: Rename a Symbol that is Declared in XAML" in the documentation. The following limitations apply to this new feature:
- Refactoring will only change the XAML files in the current project and will not be applied across all the projects in the solution

- Refactor can be used only on type names and certain attributes. Refactor cannot be used on the following:

o    The Setter Property attribute

o    The TemplateBinding path attribute

o    The Binding path and ElementName attributes

o    The MethodName property of ObjectDataProvider

To resolve this issue:

Complete the modifications manually; for example, by using Find and Replace.

2.3.8.3 Making changes to XAML will not refactor code files

If you change a type or member in a XAML file, those changes will not propagate to the code files.

For example, if you change the name of a Button, which has event handlers associated with it, by using the XAML editor, the code behind will not be updated.

To resolve this issue:

Modifications to code files must be made manually; for example, by using Find and Replace.

2.3.8.4 Renaming in Solution Explorer does not prompt rename refactoring in WPF projects

In Solution Explorer, if you right-click a XAML file, click Rename, and then rename the file, the file name will be changed, but there will not be any prompt to refactor the class name in XAML or the code behind. In particular, if you rename the XAML file that is referenced by the StartupUri property in the Application XAML file (for example, if you change Window1.xaml to MainWindow.xaml), then you must manually change the StartupUri property.

To resolve this issue:

Modifications must be made manually; for example, by using Find and Replace.

2.3.8.5 Find All References will not find unnamed controls in XAML files

In a code-behind file, you can find all references to a symbol by right-clicking the symbol and then clicking Find All References. Find All References will not find XAML elements that do not have the Name property set.

 

For example:

The following XAML shows the MyUserControl element, which does not have a name:

<Grid>
            <MyUserControl/>
 (...)

In the code-behind file, if you right-click the MyUserControl symbol and then click Find All References, only references in code will be found and not in XAML.

To resolve this issue:

Name the control or search manually (for example, by using Find in Files).

2.3.8.6 Visual Studio may stop responding when you bind to long ObjectDataProvider method calls

If you bind to an ObjectDataProvider, through XAML and the ObjectDataProvider, makes a call to a database; when you load the XAML in the WPF Designer, the operation can be very long and memory-intensive. As a result, the WPF Designer may stop responding until the operation is finished.

To resolve this issue:

Avoid setting up an ObjectDataProvider in this way at design time. Programmatically, use the DesignerProperties.IsInDesignMode() method only to perform long or memory-intensive work at run time.

2.3.8.7 Failure to load XAML with "{Binding RelativeSource={RelativeSource TemplatedParent}}"

 There is a known issue in Visual Studio 2008 SP1 where the WPF Designer fails to load if a Binding uses RelativeSource TemplatedParent without a path.

For example:

    <RepeatButton Command="{x:Static ScrollBar.LineUpCommand}"

CommandTarget="{Binding RelativeSource={RelativeSource TemplatedParent}}" />

To resolve this issue:

Specify a path by using the "." notation, which resolves to the same object.

For example:

    <RepeatButton Command="{x:Static ScrollBar.LineUpCommand}" CommandTarget="{Binding RelativeSource={RelativeSource TemplatedParent}, Path=.}" />

2.3.8.8 WPF Designer may crash if you reference values from a stand-alone or an external resource dictionary

WPF Designer may crash if you reference values from a stand-alone or an external resource dictionary as follows:

- The stand-alone dictionary has resource references between items in this same dictionary (for example, style referencing a color),
- And you have an open project file (Window, etc) that references a value from this stand-alone resource dictionary,
- And you modify a value in the stand-alone resource dictionary.

To resolve this issue:

Close any open documents that reference values from the dictionary before the dictionary is updated.

2.3.9 Windows Workflow Foundation (WF) Tools

There are no known issues.

2.3.10 Windows SDK Integration

2.3.10.1 x64 Sgen.exe does not generate assembly when types marked with the [Obsolete(IsError = true)] attribute are processed

The x64 version of Sgen.exe will not generate a serialization assembly when it processes an assembly that contains types that are marked with the [Obsolete(IsError=true)] attribute.

To resolve this issue:

Use the x86 version of Sgen.exe.

3. Related Links

Team Foundation Server Readme
Visual Studio Express Edition Readme
.NET Framework Readme


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