Hello,
I have been using Visual Studio, and most specifically, VC++ from version 4.0 to version 6.0, and lately I have been meaning to finally catch up with the latest. Since I've skipped a generation and another one is about to be released, I thought I'd skip 2003 as well and wait for 2005. To prepare for it I decided to download VC++ Express 2005 Beta 2 and the install went flawlessly (I downloaded the CD-image and installed that). Then I got the latest Platform SDK and installed it, after which I made the suggested modifications to make VC++ Express work with the Windows API. After customizing a bit some user preferences (options) I started playing with console applications. The first thing I noticed was that when there is an error, if I tried to get to the location in the file where the specific error occurred, it would not work as expected. For instance, in VC++ 6.0 I'd just hit "F4" or the double-click the error line in the output window to automatically go to the line of code where the error occurred - the "Edit - Go To Error/Tag" command. In VC++ 2005 Express, however, if I were to double-click in the output window, nothing would happen, and if were to do that in the Error List window (which I have auto-hidden at the bottom of the screen or in the tabbed list), it would take me to the Document Explorer and show me help about the kind of error, not the specific error in my code. For example, if I had a warning about "_vsnprintf" being deprecated, I'd get the page explaining what the C4996 compiler warning means. The documentation about the "Error List Window" does say that you can "Double-click any error message entry to open the file where the problem occurs, and move to the error location." That should be the "Edit - Go To Next Location" command. But it doesn't work for me as I believe it is supposed to. Am I missing something here I can't believe it is a plain bug since hundreds of people would have noticed it, unless it is related to some of my settings.
I do also have a question about the deprecation of a bunch of CRT functions, and mostly about using some of the macros supposed to assist in the transition, but that will wait until later.
Kamen
Moving through error list
Hot Topic
- Write and read a file in Visual Basic 2005?
- Visual C++ & Windows Forms Application without .NET framework
- Installation Error
- Can see only a few classes in .NET library
- Let's go to work on an FAQ for this Forum
- Large solutions and dealing with a cluttered Solution Explorer
- Automatically discover folder path
- How Do I Rename a Project Folder
- Mdi forms title in toolbar!
- How Do I...Hide the startup form in VB, for system tray applications
VS Express Editions
- Random Numbers again!!!
- Visual Studio Installation Express
- How to include winsock2.h?
- No verification e-mail message
- Searching for Text
- Error Report for my App.
- demo projects
- Possible to continue to use Framework 1.1?
- A problem connecting to the database. Cant update it from the program
- MS Access Combo box Drop Down Equivilant
Moving through error list
.net and xml newbie
Kamen
ilr
The "show error help" is often confusing . It shows some help , but not one related to error occured.
9727604
I used the "Express" version for a little longer then switched to the "Pro". The context-sensitive help has worked for me flawlessly since that post. The only time I'd get the wrong help page is when I accidentally had focus on another window. That is, if the focus happened to be on the code, even though I was "looking" at the error window
, the system had no way to know that and it tried to get help on whatever was in the code (which is usually blank space and help shows me "C++ keywords" or "Information not found"). Make sure the specific error is highlighted before you hit "F1".
Kamen