Compilation errors appear in the Output window when you build a Smartphone 2003 project that includes code that contains new Visual Basic 2005 language features in Visual Studio 2005

Consider the following scenario. In Microsoft Visual Studio 2005, you create a Microsoft Visual Basic Smartphone 2003 project that uses the Class Library 1.0 template. You add code that contains language features that are new in Visual Basic 2005. For example, you add code that contains partial types or generic types. No indications appear in the Editor window that the code contains errors. You build the project. In this scenario, the Visual Basic 2005-specific code generates compilation errors that appear in the Output window.

This behavior occurs because Visual Studio 2005 uses the following two compilers for Smartphone 2003 projects:

• An IDE compiler
• A code compiler

Visual Studio 2005 uses the IDE compiler in the Editor window to check language syntax as you type. The IDE compiler is a later version that supports Visual Basic language features that are not present in earlier versions.

The code compiler is used to actually compile the project code. Visual Studio 2005 uses an earlier version of the code compiler to build Smartphone 2003 projects. This earlier version does not support the new Visual Basic 2005 language features. Therefore, when you build a Smartphone 2003 project, Visual Basic 2005-specific code generates errors during code compilation. This behavior occurs even though the same code does not generate errors in the Editor window.

This behavior is by design.