tag:blogger.com,1999:blog-5238131531249720750.post5428186249125551199..comments2024-03-19T13:28:26.291+01:00Comments on Everything SQL Server Compact: A breaking change in Entity Framework 6.1.2 when using EDMX and SQL Server 2008/2005ErikEJhttp://www.blogger.com/profile/12641272161018114573noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-5238131531249720750.post-24650725390639022312018-03-02T22:55:53.784+01:002018-03-02T22:55:53.784+01:00The way to fix this with SQL Server 2008 and EF Co...The way to fix this with SQL Server 2008 and EF Core is noted at https://github.com/aspnet/EntityFrameworkCore/issues/4616#issuecomment-221331425ferventcoderhttps://www.blogger.com/profile/08907108080259292428noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-32633031658069280472017-09-20T09:33:04.273+02:002017-09-20T09:33:04.273+02:00He Mark Clouden: I know this is an old post, but I...He Mark Clouden: I know this is an old post, but I just had the same issue you describe. So this does affect Code First apps as well. <br />We have one DbContext, which can connect to different databases - if the first database is a 2012 SQL Server and another one is a 2008 SQL Server the SQL generation fails.Remanhttps://www.blogger.com/profile/13301226000263624096noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-62240869098037790122017-07-24T17:43:20.916+02:002017-07-24T17:43:20.916+02:00Ricker: Yes, you can also fix it in code: https://...Ricker: Yes, you can also fix it in code: https://romiller.com/2014/06/10/reducing-code-first-database-chatter/ ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-71225349003304716502017-07-24T17:06:15.608+02:002017-07-24T17:06:15.608+02:00Ihave some news on this. I'm writing an Web. A...Ihave some news on this. I'm writing an Web. API project in VS 2017. It has no edmx file anymore, and the error is thrown. Am I Doomed, any way to do this programatically?Ricker Silvahttps://www.blogger.com/profile/10861485242115599670noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-66966105280475293602017-03-14T06:37:44.857+01:002017-03-14T06:37:44.857+01:00Thanks for this , saved me a lot of time.Thanks for this , saved me a lot of time.Jorge Chinchillahttps://www.blogger.com/profile/09311260660457941399noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-20128124155779174892016-08-29T13:50:20.462+02:002016-08-29T13:50:20.462+02:00I consider this a breaking change, too - a bug in ...I consider this a breaking change, too - a bug in the Entity Framework Designer in Visual Studio. Thank you for the fix. I'm sure you saved me a ton of time!Suncat2000https://www.blogger.com/profile/10404022711477229533noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-39761532562053881742016-07-01T17:23:53.337+02:002016-07-01T17:23:53.337+02:00Thanks to you, it works for me!Thanks to you, it works for me!Panchofhttps://www.blogger.com/profile/02959587490135695030noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-86705860237987298662016-05-12T10:09:31.330+02:002016-05-12T10:09:31.330+02:00Thanks!Thanks!Lazy Foxhttps://www.blogger.com/profile/02476886020441078409noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-89436347557630079222016-05-03T16:56:34.109+02:002016-05-03T16:56:34.109+02:00Downright terrible that the EDMX tool doesn't ...Downright terrible that the EDMX tool doesn't remember the version of the ProviderManifestToken, or that you can only access it via the XML file rather than the properties window.<br />larrybudhttps://www.blogger.com/profile/10113342747864555237noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-6778779183335063092016-04-18T14:50:36.330+02:002016-04-18T14:50:36.330+02:00Tim: As noted in my blog post, I am not sure that ...Tim: As noted in my blog post, I am not sure that an official fix is "possible"ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-12945382872641216682016-04-18T14:44:11.945+02:002016-04-18T14:44:11.945+02:00I'm also having this problem. Is there still n...I'm also having this problem. Is there still no official Fix?Anonymoushttps://www.blogger.com/profile/09709321340993458571noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-50447961694973134602015-03-13T19:50:57.771+01:002015-03-13T19:50:57.771+01:00Thanks, Mark. Are both the DcContext instances you...Thanks, Mark. Are both the DcContext instances you mention the same class?ErikEJhttps://www.blogger.com/profile/12641272161018114573noreply@blogger.comtag:blogger.com,1999:blog-5238131531249720750.post-33244128587907549182015-03-13T19:39:07.415+01:002015-03-13T19:39:07.415+01:00Just so you know, and since your post appears earl...Just so you know, and since your post appears early in a search, this _can_ impact code first - in a very specific scenario.<br /><br />I like to keep all configuration data in a database. So with this custom config provider I bootstrap an application with a connection string 'A' and retrieve application configuration from it, including the connection string to the real database (connection string 'B').<br /><br />I create a dbcontext instance to 'A' and retrieve the connection string 'B', and then create a new dbcontext to query 'B' with a EF query using Take/Skip constructs, and it fails in exactly the way you describe.<br /><br />After a bit of thought I realized that my database 'A' was 2012 and 'B' was 2008, matching your description of the issue - just with the difference that CodeFirst builds its assumptions based on the first database that it connected to.<br /><br />Wouldnt have found this without your initial post to get me thinking - so thanks. And hopefully you can include this info about CodeFirst so the next person searching on this can benefit.<br /><br />Mark CloudenAnonymoushttps://www.blogger.com/profile/09849392315490617746noreply@blogger.com