troubleshooting Question

.NET Entity Framework 4.1 Code First Problem with ProviderManifestToken

Avatar of retailex
retailex asked on
Microsoft SQL Server.NET Programming
11 Comments1 Solution1670 ViewsLast Modified:
My application needs to connect to two versions of SQL Server, 2005 and 2008.  Because of the differences between the datetime data type on 2008 (datetime2) and 2005 the cached entity model (built by EF 4.1 in memory) is incompatible between the two if I go through a process to connect to an instance of 2008 and then try to connect to an instance of 2005.  If I connect to 2005 and then to 2008 there are no problems.  Before you start telling me to modify the SSDL file's ProviderManifestToken value remember that the POCO (code first) pattern does not use any EDMX file types in the project.  All of that model data is generated at runtime by the entity framework and is not maintained in the project as EDMX (ssdl,csdl,msl) configuration files.  So in essence what I need is a solution or work around to this problem so as not to have to redesign my model too much.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 11 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 11 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros