Updating Projects Created with Previous Tools
Microsoft Visual Studio 2005 provides powerful development tools for the smart device developer. Programmers using C# and Visual Basic can now take advantage of the improved tools offered by Visual Studio 2005, and it is now possible to create a C++ project for a Pocket PC, Smartphone or Windows CE device using the same development environment as is used to create desktop applications.
The improvements to the Visual Studio 2005 development environment, include:
C# source code refactoring tools. For more information, see.
Improved debugging. For more information, see.
Code snippets for C# and Visual Basic. For more information, see.
Improved deployment tools. For more information, see.
Improved smart device emulators. For more information, see.
Migrating Projects from eMbedded Visual C++ to Visual Studio 2005
You can migrate eMbedded Visual C++ projects using a migration wizard. For more information, see.
Migrating Projects from eMbedded Visual Basic to Visual Studio 2005
Projects created in eMbedded Visual Basic (eVB) are not automatically converted to Visual Studio 2005 projects. Instead, you must add the existing source and resource files to a new Visual Basic Smart Device project created in Visual Studio 2005.
Windows Mobile 2003 devices do not contain the eMbedded Visual Basic runtimes in ROM, and although the runtimes may be downloaded to the device as a RAM install, this configuration is not supported.
For more information on using Visual Studio 2005 to convert an eVB project, see the following topics:
Migrating Managed Projects from Visual Studio .NET 2003 to Visual Studio 2005
Visual C# and Visual Basic smart device projects developed in Visual Studio .NET 2003 can be imported into Visual Studio 2005. The Visual Studio Conversion Wizard makes any required changes to the projects.
Updating Projects from 2002 Devices to 2003 Devices
For more information about updating projects to Windows Mobile 2003 from Windows Mobile 2000, see Windows Mobile Platform Migration FAQ for Developers.
Migrating to the eVC 4.0 Environment