Visual Studio 2008 Readme

 

·     1.1. Supported Architectures

·     1.2. Supported Operating Systems

·     1.3. Installation Requirements

·     2.1. Installing

·     2.2. Uninstalling

·             2.2.1. On computers that have earlier versions of Visual Studio

·             2.2.2. On computers that do not have earlier versions of Visual Studio

·     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

·  Windows XP Service Pack 2 or above

·  Windows Server 2003 Service Pack 1 or above

·  Windows Server 2003 R2 or above

·  Windows Vista

·  Windows Server 2008

1.3. Hardware Requirements

·  Minimum: 1.6 GHz CPU, 384 MB RAM, 1024x768 display, 5400 RPM hard disk

·  Recommended: 2.2 GHz or higher CPU, 1024 MB or more RAM, 1280x1024 display, 7200 RPM or higher hard disk 

·  On Windows Vista: 2.4 GHz CPU, 768 MB RAM

2. Known Issues

2.1. Installing

2.1.1. Visual Studio SharePoint Workflow features have specific installation requirements.

To use SharePoint workflow development tools in Visual Studio Tools for Office, use the following installation instructions, in the specified order.

1)     Install Windows Server 2003.

2)    Install Internet Information Services (IIS). (In Control Panel, Add/Remove Windows Components, Application Server, Details, Internet Information Services (IIS).)

3)     Install .NET Framework 2.0 and.NET Framework 3.0.

4)     Enable ASP.NET 2.0.5727 in IIS Manager.

5)     Install Microsoft Office SharePoint Server 2007. Make sure to run the configuration wizard.

6)     Install Visual Studio 2008. Use the default installation, or make sure that Visual Studio Tools for Office is selected on the Custom installation page of the Setup wizard.

7)     Optional: SMTP Service. Installing this service lets you use SharePoint email-enabled features. Consult SharePoint product documentation to learn more about these capabilities.

To resolve this issue:

There is no workaround.

2.1.2. If the computer goes into sleep mode or hibernation mode during Visual Studio installation, Setup might hang when the computer returns from sleep mode or hibernation mode.

If the computer goes into sleep mode or hibernation mode during Visual Studio installation, Setup might hang when the computer returns from sleep mode or hibernation mode.

To resolve this issue:

1. Open Task Manager.

2. Select Visual Studio 2008 Setup.

3. Click End Task.

4. When the Visual Studio 2008 Setup screen disappears, restart Visual Studio 2008 Setup.

2.1.3. 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.4. Upgrading to the final version of SQL Server Compact 3.5 from SQL Server Compact 3.5 CTP or SQL Server Compact 3.5 Beta is not supported.

Upgrading from the CTP or Beta versions of SQL Server Compact 3.5 to the release version is not supported. Uninstalling the CTP or Beta version of Visual Studio 2008 does not uninstall SQL Server Compact 3.5. The CTP or Beta versions of SQL Server Compact 3.5 must be manually uninstalled before the release version of Visual Studio 2008 can be installed.

To resolve this issue:

1. Uninstall the CTP or Beta version of Visual Studio 2008.
2. In Windows Vista, use Programs and Features (in the Control Panel) to uninstall all Beta and CTP versions of SQL Server Compact 3.5, SQL Server Compact 3.5 for Devices and SQL Server Compact 3.5 Design Tools.
3. In Windows XP or Windows Server 2003, use Add or Remove Programs (in the Control Panel) to uninstall the Beta and CTP versions of SQL Server Compact 3.5, SQL Server Compact 3.5 for Devices and SQL Server Compact 3.5 Design Tools.

2.1.5. Network share path for Visual Studio 2008 Setup should not contain Unicode characters.

If the network share path of Visual Studio 2008 Setup contains Unicode characters, Setup gives the following error: "Source file not found" .

To resolve this issue:

Make sure that the network share path of Visual Studio Setup does not contain Unicode characters.

2.1.6. Users get an error message, "A problem has been encountered while loading the setup components. Canceling setup".

The user gets the message, "A problem has been encountered while loading the setup components. Canceling setup" and then Setup is canceled.  This only occurs on systems that do not have Windows Installer 3.1.

To resolve this issue:

1. Go to Windows Installer 3.1 Redistributable (v2) and install Windows Installer 3.1.

2. In Add or Remove Programs, make sure that Windows Installer 3.1 is on the list of installed programs.

3. Retry Visual Studio 2008 installation.

2.1.7. Setup will fail if the network share path from which Visual Studio 2008 is installed is too long.

Setup will fail if the network share path from which Visual Studio 2008 is installed is too long.

To resolve this issue:

Use a network share path that is fewer than 65 characters.

2.1.8. Setup stops and displays the following error message: "Setup failed to stop Windows Installer service. You must stop all other applications running Windows Installer service or restart your computer before the installation".

Setup stops and displays the following error message: "Setup failed to stop Windows Installer service. You must stop all other applications running Windows Installer service or restart your computer before the installation".

To resolve this issue:

Try the following options.

- This error message may indicate that a Setup other than Visual Studio 2008 Setup is already running on the computer. After the other setup is finished, restart the computer and then run Visual Studio 2008 Setup.

- This error message may also occur because Windows Updates are being installed on the computer. After Windows Updates are finished, restart the computer and then run Visual Studio 2008 Setup.

- Check for msiexec.exe in the Task Manager. If msiexec.exe is already running, wait for it to finish. Restart the computer and then run Visual Studio 2008 Setup.

- If none of these options apply to your problem, restart the computer and then run Visual Studio 2008 Setup.

2.1.9. Installing Visual Studio 2008 on Windows Vista sometimes fails due to simultaneous installations by Windows Update.

Visual Studio 2008 Setup on Windows Vista may fail if Windows Update is installing updates on the computer at the same time as Visual Studio 2008 Setup is running. It may also fail if SMS is installing Windows Updates.

To resolve this issue:

Wait for Windows Updates to finish, and then restart the computer and run Visual Studio 2008 Setup.

2.1.10. Installing Visual Studio 2008 on the same computer as Visual Studio 2005 causes Visual Studio 2005 repair of .NET Framework 2.0 to fail.

When Visual Studio 2008 is installed on the same computer as Visual Studio 2005, Visual Studio 2005 repair fails to repair .NET Framework 2.0.

To resolve this issue:

Repair the .NET Framework 2.0 separately by using Add or Remove Programs.

2.1.11. Installing Visual Studio 2008 on a Windows Vista computer that has had earlier versions of .NET Framework 3.5 may fail.

When Visual Studio 2008 is installed on a Windows Vista computer that has had earlier versions of Visual Studio, Setup fails during the installation of the .NET Framework 3.5 component.

