Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
End Users
Pocket PCActiveSyncMultimediaEBooksWirelessSmartPhones
Developers
Windows MobileSmartPhonesWinCE ProgrammingVB for WinCEVC++ for WinCEPlatform BuilderTest Tools
PocketPC DirectoryFree SoftwareWeb Resources
Related Topics
PalmMobile PhonesMore Topics ...

Pocket PC Forum / Developers / SmartPhones / January 2010

Tip: Looking for answers? Try searching our database.

Converting .NETCF 2.0 VS 2005 App to VS 2008 Issues

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Noble Bell - 26 Jan 2010 15:09 GMT
Hello,

I am trying to convert a .NETCF 2.0 application I wrote with VS 2005 Pro
over to a .NETCF 2.0 application in VS 2008.

The first thing that comes up is the "Visual Studio Conversion Wizard". I
click "Finish" on the dialog and the project appears to be converting. Then
after a short while I get a popup that tells me,

"One or more projects in the solution could not be loaded for the following
reasons: The application for the project is not installed. These projects
will be labeled as unavailable in Solution Explorer. Expand the project node
to show the reason the project could not be loaded."

Looking at the conversion log, the only thing it tells me is that the
operation could not be completed. Unspecified error.

Any thoughts on how to go about converting this project to VS 2008?

Some controls that I am using:
CameraCaptureControl - Custom written for us
EACompressionCF2
GeoFramework GPS/GIS Component
OpenNETCF
VistaDB.CF20

I don't think these should cause a problem, should they?

Signature

Noble D. Bell
www.noblesoftware.com

Peter Foot [MVP] - 26 Jan 2010 23:11 GMT
Do you have all the same SDKs etc installed in 2008 - e.g. if you installed
WM6 SDK prior to VS2008 you'll need to repair it so it shows up in VS2008.
Are these dependencies referenced locally or were they installed into Visual
Studio so they show up in the Add References dialog - check that they are
all visible from a fresh project in VS2008.
A fairly simple workaround would be to create a new blank Solution/Project
in VS2008 and then add the existing source files to it.

Peter

> Hello,
>
[quoted text clipped - 26 lines]
>
> I don't think these should cause a problem, should they?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.