Release Roadmap
th
Support for Visual Studio 2010 RC
DevForce 2009 now works with both Visual Studio 2008 and Visual Studio 2010 RC (does not support Beta 2).
Note: DevForce 2009 supports .NET 3.5, not 4.0. You must set the project that includes your DevForce domain model to target .NET 3.5. PLEASE READ THE RELEASE NOTES!
MVVM Version of Four Simple Steps Tutorial
There are now three additional solutions demonstrating how to take the Four Simple Steps solution and use it with MVVM.
The first half of 2010 is going to be big. Microsoft is releasing Visual Studio 2010, .NET 4, Azure, Entity Framework 4, and Silverlight 4. Not to worry… we have a well paved path for you.
We have updated the current version of DevForce with our March 4th
release of DevForce 2009 (v5.2.6)
The target Microsoft technologies are:
- .NET 3.5
- Entity Framework v.1
- Silverlight 3
- Visual Studio 2008 or Visual Studio 2010
Please note that DevForce 2009 developers can only build .NET 3.5 / Silverlight 3 applications even with a version that supports Visual Studio 2010. You’ll need DevForce 2010 to target .NET 4 / Silverlight 4.
We will release DevForce 2010 by the end of April to coincide with Microsoft’s VS 2010 / .NET 4 launch. With so many Microsoft fundamental technologies arriving at once, this will be a major release.
The April release of DevForce 2010 targets these Microsoft technologies:
- .NET 4
- Silverlight 4
- Entity Framework v.4
- Visual Studio 2010
- Azure
Highlights of the April 2010 release
|
Azure
In Q1 2010, Microsoft goes into full production with its cloud computing “Azure” offering
and customer interest has been building steadily. We will demonstrate a DevForce sample application running on
Azure and release it as part of DevForce 2010 along with guidance for you to follow.
|
|
Visual Studio 2010
New extensibility features in VS 2010 enable tighter integration of DevForce with the IDE. Developers can set DevForce model properties and code generation options within the Entity Framework visual designer. Our Silverlight ObjectDataSource can be dragged from The Data Source Window on to the canvas for binding to Data Grids and other visual controls.
|
|
Optional Automatic Save Validation
You can opt-in or opt-out of automatic server and client validation when you save entity changes. You’ll continue to have fine grained, context-sensitive, dynamic control over validation as you do today.
|
|
Asynchronous Collections
Most seasoned developers prefer to implement the async query pattern explicitly. DevForce offers LINQ query extensions that produce async collections – collections that encapsulate the async mechanics – for those developers who would rather DevForce handle those details.
|
|
|
Entity Framework 4
EF 4 is actually the second version of Entity Framework and an enormous step forward for the product, most notably for its design-first and code-first support. DevForce 2010 is retooled to leverage many of these new capabilities and to benefit from the performance enhancements that EF 4 makes possible.
|
|
T4 Code Generation
DevForce has been generating model objects from T4 templates since DevForce v.5.3; we just didn’t tell anyone. With DevForce 2010 developers can customize those templates using a simple, extensible API. No need to learn T4 or risk breaking the template... Now anyone can take control of the generated code with ease and safety.
|
|
INotifyDataErrorInfo
You decide how your objects respond to validation errors detected during property sets. They can throw exceptions as they do by default today or they can observe the protocols expected of objects that implement IDataErrorInfo or the new INotifyDataErrorInfo interface in .NET 4.
|
|
|
Disclaimer:
Release dates and features mentioned are our best estimates, not commitments; please plan accordingly.
|
Find out about everything new in our
Release Notes