回帖总数:
28
业力:
304
注册日期:
2013/4/12
位置:
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
回帖总数:
4
业力:
30
注册日期:
2014/1/24
位置:
United States
Worked for me as well! Starting to remember why I don't use EF.
回帖总数:
18
业力:
90
注册日期:
2014/8/26
位置:
India
Thank you very much. I had no clue why all of sudden it stopped working.Your solution worked like charm. Thank you.
回帖总数:
14
业力:
100
注册日期:
2009/10/15
位置:
United States
This worked - thanks so much! EF is blowing my mind!
回帖总数:
152
业力:
874
注册日期:
2014/8/5
位置:
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?
回帖总数:
3
业力:
25
注册日期:
2016/10/23
位置:
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.