5

The "Build" menu appears as it would if the solution were building, but the Cancel Build (Ctrl+Break) menu item has no effect.

Trying to close the application prompted as:

The build must be stopped before the solution can be closed.

Can anyone help me to resolve this problem?

mtb
  • 1,350
  • 16
  • 32
Kanak Shukla
  • 229
  • 1
  • 4
  • 11
  • 1
    Usually it doesn't work immediately because cancelling takes some time, so how long before you try to close the application? – Kyra Jun 11 '15 at 12:12

2 Answers2

12

Do this, look for msbuild process(es) and kill them before devenv. And make sure vbc really has gone too....

For any further crashes that occur frequently submit them to microsoft so that they can fix the bug...

Hoping it helped....

CoderNeji
  • 2,056
  • 3
  • 20
  • 31
  • 4
    `Ctrl+Break` or Go to Visual Studio 2013 Build Menu -> cancel build , that easy. [reference](http://stackoverflow.com/questions/8997430/how-to-cancel-a-build-that-is-in-progress-in-visual-studio) Hope helps someone. – Shaiju T Jul 20 '16 at 09:22
  • 1
    I came here because I just got the same problem in VS 2017. It should be noted that the Ctrl+Break command did not work for me in this case. Normally that will cancel the build (same with using the menu feature) but in this particular instance neither worked: it still said it was building even though nothing was happening. Killing the msbuild process(es) fixed the issue and I was able to restart VS. – Architekt Apr 27 '17 at 23:49
3

I was having this problem and I think I discovered why.

I was drawing way outside the boundaries of a bitmap and it was overwriting some memory location that affected Visual Studio.

I added a line of code as a safety while testing that looked for when writing bitmap.Top < 0 or writing > bitmap.Width or > bitmap.Height.

This is supposed to be trapped by Visual Studio but I think it's getting by.

In straight C it's called a wild pointer.

dnennis
  • 140
  • 1
  • 9