Thursday, April 22, 2004


I was porting some code from vc6 to vc7.1 and I got stuck in:


c:\build\main\.......\inc.h(27) : fatal error C1001: INTERNAL COMPILER ERROR

(compiler file 'msc1.cpp', line 2701)

Please choose the Technical Support command on the Visual C++

Help menu, or open the Technical Support help file for more information


Looking trough newsgroups gave me a good hint:

"I spoke with Microsoft incident support for my MSDN licence and the fix is:

#if _MFC_VER < 0x0700
class CString;

CString is not a class in MFC anymore. It is a template in ATL so forward
declarations are invalid."

So I searched for CString forward declarations and I solved - quickly - my problem.

Tuesday, April 20, 2004


PINVOKE.NET attempts to address the difficulty of calling Win32 or other unmanaged APIs in managed code (languages such as C# and VB .NET).   Manually defining and using PInvoke signatures (also known as Declare statements in VB .NET) is an error-prone process that can introduce extremely subtle bugs.  The rules are complex, and if you make a mistake, you’ll probably corrupt memory.

 Therefore, this site is a repository where you can find, edit, and add PInvoke signatures, user-defined types, and any other information that helps us leverage each other’s efforts.  Think of this as the 21st century version of VB6’s "API Text Viewer," a standalone application which used static files such as WIN32API.TXT as input.  Did you spend hours figuring out how to successfully define & call a given unmanaged API in managed code?  Share (and get credit for) your discovery here!  Is there an error on this site?  Go ahead and fix it!


Tuesday, April 13, 2004