To resolve this issue:

By using the Control Panel, uninstall the following Windows Updates:

- Hotfix for Microsoft Windows (KB110806)

- Hotfix for Microsoft Windows (KB930264)

- Hotfix for Microsoft Windows (KB929300)

2.1.12. Visual Studio 2008 Setup may display a message that prompts you to close running applications.

Visual Studio 2008 Setup may display a message that prompts you to close running applications.  Some of the listed applications may have numeric identifiers and some may have empty identifiers.

Also, you may see the Process IDs of applications that should be closed, but not the names of the applications.

To resolve this issue:

We recommend that you close these applications so that they do not affect the installation process.

You can find names of applications that should be closed by looking up the Process IDs in Task Manager, as follows.

   1. Press CTRL+ALT+DEL and then click Task Manager.

   2. On the View menu, click Select Columns.

   3. Select PID (Process Identifier) and then click OK.

   4. In Task Manager, click PID to sort entries by PID.

   5. Look for the Process IDs that are shown in the message.

You may also click Ignore in the message box and then continue with the installation. This may require a restart at the end of Setup.

2.1.13. Windows Automatic Update notification appears during Visual Studio installation on Windows Vista.

When Visual Studio 2008 is being installed on a Windows Vista computer that does not have .NET Framework 2.0 SP1 and .NET Framework 3.0 SP1, a Windows Automatic Update  notification pops up  and asks you to restart the computer.

To resolve this issue:

Postpone the restart until the Visual Studio installation finishes.

2.1.14. Some tools contain components that do not display in the expected language after you install Visual Studio 2008 and then install a version of Visual Studio 2008 in a different language.

Tools installed by the Windows SDK contain components that do not display in the expected language when Visual Studio 2008 is installed and then a different language version of Visual Studio 2008 is installed.

To resolve this issue:

By using Add or Remove Programs (Windows Server 2003 and Windows XP) or Programs and Features (Windows Vista and Windows Server 2008), repair the most recently installed version of Visual Studio 2008.

2.1.15. Installing MSDN Express Library 2008 for products other than Visual Studio 2008 Express Editions or Visual Studio 2008 Standard will fail.

The Setup-complete screens for all editions of Visual Studio 2008 display the following message: "To install MSDN Library for Visual Studio 2008, run setup.exe in the MSDN folder on the installation media, or download MSDN Library Express Edition."

Installation of MSDN Express Library 2008 for any version of Visual Studio other than Visual Studio Express Editions or Visual Studio 2008 Standard will fail.

MSDN Express Library 2008 was designed to be installed only in coordination with Visual Studio 2008 Express Editions and Visual Studio 2008 Standard.

To resolve this issue:

For Visual Studio 2008 versions other than the Visual Studio 2008 Express Editions or Visual Studio 2008 Standard, click the Install Documentation link in the Visual Studio Setup launcher.

2.1.16. During Visual Studio 2008 installation or uninstalling, a dialog pops up and asks you to close setup process.

During Installation or Uninstalling of Visual Studio 2008, a dialog pops up with the message "The following application should be closed before continuing with setup:"

The list of applications shown contains the setup itself, and looks like the below:

Microsoft Visual Studio 2008 Setup

setup

To resolve this issue:

Click on "Ignore" and continue with setup.

2.2. Uninstalling

2.2.1. On computers that have earlier versions of Visual Studio.

2.2.1.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 together with Visual Studio 2008, 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:

- Repair Visual Studio 2008 by using Add or Remove Programs (Windows Server 2003 and Windows XP) or Programs and Features (Windows Vista and Windows Server 2008).

- Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5.

2.2.1.2. Manual uninstalling of earlier versions of Visual Studio 2008.

A). If you installed Visual Studio Code Name "Orcas" Beta 1 or Visual Studio 2008 Beta 2, use the Control Panel to remove all related, such as Professional, Standard, Enterprise Architect, or Team Suite. 

All pre-release components are chain-uninstalled together with the Visual Studio product so that uninstalling components manually is not required.

B) If you installed an earlier version of Visual Studio, such as a Visual Studio Code Name "Orcas" Community Technology Preview (CTP), then you must uninstall it by performing the following steps in exact order.

1. Open Add or Remove Programs (Windows Server 2003 and Windows XP) or Programs and Features (Windows Vista and Windows Server 2008).

2. Remove "Microsoft SQL Server Compact Edition 3.5".

3. Remove "Microsoft SQL Server Compact Edition 3.5 Design Tools".

4. Remove "Microsoft SQL Server Compact Edition 3.5 for Devices".

5. Remove "Microsoft Visual Studio Performance Collection Tools".

6. Remove "Windows Mobile 5.0 SDK R2 for Pocket PC".

7. Remove "Windows Mobile 5.0 SDK R2 for Smartphone".

8. Remove "Crystal Reports 2007".

9. Remove "Visual Studio Asset System".

10.Remove "Visual Web Developer Design Service Reminder Tools".

11.Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime".

12.Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime Language Pack". This step is not required if you have only the English ENU edition.

13.Remove "Microsoft Visual Studio Tools for Office Runtime 3.0".

14.Remove "Microsoft Visual Studio Codename Orcas Professional" or other related Visual Studio installations, such as Professional, Standard, Enterprise Architect, or Team Suite.

15.Remove "Microsoft Document Explorer".

16.Remove "Microsoft Document Explorer 2005 Language Pack". This step is not required if you have only the English ENU edition.

17.Remove "Microsoft Device Emulator 3.0".

18.Remove "Microsof`t .NET Compact Framework 2.0 SP1".

19.Remove ".NET Framework 2.0 SDK".

20.Remove "Microsoft Visual Studio Codename Orcas Remote Debugger".

21.Remove "Microsoft Visual Studio 64bit Prerequisites Beta". This step is required only if Visual Studio is installed on a 64-bit computer.

22.Remove "Microsoft .NET Framework 3.5".

To resolve this issue:

No workaround is available.

2.2.1.3. Uninstalling Visual Studio 2005 will clear the registry entries that are required by the Load Agent

If you install Visual Studio 2008 Team Test Load Agent on a computer that has Visual Studio 2005 Team System Edition for Testers or Visual Studio 2005 Team Suite Edition, and then uninstall Visual Studio 2005, the uninstall will clear the following registry entries, which are required for load generation:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

"MaxUserPort"=dword:0000FFFE

"TcpTimedWaitDelay"=dword:0000001e

To resolve this issue:

Add these entries back into the registry after you uninstall Visual Studio 2005.

2.2.2. On computers that do not have earlier versions of Visual Studio.

