Because Visual Studio doesn’t look for references in the GAC:

When you import a project from Visual C++ 6 into Visual Studio 2003 (i.e. Visual C++ 7.1), it doesn’t fix up the output directories to use the correct definitions.

It turns out that Visual Studio.NET Professional can’t be used to design databases with SQL Server. It can be used with MSDE.

I got this error message today:

I just had a strange error message from Visual Studio.NET when attempting to add a handler for WM_DESTROY to a C++ dialog class. It said:

The program that I’m working on at the moment needs a wizard to walk the user through something. I copied over some files from a Wizard97 demo project that I wrote a while ago. It all seemed to be going well.

This document contains some quick tips for getting remote debugging with Visual C++ working. The document was originally written by Roger Lipscombe to cover VC5. Rei Wilkinson reviewed it, and added some stuff for VC6 use.

There are times when you want to have multiple input files in a Visual C++ project configured to generate the same output file. For example, you want to catenate a bunch of files to generate a file to be #included.