Feedback
Did this article resolve your question/issue?

   

Article

Is it possible to upgrade to Connect for ADO.Net 4.2 with a WCF RIA services implementation?

Information

 
TitleIs it possible to upgrade to Connect for ADO.Net 4.2 with a WCF RIA services implementation?
URL Nameis-it-possible-to-upgrade-to-connect-for-ado-net-4-2-with-a-wcf-ria-services-implementation
Article Number000114699
EnvironmentProduct: Connect for ADO.Net
Version 4.2
O/S: Windows
Database: N/A
Application: N/A
Question/Problem Description
Problems encountered after upgrading to ADO.Net 4.2 with updating the .edmx using the GUI in VS 2015.  Originally working with Visual Studio 2010 and ADO.Net Version 4.1
 
Steps to Reproduce
Clarifying Information
Error MessageUnable to cast object of type 'DDTek.DB2.Entity.DB2ProviderServices'' to type 'System.Data.Common.DbProviderServices'
Defect Number77200
Enhancement Number
Cause
Due to a Microsoft limitation that makes WCF RIA incompatible with Entity Framework 6.0, it is not possible to keep a WCF RIA services implementation and still upgrade to ADO.Net 4.2.

The WCF RIA is stabalized and Microsoft is not planning to enhance it further.
https://social.msdn.microsoft.com/Forums/silverlight/en-US/afc058f4-2d01-45b8-89c5-2d6fa4f5ca94/is-wcf-ria-services-at-the-end-of-its-life-cycle?forum=silverlightwcf 
Resolution
The Connect for ADO.NET 4.2 Provider only supports entity Framework 6.0.

Microsoft is encouraging WCF users to move to Open RIA services. It is best to port the application to use the Open RIA with Entity Framework 6, which will be aligned with the latest technology stack in the .NET Domain.

With this, it is possible to migrate to Connect for ADO.NET 4.2.
Workaround
Notes
Last Modified Date9/5/2017 7:54 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.