2.2.2.1. After a Visual Studio instance in a side-by-side configuration is uninstalled, Workflow debugging is no longer possible.

If the computer has two versions of Visual Studio 2008 (for example the English and Japanese versions) and you uninstall one of them, you can no longer debug workflows in the remaining installation. WDE.dll, which is part of the Workflow debugger, is uninstalled when either one of the installations is removed from the computer.

To resolve this issue:

Repair or reinstall the Visual Studio installation that you want to remain on the computer.

2.2.2.2. Uninstalling Visual Studio 2008 may display a dialog box that prompts to close running applications.

Uninstalling Visual Studio 2008 may display a message that prompts to close running applications. Some of the applications may have numeric identifiers and some may have empty identifiers. In the message, you may see the Process IDs of applications that should be closed. Names of applications are not shown.

To resolve this issue:

We recommend that you close these applications so that they do not affect the uninstallation process. You can find names of applications that should be closed by looking up the Process IDs in Task Manager.

1. Press CTRL+ALT+DEL and then click Task Manager.

2. On the View menu, click Select Columns.

3. Select PID (Process Identifier) and then click OK.

4. In Task Manager, click PID so that the entries are sorted by PID and then find the application names.

You may also click Ignore in the message box and continue. Doing this may require a restart at the end of uninstallation.

2.2.2.3. On a system that has two Visual Studio languages, Performance Tools stop working after one language is uninstalled.

Uninstalling a Visual Studio language after you have installed two Visual Studio languages on your system will cause the Performance Tools to stop working.

To resolve this issue:

1. Run Visual Studio Setup.

2. Select Add/Remove features.

3. Clear the Performance Tools check box.

4. Click Update.

5. Repeat steps 1-2.

6. Select the Performance Tools check box.

7. Click Update.

2.2.2.4. Manual uninstall of Visual Studio 2008.

You must uninstall Visual Studio 2008 components in following order.

Open Add or Remove Programs (Windows Server 2003 and Windows XP) or Programs and Features (Windows Vista and Windows Server 2008).

1.   Remove "Microsoft SQL Publishing Wizard".
2.   Remove "Crystal Reports Basic for Visual Studio 2008".
3.   Remove "Crystal Reports Basic 64-bit Runtime for Visual Studio 2008 (x64)". This step is required only if Visual Studio is installed on a 64-bit computer.
4.   Remove "Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies and IntelliSense".
5.   Remove "Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools".
6.   Remove "Microsoft Windows SDK for Visual Studio 2008 Win32 Tools".
7.   Remove "Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries".
8.   Remove "Microsoft Windows SDK for Visual Studio 2008 Tools".
9.   Remove "Microsoft Visual Studio 2008 Remote Debugger". This step is required only if Visual Studio is installed on a 64-bit computer.
10. Remove "Microsoft SQL Server 2005 Express Edition".
11. Remove "Microsoft SQL Server Native Client".
12. Remove "Microsoft Device Emulator version 3.0".
13. Remove "Windows Mobile 5.0 SDK R2 for Smartphone".
14. Remove "Windows Mobile 5.0 SDK R2 for Pocket PC".
15. Remove "Microsoft SQL Server Compact 3.5 For Devices".
16. Remove "Microsoft SQL Server Compact 3.5 Design Tools".
17. Remove "Microsoft SQL Server Compact 3.5".
18. Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime".
19. Remove "Microsoft Visual Studio Tools for the Microsoft Office system (version 3.0 Runtime)".
20. Remove "Microsoft .NET Compact Framework 3.5".
21. Remove "Microsoft .NET Compact Framework 2.0 SP2".
22. Remove "Microsoft Visual Studio".
23. Remove "Microsoft Visual Studio Web Authoring Component".
24. Remove "Microsoft Document Explorer 2008".
25. Remove "Microsoft Visual Studio 2008 64bit Prerequisites". This step is required only if Visual Studio is installed on a 64-bit computer.
26. Remove "Microsoft .NET Framework 3.5".

To resolve this issue:

No workaround is available.

2.3. Product Issues

2.3.1. General Issues

2.3.1.1. Visual Studio 2008 does not work after Windows XP or Windows Server 2003 is upgraded to Windows Vista RTM.

Visual Studio 2008 does not work after Windows XP or Windows Server 2003 is upgraded to Windows Vista RTM.

To resolve this issue:

1. Open Programs and Features.

2. Uninstall .NET Framework 3.5.

3. Reinstall .NET Framework 3.5 from the Visual Studio 2008 installation media or from http://www.microsoft.com/.

4. Repair Visual Studio 2008.

2.3.1.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:

Either 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.

2.3.1.3. Windows Workflow debugging with T-SQL is not supported.

Do not debug your workflow with both workflow debugging and T-SQL debugging enabled, or unexpected results could occur.

To resolve this issue:

No workaround is available.

2.3.1.4. Locals window does not work on the 64-bit version of Windows Vista.

The Locals window is not visible in Visual Studio 2008 when it is running on the 64-bit version of Windows Vista.

To resolve this issue:

No workaround is available.

2.3.1.5. Adding a new database unit test to a workflow project displays an error message. 

Adding a new database unit test to a workflow project displays the following error message: "An error occurred while loading the workflow. Please correct the following error and try reloading the document to view the workflow. The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected the following classes in the file: DatabaseUnitTest1. The base clase DatabaseUnitTest1 for the class needs to be an Activity." 

This error is not correct. The new database unit test is actually valid. You can ingore the error; it will not reappear after it is dismissed.

To resolve this issue:

Close and ignore the error. It will not reappear.

2.3.1.6. To work correctly, the Visual Basic Workflow designer requires the Visual Web Developer feature to be installed.

After Visual Studio 2008 is installed in Visual Basic-only mode, the Workflow Foundation designer does not work correctly. You cannot specify the required fields in Workflow projects, which makes it impossible to build the solution.

To resolve this issue:

Install the Visual Web Developer feature from the Visual Studio 2008 installation disk.

2.3.1.7. Visual Studio 2008 projects cannot be built in Expression Blend.

Solutions and projects that were created in Microsoft Visual Studio 2008 can be opened and edited in Expression Blend, but they will not build.  Additionally, when you open Expression Blend projects in Visual Studio 2008 they will be upgraded to the Visual Studio 2008 format. When this upgrade is complete, the project will no longer build in Expression Blend. You can still open and edit the project in Expression Blend, but the project will not build in Expression Blend.

To resolve this issue:

For more information about availability and installation instructions, visit here or the Microsoft Expression site.

2.3.1.8. Visual Studio 2008 does not recognize Windows Mobile 6 SDK when the SDK is already installed.

