Jump to errors using F4

[Rudy Ray Moore]

Hi all,

Occasionally I make mistakes when programming in c++. Visual Studio 6
catches most of these when compiling and stops the compiling process.
Pressing F4 jumps to the first error.

With "Visual Studio .net 2003 7.1 c++", I have found that pressing F4 does
something different. It opens an HTML log file (and takes a long time at
that). Note that I use a workspace with many projects.

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6
and jump to the first error when I press F4?

Thanks,

Rudy

[Hendrik Schober]

Rudy Ray Moore <ru*******@hotmail.com> wrote:

[...]
With "Visual Studio .net 2003 7.1 c++", I have found that pressing F4 does
something different. It opens an HTML log file (and takes a long time at
that). Note that I use a workspace with many projects.
Ahh. That's annoying as well.
Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6
and jump to the first error when I press F4?
What I do if I compile expecting an error is
To move the curser up one line as soon as the
first file to be compiled is listed. Then F4
will bring you to the first error.
Thanks,

Rudy

Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers

[Rudy Ray Moore]

I see. What I did was disable generation of .html log files. Now F4 goes
to the first error! :-/

"Hendrik Schober" <Sp******@gmx.de> wrote in message
news:uR**************@TK2MSFTNGP10.phx.gbl...

Rudy Ray Moore <ru*******@hotmail.com> wrote:

[...]
With "Visual Studio .net 2003 7.1 c++", I have found that pressing F4 does something different. It opens an HTML log file (and takes a long time at that). Note that I use a workspace with many projects.

Ahh. That's annoying as well.

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6 and jump to the first error when I press F4?

What I do if I compile expecting an error is
To move the curser up one line as soon as the
first file to be compiled is listed. Then F4
will bring you to the first error.

Thanks,

Rudy

Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers

[Ronald Laeremans [MSFT]]

You should not need to. I am asking someone to take a look.

Ronald Laeremans
Visual C++ team

"Rudy Ray Moore" <ru*******@hotmail.com> wrote in message
news:eO**************@TK2MSFTNGP10.phx.gbl...

I see. What I did was disable generation of .html log files. Now F4 goes
to the first error! :-/

"Hendrik Schober" <Sp******@gmx.de> wrote in message
news:uR**************@TK2MSFTNGP10.phx.gbl...

Rudy Ray Moore <ru*******@hotmail.com> wrote:

[...]
With "Visual Studio .net 2003 7.1 c++", I have found that pressing F4 does something different. It opens an HTML log file (and takes a long time at that). Note that I use a workspace with many projects.

Ahh. That's annoying as well.

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6 and jump to the first error when I press F4?

What I do if I compile expecting an error is
To move the curser up one line as soon as the
first file to be compiled is listed. Then F4
will bring you to the first error.

Thanks,

Rudy

Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers

[Tarek Madkour [MSFT]]

> From: "Rudy Ray Moore" <ru*******@hotmail.com>

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6
and jump to the first error when I press F4?

Yes there is. You can set the keyboard bindings to use the VC6 keyboard
scheme from the "Tools|Options" menu under the "Environment.Keyboard" tab.

You can also manually map F4/shift-F4 to
Edit.GotoNextOutputWindowError/Edit.GotoPreviousOutputWindowError from the
same dialog.

This will get you the closest possible behavior to VC6. The only exception
will be that you will also cycle through the bulid log (not just the
errors).

Thanks,
--
Tarek Madkour, Visual C++ Team
This posting is provided AS IS with no warranties, and confers no rights.

[Hendrik Schober]

"Tarek Madkour [MSFT]" <ta****@online.microsoft.com> wrote:

From: "Rudy Ray Moore" <ru*******@hotmail.com>

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6
and jump to the first error when I press F4?

Yes there is. You can set the keyboard bindings to use the VC6 keyboard
scheme from the "Tools|Options" menu under the "Environment.Keyboard" tab.

You can also manually map F4/shift-F4 to
Edit.GotoNextOutputWindowError/Edit.GotoPreviousOutputWindowError from the
same dialog.

This will get you the closest possible behavior to VC6. The only exception
will be that you will also cycle through the bulid log (not just the
errors).

There is another subtle, but annoying
difference, though: F4 will also cycle
through the list of files to compile
that appeares when you don't specify
"/nologo".
(I know this is off by default, but we
have it turned on for every project.)
Thanks,

Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers

[Tarek Madkour [MSFT]]

> From: "Hendrik Schober" <Sp******@gmx.de>

"Tarek Madkour [MSFT]" <ta****@online.microsoft.com> wrote:

From: "Rudy Ray Moore" <ru*******@hotmail.com>

Is there any way to make "Visual Studio .net 2003 7.1 c++" behave like VS6 and jump to the first error when I press F4?

Yes there is. You can set the keyboard bindings to use the VC6 keyboard
scheme from the "Tools|Options" menu under the "Environment.Keyboard" tab.
You can also manually map F4/shift-F4 to
Edit.GotoNextOutputWindowError/Edit.GotoPreviousOutputWindowError from the same dialog.

This will get you the closest possible behavior to VC6. The only exception will be that you will also cycle through the bulid log (not just the
errors).

There is another subtle, but annoying
difference, though: F4 will also cycle
through the list of files to compile
that appeares when you don't specify
"/nologo".
(I know this is off by default, but we
have it turned on for every project.)

First time I see this one! Thanks for the report :)

--
Tarek Madkour, Visual C++ Team
This posting is provided AS IS with no warranties, and confers no rights.