Visual Studio 2008 Express Editions Readme

 

·     1.1. Supported Architectures

·     1.2. Supported Operating Systems

·     1.3. Hardware Requirements

·     2.1. Installing

·             2.1.1. General Issues

·             2.1.2. Visual C++ Express Edition

·             2.1.3. Visual C# Express Edition

·             2.1.4. Visual Basic Express Edition

·             2.1.5. Visual Web Developer Express Edition

·     2.2. Uninstalling

·             2.2.1. General Issues

·             2.2.2. Visual C++ Express Edition

·             2.2.3. Visual C# Express Edition

·             2.2.4. Visual Basic Express Edition

·             2.2.5. Visual Web Developer Express Edition

·     2.3. Product Issues

·             2.3.1. General Issues

·             2.3.2. Visual C++ Express Edition

·             2.3.3. Visual C# Express Edition

·             2.3.4. Visual Basic Express Edition

·             2.3.5. Visual Web Developer Express Edition

·      

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, 192 MB RAM, 1024x768 display, 5400 RPM hard disk

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

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

·  1.3 GB of available disk space for the full installation

2. Known Issues

2.1. Installing

2.1.1. General Issues

2.1.1.1. Repair from media option does not work for repairing Visual Studio Express language pack.

User decides to repair Visual Studio Express language pack and selects the source media option instead of the download again option. User cannot select SFX, which contains the source media, because the only available option is to select CD layout.

To resolve this issue:

1. By using Control Panel, run a repair on the Visual Studio Express language pack.

2. When the dialog box appears, select the download again option.

-or-

- Uncompress SFX and then select it as the source media option.

2.1.1.2. Download of Visual Studio Express failed.

2.1.1.2.1. Configuration Errors

This error occurs when BITS interfaces are not registered or the registry settings are corrupted.

To resolve this issue:

- Upgrade to BITS 2.0 from http://www.microsoft.com/downloads/details.aspx?FamilyId=B93356B1-BA43-480F-983D-EB19368F9047&displaylang=en

-or-

- Repair the BITS service by running the Bitsadmin tool at the command prompt, as follows: bitsadmin /util /repairservice /force

You can download the Bitsadmin tool from: http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en.

2.1.1.2.2. Network Errors

These errors may occur for the following reasons:

- Unable to reach download server.

- URL not found on the server.

- Server is overloaded.

- Bad Gateway or Proxy.

- Network is disconnected.

- Proxy does not support HTTP 1.1.

To resolve this issue:

1. Make sure that you are connected to the network. You may have to exit Setup.

2. Do one of the following things.

- Provide correct settings for the proxy server and ensure that your computer can correctly resolve the proxy server.

-or-

- Upgrade to BITS 2.0. You can download BITS 2.0 from
http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en .

2.1.1.2.3. Disk Errors

This error occurs when the BITS service failed to create a file or write to a file. Because another program, such as chkdsk.exe, might be running, the disk might be locked and BITS might be prevented from writing to the file.

To resolve this issue:

- Make sure that no other program that could lock the disk is running and then try the download again.

-or-

- Restart the computer and then run Setup again. Make sure that you are connected to the Internet.

2.1.1.2.4. Proxy Errors

The BITS service failed because of one of the following proxy-related errors:

- The Proxy settings are not valid.

- The proxy server requires authentication.

- The computer is not able to resolve the proxy server.

To resolve this issue:

- Provide correct credentials for proxy server authentication and then start Setup again.

-or-

- Upgrade the proxy server to support HTTP1.1 and ensure that the proxy supports implicit credentials (for example, NTLM). You may have to contact your network administrator.

-or-

Bypass the proxy server by changing your Internet Explorer proxy settings.

To bypass a proxy server:

1. In Internet Explorer, click Tools and then click Internet Options.

2. Click the Connections tab and then click LAN Settings.

3. Under Proxy server, clear Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections.) and then click OK.

4. Click OK again.

If you need further assistance with your proxy server settings, contact your network administrator.

2.1.1.2.5. Other Errors

The BITS Service does not run in the following scenarios:

- Safe-boot mode.

- On Windows 2000 from a remote desktop connection.

- When Setup is installed by using a "run as" command.

To resolve this issue:

No workaround is available. These scenarios are not supported.

2.1.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 with SQL Server and then upgrade to SQL Server 2008 SP1 or SQL Server 2005 SP3 by using Windows Update.  As an alternative, you can install SQL Server 2008 SP1 before you install Visual Studio. 

The following steps are for installing Visual Basic 2008 Express Edition with SP1, together with SQL Server 2008, on Windows 7 RC.    Other Express Editions can be installed the same way.  

