Converting DevForce 2009 to DevForce 2010

   Here's a checklist of items to go through if you are converting your DevForce 2009 application to DevForce 2010: 

Designer and API Changes
Read the 6.0.1 section of the Release Notes.  The Object Mapper is now fully integrated with the Entity Framework designer, and we have cleaned up portions of the API with some breaking changes.

Rebuilding your Model
You must rebuild your model again using the Entity Framework designer in .NET 4.0.  This is a pain, but unfortunately, Microsoft did not provide a migration tool and you will encounter errors if you try to use your model from .NET 3.5.

Deployment Files
We have simplified much of the deployment, and typical deployments no longer need to have an app.config, EntityService.svc, EntityServer.svc, or ServiceReferences.ClientConfig files.  Instead of trying to modify the DevForce 2009 deployment files, create a sample application using the DevForce template (Silverlight/WPF/WinForms) and use the files and settings from that project as a baseline.

Please chime in on any other areas we should draw attention to, and I will update this post to reflect the best practices.

Edited by ting - 12-Aug-2010 at 6:28pm