When remote debugging a windows application (windows form/service) across 2 networks, 2 machines on 2 different domains, you may get an error message similar to this one if there is a Network Address Translation (NAT) or a hardware firewall/router between the 2 machines.

“Error while trying to run project: Unable to start debugging. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. A firewall may be preventing communication via DCOM to the local computer”

Result

Even after setting all the firewall settings on the machines correctly and on the local machine when going to Debug->Attach to Process, and browsing on the remote machine the process to be debugged appears but still unable to attach to the process and continue to get the same error message.

Cause

This is by design.  The router/NAT is causing the problem with communication between the 2 machines in order to debug the application.

Resolution

There isn’t a way to by-pass the NAT, so one of the following needs to happen:

1.       Move both machines to one side of the NAT, server side or client side.

2.       Move the firewall up a level making both remote and local machines under the same firewall/NAT

More Information

One way to make sure both machines are communicating correctly is to use net view command from both server and client to see if each can see the other.

Net view
http://technet.microsoft.com/en-us/library/bb490719.aspx (http://technet.microsoft.com/en-us/library/bb490719.aspx)

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

OLE controls can be registered by using Visual C++ from the Tools menu, from the Test Container provided with the Control Development Kit (CDK), or by using the regsvr or regsvr32 applications provided with Visual C++. In some cases, the registration of a control may fail; use this article to help troubleshoot the problem.

MORE INFORMATION

All of the previously mentioned methods for registering an OLE Control use essentially the same technique. LoadLibrary() is called to load the control into memory, GetProcAddress() is called to get the address of the DllRegisterServer() function, and then DllRegisterServer() is called to register the control.

Reasons Why the Registration of a Control May Fail

Troubleshooting Techniques

If none of the possible causes are true in your case, try the following techniques.

As an alternative, you can attempt to register the control programmatically. First create an MFC AppWizard application selecting Dialog-based application and OLE Automation. Enabling OLE Automation will initialize OLE so that the code to register the control will work properly. In the CWinApp-derived class, you will find the function InitInstance() with the initial code as follows:

BOOL CTestregApp::InitInstance()

{

   // Initialize OLE libraries

   if (!AfxOleInit())

   {

      AfxMessageBox(IDP_OLE_INIT_FAILED);

      return FALSE;

   }

At this point, add the following code segment, which will allow you to check the return codes from LoadLibrary(), GetProcAddress(), and DllRegisterServer.

#ifdef _WIN32

    HINSTANCE hDLL = LoadLibrary("some.ocx");

    if(NULL == hDLL)

    {

        // See Winerror.h for explaination of error code.

        DWORD error = GetLastError();

        TRACE1("LoadLibrary() Failed with: %i\n", error);

        return FALSE;

    }

    typedef HRESULT (CALLBACK *HCRET)(void);

    HCRET lpfnDllRegisterServer;

    lpfnDllRegisterServer =

            (HCRET)GetProcAddress(hDLL, "DllRegisterServer");

    if(NULL == lpfnDllRegisterServer)

    {

        // See Winerror.h for explaination of error code.

        DWORD error = GetLastError();

        TRACE1("GetProcAddress() Failed with %i\n", error);

        return FALSE;

    }

    if(FAILED((*lpfnDllRegisterServer)()))

    {

        TRACE("DLLRegisterServer() Failed");

        return FALSE;

    }

#else // 16-bit

    HINSTANCE hDLL = LoadLibrary("regtest.ocx");

    if(HINSTANCE_ERROR > hDLL)

    {

        // See LoadLibrary() help for explaination of error code.

        TRACE1("LoadLibrary() Failed with: %i\n", hDLL);

        return FALSE;

    }

    typedef HRESULT (CALLBACK *HCRET)(void);

    HCRET lpfnDllRegisterServer;

    lpfnDllRegisterServer =

            (HCRET)GetProcAddress(hDLL, "DllRegisterServer");

    if(NULL == lpfnDllRegisterServer)

    {

        // See GetProcAddress() help for explaination of error code.

        TRACE("GetProcAddress() Failed");

        return FALSE;

    }

    if(FAILED((*lpfnDllRegisterServer)()))

    {

        TRACE("DLLRegisterServer() Failed");

        return FALSE;

    }

#endif

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Consider the following scenario:

In this scenario, you may experience the following performance issues in the IDE:

CAUSE

This problem occurs because of how the Visual Studio 2008 compiler processes large files that contain XML documentation.

RESOLUTION

Download information

The following file is available for download from the Microsoft Download Center:
Download the 338762_ENU_i386_zip.exe package now. (https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=11026&wa=wsignin1.0))

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 2008 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