1.     Download Microsoft Visual Basic 2008 Express Edition with SP1 from the Express Edition download page.

2.     During setup, make sure to select “Microsoft SQL Server 2008” on the “Optional Components” page.

3.     When SQL Server 2008 installation starts, you will receive a compatibility warning message.

4.     Select Run Program to continue the installation.

5.     You will then be presented with a second compatibility warning dialog when running “setup.exe”.  Select Run Program again.

6.     After installation is completed, start Windows Update.

7.     If you do not have Microsoft Update installed, click “Get updates for other Microsoft products. Find out more” and follow the instructions to install Microsoft Update.   

8.     Select Check for updates in the left-hand pane.   

9.     Under the optional updates, “Microsoft SQL Server 2008 Service Pack 1” should be listed.

10.  If “Microsoft SQL Server 2008 Service Pack 1” is not listed listed as an optional update, go here to download the service pack.

11.  Select the box next to the entry and click OK.   

12.  Windows update will then install SQL Server 2008 SP1.

13.  After installation is completed, you may be prompted to reboot.

More Information

If you are installing SQL Server 2005 Express (any Express edition) or SQL Server 2008 Express (Runtime Only), you can just download the SQL Server Express package that contains the latest service pack. This may seem counter-intuitive if you already have an Express package, but installing it and then downloading and applying the service pack takes longer than downloading and installing a package that already contains the latest service pack. Also, the SQL Server 2008 Express service pack package is actually bigger than the SQL Server Express package because the service pack is shared with all SQL Server 2008 editions.

·         Download SQL Server 2008 Express SP1

·         Download SQL Server 2005 Express Edition SP3

·         Download SQL Server 2005 Express Advanced Edition SP3

·         Download SQL Server 2005 Express Toolkit Edition SP3

·         Download SQL Server 2005 SP3

·         Download SQL Server 2008 SP1

If you have to install a SQL Server 2008 Express edition other than Runtime Only edition 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.1.4. Upgrading to SQL Server Compact 3.5 RTM from SQL Server Compact 3.5 CTP or SQL Server Compact 3.5 Beta is not supported.

Upgrading from the CTP and Beta versions of SQL Server Compact 3.5 to the release version is not supported. Uninstalling the CTP and Beta versions of Visual Studio 2008 does not uninstall SQL Server Compact 3.5. The CTP and Beta versions of SQL Server Compact 3.5 must be manually uninstalled before the release version of Visual Studio 2008 is 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.1.5. Users get an error message, "A problem has been encountered while loading the setup components. Canceling setup".

An error message, "A problem has been encountered while loading the setup components. Canceling setup", is displayed and then Setup is canceled.  This only occurs on systems that do not have Windows Installer 3.1.  Users should install Windows Installer 3.1 and then try Setup again.

To resolve this issue:

1. By using the Control Panel, check whether Windows Installer 3.1 is in the list of installed programs.

2. If Windows Installer 3.1 is not installed, install it from Windows Installer 3.1 Redistributable (v2) and then try Visual Studio 2008 Setup again.

2.1.1.6. 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 resolutions:

- This error message indicates that other Setup programs might be running on the computer. After the other Setups have finished, restart the computer and then run Visual Studio 2008 Setup.

- Windows Updates might be installing on the computer. Wait for the Windows Update installations to finish and then restart the computer and run Visual Studio 2008 Setup.

- In Task Manager, check whether msiexec.exe is running. If msiexec.exe is running, wait for it to finish and then restart the computer and run Visual Studio 2008 Setup.

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

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

A. If you have installed Visual Studio Code Name "Orcas" Beta1 or Visual Studio 2008 Beta 2, uninstall them as follows.

- By using the Control Panel, remove "Microsoft Visual Studio Codename Orcas Professional" and other related Visual Studio IDE installations, such as Professional, Standard, Enterprise Architect, or Team Suite. All components will be chain-uninstalled with the product. This lets the user uninstall an earlier release, and then install a newer release without manually uninstalling the product.

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

1. In the Control Panel, open Add or Remove Programs.

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 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 IDE 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.1.1.8. Installing Visual Studio Express 2008 on Windows Vista sometimes fails when Windows Updates are installed at the same time. 

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

To resolve this issue:

Wait for Windows Updates to finish. Restart the computer and then restart Visual Studio Express Edition Setup.

2.1.1.9. Installing Visual Studio 2008 side-by-side with Visual Studio 2005 on the same computer 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 the .NET Framework 2.0.

To resolve this issue:

