Supposedly vs 2013 added support for edit and continue 64 bit (see http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/26/debugging-support-for-64-bit-edit-and-continue-
This is a known issue when referencing portable libraries and using Edit & Continue. We are looking to fix this in a future version of Visual Studio.
A workaround for now:
<PropertyGroup>
element, add the following: <_ResolveReferenceDependencies>true</_ResolveReferenceDependencies>
This should fix the build issue.
Note: Depending on the project, this might have a performance hit, not only during Edit & Continue usage, but just general usage within VS.
In my case, the only solution that worked was to remove the workspace and map&get again.
To remove the workspace, Source control
→ Advanced
→ Workspace
→ Remove
.