WORKAROUND

To work around this problem, use one of the following methods.

Method 1: Disable XML comment generation

To disable XML comment generation for the project, use one of the following procedures.

Visual Studio 2008

Visual Basic 2008 Express Edition

Method 2: Remove the XML comments

To remove the XML comments, follow these steps for the designer-generated file:

Note You must repeat these steps if you perform one of the following actions:

Method 3: Create a separate project to store the file that has the XML comments

Create a new class library project to store the designer-generated files. The following procedure is an example of to do this:

Note You may have to add import statements to the Visual Basic code.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION

Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

For more information about how to generate XML documentation for a project, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/x4sa0ak0(VS.90).aspx (http://msdn2.microsoft.com/en-us/library/x4sa0ak0(VS.90).aspx)

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

class TestClass;

void Disp(TestClass& rObj, void (TestClass::*pFun)())
{
(rObj.*pFun)();
}

Here ‘TestClass’ and function ‘Disp’ are in the same project, but defined in different .CPP files.

Result

The VC++ compiler compiles this without any errors, but the application fails with access violation exception (0xc0000005) during runtime at ‘(rObj.*pFun)();’.

Cause

The representation of a pointer-to-member depends on the declaration of the class.  It can vary from a simple offset or pointer in the simple case to a complicated structure in the case where virtual functions or multiple inheritance is involved.  When you just forward declare like this, the compiler doesn’t know about it and generates code assuming the “simple” representation.  At runtime, the value of pFun (which was built by code that does know it needs to be complicated) isn’t using the same layout and you get a crash.

Resolution

If possible, #include the header file that contains the whole declaration of the class TestClass (making forward declaration ‘class TestClass;’ unnecessary).
If including the header is not possible (such as cases where a header is not available or when a circular reference would result), you can give the compiler information about the complexity of the class inheritance, so that it can generate the appropriately more ”pessimistic” code, using one of the following options:

More Information

Pointers to Members (http://msdn2.microsoft.com/en-us/library/f2wbycwh.aspx)
Pointers to Members and Virtual Functions (http://msdn2.microsoft.com/en-us/library/fa0207h3.aspx)

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

The remote procedure call failed.

CAUSE

Every thread that uses COM or OLE must call the CoInitialize function or the OleInitialize function, respectively. When this call is made, the OS creates a hidden top-level window, owned by your thread, for implementation purposes. Because the OS relies on Windows messaging behind-the-scenes, your thread should, and in some cases MUST, pump messages. Failure to do so can result in automation errors, and sometimes in a deadlock situation when another application broadcasts a message to all top-level windows (for example, an application might broadcast a WM_WININICHANGE or WM_SETTINGCHANGE message to notify other applications the default printer has changed).

RESOLUTION

If you are using OLE Automation in a loop (for example, writing out 10,000 rows of data to Microsoft Excel), you need a PeekMessage loop inside your loop so that messages will get processed.

STATUS

This behavior is by design.

MORE INFORMATION

Here is an example of a PeekMessage loop you can use in your code.

MSG msg;

   while(PeekMessage(&msg, NULL, NULL, NULL, PM_REMOVE)) {

      TranslateMessage(&msg);

      DispatchMessage(&msg);

   }

error LNK2001: unresolved external symbol

This also occurs if the classes reside in a DLL and are declared with the __declspec( dllexport ) storage-class attribute.

In Visual C++ .NET you will receive the following error message:

LNK2019: unresolved external symbol

CAUSE

This behavior is by design. The assignment operator is not inherited. Normal inheritance rules do not apply, and declaring it pure virtual does not have the usual affect.

RESOLUTION

Since operator= is not inherited, any declaration of operator= in the base class is unused and unnecessary. Do not declare the operator= in the base class.

MORE INFORMATION

When built, the following code sample will generate the discussed LNK2001 error. Comment the declaration of the operator=() member in the base class to resolve.

Sample Code

/* Compile options needed: none

*/

class A

{

public :

   // To workaround LNK2001, comment the following line.

   virtual const A& operator=( const A& f ) = 0;

};

class B : public A

{

public :

   const A& operator=( const A& g ) {return g;}

};

B aB1, aB2;

void main( void )

{

   aB2 = aB1;

}

Result

You get a warning during the build:
Generating XML documentation…
warning XDC0017 : Unrecognized XDCMake option: /validate
XDCMAKE /old output_filename [options]
(and a list of valid options…)

Cause

The XDCMake tool had, at one time, a /validate option in its old command line interface.  It was decided, due to weaknesses in its implementation, that its usefulness was limited, and the feature was removed.  The compiler is guaranteed to generate good XML documentation, and there is little need (or none at all) to add a validation step to the build.  However, due to an oversight, this option was not removed from the IDE and its corresponding documentation. Consequently, selecting “Yes” for this option in the IDE causes “/validate” to be added to the XDCMake command line, and the tool generates the warning.

Resolution

Do not use this option.  Leave it at the default setting (“No”), or pay no heed to the warnings if you leave it on “Yes”.

More Information

MIcrosoft has no plans to re-implement the /validate switch, and the IDE option will be removed in a future release of the Visual C++ project engine.
The XDCMake command line (http://msdn2.microsoft.com/en-us/library/ms177247.aspx), when used outside of Visual Studio, also supports a different set of options than the “/old” interface supported in Visual Studio 2005 and 2008.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

nafxcwd.lib(thrdcore.obj) : error LNK2001:
unresolved external symbol “__beginthreadex”

nafxcwd.lib(thrdcore.obj) : error LNK2001:
unresolved external symbol “__endthreadex”

CAUSE

Starting with version 3.0, all MFC classes are “thread safe” and require the multi-threaded run-time libraries to link successfully. Many people try to use the single-threaded run-time libraries because they assume these libraries are needed to enable the application to run in Win32s. This is not the case. MFC versions 3.0 and later will use a single thread, so as long as you are not creating additional threads in the application, the application will run under Win32s.

RESOLUTION

To avoid these unresolved external errors, do not set the Project Settings to Single-Threaded for an MFC version 3.0 or later application. This setting can be changed by doing the following:

STATUS

This behavior is by design.

MORE INFORMATION

For Win32s, MFC version 3.0 and later versions do not create additional threads. However, the MFC does use Thread Local Storage (TLS) in the multithreaded libraries to provide per-process data in DLLs that are used by multiple applications under Win32s.

In the Project Settings dialog box, if you select the run-time library option to link “Multithreaded using DLL,” you can take advantage of using the shared DLL, MSVCRTx0.DLL (where x represents the major version of Visual C++). There are separate versions of MSVCRTx0.DLL for Windows NT and Win32s that cannot be interchanged. “Multithreaded using DLL” is required when building an AFXDLL.

Linking to the multithreaded libraries may cause multiple defined symbol errors. This usually occurs when the application uses user-created or third-party static libraries that were created as single-threaded.

The best solution in this case is to rebuild the static libraries to use the same library options as MFC (either /MT or /MD, depending on which MFC lib is used).

In this case, you may be able to use /NOD:LIBC.LIB. However, if the static library accesses any static global C Run-Time data such as _errno or stdin, you will get unresolved externals on these symbols.

One solution which will always work is to isolate the single-threaded code into a DLL, and call it, protected by semaphores, from the multithreaded MFC code.

CAUSE

The default settings for the Command Prompt on Microsoft Windows Server 2003, Microsoft Windows XP, Microsoft Windows Server 2000, Microsoft Windows NT, Microsoft Windows Millennium Edition, Microsoft Windows 98, or Microsoft Windows 95 are set to full screen.

RESOLUTION

Depending on whether you are on Windows Server 2003, Windows XP, Windows Server 2000, Windows NT, Windows Millennium Edition, Windows 98, or Windows 95, the resolution process is different:

Follow the instructions given in the “More Information” section.

MORE INFORMATION

On Windows NT, Windows Server 2000, Windows XP, and Windows Server 2003, Visual C++ repeatedly invokes a background process called Vcspawn.exe for each command-line tool executed by the development environment. Tools such as Cl.exe, Link.exe, and Bscmake.exe run in the Vcspawn.exe environment, which is a 32-bit console application.

Usually Vcspawn.exe is invoked as a hidden window and you never see it. However, if the setting for Vcspawn.exe is in “full screen” mode, the screen switches to text mode each time Vcspawn.exe is invoked. No text is actually sent to the Vcspawn screen, so the screen appears blank.

On Windows 95, Windows 98, and Windows Me, Vcspawn.exe is affected by the presence of the _Default.pif and the settings of the Conagent.exe file. If a _Default.pif is in the path, its properties will be used for all invoked console applications. Often, a _Default.pif is left over from a previous Windows 3.1 or 3.11 installation. Windows 95, Windows 98, and Windows Me do not create one during installation. If _Default.pif is not present, Windows 95, Windows 98, and Windows Me use the properties of Conagent.exe.

On Windows NT, Windows Server 2000, Windows XP, or Windows Server 2003

Use one of the following two procedures to correct the problem:

Steps to Reset Default Configuration of ALL Command Prompts

On Windows NT:

On Windows Server 2000, Windows XP, and Windows Server 2003:

Steps to Reset Configuration for Just Vcspawn.exe by Using Regedt32

Use the following process to add a registry entry so only Vcspawn’s settings are not “full screen.”

C:_MSVC20_BIN_vcspawn.exe

<drive>:_DIR1_DIR2_DIR3..._vcspawn.exe

Steps to Reset Configuration for Just Vcspawn.exe Without Using Regedt32

If you are unfamiliar with the system registry and do not want to reset the default configurations for the Command Prompt, use the following procedure to reset the settings for Vcspawn. This procedure adds the same registry entry.

NOTE: if you have a fast machine, you may have trouble performing some of the following steps and you need a larger project. Therefore, if you have a fast machine, use one of the previous methods to work around the problem.

If you are compiling a large project, you can switch tasks and see the minimized Vcspawn.exe icon. Resetting the attributes of this icon will reset the attributes of Vcspawn.

NOTE: You must save the configuration before the development environment finishes the build process. If you do not, the Vcspawn.exe window will be terminated, the icon will disappear and any changes you made will not be saved.

On Windows 95, Windows 98, and Windows Me:

Use one of the following procedures to correct the problem.

Steps to Reset Configuration of _Default.pif

Steps to Reset Configuration of Conagent.exe

APPLIES TO

NMAKE : fatal error U1045: spawn failed : Invalid argument

CAUSE

NMAKE uses the command interpreter to spawn the different tools that are needed to build the targets. The path to the command interpreter is found by querying for the value of the ComSpec environment variable. If the ComSpec environment variable is set incorrectly, you receive the error message shown in the “Symptoms” section.

RESOLUTION

To resolve this problem, ensure that the ComSpec environment variable is set correctly.

For Microsoft Windows NT and Microsoft Windows 2000, the command interpreter is Cmd.exe. The ComSpec environment variable should contain the following:

%SYSTEMROOT%\System32\Cmd.exe

To view and modify the ComSpec environment variable in Windows NT:

To view and modify the ComSpec environment variable in Microsoft Windows Server 2003, in Windows 2000, and in Windows XP, follow these steps:

For Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Millennium (Me), the command interpreter is Command.com. The ComSpec environment variable should contain the following:

%WINDIR%\Command.com

To view the value of the ComSpec environment variable:

A list of all of the environment variables should be displayed in alphabetical order.

To correctly set the ComSpec environment variable:

NOTE: On all these operating systems, ComSpec must not contain multiple paths. Only a single path is acceptable.

MORE INFORMATION

Steps to reproduce the behavior in Windows 2000

APPLIES TO

A Microsoft Visual C++ 2005 Active Template Library (ATL) Server project contains performance counters. This project is configured to register an Internet Server API (ISAPI) DLL on a Windows Vista-based computer. However, the ISAPI DLL is not registered when you run the ATL Server application. Additionally, when you try to register the ISAPI DLL manually, you may receive an error message that resembles the following:

0×80070002 COR_E_FILENOTFOUND

CAUSE

This problem occurs because the performance counter infrastructure in Windows Vista prevents a call to the RegSetValue function from modifying system files. Windows Vista prevents changes to system files to guarantee reliability of the operating system. The RegSetValue function must modify system files to install ATL-based performance counters.

WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, modify the registry to configre the Windows Vista performance counter infrastructure to bypass the system files integrity check. To do this, you must modify the Configuration Flags registry value that is located in the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib registry key. If the registry value contains the 0×00010000 flag, Windows Vista bypasses the integrity check.

To do this, follow these steps:

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION

The ATL is a set of template-based C++ classes that simplify programming Microsoft Component Object Model (COM) objects. The ATL Server Library is a set of template-based C++ classes for creating Web applications, Web services, and other server applications.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You have a Visual J++ project with a class that uses the java.io.PipedOutputStream object. When you convert your Visual J++ project to a Visual C# .NET project by using the Java Language Conversion Assistant (JLCA), the java.io.PipedOutputStream object is not converted completely in the Visual C# .NET or in Visual C# 2005 code that is generated. When you open the Microsoft Visual Studio .NET or Microsoft Visual Studio 2005 Help topic that is listed in the UPGRADE_ISSUE comment, the java.io.PipedOutputStream class is listed as System.IO.StreamReader in the Help topic. This is not correct.

In Visual J++, this constructor creates a piped output stream that is not yet connected to a piped input stream.
In the .NET Framework, the equivalent is the System.IO.StreamReader class, but it has no empty constructor.
To correct this error

RESOLUTION

In the Microsoft .NET Framework, the equivalent of java.io.PipedOutputStream is System.IO.StreamWriter, not System.IO.StreamReader. The Help topic should read as follows:

In Visual J++, this constructor creates a piped output stream that is not yet connected to a piped input stream.
In the .NET Framework, the equivalent is the System.IO.StreamWriter class, but it has no empty constructor.
To correct this error

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Behavior

import java.io.*;

public class Class1

{

        public static void main (String[] args)

        {

               // Create a new PipedOutputStream object.

               PipedOutputStream myOutStream = new PipedOutputStream();

        }

}

REFERENCES

For more information about the java.io.PipedOutputStream class, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/library/en-us/vjref98/html/java.io.pipedoutputstream.asp (http://msdn.microsoft.com/library/en-us/vjref98/html/java.io.pipedoutputstream.asp)

APPLIES TO

Error C2710 : cannot delete a pointer to a const object

NOTE: Visual C++ .NET compiler does not demonstrate this issue in conformance to the changes made in the C++ ANSI Standards.

CAUSE

Deleting a pointer to a constant should not be allowed by definition (ARM section 5.3.4) because it modifies the object pointed to. However, if you deliberately or accidentally use the explicit conversion, the compiler doesn’t generate the error. The consequences of a such attempt are unpredictable and compiler implementation dependent.

STATUS

This behavior is by design.

MORE INFORMATION

Sample Code #1 to Demonstrate Behavior

/* No special compile options needed. */

const int * pi   = new int(1000);

const char * pch = new char(65);

void main(void)

{

  delete  pi  ;// Error C2710:cannot delete a pointer to a const object

  delete  pch ;// Error C2710:cannot delete a pointer to a const object

}

Visual C++ version 5.0 and 6.0 generate the following error:

Error C2664: ‘delete’ : cannot convert parameter 1 from ‘const char *’ to ‘void *’

Sample Code #2 to Demonstrate Behavior

/* No special compile options needed.

   The type casting of the pointer to const argument of the delete

   operator prevents the C2710 error but is not recommended. */

const int * pi   = new int(1000);

const char * pch = new char(65);

void main(void)

{

   delete (int *) pi;   //no error C2710 generated

   delete (char *) pch; //no error C2710 generated

}

Action

1. Open Visual Studio 2005 or 2008 and create default MFC Single Document application.
2. Add the following code in the OnDraw() method of the wizard-generated custom view class:
COleDateTime t = COleDateTime::GetCurrentTime();
DBTIMESTAMP ts;
t.GetAsDBTIMESTAMP( ts ); // retrieves the time in t into the ts structure
3. Now compile the project.

Result

You receive the following error:
“testoleview.cpp(59) : error C2039: ‘GetAsDBTIMESTAMP’ : is not a member of ‘ATL::COleDateTime’
C:\Program Files (x86)\Microsoft Visual Studio 8\VC\atlmfc\include\atlcomtime.h(104) : see declaration of
‘ATL::COleDateTime’”
[Even including the required header files in the View class does not resolve the error:
#include <oledb.h>
#include <ATLComTime.h>]

Cause

Only ATLComTime.h was included indirectly from #include <afxdisp.h>, which was added in stdafx.h by the wizard while generating the default code for the project.  But for GetAsDBTIMESTAMP to be compiled as part of COleDateTime, __oledb_h__ must have been defined previously. Even if Database support was selected in the wizard during project generation, afxoledb.h is added to stdafx.h, but it is added after afxdisp.h, which is too late.

Resolution

Move the #include <afxoledb.h> above the #include <afxdisp.h> in the precompilation header file, stdafx.h.

More Information

This bug has been reported, and may be fixed in a later Service Pack.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Expression does not produce a value

RESOLUTION

To resolve this problem, use one of the following methods.

Method 1

Make the first method call an early bound method call by specifying the type for the first object.

Method 2

Assign the lambda expression to a separate variable before you pass the lambda expression to the late-bound method call.

For example, the following code causes the error message that is mentioned in the “Symptoms” section.

Dim variable1, variable2 As Object

variable1.LateBoundCall(variable2.LateBoundCall(Function(a As Integer) a))

To resolve this problem, change this code as follows.

Dim variable1, variable2 As Object

Dim delegateName As Func(Of Integer, Integer) = Function(a As Integer) a

variable1.LateBoundCall(variable2.LateBoundCall(delegateName))

MORE INFORMATION

Steps to reproduce the problem

Public Class SampleClass

        Sub LateBoundCall(ByVal x As Object)

        End Sub

End Class

Dim variable1, variable2 As Object

variable1.LateBoundCall(variable2.LateBoundCall(Function(a As Integer) a))

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

LINK : warning LNK4018: too many type indexes in PDB “filename”, discarding subsequent type information

NOTE: You will not be able to see the subsequent types in the debugger.

CAUSE

The number of type indexes in the Program Database File (.pdb file) for your project exceeded 64K for Visual C++ 4.x and 16M for later versions. This is a limitation of the debugging format in a .pdb file. The format uses a 16-bit field to store the number of types. This field was increased to 24 bits in Visual C++ 5.0.

RESOLUTION

To avoid this warning, use one or more of the following methods to decrease the number of type indexes in your .pdb file: