Seems that the special constructor I added to the DbContext
caused the problem. After commenting out the constructor and re-compiling, it's working back again.
Perhaps I should wrap the constructor contents in a conditional statement that is skipped at design-time, meanwhile commenting-out is enough for me.