If a user installs Visual Studio 2008 on a computer that already has Windows Mobile 6 SDK, Visual Studio 2008 fails to recognize the SDK.  Repairing Windows Mobile 6 SDK does not solve this problem.

To resolve this issue:

1. Uninstall Windows Mobile 6 SDK.

2. Install Windows Mobile 6 SDK.

2.3.1.9. SQL Server Compact 3.5 does not use the Encrypt property of the SqlCeConnection class.

The Encrypt property is no longer used in the SqlCeConnection class. The property is retained in SQL Server Compact 3.5 for backward compatibility. The property should not be used.

To resolve this issue:

Use the encryption mode property of the SqlCeConnection class to encrypt SQL Server Compact 3.5 database files. Uses of encryption mode, together with code samples, are as follows.

1. To create a new encrypted SQL Server Compact 3.5 database.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;encryption mode=platform default;Password=<enterStrongPasswordHere>;");

engine.CreateDatabase();

[Visual Basic]

Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;encryption mode=platform default;Password= <enterStrongPasswordHere>;")

engine.CreateDatabase()

2. To upgrade a SQL Server 2005 Compact Edition (version 3.1) or SQL Server 2005 Mobile Edition (version 3.0) database to an encrypted SQL Server Compact 3.5 database.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password= <enterStrongPasswordHere>;");

engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password= <enterStrongPasswordHere>>;");

[Visual Basic]

Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;Password=<enterStrongPasswordHere>>;")

engine.Upgrade("Data Source=Northwind.sdf;encryption mode=platform default;Password=<enterStrongPasswordHere>;")

3. To change the encryption mode of an existing SQL Server Compact 3.5 database.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password= <enterStrongPasswordHere>;");

engine.Compact("Data Source=Northwind.sdf;encryption mode=ppc2003 compatibility;Password= <enterStrongPasswordHere>;");

[Visual Basic]

Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;Password=<enterStrongPasswordHere>;")

engine.Compact("Data Source=Northwind.sdf;encryption mode=ppc2003 compatibility;Password=<enterStrongPasswordHere>;")

4. To encrypt an unencrypted SQL Server Compact 3.5 database.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf");

engine.Compact("Data Source=Northwind.sdf;encryption mode=platform default;Password= <enterStrongPasswordHere>;");

[Visual Basic]

Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;")

engine.Compact("Data Source=Northwind.sdf;encryption mode=platform default;Password=<enterStrongPasswordHere>;")

2.3.1.10. Unable to use design-time experience in Smart Device programs when SQL Server 2005 Compact Edition (version 3.1) database is targeted. 

A Smart Device programmer cannot use any of the designer features, such as Add Datasource, Add New Connection, Create Database, Generate Data Forms, and drag-and-drop datasource objects onto form designer, when programming against SQL Server 2005 Compact Edition (version 3.1) database. All of the Smart device designer features default to SQL Server Compact 3.5 database.

To resolve this issue:

Use Visual Studio 2005 Service Pack 1 for programming against SQL Server 2005 Compact Edition (version 3.1) database for Smart Device programs. To use Visual Studio 2008 with SQL Server 2005 Compact Edition (version 3.1) database, see http://go.microsoft.com/fwlink/?LinkID=101885.

2.3.1.11. During an upgrade of a Visual Studio 2005 project to a Visual Studio 2008 project, encrypted SQL Server Compact database is not upgraded and ClickOnce applications have to be republished.

Database files (*.sdf) created by earlier version of SQL Server Compact are not compatible with SQL Server Compact 3.5. Unencrypted database files from earlier versions of SQL Server Compact are upgraded when a Visual Studio 2005 project is upgraded in Visual Studio 2008. Encrypted database files have to be manually upgraded. If the Visual Studio 2005 project uses ClickOnce to publish applications, the application should be re-published after the project has been upgraded in Visual Studio 2008.

To resolve this issue:

Upgrade the encrypted database files by completing the following steps.

1. Click Data.
2. Click Add New Data Source.
3. Click Add Connection. If an earlier version of the database file is open, a message appears. If you click OK, the Upgrade to SQL Server Compact 3.5 Database dialog box appears.

Alternatively the SqlCeEngine.Upgrade API can be used for programmatic scenarios, as shown in the following code example.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password=<enterStrongPasswordHere>;");
engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password=<enterStrongPasswordHere>;");

[Visual Basic]

Dim engine As SqlCeEngine
engine = New SqlCeEngine("Data Source=Northwind.sdf;Password=<enterStrongPasswordHere>;")
engine.Upgrade("Data Source=Northwind.sdf;encryption mode=platform default;Password=<enterStrongPasswordHere>;")

If the project uses ClickOnce to publish applications, the application should be re-published after it has been upgraded in Visual Studio 2008. When you re-publish the ClickOnce application in Visual Studio 2008, you may see a warning that SQL Server 2005 Compact Edition prerequisite cannot be found for bootstrapping. You can ignore the warning.

2.3.1.12. SQL Server Compact 3.5 data type for parameters like SqlDbType or DbType should be explicitly set.

If the data types for parameters like SqlDbType or DbType are not explicitly set an exception will be thrown.

To resolve this issue:

Explicitly set the data type for parameters such as SqlDbType or DbType. Doing this is critical in case of BLOB data types (image and ntext). A code example follows.

