Corrupt Builds After Cancel

Our team has a ~50 project solution with a few dlls, lots of libs, and three executables. If I do a build solution, and at any point during the build hit Control-C to cancel it, whatever is being built at the time I hit the button is now corrupt. It looks like it leaves the partially created .obj, .exe, or .dll around and doesn't detect that it only got halfway through. Is this a common symptom Is there some known fix (MSDN and google searches didn't turn up any hits) Our projects and solution are all converted from 2003, if that's any help.

Thanks for any info,
Chris Jurney
Senior Programmer
Relic Entertainment

Answer this question

Corrupt Builds After Cancel

Operator10
I tried using the menu instead, but that still causes the problem. The most common error I get is:

fatal error LNK1136: invalid or corrupt file

on a .obj file.
AxelW
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=135815

new entry.
Steve Nunez

What language are you using, C#, C++, VB Does pressing Ctrl+Break or pressing the Cancel button on the Build toolbar make a difference

I suggest you log this as a suggestion on Visual Studio and .NET Framework Feedback.

ConradC

JFRoy3 wrote:

This is unbelievable and I hope you are wrong about it not being fixed in the SP. Cancelling a build is something I do multiple times every day, (modify .h, compile, modify other files, break build, recompile) and this issue, combined with the multiple VS2005 issues, is an incredible frustration right now.

Anyone from MS to comment on this

You could always create an add-in to subscribe to the OnBuildProjConfigDone event, in the case of Success == false, call the Clean method...

CritterNZ
Poke. Any news on this Still no updates to the bug or replies to email inquiry.
Lisber
No update to the feedback bug (https://connect.microsoft.com/feedback/viewfeedback.aspx FeedbackID=135815&siteid=210) and no response after following up via email... is there any movement on this bug Is a hotfix available Is anyone working on it This continues to happen to us daily.
Dhinesh C

simdoc wrote:
I hope this is fixed in SP1. To close it as not reproducible means only one thing--someone was lazy. It is very easy to reproduce.
If it wasn't known until this particular Connect bug, it won't be in SP1.
Jon D.
This is a C++ issue when you cancel the build at a certain time while compiling. A .obj file of 0 bytes is created and is considered corrupt by the linker. Since it is there and the timestamp on the .obj file > the timestampt of the cpp file it is not rebuilt by the normal build command. It is very frustrating and you have to either rebuild just the offending cpp file, or delete the 0 byte obj file. I can't find the thread now but this issue will not be fixed in the SP even through the fix should be rediculously trivial.

Juval Lowy

Mike Barry wrote:
This is a C++ issue when you cancel the build at a certain time while compiling. A .obj file of 0 bytes is created and is considered corrupt by the linker. Since it is there and the timestamp on the .obj file > the timestampt of the cpp file it is not rebuilt by the normal build command. It is very frustrating and you have to either rebuild just the offending cpp file, or delete the 0 byte obj file. I can't find the thread now but this issue will not be fixed in the SP even through the fix should be rediculously trivial.

Is there an entry in the Visual Studio and .NET Framework Feedback site for this

Ruepen
This is unbelievable and I hope you are wrong about it not being fixed in the SP. Cancelling a build is something I do multiple times every day, (modify .h, compile, modify other files, break build, recompile) and this issue, combined with the multiple VS2005 issues, is an incredible frustration right now.

Anyone from MS to comment on this
Reto Scherrer
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=101331

Closed. Not Reproducable. BOOOOOO
StefanS
It's exclusively C++. I haven't tried clicking the menu, but control+break causes the problem. I'll try that next build.

I'll try the feedback page... thanks for the tip.
Prasanta
I hope this is fixed in SP1. To close it as not reproducible means only one thing--someone was lazy. It is very easy to reproduce.
Rupreet Singh Gujral

Hi JFRoy,

We are actively working on this issue and it's too early to say whether this will be fixed in SP1. Rest assured though that we are aware of this issue's importance. It's fairly probable we will release a hotfix as well and you can follow up with me directly if you wish (borisj@microsoft.com).

Thanks,
Corrupt Builds After Cancel

Answer this question