Build errors - why are they not highlighted in the source ?
-
I am completely puzzled by Visual Studio's handling of build errors. Other IDEs that I work with, e.g. Delphi or Code::Blocks, change the focus to the text editor and highlight the source code line of the first occurring error once the build aborts. VS does not - focus is left in the build window where you can see that a build error occurred. You then have to navigate to one of the errors and double-click it to see where it is. I thought it was just VS 2005 but VS 2010 shows the same behavior (just installed 2010 RC and tried it today). I have looked and looked - is there any way of switching this to a more normal behavior ? I mean - you can double-click errors in the build log and the error will be highlighted in the source, so it almost feels like VS deliberately refuses to do it automatically for you :confused:. Cheers -- Jan Holst Jensen
-
I am completely puzzled by Visual Studio's handling of build errors. Other IDEs that I work with, e.g. Delphi or Code::Blocks, change the focus to the text editor and highlight the source code line of the first occurring error once the build aborts. VS does not - focus is left in the build window where you can see that a build error occurred. You then have to navigate to one of the errors and double-click it to see where it is. I thought it was just VS 2005 but VS 2010 shows the same behavior (just installed 2010 RC and tried it today). I have looked and looked - is there any way of switching this to a more normal behavior ? I mean - you can double-click errors in the build log and the error will be highlighted in the source, so it almost feels like VS deliberately refuses to do it automatically for you :confused:. Cheers -- Jan Holst Jensen
You could always post this as a suggestion on MS forums - you never know, it mightly actually get considered for the next release of Visual Studio.
Me, I'm dishonest. And a dishonest man you can always trust to be dishonest.
Honestly. It's the honest ones you want to watch out for... -
You could always post this as a suggestion on MS forums - you never know, it mightly actually get considered for the next release of Visual Studio.
Me, I'm dishonest. And a dishonest man you can always trust to be dishonest.
Honestly. It's the honest ones you want to watch out for...Yeah. But given that it's been this way for 5 years+ I wonder about the chances of it getting through :doh: . If I am the only one being annoyed by this, I'll just live with it. I mean, Notepad++ with a command-line compile gives almost the same interactivity, so I just use that instead... ;P
-
Yeah. But given that it's been this way for 5 years+ I wonder about the chances of it getting through :doh: . If I am the only one being annoyed by this, I'll just live with it. I mean, Notepad++ with a command-line compile gives almost the same interactivity, so I just use that instead... ;P
Jan Holst Jensen2 wrote:
Yeah. But given that it's been this way for 5 years+ I wonder about the chances of it getting through
Excellent point, I must say....but then perhaps they just did not know about it :doh:.... :)
Me, I'm dishonest. And a dishonest man you can always trust to be dishonest.
Honestly. It's the honest ones you want to watch out for...