[Visual C#]

SqlCeEngine engine = new SqlCeEngine(connString);
engine.CreateDatabase();
engine.Dispose();
SqlCeConnection conn = new SqlCeConnection(connString);
conn.Open();
SqlCeCommand cmd = conn.CreateCommand();
cmd.CommandText = "CREATE TABLE BlobTable(name nvarchar(128), blob ntext);";
cmd.ExecuteNonQuery();
cmd.CommandText = "INSERT INTO BlobTable(name, blob) VALUES (@name, @blob);";
SqlCeParameter paramName = cmd.Parameters.Add("name", SqlDbType.NVarChar, 128);
SqlCeParameter paramBlob = cmd.Parameters.Add("blob", SqlDbType.NText);
paramName.Value = "Name1";
paramBlob.Value = "Name1".PadLeft(4001);
cmd.ExecuteNonQuery();

[Visual Basic]

Dim engine As SqlCeEngine  = New SqlCeEngine(connString)
engine.CreateDatabase()
engine.Dispose()
Dim conn As SqlCeConnection = New SqlCeConnection(connString)
conn.Open()
Dim cmd As SqlCeCommand= conn.CreateCommand()
cmd.CommandText = "CREATE TABLE BlobTable(name nvarchar(128), blob ntext);"
cmd.ExecuteNonQuery()
cmd.CommandText = "INSERT INTO BlobTable(name, blob) VALUES (@name, @blob);"
Dim paramName As SqlCeParameter
Dim paramBlob As SqlCeParameter
paramName = cmd.Parameters.Add("name", SqlDbType.NVarChar, 128)
paramBlob = cmd.Parameters.Add("blob", SqlDbType.NText)
paramName.Value = "Name1"
paramBlob.Value = "Name1".PadLeft(4001)
cmd.ExecuteNonQuery()

2.3.1.13. Windows Embedded CE 6.0 SDK fails to install into Visual Studio 2008.

If Platform Builder for Windows Embedded CE 6.0 creates an SDK, the SDK might not install into Visual Studio 2008.

To resolve this issue:

For a partial workaround, on the Choose Setup Type page of the installation wizard, select Custom instead of Complete, and then on the Custom Setup page remove the Documentation component from the list of components that will be installed. This workaround enables the rest of the SDK to install, but you will not be able to filter the installed Help documentation for content that is specific to your SDK.

2.3.1.14. Unable to initialize Help System on Visual Studio Remote Tools.

On a computer that has Visual Studio 2008, invoking the Help menu on the Visual Studio Remote Tools does not initialize the Help System.

(Note: This problem occurs only on systems that have never had Visual Studio 2005 installed.)

To resolve this issue:

As a workaround, customers must invoke the MSDN documentation for these Remote Tools from http://msdn2.microsoft.com/en-us/library/aa935675.aspx.

2.3.2. ADO.Net

2.3.2.1. After an upgrade to Visual Studio 2008, user gets a warning that the MDAC 2.8 prerequisite is missing or that the user's application does not run on Windows 2000 after it is installed.

You may encounter one of the following problems:

After you upgrade your Visual Studio 2005 project to Visual Studio 2008, you get a build warning that says there is a missing prerequisite.

You built an application that depends on MDAC and it does not run on Windows 2000.

Windows 2000 users cannot run a ClickOnce application because MDAC is missing.

To resolve this issue:

If you do not require MDAC and you are getting a build warning, open the prerequisites dialog box and clear the MDAC prerequisite.

If you are targeting Windows 2000 clients and require the MDAC prerequisite, get the Bootstrapper package from the Internet, as follows.

1)      Open the Prerequisites dialog box and click "Check Microsoft Update for more redistributable components". Doing this will open http://go.microsoft.com/fwlink/?linkid=40981.

2)      From this Web site, download the MDAC Bootstrapper package and save it to a new folder in the ...\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\ directory.

You can also get the Bootstrapper package from Visual Studio 2005, as follows: If Visual Studio 2005 is installed on the same computer, you can copy the MDAC28 folder from the ...\Program Files Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ directory and then paste it in the ...\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\ directory.

2.3.3. Languages

2.3.3.1. Compiler displays an error message a lambda is passed to a doubly-nested latebound method call.

If a lambda is passed to a latebound method call that is nested inside another latebound method call, the following error is displayed:

"Expression does not produce a value"

Dim o1, o2 As Object

'Can't use lambda in a doubly-nested latebound call:

o1.Foo(o2.SomeLateBoundCall(Function(a As Integer) a))

...

Class C1

    Sub Foo(ByVal x As Object)

    End Sub

End Class

To resolve this issue:

Either make the first method call early-bound by specifying the type for o1, or assign the lambda to a separate variable before passing it into the method:

Dim o1, o2 As Object

Dim someDelegate As Func(Of Integer, Integer) = Function(a As Integer) a

'This will work:

o1.Foo(o2.SomeLateBoundCall(someDelegate))

2.3.3.2. Debugger incorrectly shows 'C++' as the language when C# code is linked by using C++ linker.

When you debug an image (.exe or .dll) that was created by linking one or more .netmodules by using link.exe, you may find that when you debug into assemblies that are contained by the linked .netmodules, the debugger interprets the code as C++/CLI rather than the language that the assembly was created with. The call stack displays C++/CLI information and the expression evaluator uses C++/CLI syntax and semantics.

To resolve this issue:

No workaround is available.

2.3.3.3. MFC ANSI application wizards that have non-ASCII project names contain invalid characters.

If a project's path contains characters that have a different ANSI encoding than the one that is associated with the Visual Studio product language, the .rc file in ANSI format will contain invalid characters. For example, when an English-language Visual Studio version is used in a Chinese-simplified operating environment, Chinese project names will only be supported on Unicode projects.

To resolve this issue:

Convert the .rc file to Unicode.

The steps to save the .rc file are as follows:

- Right-click the .rc file, and then click View Code.

- After the .rc file opens in the editor, click Save As on the File menu.

- Click Save with Encoding.

- In Advanced Save Options, select Encoding: Unicode Codepage 1200.

- Click OK.

2.3.3.4. Visual Basic and C# breaking changes between Visual Studio 2005 and Visual Studio 2008.

Breaking changes are changes that could make existing code behave differently when it is compiled under the compilers that are included in Visual Studio 2008. We make every effort to avoid breaking changes, but sometimes such changes are required for security reasons or to fix known problems in code generation.  Most breaking changes impact very few users.

To resolve this issue:

You can view the list of breaking Visual Basic and C# changes and the steps you should take to update your code here: http://go.microsoft.com/fwlink/?LinkId=104111.

2.3.3.5 You may experience performance issues in Visual Studio 2008 when compiling files with a large number of XML comments

When using Visual Studio 2008 to build a Microsoft Visual Basic project that contains a large number of XML comments in a single file, (most likely a designer-generated file for a Dataset or Web Reference), you may experience the following performance issues in the IDE:

To resolve this issue:

You can check for updates at the following link: http://go.microsoft.com/fwlink/?LinkId=105878

Option 1 – Disable XML Comment Generation

You can work around this issue by disabling XML documentation for your project, by performing the following steps:

  1. Double-click “My Project”
  2. Click on the Compile tab
  3. De-select the checkbox for “Generate XML documentation file”

If you are using Visual Basic 2008 Express Edition, this option will not be available in the IDE, and you will need to do the following steps instead:

  1. Create a backup of your project
  2. Open your .vbproj file in Notepad
  3. Remove all elements or lines in the file (typically there are two instances to delete).
  4. Save the file and reload your project in Visual Studio

Option 2 – Remove the XML comments

In the designer-generated file, do a Find/Replace and change every occurrence of ’’’ (i.e. three apostrophes) to ‘’ (i.e. two apostrophes). Note that any time you make a change in the designer or right-click the file and select “Run Custom Tool” you will have to do this again.

Option 3 – Create a separate project to store the file with the XML comments

