Ayende @ Rahien

Brian commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Thu, 01 Sep 2011 16:02:27 GMT

And here's a link to the beta for anyone who didn't just come here to whine and not return to say "hey, gotta give them credit...they did the right thing this time": http://blogs.msdn.com/b/adonet/archive/2011/08/22/ef-4-2-beta-1-available.aspx

Glenn commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Mon, 15 Aug 2011 15:41:31 GMT

Good to see that this bug is being fixed as we speak: http://blogs.msdn.com/b/adonet/archive/2011/08/11/next-ef-release-plans.aspx

Fish commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sat, 13 Aug 2011 13:45:09 GMT

Hm, i wouldn't shout that loud. Look at the current NH 3.2 release it is'nt so much better...

Aaron Jensen commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Thu, 11 Aug 2011 02:32:28 GMT

Just fork it on github! *duck*

Philip commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Mon, 08 Aug 2011 20:06:49 GMT

To me, there need to be two fixes deployed to the community for this: Fix 1) Remove this regression and fix the bug Fix 2) Fix whatever allowed a breaking change in something that isn't even a minor version or service pack... it's "update 1". That's just for this issue, of course. Separately, they must fix the versioning "strategy" that forces us to track things like "4.1u1 has feature X while 4.1sp1 does not".

Goblin commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Mon, 08 Aug 2011 06:04:32 GMT

@Adam - That is pretty quick - I had a grievous application error in one of their ERP-products (An insert trigger was fired for every row returned by a query - leading to odd results as well as crippling performance). That took 2 and a half years before they said: "We'll fix that in a version that is scheduled for either 3 or 5 years from now"... I wouldn't hold my breath for Connect to shine...

Adam commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sun, 07 Aug 2011 21:16:50 GMT

I have found that Connect is a great place for 'tracking' an issue, but if you want to get traction, you need to find someone within Microsoft who can champion the issue on your behalf. If you are able to do this, and the issue requires only an isolated modification, then you can get a QFE in more reasonable timeframes. I say 'more' reasonable, because the definition of 'reasonable' obviously depends on the severity of the issue. My last QFE turnaround (from initial report), was approximately 12 months.

Dor "The Configurator" Kleiman commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sun, 07 Aug 2011 11:27:12 GMT

Well they can't fix it now, it's too late - it wiuld break backward compatibility with EF 4.1u1...

Ayende Rahien commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sun, 07 Aug 2011 05:46:26 GMT

Tobi, Probably you run into the safety filters. At any rate, yes, we can do that. The problem is that we can do that only for a single provider, and there are dozens out there. Another piece of code in EF now ensures that there can be only a single provider per assembly.

tobi commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sat, 06 Aug 2011 21:31:59 GMT

Oh god why do you strip HTML? Just encode it which almost always is the correct way. class Wrapper : ProfilerDbProviderFactory[System.Data.SqlClient.SqlClientFactory].

tobi commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sat, 06 Aug 2011 21:30:23 GMT

I do not understand the full technical issue, but maybe you can get around it by generating an assembly at runtime containing a single type: class Wrapper : rofilerDbProviderFactory. Set XXX at runtime.

Brian Vallelunga commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sat, 06 Aug 2011 13:54:30 GMT

I asked about fixing this bug on the ADO.NET blog in the comments: http://blogs.msdn.com/b/adonet/archive/2011/08/04/code-first-migrations-your-feedback.aspx Their response was encouraging: "We are working on the logistics of the fix for that issue at the moment, we'll post up our plans shortly."

Cassio Tavares commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Sat, 06 Aug 2011 01:40:29 GMT

I found a bug on Excel because I was developing an application for it using VSTO. I informed MS about the bug, they confirmed it, but I have no perspective to see it fixed because it doesn't happens to normal Excel users and I don't have the necessary level of relationship with MS. I understand that as, "you're not a gold partner or above" or "you didn't buy 2000 Office copies". The problem is killing my application because it has relation to copy & paste. Is there anyone that don't use copy & paste on Excel?

Martin commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 19:15:34 GMT

EF is a terribly engineered product. Because MS has tried and failed so many times to create a decent ORM layer, it's probably become this bastion of politics and in fighting.

fschwiet commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 19:04:00 GMT

I don't use MS Connect as I was scared off just reading their terms of service. The final outcome here isn't in stone hopefully someone on the MS side hears your plea and does the right thing.

Matthew Shapiro commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 18:28:01 GMT

Does Microsoft even do anything with Connect issues? This isn't meant to be funny, I've just seen many legitimate issues on MS Connect that have been ignored.

gunteman commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 15:58:26 GMT

Ugh. It's sad that MS is more and more going this way. Not fixing bugs. Customers and top management often require the use of MS tools, because "it's crucial to have the support". I usually respond that that support is what is lacking. You are much more likely to get support or a fix to a problem when using open source or 3rd party vendor tools. @Rob +1 @Ayende Whatever=Whether

Vadim commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 15:27:24 GMT

Oren, now you should use the code that I'd sent to you :)

Colin Bowern commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 14:42:30 GMT

The lack of proper extensibility points makes EF tough to work with on a number of fronts. This is just another example of ivory tower thinking. Let's hope the EF team is listening and does the right thing because UberProf is an essential tool for teams using ORMs to learn how to use the ORM properly.

Frans Bouma commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 13:41:01 GMT

Khalid: my post on the same issue (linked in the blog above) has a small piece of code which Microsoft can use to fix it (it's for them very easy to fix). For us profiler writers (e.g EF prof or our own) and others who try to integrate into EF using the factory, it's not easy to fix. The only thing I could come up with was generating wrapper classes in memory and compile them in-memory into separate assemblies, which would make the method inside EF work again, but it will always have a 2-3 second penalty due to the compiling of the separate assemblies. That's the sucky part.

NC commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 12:41:31 GMT

MS was doing so well. They were changing there ways, then they go pull a stunt like this. Not cool at all.

Rob Cannon commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 12:19:10 GMT

Is there a connect issue for this? You can certainly get all of your customers (and blog readers) to vote on the issue.

Scooletz commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 11:37:16 GMT

Ugh. That's a MS failure. Period.

Khalid Abuhakmeh commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 11:33:45 GMT

Is the solution an easy fix? If it is, then post the solution online and let's get something rolling to get Microsoft to accept it (in a nice way). EF is getting better, but the versioning is kind of wonky. As an EF user I definitely fear breaking changes with minor upgrades. Thanks for the informative post.

Felipe Fujiy Pessoto commented on Entity Framework 4.1 Update 1, Backward Compatibility and Microsoft

Fri, 05 Aug 2011 10:11:05 GMT

I just don't unserstand, why they did that "voodoo string manipilation" And it isn't possible that anyone on EF team tested this new version with EfProf or any other wrapper like that sample on Microsoft Msdn that make profile and cache