I tried to up-vote, but I think the folks from MS are getting home. I got the same problem, and it killed my migration plans and inheriting constructors.
Thank you. And don't get me started on vs2013 update 2. I wasted a day putting up with it but eventually had to uninstall out of frustration. After that experience I can't see myself ever installing update 2 unless there is a showstopper bug in update 1.
What's your dev environment? If I've ever had a problem with Visual Studio it always is some type of add-on.
I've been using it for years and have never had a problem.