Repair .NET Framework 2.0 separately.

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

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

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.1.11. 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 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 installation process.

You can find the 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 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. Doing this may require a restart when Setup is finished.

2.1.1.12. Windows Automatic Update balloon 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 balloon notification pops up  and asks you to restart the computer.

To resolve this issue:

Do not restart until Visual Studio installation finishes.

2.1.1.13. Visual Studio Express 2008 does not work after an upgrade to Windows Vista RTM from Windows XP or Windows Server 2003.

Visual Studio Express 2008 does not work after an upgrade to Windows Vista RTM from Windows XP or Windows Server 2003.

To resolve this issue:

By using the Control Panel, do the following steps.

1. Uninstall .NET Framework 3.5.

2. Reinstall .NET Framework 3.5 from Visual Studio Express 2008 CD or http://www.microsoft.com/.

3. Repair Visual Studio Express 2008.

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

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

To resolve this issue:

1. Open Task Manager.

2. Depending on  which Visual Studio Express Edition Setup is running, select one of the following in Task Manager: "Visual C++ 2008 Express Edition Setup" or "Visual Basic 2008 Express Edition Setup" or "Visual C# 2008 Express Edition Setup" or "Visual Web Developer 2008 Express Edition Setup".

3. Click End Task.

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

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

During Installation or Uninstalling of Visual Basic 2008 Express Edition, Visual C++ 2008 Express Edition, Visual C# 2008 Express Edition, Visual Web Developer 2008 Express Edition, 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:

Visual C++ 2008 Express Edition Setup

Visual C# 2008 Express Edition Setup

Visual Visual Basic 2008 Express Edition Setup

Visual Web Developer 2008 Express Edition Setup

setup

To resolve this issue:

Click on "Ignore" and continue with setup.

2.1.1.16. Setup could not install the following component: Microsoft Silverlight Runtime

Silent installation of Silverlight runtime may fail on the machines with existing pre-release versions of Silverlight engine.

To resolve this issue:

Visit http://www.microsoft.com/silverlight/, or manually run Silverlight setup from WCU\Silverlight\Silverlight1.0.exe on Visual Studio Express media.

Visiting Silverlight enabled web location will install latest Silverlight runtime on the machine, or upgrade the existing version.

2.1.2. Visual C++ Express Edition

There are no known issues.

2.1.3. Visual C# Express Edition

There are no known issues.

2.1.4. Visual Basic Express Edition

There are no known issues.

2.1.5. Visual Web Developer Express Edition

There are no known issues.

2.2. Uninstalling

2.2.1. General Issues

2.2.1.1. When Visual Studio 2008 Express is being uninstalled, the user is prompted to close running applications and the message only shows numbers. 

During uninstallation, Visual Studio Express Setup may prompt the user to close existing applications that could affect the uninstallation process. In the message, the user may see Process IDs of applications that should be closed. The user cannot see the names of the applications.

To resolve this issue:

The user can find the names of the applications that should be closed by looking up 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 uninstallation. Doing this may require a restart when uninstallation is finished.

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

Uninstalling Visual Studio 2008 may display a message that prompts the user to close running applications. Some of the applications may have numeric identifiers and some may have empty identifiers. In the message, Process IDs may be shown, but the names of the applications that should be closed 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 when uninstallation is finished.

2.2.1.3. Uninstalling one language version of an Express Edition removes the Start menu shortcuts for all language versions of the same edition.

Multiple language versions of Visual Studio 2008 Express Editions can be installed and used on the same computer. However, uninstalling one language version of an Express Edition removes the Windows Start menu shortcuts for all language versions. For example, if you have installed both the English and French editions of Visual Basic 2008 Express Edition, and then uninstall either language version, the remaining version cannot be started from the Start menu.

Note: This affects all Express Editions except Visual Web Developer 2008 Express Edition.

To resolve this issue:

You can replace the missing shortcuts by performing a Repair through the Express Edition's Setup Maintenance Mode, as follows.

1. In the Control Panel, click Add or Remove Programs (Programs and Features on Windows Vista).

2. Select the product you want to repair and then click the Change/Remove button (Uninstall/Change on Windows Vista).

3. Select Repair or Reinstall and then click Next.

4. Choose the installation media path and then click Install.

The Start menu shortcuts should now be available.

2.2.2. Visual C++ Express Edition

There are no known issues.

2.2.3. Visual C# Express Edition

There are no known issues.

2.2.4. Visual Basic Express Edition

There are no known issues.

2.2.5. Visual Web Developer Express Edition

There are no known issues.

2.3. Product Issues

2.3.1. General Issues

