Total de publicaciones:
28
Karma:
304
Unido:
12/4/2013
Ubicación:
Germany
Hi folks, I have exactly the same issue. It can be fixed by setting this in the constructor of the context object as well. Might be slower - but anyway - what is the root cause of this issue? This might have side effects. Regards Jörg
Total de publicaciones:
4
Karma:
30
Unido:
24/1/2014
Ubicación:
United States
Worked for me as well! Starting to remember why I don't use EF.
Total de publicaciones:
18
Karma:
90
Unido:
26/8/2014
Ubicación:
India
Thank you very much. I had no clue why all of sudden it stopped working.Your solution worked like charm. Thank you.
Total de publicaciones:
14
Karma:
100
Unido:
15/10/2009
Ubicación:
United States
This worked - thanks so much! EF is blowing my mind!
Total de publicaciones:
152
Karma:
874
Unido:
5/8/2014
Ubicación:
Austria
having exactly the same issue. how do you implement code first migration with a plugin? http://www.pronopcommerce.com/using-entity-framework-ef-code-first-migrations-in-nopcommerce-for-fast-customizations this didnt help me too much sadly. the aformentioned "fix" seems more like a workaround? could that have any adveserial side effects?
Total de publicaciones:
3
Karma:
25
Unido:
23/10/2016
Ubicación:
Belgium
This message is also thrown when you forget to add your entity mapping to the modelbuilder in your objectcontext. In my case: i added an extra table. This table was created when the plugin installed, but EF did throw this exception.