Create a new Class Library project to store your designer-generated file (i.e. your Dataset or Web Reference), and add a reference to it from your original project. In this new project, disable the XML documentation file using the steps in Option 1. You also may need to add additional imports statements to your code.

2.3.4. LINQ

2.3.4.1. O/R Designer error message, "There is no Unicode byte order mark. Cannot switch to Unicode" when a .DBML file that was created by using Visual Studio 2008 Beta 2 is opened. 

In Visual Studio 2008 Beta 2, the Object Relational Designer (O/R Designer) created .DBML files as UTF-8 byte-order even if UTF-16 encoding was specified in the actual file.  Opening .DBML files that were created by using Beta 2 could result in the error message, "There is no Unicode byte order mark. Cannot switch to Unicode".

To resolve this issue:

Right-click the .DBML file in Solution Explorer, open with the XML Editor, and then save the file.  Doing this does not impact the actual content of the .DBML file and there is no data loss.

2.3.4.2. LINQ to SQL breaking changes between Beta 2 and the release version.

There have been changes to LINQ to SQL since Beta 2 that may affect applications you choose to upgrade.

To resolve this issue:

The list of breaking changes together with the steps to upgrade your code is available here: http://go.microsoft.com/fwlink/?LinkId=104112

2.3.5. Visual Studio Tools for Office

2.3.5.1. Microsoft Office 2007 Service Pack 1 is required to preview Microsoft Office InfoPath 2007 form templates.

Previewing Microsoft Office InfoPath 2007 form templates by pressing F5 or clicking the Preview button will fail with an error in Visual Studio 2008, unless InfoPath 2007 Service Pack 1 or the QFE is installed.

To resolve this issue:

The QFE is available at http://go.microsoft.com/fwlink/?LinkId=102084.

2.3.5.2. Migrating Visual Studio Tools for Office (VSTO) projects from Visual Studio 2008 Beta 2 to the release version of Visual Studio 2008.

You may experience build and runtime errors when you build and run Beta 2 Office projects in the release version of Visual Studio 2008. Changes have been made to a number of VSTO reference assemblies.

To resolve this issue:

Renamed Assemblies: If you receive an error for any of the following reference assemblies, delete the old reference assembly and then add the corresponding new reference assembly to your project and rebuild.

Old Reference                                                                                            New Reference
 
Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll        Microsoft.VisualStudio.Tools.Applications.ServerDocument.v9.0.dll
Microsoft.VisualStudio.Tools.Office.dll                                          Microsoft.Office.Tools.v9.0.dll 
Microsoft.VisualStudio.Tools.Office.Common.dll                            Microsoft.Office.Tools.Common.v9.0.dll 
Microsoft.VisualStudio.Tools.Office.Excel.dll                                 Microsoft.Office.Tools.Excel.v9.0.dll 
Microsoft.VisualStudio.Tools.Office.Outlook.dll                              Microsoft.Office.Tools.Outlook.v9.0.dll
Microsoft.VisualStudio.Tools.Office.Word.dll                                  Microsoft.Office.Tools.Word.v9.0.dll

2.3.5.3. The .vsto file extension must be registered as a MIME type on a secured installation of IIS.

Users can install Microsoft Office solutions by opening the deployment manifest from the Web. However, a secured installation of Internet Information Services (IIS) will block the .vsto file name extension. The MIME type must be defined in IIS before you deploy Office solutions by using IIS.

To resolve this issue:

To add the .vsto MIME type to IIS 6.0:

1. On the server that is running IIS 6.0, click Start, point to All Programs and Administrative Tools, and then click Internet Information Services (IIS) Manager.

2. Click the computer name, the Web Sites folder, or the Web site that you are configuring. Click Action and then click Properties. Click the HTTP Headers tab.

3. Click MIME Types.

4. In the MIME Types window, click New.

5. In the MIME Type window, type .vsto as the extension and application/x-ms-vsto as the MIME type.

6. Apply the new settings.
Note   You must restart the World Wide Web Publishing Service, or wait for the worker process to recycle for the changes to take effect.

7. Flush the browser's disk cache, and try opening the .vsto file again.


To add the .vsto MIME type to IIS 7.0:

1. On the server that is running IIS 7.0, click Start, point to All Programs, and then click Accessories.

2. Right-click Command Prompt, and then click Run as administrator.

3. In the Open box, type the following path and then click OK.
%windir%\system32\inetsrv

4. Type the following command.
set config /section:staticContent /+[fileExtension='.vsto',mimeType='application/x-ms-vsto']

5. Apply the new settings.
Note   You must restart the World Wide Web Publishing Service, or wait for the worker process to recycle for the changes to take effect.

6. Flush the browser's disk cache, and try opening the .vsto file again.

2.3.5.4. Adding unsupported content to Word content controls in document-level projects at design time may corrupt the document.

Many of the limitations that Microsoft Office Word imposes on content controls at run time are not enforced in document-level projects for Word at design time. When you design the UI of your solution in Visual Studio, be sure to modify content controls only in ways that are supported at run time. Specifically, do not insert any non-text content, such as other content controls, pictures, or tables, into a plain-text content control.

Although Word appears to let you insert this kind of content at design time, this content will cause document corruption problems when the document is re-opened. Similarly, do not insert any content other than pictures into a picture content control. If you are unsure whether a content control allows a certain type of content or not, first run the solution without that content and then try to add it to the content control at run time. If Word does not let you do that, then you should not insert that kind of content into that content control at design time either.

If you modify a content control at design time in a way that the control does not support at run time, the Visual Studio designer will not alert you about the unsupported changes. However, when you debug or run the project, or if you save and then re-open the project, Word will display an error message and request permission to repair the document. When you repair the document, Word removes all unsupported content and formatting from the control.

To resolve this issue:

Do not add unsupported content to content controls at design time.

2.3.5.5. Using Office SharePoint workflow templates on a 64-bit operating system is unsupported and causes an exception.

Visual Studio 2008 throws two exceptions if you try to create a SharePoint workflow project (SharePoint 2007 Sequential Workflow or SharePoint 2007 State Machine Workflow) on a 64-bit computer. The first exception message is: "Object reference not set to an instance of an object". The second message is: "SharePoint site location entered is not valid. The SharePoint site at http://<serverpath> could not be found. Verify that you have typed the URL correctly".

To resolve this issue:

Do not use the Visual Studio SharePoint workflow templates on a computer that is running a 64-bit operating system. For more information, see the Help topic "Troubleshooting SharePoint Workflow Solutions", which describes the problem.

2.3.5.6. Visual Studio Tools for Office (VSTO) solution does not run on a x64 computer if you set the platform target to x64.

