- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More than 2/3 of the time I get.
"Cannot reference updated manifest"
This is apparently because the the debugger WILL NOT quit when we want to go back and edit source code.
This is a minor annoyance, but since it annoys so many of us, one would think they would want to fix that issue.
One easy fix is to put a random number at the end of the executable,
that way we arent trying to reference an executable the debugger is attached to.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was a longstanding bug in Visual Studio, one that affected all languages. I have not seen it in VS2017. There have been several threads on this here - a simple solution is to exit VS and restart.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page