Annoying messagebox

[Andreas Delp]

Hello,
I changed from Borland C++ to VC++. Looks nice.
But one thing really sucks: After modifying my source file, I press F5 to
build and run my app.
Then, a message box appears, telling me that some files are outdated and
have to be rebuild (app.bcs;app.exe;app.obj).
I agree, these files are outdated. That愀 the reason I pressed F5. Why this
stupid question ?
Do you know, how to supress this message ?

TNX, Andreas

P.S: Win 2000, vc++ 6.0 SP5

[Bruce Dawson]

This is definitely a FAQ.

I haven't heard of a great solution.

I type Alt+B,B, to build, then F5 to run.

Maybe some day Microsoft will add a 'build-and-run' command, to
satisfy these frequent desire.

[Greg Berchelmann]

On Thu, 7 Feb 2002 17:18:03 +0100, Andreas Delp <mgu...@gmx.de>
wrote:

I get a similar problem with VC++6 on Windows98. If I click the build
all button, then the execute button, it gives me the same messagebox.
If I do the same thing on my Windows2000 box, I don't get the message.
Strange considering it is the exact same source code, project, etc.

-GJB

[Robert Marshall]

On Thu, 7 Feb 2002, Andreas Delp stated:

Another message box that annoys....

If I click compile (rather than build) and I'm in the wrong project, I
get asked if I want to add the file to the current project, I say no,
so I then get told I can't do the build.

What I actually want is a cancel on the first dialog because I then
realise I've done something stupid, rather than VS lecturing me (in
the second box) about why you can't compile a file that isn't in the
current project

R
--
Poetry's not window cleaning.
It breaks the glass.
-- Chase Twichell

[Levon Hayrapetyan]

Hi
Consider a situation when you did some changes to your sources. Then you
need to execute the last built version (f.e. your changes made your project
temporarily "unbuildable")
What will you do? That's right! you'll press (Ctrl+) F5. If there is no
message you'll loose your binary...
Try to build (F7) first, then press F5, if you don't like the message.

Good luck,
Levon Hayrapetyan

"Andreas Delp" <mgu...@gmx.de> wrote in message
news:Xns91AEAF0FBDC...@62.153.159.134...

[Alexander Shargin]

Well I never had a problem pressing F7 and then F5. But if you don't like
this you could write a simple macro implementing Build&run functionality.
Here is a simple version of such a macro.

--- cut ---
Dim bNeedToRun

Sub BuildAndRun()
Documents.SaveAll True
bNeedToRun = True
ExecuteCommand "Build"

End Sub

sub Application_BuildFinish(numErr, numWarn)
if (bNeedToRun=True) Then
bNeedToRun = False
if (numErr=0) Then
ExecuteCommand "DebugGo"
end if
end if
end sub
--- cut ---

--
Sincerely,
Alexander

mailto:al...@rsdn.ru
http://www.RSDN.ru - Russian Software Developer Network

"Andreas Delp" <mgu...@gmx.de> ???????/???????? ? ???????? ?????????:
news:Xns91AEAF0FBDC...@62.153.159.134...

[Bruce Dawson]

The "Do you want to add to the current project" message box is
extremely dangerous. I teach a programming class using VC++ 6.0
and, apparently, my class is the first exposure these students have to
workspaces that contain a library and an executable. Inevitably
some 10% of my students will 'compile' a file that is in the library
(while the executable project is, naturally, active) and will answer
yes to the tempting "do you want to add" question. This ruins the
projects such that they won't build until the file is deleted from the
application workspace.

The compile command should search all projects - or at least all
projects that the current project depends on - to try and find one
that it can compile the source file for. And, it shouldn't offer such
dangerously misguided help - it is wrong far too often.