If you set the platform target on the Build tab of the project properties to x64, you can compile the project, but the solution will not run. Setting the platform target to x64 requires the solution to run in a 64-bit process. Office runs in a 32-bit process. Therefore, Office cannot load the solution.

To resolve this issue:

Set the platform target in the Build tab of the project properties to 'Any CPU'. Doing this causes the solution to run in Office as a 32-bit process.

2.3.5.7. Excel and Word projects do not run when projects are open in both Visual Studio 2008 and Visual Studio 2005.

This error may occur if you have Excel 2003 projects or Word 2003 projects open in both Visual Studio 2008 and Visual Studio 2005 at the same time. When you run a project, the following message appears:  "The customization assembly could not be found or could not be loaded. You can still edit and save the document. Contact your administrator or the author of this document for further assistance."

To resolve this issue:

Close one of the projects. Then, you can run the other project.

2.3.5.8. Controls on a document are not rendered correctly after the document is copied into a new project.

This problem may occur if you create a new document-level customization project by using a document that was customized in another project. If the document contains managed controls, these controls appear as blank squares in the designer of the new project. This happens because the property values of these controls are stored in the designer file of the original project.

To resolve this issue:

Copy the property values and custom event handling code for each control from the designer file of the original project and paste them in the new project.

2.3.5.9. Crystal Reports throws exceptions when it is used with Visual Studio Tools for Office (VSTO) solutions.

If you use Crystal Reports and specify ADO.NET as a data provider, exceptions might be thrown even in valid scenarios.

To resolve this issue:

If you are planning to use Crystal Reports in a VSTO solution, create a separate application domain and use Crystal Reports only in that application domain.

2.3.5.10. Visual Studio 2008 throws an exception if you attempt to create a SharePoint workflow project on a computer that does not have SharePoint installed.

Visual Studio 2008 throws the following exception message: "Could not load file or assembly 'Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified."

To resolve this issue:

Install SharePoint on the development computer before you create a SharePoint 2007 Sequential Workflow or SharePoint 2007 State Machine Workflow project. For more information, see the Help topic "Troubleshooting SharePoint Workflow Solutions", which describes the problem.

2.3.5.11. Compiling the SharePoint workflow sample causes an error message to appear.

When you compile the C# version of the SharePoint workflow sample, the following error message appears:

"Microsoft.Build.Tasks.Delete" task could not be loaded from the assembly D:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Build.Tasks.dll. Could not load file or assembly 'file:///D:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available."

This error appears because the project file, SeqWKFlow.csproj, references an incorrect version of the .targets file.

To resolve this issue:

Open SeqWKFlow.csproj in a text editor, and remove the following line of text, which you can find at line number 86 in the file:

<Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets" />.

Add the following line of text:

<Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" />

2.3.6. Web Development

There are no known issues.

2.3.7. Windows Communication Foundation (WCF) Tools

2.3.7.1. WcfTestClient may throw an exception if Biztalk Service SDK is installed.

The Biztalk Service SDK introduces a metadata exchange (MEX) endpoint in the <client> section of the <system.serviceModel> element in the machine.config file. This setting generates the following exception when the service is invoked in WcfTestClient:

System.NullReferenceException: Object reference not set to an instance of an object

To resolve this issue:

When you run the WcfTestClient, modify the machine.config file (located in \WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG) by commenting out the <client> section that is nested in the <system.serviceModel> element. Re-enable the section when you use the Biztalk service SDK.

2.3.7.2. Setupvroot.bat setup script for WCF samples may fail on Windows Vista.

On Windows Vista, if the NetMsmqActivator service is enabled and Message Queuing (MSMQ) is not installed, then the iisreset utility does not work and the WCF samples setup script Setupvroot.bat will not run.

To resolve this issue:

Before you run the WCF samples setup script Setupvroot.bat, make sure MSMQ is installed or disable the NetMsmqActivator service on Windows Vista.

2.3.7.3. WcfTestClient does not support some features of WCF.

The following features of WCF are not supported by the WcfTestClient in this release.

- Message contract & XML serialization, non-WCF Web services

- Session/Context binding

- Transaction

- Duplex contract

- Windows CardSpace, Certificate,  User name/Password, Windows Authentication

- Types: Stream, IDictionary collection and DataSet

To resolve this issue:

No wokaround is available.

2.3.7.4. Service Model Metadata Utility tool (SvcUtil.exe) cannot generate data contracts from a running service.

An example at the end of the Svcutil.exe help output indicates that you can use the /dataContractOnly (/dconly) option to generate data contracts from a running service:

svcutil.exe /dconly http://service/metadataEndpoint
- Generate Data Contract types from a running service or online metadata documents.

This usage does not work. You can only use the /dconly option to generate data contracts from local metadata files.

To resolve this issue:

Download the metadata from the running service by running the following command: 

svcutil.exe /target:metadata http://service/metadataEndpoint

Run Svcutil.exe with the /dconly option on the downloaded metadata files, as follows:

svcutil.exe /dconly *.wsdl *.xsd

2.3.7.5. Code generation language support in the Service Model Metadata Utility tool (Svcutil.exe).

The Svcutil.exe tool can generate code for Web service clients and data types from metadata in any language that has a managed code provider. Svcutil.exe has been tested with the C#, Visual Basic, and C++ managed code providers. Other code providers have not been tested and may generate code that does not compile or may be otherwise unusable.

To resolve this issue:

Use one of the supported managed code providers, or manually edit the generated code to resolve any compilation issues.

2.3.7.6. Managed C++ code generated by using the Service Model Metadata Utility tool (Svcutil.exe) may not compile.

You can use the Svcutil.exe tool to generate code for Web service clients and data types from metadata. However, there are known issues with the C++ code provider in Visual Studio 2008 that can cause the tool to generate Managed C++ code that may not compile.

To resolve this issue:

Manually alter the generated code to resolve any compiler errors.

2.3.7.7. WCF service library project will always run when it is part of a solution.

WCF service library projects are set up to automatically start their service when a project in the solution is run regardless of the settings in Multiple Startup projects.

To resolve this issue:

Create separate WCF service library solutions that include only client projects that depend on the services contained in the library that is executing. Include the service assemblies in the hosting application's solution in all other scenarios.

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

2.3.8.1. Property Browser displays values, such as dates and numbers, by using the U.S. format.

The property browser 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 property browser it will be converted with the assumption that it is in mm/dd/yy format.

To resolve this issue:

No workaround is available.

2.3.8.2. Code Refactoring does not change XAML files.

If you use code refactor to make type or member modifications, the refactoring will not propagate to the XAML files. 

