投稿総数:
28
カルマ:
304
参加:
2013/04/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/01/24
ロケーション:
United States
Worked for me as well! Starting to remember why I don't use EF.
投稿総数:
18
カルマ:
90
参加:
2014/08/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/08/05
ロケーション:
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.