VS2008 Smart Device Project Conversion Scenarios

  • Article

This post summarizes the various combinations of project conversion scenarios when a VS2005 Smart Device project is opened inside VS2008.

 

1. When a user opens a VS2005 project inside VS2008 Visual Studio Conversion wizard is automatically launched.

2. User is presented with below messages on what will be converted. Items marked in Yellow are specific to Smart Device projects.

If the solution or project is under source control, it will be checked out automatically during the conversion. Be sure the correct Source Control Plug In is active, and no files are exclusively checked out by other users.

 

The Upgrade Wizard upgrades projects that target the .NET Compact Framework 1.0 to target the .NET Compact Framework 2.0.

.NET Compact Framework 2.0 applications will remain unchanged.

SQL Server Mobile 3.0 and SQL Server Compact Edition 3.1 references will be upgraded to SQL Server Compact 3.5 reference.

Additionally, managed Smartphone 2003 projects are upgraded to target Windows Mobile 5.0.

 

Conversion type: In-place with backup to user specified location.

Backup location for projects: <location-of-backup-project>

 

Solution to be converted: <name-of-solution>

Projects:

<name-of-project>

3. User is presented with a project conversion report once finished.

 

What Gets Converted?

4. The conversion wizard upgrades projects that target the .NET Compact Framework 1.0 to target the .NET Compact Framework 2.0.

5. .NET Compact Framework 2.0 applications will remain *unchanged* i.e. they’ll continue to target NETCF 2.0

6. SQL CE 2.0, SQL Server Mobile 3.0 and SQL Server Compact Edition 3.1 references will be upgraded to *SQL Server Compact 3.5* reference.

o User app will now target SQL Server Compact 3.5 instead of 3.0 or 3.1 or 2.0

o SQL Server Compact database file (SDF file) will be converted to be compatible with SQL Server Compact 3.5 from SQL Server Mobile 3.0 or SQL Server Compact Edition 3.1. See below for further details. MSDN Ref: https://msdn2.microsoft.com/en-us/library/bb892923(VS.90).aspx

o SSCE 2.0 SDF file won’t be upgraded to SSC 3.5 SDF format. User must run upgrade.exe tool on the device to do the necessary conversion.

7. Additionally, managed Smartphone 2003 projects are upgraded to target Windows Mobile 5.0.

 

SDF File format conversion related special cases:

1. Scenario: SDF file in the original project is not password protected.

a. SDF file is upgraded to SSC 3.5. Pressing F5 will result in success at runtime.

 

2. Scenario: SDF file in original project is *password protected* and encryped

a. SDF file is *not upgraded to SSC 3.5*. Pressing F5 will result in runtime errors.

b. User must manually perform the SDF file upgrade by removing the connection & re creating the connection to the SQL Server Compact 3.5

 

3. Scenario: SDF file in original project is *password protected* and password is part of connection string

a. SDF file is upgraded to SSC 3.5. Pressing F5 will result in success at runtime.