For example, given a UserControl named MyCustomControl, if you use refactor to change the name of that UserControl to FancyControl from the code file, that name change will only affect code files and any instances of MyCustomControl in XAML files will not be updated.

Additionally, the build may incorrectly succeed without error until a rebuild or clean of the project or solution is performed.

To resolve this issue:

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

2.3.8.3. Making changes to XAML will not refactor code files.

If you make changes to 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 Button, which has event handlers associated with it, from 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.

If you right-click a XAML file in Solution Explorer and then click Rename, the file name will be changed but there will not be any prompt to refactor the class name in XAML or 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. Using the Property Browser during debugging may cause Visual Studio to crash.

If you use the Property Browser to make changes to your XAML files while you are debugging an application, Visual Studio may crash.

To resolve this issue:

Change your XAML file before you debug, or stop debugging before you change the XAML file.

2.3.8.6. Visual Studio hangs or crashes when a XAML file that contains a ControlTemplate in a ResourceDictionary is being edited.

Visual Studio may hang or crash while you are editing a XAML file because there is a known issue with ControlTemplate resources in an resources block. 

For example:

<Window.Resources>
    <ControlTemplate x:Key="ct" . . . > . . . </ControlTemplate>
. . .
</Window.Resources>

To resolve this issue:

Do one of the following things:

- Put your control templates in a separate ResourceDictionary and use the MergedDictionaries property in the element resources block.

- Put your control templates in an app.xaml dictionary.

- Wrap your resources in an unnecessary but harmless <ResourceDictionary></ResourceDictionary>.

- Put your ControlTemplate in a Style.

2.3.8.7. Visual Studio may hang when you bind to long ObjectDataProvider method calls.

When you bind to an ObjectDataProvider through XAML and load it in the WPF designer, if the ObjectDataProvider makes a call to a database, the operation can be very long and memory-intensive. As a result, the WPF designer may hang until the operation completes.

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.8 You receive an "Option Strict On disallows implicit conversions" error message when you compile a WPF application in Visual Basic 2008

You may receive an error message that resembles the following when you try to compile a Windows Presentation Foundation (WPF) program in Microsoft Visual Basic 2008:

Option Strict On disallows implicit conversions from 'System.Windows.Application' to 'WpfApplication1.Application'.

This issue occurs when Option Strict is set to On at the project level

To resolve this issue:

To work around this issue in the current project, modify the code in the Mywpfextension.vb file. To modify the code in the Mywpfextension.vb file, follow these steps:

  1. In the Error List, double-click the error message in described in the "Symptoms" section. Notice that the Mywpfextension.vb file opens.
  2. Locate the following line of code: Return Global.System.Windows.Application.Current
  3. Modify the code in step 2 as follows:  Return CType(Global.System.Windows.Application.Current, Application)
  4. Build the project again.

An updated template will be released in the near future; to obtain the updated template, check the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=105130

Important: You do not have to unzip the compressed file with a .zip file name extension to install the updated template. To install the updated template, put the .zip file in the \Visual Studio 2008\Templates\ProjectTemplates\Visual Basic folder, and then restart Visual Studio 2008.

2.3.9. Windows Workflow Foundation (WF) Tools

2.3.9.1. Custom activities do not appear in the Visual Studio Toolbox if you use Visual C++ development settings.

Custom activities do not appear in the Visual Studio 2008 Toolbox if you use Visual C++ development settings.

To resolve this issue:

Use different development settings, for example, Visual Basic or C#.

2.3.9.2. Cannot select overloaded method names on CallExternalMethodActivity.

When you have two or more methods on a CallExternalMethodActivity activity that have the same name but different parameters, you cannot select unique versions of the methods in the drop-down list in the workflow designer. Any overloaded method you select is automatically defaulted to the first method that is defined in your activity.

To resolve this issue:

Use unique method names to avoid this problem.

2.3.10. Windows SDK Integration

2.3.10.1. To develop applications targeted for the IA64 platform, the Windows SDK must be installed.

IA64 platform-specific libraries, compilers, and tools are not included in Visual Studio 2008. Code that targets the IA64 platform cannot be compiled in Visual Studio 2008 without an additional installation. If you try to compile by using the IA64 cross-compiler, you will get an error that resembles the following one:

> cl /EHa /clr /TP /MD /D_CRT_SECURE_NO_DEPRECATE /D_SCL_SECURE_NO_DEPRECATE repro.cpp

C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\msclr\appdomain.h(23) : fatal error C1083: Cannot open include file: 'mscoree.h': No such file or directory.

To resolve this issue:

To install IA64 platform-specific libraries, compilers, and tools, install the Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5, and ensure that IA64 Compilers and Libraries are selected on the Installation Options screen.

3. Related Links

3.1. Visual Studio Team Foundation Server Readme: http://go.microsoft.com/fwlink/?LinkId=102510.

3.2. Visual Studio Express Edition Readmehttp://go.microsoft.com/fwlink/?LinkId=102509.

3.3. .NET Framework Readme:http://go.microsoft.com/fwlink/?LinkId=102511

.

3.4. MSDN Library for Visual Studio Readme: http://go.microsoft.com/fwlink/?LinkId=102512

3.5. Download SQL Server Compact 3.5 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkID=96191 and Synchronization Services for ADO.NET v1.0 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkId=80742. To add these to the Visual Studio Combined Help Collection, complete the following steps.

1. Click Start, point to All Programs, Microsoft Visual Studio 2008, and then click Microsoft Visual Studio 2008 Documentation.

2. In the Visual Studio Combined Help Collection, click Help and then click Index.

3. In the Look for box, type "collection manager", and then click the Help entry under collection manager in the Index.

4. In the Combined Help Collection Manager topic, select SQL Server Compact 3.5, and then click Update VSCC.

5. In the two dialog boxes that appear, read the requirements, and then click OK.

6. Close and then reopen the Visual Studio Combined Help Collection. SQL Server Compact Books Online is now available in the Table of Contents, Index, Search, and F1 Help.

3.6. For the latest information about issues with using the WPF designer in Visual Studio 2008, see the Cider wiki on Channel9, http://go.microsoft.com/fwlink/?LinkId=83541.

3.7. Visual J# MSDN developer center:http://go.microsoft.com/fwlink/?LinkId=102513.

3.8. The XML to Schema tool can be downloaded from http://go.microsoft.com/fwlink/?LinkId=102514.

The XML to Schema tool is a free project-item template that automates the creation of XML schema sets from any number of XML documents. If you are working with LINQ to XML in Visual Basic 2008, this utility may significantly improve your editing experience by adding XML schemas (.xsd files) to your project that then provide IntelliSense for XML properties. The tool can also be used to create an XML schema set from a set of existing XML documents.

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