2.3.1.1. In O/R Designer, an error message, “There is no Unicode byte order mark. Cannot switch to Unicode”, occurs 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 raise the “There is no Unicode byte order mark. Cannot switch to Unicode” error.

To resolve this issue:

- Right-click the .DBML file in Solution Explorer, open it 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.1.2. Cannot publish ClickOnce applications to a remote server by using FTP or HTTP in Visual Basic Express Edition and Visual C# Express Edition. 

When you try to publish a ClickOnce application to a remote server from Visual Basic Express Edition or Visual C# Express Eidition by using FTP or HTTP, the message "Failed to connect to '<server_name>' with the following error: Unable to create the Web site '<server_name>'. The components for communicating with FrontPage Server Extensions are not installed." is displayed.

To resolve this issue:

- Install Visual Web Developer Express Edition.

-or-

1. Use a local file path to publish, for example, '\publish'.

2. Use a Windows FTP program or an external FTP program to copy the '\publish' directory to the remote server.

For more details about this issue, see http://go.microsoft.com/fwlink/?LinkId=102310.

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

The Encrypt property is no longer used in the SqlCeConnection class. The property is retained in SQL Server Compact 3.5 only 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.4. During the upgrade of a Visual Studio 2005 project to Visual Studio 2008, an encrypted SQL Server Compact database is not upgraded and ClickOnce applications must be republished.

Database (*.sdf) files that were created by earlier versions 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 must be manually upgraded. If the Visual Studio 2005 project uses ClickOnce to publish an application, 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.

As an alternative, 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 anapplication, 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.5. SQL Server Compact 3.5 data type for parameters such as SqlDbType or DbType should be explicitly set.

If the data types for parameters such as SqlDbType or DbType are not explicitly set, an exception is 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.6. Property Browser displays values such as dates and numbers by using the U.S. format.

The property browser in the Windows Presentation Foundation (WPF) designer displays and edits values by using the U.S. format. This matches the XAML convention of using the en-US CultureInfo.  For example, dates and numbers are always in U.S. format. Dates are always displayed as 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.1.7. 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 in the code file, that name change only affects code files and any instances of MyCustomControl in XAML files are not 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 in the XAML files must be made manually. We recommend that you use Find and Replace to do this.

2.3.1.8. Making changes to XAML does not refactor code files.

If you change types or members 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 is not updated.

To resolve this issue:

Modifications in the code files must be made manually. We recommend that you use Find and Replace to do this.

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

Solutions and projects that were created in Visual Studio 2008 can be opened and edited in Expression Blend, but they cannot be built. Also, when you open Expression Blend projects in Visual Studio 2008, they are upgraded to the Visual Studio 2008 format. After this upgrade, the project can still be opened and edited in Expression Blend, but it cannot be built in Expression Blend.

To resolve this issue:

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

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

Make changes to your XAML file before you debug, or stop debugging before you modify the XAML file.

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

If Visual Studio hangs or crashes when you are editing a XAML file, the cause may be 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.1.12. 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.  That situation may cause the WPF designer to hang until the operation finishes.

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.2. Visual C++ Express Edition

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

If a project 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 SKU 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, as follows.

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

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

3. Select Save with Encoding and then select Encoding: Unicode - Codepage 1200.

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

When customers are debugging an image (exe or dll) that was created by linking one or more .netmodules by using link.exe, they may find that when they debug into assemblies that are contained by the linked .netmodules, the debugger interprets the code as C++/CLI rather than the language that was used to create the assembly. 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. Visual C# Express Edition

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

When customers are debugging an image (exe or dll) that was created by linking one or more .netmodules by using link.exe, they may find that when they debug into assemblies that are contained by the linked .netmodules, the debugger interprets the code as C++/CLI rather than the language that was used to create the assembly. 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.4. Visual Basic Express Edition

2.3.4.1. Renaming a file 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 is changed but there is no prompt to refactor the class name in XAML or code-behind. In particular, if you rename the XAML file that is referenced in 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. We recommend that you use Find and Replace to do this.

2.3.5. Visual Web Developer Express Edition

There are no known issues.

3. Related Links

3.1. Visual Studio Readmehttp://go.microsoft.com/fwlink/?LinkId=102508.

3.2. .NET Framework Readme:http

://go.microsoft.com/fwlink/?LinkId=102511

.

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

3.4. 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 the Visual Studio Combined Help Collection and then reopen it. SQL Server Compact Books Online is now available in the Table of Contents, Index, Search, and F1 Help.

3.5. 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.6. Visual J# MSDN developer center:http://go.microsoft.com/fwlink/?LinkId=102513.

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