Hello, the problem with EF6 is solved for VS 2012 but still exists in VS 2013. Everything is fine with SA 16.0.0.2052 and VS 2012 Update 4 now. Installed SA after VS, updated SA. Then:
Works perfectly. No need to do anything fancy anymore. Now the same in VS 2013 Update 3. This time, the assistant produces the well known error message "Your project references the latest version of Entity Framework; however ..." as described in this question. The solution is to manually add the provider to the providers in the app.config (or web.config in web projects):
Make sure the version is the exact version of your assembly depending on your patch level. This fix was one of the steps of the workaround described in the question mentioned above and it is still necessary! asked 02 Feb '15, 08:31 Michael Fischer |
In my understanding, Jeff's newer answer to the cited question and the cited CR #770760 description do tell that it is still necessary to add the provider to the according .config file (and they both tell that these are required steps, not workaorunds for older EBFs) so I would think the reported behaviour is still "as documented"... - though not what you are expecting, obviously.
You're right, Volker, I just wanted to point to the fact that - in VS 2012 - it works without any additional steps now. Just like with MS SQL Server and just like you would expect it. (And that I would like to see the same behaviour in VS 2013, of course.)
Have you registered the provider using "SetupVSPackage.exe /i /v EF6"? Worked for me using For me using SA 16.0.0.2158.