Problem:

In vc6, there is such a declaration in stdafx.h as:
extern CComModule _Module;

and in the main module:

CComModule _Module;

But when you complie it in vc8, the following errors apears:

c:\temp\myatl\stdafx.h(24) : error C2146: syntax error : missing ‘;’ before identifier ‘_Module’
c:\temp\myatl\stdafx.h(24) : error C4430: missing type specifier – int assumed. Note: C++ does not support default-int
c:\temp\myatl\stdafx.h(24) : error C4430: missing type specifier – int assumed. Note: C++ does not support default-int

Solution:

In ATL 7.0, which is the ATL version that is included in Visual C++ .NET and in Visual C++ 2005, the CAtlBaseModule class has replaced the obsolete CComModule class.

Microsoft has given the solution in KB309705 – “_AtlBaseModule.m_hInst replaces _Module.m_hInst in ATL 7.0″

http://support.microsoft.com/kb/309705/

From MSDN:
The profiler is an analysis tool that you can use to examine the run-time behavior of your programs. By using profiler information, you can determine which sections of your code are working efficiently. The profiler can produce information showing areas of code that are not being executed or that are taking a long time to execute.

But in Visual C++ 6.0, you often found that the profile menu item is grayed. How to enable it?

To enable profile in VC 6.0, you first need to set the correct link parameter, and rebuild all the project.

Wait a minute, do you find that the profile menu item is still grayed?
OK. It’s because that you installed vc6 with one account but use it with another one. It’s mayby a bug of VC6.
But how can you to correct it? It’s easy. Just modify the entry value in the registery.

[HKEY_CURRENT_USER\Software\Microsoft\Devstudio\6.0\General]
“ProfilerInstalled”=dword:00000001

1. delete *.ncb, *.opt, *.plg and *.clw files from your project directory
2. rebuild your project.

And you often need CTRL+W to generate the class wizard infmation again.

But the above works quite often but not always. For a better experience, you need to try some comercial tools, for example, Visual Assistant.It is a product of Whold Tomato Software and  provides more powerful functions.

Ctrl+Shift+8

• Column Selection

Alt+Mouse

• SelectLine

Ctrl+F8

• LineCut

Ctrl+L

• LineDelete

Ctrl+Shift+L

• Virtual Space

menu: Options->Compatibility->Enable virtual space

• Browse Navigate: GotoMatchBraceExtend

Ctrl+]

• Browse Navigate: MatchBrace Selection

Ctrl+Shift+]

• Browse Navigate: ConditionUp/Down

Ctrl+J Ctrl+K

• Browse Navigate: Condition Selection

Ctrl+Shift+J Ctrl+Shift+K

• Browse Navigate: ErrorTags(Next/Previous)

F4 / Shift+F4

• Bookmarks: temp bookmark:

Ctrl+F2

• Bookmarks: named bookmark

Ctrl+Shift+J Ctrl+Shift+K

• Bookmarks: Next/Previous

F2 /Shift+F2

• Code complete: global function

Ctrl+Alt+T

• Code complete: switch between overloaded function

Ctrl+PageDown /Ctrl+PageUp

• Code complete: show tip

Ctrl+Shift+Space

• Code complete: complete word

Ctrl+Spache

The author introduced the shortcomings of SourceSafe and hoped  to dissuade us from using SourceSafe, and have spared us the bad experiences he had.

Alan De Smet provided the missing features of the Micosoft SourceSafe:

• SourceSafe lacks usable branching support
• SourceSafe cannot be safely extended
• SourceSafe silently leaves stale files on your local system
• SourceSafe badly handles slow networks and the public internet
• Managing third party modules is difficult with SourceSafe
• Viewing and retrieving historical versions is extremely slow
• Difficult to maintain multiple local copies of one project

Alan De Smet also thought that the safety of SourceSafe was bad.

• SourceSafe degrades on large projects
• SourceSafe integration can crash Visual Studio
• SourceSafe relies on dangerous file sharing
• SourceSafe should be scanned for corruption weekly
• SourceSafe handles multiple time zones badly
• SourceSafe becomes corrupted

And at last, Alan De Smet  suggested us to transfer our souce control system to some better choice.

The original fulltext is here.  

Display the LastError’s value

When we want to get the LastError message, we often using the following code.

LPVOID lpMsgBuf;
FormatMessage(
FORMAT_MESSAGE_ALLOCATE_BUFFER |
FORMAT_MESSAGE_FROM_SYSTEM |
FORMAT_MESSAGE_IGNORE_INSERTS,
NULL,
GetLastError(),
MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
(LPTSTR) &lpMsgBuf,
0,
NULL
);
// Process any inserts in lpMsgBuf.
// …
// Display the string.
MessageBox( NULL, (LPCTSTR)lpMsgBuf, “Error”, MB_OK | MB_ICONINFORMATION );
// Free the buffer.
LocalFree( lpMsgBuf );


But now VisualSudio 6.0 has provied a virtual Pseudoregister called @ERR
we can simply input the expression in the watch window and we will get the LastError message.@ERR,hrHere is supported pseudoregisters list:[1]


@ERR
;Last error value,the same value returned by the GetLastError() API function

@TIB
;Thread information block for the current thread

@CLK
;Undocumented clock register; usable only in the Watch window

@EAX, @EBX, @ECX, @EDX, @ESI, @EDI, @EIP, @ESP, @EBP, @EFL
;Intel CPU registers

@CS, @DS, @ES, @SS, @FS, @GS
;Intel CPU segment registers

@ST0, @ST1, @ST2, @ST3, @ST4, @ST5, @ST6, @ST7
;Intel CPU floating-point registers

Acknowledge:

[1]An introduction to debugging in MSVC++ using Pseudoregisters

[2]Microsoft Visual C++ Tips and Tricks