Open Software Solutions » MS Visual Studio

FIX: A Stop error or a crash occurs on the operating system when you profile an application by using Visual Studio 2008 Service Pack 1

admin — Mon, 06 Sep 2010 11:56:23 +0000

Article ID: 958842 – Last Review: February 23, 2009 – Revision: 2.1

FIX: A Stop error or a crash occurs on the operating system when you profile an application by using Visual Studio 2008 Service Pack 1

View products that this article applies to.

SYMPTOMS

You may experience a Stop error, or the operating system may crash when you create a profile of an application by using Microsoft Visual Studio 2008 Service Pack 1 (SP1). The problem occurs when the following conditions are true:

You use the sampling profiling method.
The computer is running on the Intel Nehalem processor.

Back to the top

CAUSE

This problem occurs because the sampling profiler uses a driver in the operating system. However, the Intel Nehalem processor was created after the release of the 2008 version of the profiler. Because the sampling feature of the profiler is specific to the driver per processor, it was not possible to be completely compatible with the Nehalem processor before the release.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB958842 (http://code.msdn.microsoft.com/KB958842)

Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

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

Prerequisites

You must have Visual Studio 2008 Service Pack 1installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Vsperfdrv90.sys	9. 0.30729.162	53,072	16-Oct- 2008	10:30	x86
Vsperfdrv90.sys	9.0.30729.162	68,944	15-Oct-2008	17:02	x64
Vsperfsys.cat	Not applicable	8,474	11-Dec- 2008	20:13	x86
Vsperfsys.cat	Not applicable	8,474	11-Dec-2008	20:13	x64

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

If you experience the same error when you use Microsoft Visual Studio 2005 SP1, apply hotfix 958840. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

958840Ã‚Â (/Feedback.aspx?kbNumber=958840/ ) FIX: A Stop error or a crash occurs on the operating system when you profile an application by using Visual Studio 2005 Service Pack 1

For more information about Nehalem, visit the following Web site:

http://en.wikipedia.org/wiki/Intel_Nehalem (http://en.wikipedia.org/wiki/Intel_Nehalem)

For more information about how to analyze application performance by using profiling tools, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/z9z62c29.aspx (http://msdn.microsoft.com/en-us/library/z9z62c29.aspx)

Back to the top

APPLIES TO

Microsoft Visual Studio 2008 Service Pack 1

Back to the top

kbhotfixserver kbexpertiseadvanced kbqfe kbsurveynew KB958842

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Problems when trying to setup remote debug across network domains

admin — Sat, 04 Sep 2010 12:40:40 +0000

Action

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 Visual Studio .NET 2002 Professional Edition
	Microsoft Visual Studio .NET 2003 Professional Edition
	Microsoft Visual Studio 2005 Professional Edition
	Microsoft Visual Studio 2008 Professional Edition

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

Microsoft Knowledge Base Article

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

Related Articles or Pages

Possible Reasons for OLE Control Registration Failure

admin — Tue, 31 Aug 2010 15:51:32 +0000

SUMMARY

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

•	One or more of the necessary OLE DLLs is not in the path. Instructions for distributing OLE Controls as well as an explanation of what DLLs are necessary to ship can be found in the Shipctrl.wri file located in the same directory as the CDK.
	The control is loading a DLL other than the OLE DLL, and that DLL is not in the path. When the control is loaded into memory, any DLLs that are implicitly loaded through an import library are also loaded. If any of these DLLs are not in the path, the control is not loaded successfully, so registration fails.
	One or more DLLs may be the wrong version. If the control was built with a newer version of a DLL than the one installed on the computer, the control may not load properly, so registration fails.
	An old version of Ocd25.lib is being linked to. If the control is using the MFC database classes, there may be a problem with the version of the Ocd25.lib file that is being linked to.
	The OLE control is located on a Novell server’s remote drive. In this case, the access rights to the .ocx file may be preventing the control from loading. Make sure that the access rights for the .ocx file are set to read-only, shareable access, which is the typical setting for executable files.

Troubleshooting Techniques

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

1.	With the control project loaded in Visual C++, set the executable for the debug session to the OLE Control Test Container (Tstcon16.exe or Tstcon32.exe). When you start the Test Container (under the debugger), you will get a warning that the Test Container does not contain debug information. Ignore this and proceed.
2.	From the Test Container, attempt to register the control. Watch for debug output from the OLE Control DLL or any of its dependent DLLs. If you are running the 16-bit product, remember to run the DBWIN program to receive debug output.For information on how to set the executable for a DLL debug session, please see the help topic “Debugging DLLs” in Books Online.

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 Visual C++ 1.5 Professional Edition
	Microsoft Visual C++ 1.51
	Microsoft Visual C++ 1.52 Professional Edition
	Microsoft Visual C++ 2.0 Professional Edition
	Microsoft Visual C++ 2.1
	Microsoft Visual C++ 2.2
	Microsoft Visual C++ 4.0 Standard Edition

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

Microsoft Knowledge Base Article

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

Related Articles or Pages

FIX: You may experience performance issues in the IDE after you use Visual Studio 2008 to build a Visual Basic project

admin — Sat, 28 Aug 2010 16:13:33 +0000

Consider the following scenario:

•	You use Microsoft Visual Studio 2008 to build a Microsoft Visual Basic project.
•	The Visual Basic project contains many XML comments in a single file.
•	The file is probably a designer-generated file for a dataset or for a Web reference.

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

•	The IDE takes a long time to build the solution and to rebuild the solution.
•	You experience a slow response time when you press F5 to start debugging.
•	You experience a slow response time in the Code Editor.
•	You experience a slow response time in IntelliSense.

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&amp;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)

File name	File version	File size	Date	Time
Avvspkdh.dll	9.0.21022.43	34,816	29-Jan-2008	03:17
Mcee.dll	9.0.21022.43	367,608	29-Jan-2008	03:17
Mpishim.exe	9.0.21022.43	26,112	29-Jan-2008	03:17
Msvb7.dll	9.0.21022.43	4,069,880	29-Jan-2008	03:17
Msvsmon.exe	9.0.21022.43	3,004,416	29-Jan-2008	03:17

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

1.	In Solution Explorer, right-click `ProjectName`, and then click Properties.
2.	On the Compile tab, click to clear the Generate XML documentation file check box.
3.	On the File menu, click Save All.

Visual Basic 2008 Express Edition

Create a backup of the project.

In Notepad, open the .vbproj file for the project.

Locate and then delete all the elements in the .vbproj file.

Note Typically, you will delete two elements in the .vbproj file.

Method 2: Remove the XML comments

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

1.	On the Edit menu, point to Find and Replace, and then click Quick Replace.
2.	In the Find what box, type ”’.
3.	In the Replace with box, type ”, and then click Replace All.

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

•	You save the designer file that generated this code file.
•	You refresh the Web reference.
•	You right-click the file, and then you click Run Custom Tool.

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:

1.	Create a new class library project to store files that contain a dataset or that contain a Web reference.
2.	In the original Visual Basic project, add a reference to the new class library project.
3.	Use Method 1 to disable the XML documentation file.

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 Visual Studio 2008 Professional Edition
•	Microsoft Visual Studio 2008 Academic Edition
•	Microsoft Visual Studio 2008 Standard Edition
•	Microsoft Visual Basic 2008 Express Edition
•	Microsoft Visual Studio Team System 2008 Team Suite
•	Microsoft Visual Studio Team System 2008 Database Edition
•	Microsoft Visual Studio Team System 2008 Architecture Edition
•	Microsoft Visual Studio Team System 2008 Development Edition
•	Microsoft Visual Studio Team System 2008 Test Edition

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

Microsoft Knowledge Base Article

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

Related Articles or Pages

You cannot host a Visual SourceSafe 2005 Web service on a computer that is running Windows Vista

admin — Mon, 23 Aug 2010 10:50:15 +0000

You cannot host a Visual SourceSafe 2005 Web service on a computer that is running Windows Vista

View products that this article applies to.

Article ID	:	933859
Last Review	:	March 26, 2007
Revision	:	1.0

SYMPTOMS

If you install Microsoft Visual SourceSafe (VSS) 2005 on a computer that is running Windows Vista, you cannot host a VSS Web service.

Back to the top

CAUSE

This behavior occurs because of changes in Microsoft Internet Information Services (IIS) 7.0. IIS 7.0 does not include the WebDAV component. The VSS Web service requires the Put method of the WebDAV component to upload files. Therefore, you cannot host a VSS Web service in Windows Vista.

Note The WebDAV component is an extension of the HTTP protocol. The WebDAV component lets you treat a Web server as a remote server.

Back to the top

WORKAROUND

To work around this behavior, put the Web service in an IIS virtual folder. For information about how to do this, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/ms230206(VS.80).aspx (http://msdn2.microsoft.com/en-us/library/ms230206(VS.80).aspx)

Back to the top

REFERENCES

For more information, visit the following MSDN blog Web site:

http://blogs.msdn.com/richardb/archive/2007/01/23/clarifying-sourcesafe-support-on-vista.aspx (http://blogs.msdn.com/richardb/archive/2007/01/23/clarifying-sourcesafe-support-on-vista.aspx)

Back to the top

APPLIES TO

â€¢	Microsoft Visual SourceSafe 2005 Standard Edition
â€¢	Windows Vista Ultimate
â€¢	Windows Vista Business
â€¢	Windows Vista Enterprise
â€¢	Windows Vista Home Basic
â€¢	Windows Vista Home Premium
â€¢	Windows Vista Business 64-bit edition
â€¢	Windows Vista Enterprise 64-bit edition
â€¢	Windows Vista Home Basic 64-bit edition
â€¢	Windows Vista Home Premium 64-bit edition
â€¢	Windows Vista Starter

Back to the top

kbexpertiseadvanced kbtshoot kbprb kbinfo KB933859

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

The DataSet designer does not allow custom data types to be used on the columns of data tables inside the data set.

admin — Fri, 20 Aug 2010 11:56:20 +0000

Article ID: 968761 – Last Review: March 9, 2009 – Revision: 1.0

The DataSet designer does not allow custom data types to be used on the columns of data tables inside the data set.

View products that this article applies to.

Expand all | Collapse all

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

Symptom

When you try to use custom data types on the columns of data tables inside a data set with the DataSet Designer your project will not compile and you receive the following error:

Ã‚Â

Custom tool error: Failed to generate code. Unable to convert input xml file content to a DataSet. Column requires a valid DataType. Column requires a valid DataType.

Back to the top

Cause

The DataSet designer does not allow custom data types to be used on the columns of data tables inside the data set.

Back to the top

Resolution

Do not use the local type in DataColumn.Type

Back to the top

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.

Back to the top

APPLIES TO

Microsoft Visual Studio 2008 Standard Edition
Microsoft Visual Studio 2008 Professional Edition
Microsoft Visual Studio 2008 Academic Edition
Microsoft Visual Studio Team System 2008 Team Suite

Back to the top

kbnomt kbrapidpub KB968761

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

After you use the ReportResult method to customize the error icon when a logon failure occurs in Windows Vista, the general error icon (CPSI_ERROR) is displayed unexpectedly

admin — Thu, 19 Aug 2010 12:04:52 +0000

After you use the ReportResult method to customize the error icon when a logon failure occurs in Windows Vista, the general error icon (CPSI_ERROR) is displayed unexpectedly

View products that this article applies to.

Article ID	:	953181
Last Review	:	May 22, 2008
Revision	:	1.0

SYMPTOMS

To develop a custom credential provider for Windows Vista, you use the ReportResult method to customize the string and the error icon that are displayed in a logon failure situation. However, when a logon failure occurs, the general error icon (CPSI_ERROR) is displayed instead of the customized error icon in the credential provider.

Back to the top

RESOLUTION

Hotfix information

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

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites

To apply this hotfix, you must have Windows Vista Service Pack 1 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

Windows Vista with SP1, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb953181~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,789	16-May-2008	17:27	Not Applicable
Package_2_for_kb953181~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,956	16-May-2008	17:27	Not Applicable
Package_3_for_kb953181~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,794	16-May-2008	17:27	Not Applicable
Package_4_for_kb953181~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,794	16-May-2008	17:27	Not Applicable
Package_for_kb953181_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	16-May-2008	17:27	Not Applicable
Package_for_kb953181_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,421	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,429	16-May-2008	17:27	Not Applicable
Update.mum	Not Applicable	3,077	16-May-2008	17:27	Not Applicable
X86_3515116c017ac72b22e29358e7ac307e_31bf3856ad364e35_6.0.6001.22180_none_adbb6519d9d9eaf4.manifest	Not Applicable	709	16-May-2008	17:27	Not Applicable
X86_microsoft-windows-authentication-authui_31bf3856ad364e35_6.0.6001.22180_none_0c269a820ec66149.manifest	Not Applicable	56,697	16-May-2008	05:34	Not Applicable
Authui.dll	6.0.6001.2218

Windows Vista with SP1, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_41c0fa786f1529b488706cf78138a781_31bf3856ad364e35_6.0.6001.22180_none_90ff3bd856c48710.manifest	Not Applicable	1,066	16-May-2008	17:27	Not Applicable
Amd64_4e8f87e8a6837219230bcf256a6a6d75_31bf3856ad364e35_6.0.6001.22180_none_13cff55103278822.manifest	Not Applicable	713	16-May-2008	17:27	Not Applicable
Amd64_microsoft-windows-authentication-authui_31bf3856ad364e35_6.0.6001.22180_none_68453605c723d27f.manifest	Not Applicable	56,755	16-May-2008	06:12	Not Applicable
Package_1_for_kb953181~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,799	16-May-2008	17:27	Not Applicable
Package_2_for_kb953181~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,195	16-May-2008	17:27	Not Applicable
Package_3_for_kb953181~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,031	16-May-2008	17:27	Not Applicable
Package_4_for_kb953181~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,031	16-May-2008	17:27	Not Applicable
Package_for_kb953181_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	16-May-2008	17:27	Not Applicable
Package_for_kb953181_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,429	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,437	16-May-2008	17:27	Not Applicable
Update.mum	Not Applicable	3,099	16-May-2008	17:27	Not Applicable
Authui.dll	6.0.6001.22180	2,271,744	16-May-2008	05:30	x64

Windows Vista with SP1, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_6326e9a85dd88b916eb63888d204b95c_31bf3856ad364e35_6.0.6001.22180_none_aca4bab8d67480f7.manifest	Not Applicable	711	16-May-2008	17:27	Not Applicable
Ia64_83b064555600877e9f2a65fba95455fa_31bf3856ad364e35_6.0.6001.22180_none_1c99b700ed4c5f55.manifest	Not Applicable	1,064	16-May-2008	17:27	Not Applicable
Ia64_microsoft-windows-authentication-authui_31bf3856ad364e35_6.0.6001.22180_none_0c283e780ec46a45.manifest	Not Applicable	55,780	16-May-2008	06:11	Not Applicable
Package_1_for_kb953181~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,794	16-May-2008	17:27	Not Applicable
Package_2_for_kb953181~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,026	16-May-2008	17:27	Not Applicable
Package_3_for_kb953181~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,026	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,425	16-May-2008	17:27	Not Applicable
Package_for_kb953181_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	16-May-2008	17:27	Not Applicable
Package_for_kb953181_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	16-May-2008	17:27	Not Applicable
Package_for_kb953181_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,433	16-May-2008	17:27	Not Applicable
Update.mum	Not Applicable	2,423	16-May-2008	17:27	Not Applicable
Authui.dll	6.0.6001.22180	2,941,952	16-May-2008	05:15	IA-64

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

For more information about credential providers in Windows Vista, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/bb530197.aspx (http://msdn.microsoft.com/en-us/library/bb530197.aspx)

For more information about the ReportResult method, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/bb776030(VS.85).aspx (http://msdn.microsoft.com/en-us/library/bb776030(VS.85).aspx)

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

â€¢	Windows Vista Enterprise 64-bit Edition
â€¢	Windows Vista Home Basic 64-bit Edition
â€¢	Windows Vista Home Premium 64-bit Edition
â€¢	Windows Vista Ultimate 64-bit Edition
â€¢	Windows Vista Business
â€¢	Windows Vista Business 64-bit Edition
â€¢	Windows Vista Enterprise
â€¢	Windows Vista Home Basic
â€¢	Windows Vista Home Premium
â€¢	Windows Vista Ultimate

Back to the top

kbexpertiseadvanced kbfix kbqfe kbhotfixserver KB953181

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Visual Studio 2008 Express Editions Service Pack 1 Beta release notes and a list of fixed issues

admin — Wed, 11 Aug 2010 12:51:00 +0000

Visual Studio 2008 Express Editions Service Pack 1 Beta release notes and a list of fixed issues

View products that this article applies to.

Article ID	:	952283
Last Review	:	May 6, 2008
Revision	:	2.1

Notice

Beta Information

This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

SUMMARY

This article lists known issues with the setup and with the removal of Visual Studio 2008 Express Editions Service Pack 1 (SP1) Beta. Additionally, this article describes supporting features in Visual Studio 2008 Express Editions SP1 Beta.

Back to the top

MORE INFORMATION

This article describes the following:

â€¢	How to obtain Visual Studio 2008 Express Editions SP1 Beta
â€¢	Changed features and fixed issues for Visual Studio 2008 Express Editions SP1 Beta
â€¢	Supported languages and operating systems
â€¢	Installation requirements
â€¢	Visual Studio 2008 Express Editions SP1 Beta support
â€¢	Installation issues for all platforms
â€¢	Removal issues for all platforms
â€¢	Known issues with the service pack

Back to the top

Products to which Visual Studio 2008 Express Editions SP1 Beta applies

â€¢

Supported Windows versions that are not running any of the following editions of Visual Studio 2008:

â€¢	Visual Studio 2008 Team Edition
â€¢	Visual Studio 2008 Standard Edition
â€¢	Visual Studio 2008 Professional Edition

â€¢

The Microsoft .NET Framework 3.5

â€¢

Visual C# 2008 Express Edition

â€¢

Visual Basic 2008 Express Edition

â€¢

Visual C++ 2008 Express Edition

â€¢

Visual Web Developer 2008 Express Edition

Back to the top

How to obtain Visual Studio 2008 Express Editions SP1 Beta

To obtain Visual Studio 2008 Express Editions SP1 Beta, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=117352 (http://go.microsoft.com/fwlink/?LinkId=117352)

This package installs Visual C# 2008 SP1 Express Edition (Beta), Visual Basic 2008 SP1 Express Edition (Beta), Visual C++ 2008 SP1 Express Edition (Beta), and Visual Web Developer 2008 SP1 Express Edition (Beta).

For more information about the download location for Visual Studio 2008 SP1 Beta for Standard, Professional, and Team editions, click the following article number to view the article in the Microsoft Knowledge Base:

945140 (/Feedback.aspx?kbNumber=945140/) Visual Studio 2008 Service Pack 1 Beta release notes and a list of fixed issues

Back to the top

Lists of changed features and fixed issues for Visual Studio 2008 Express Editions SP1 Beta

For lists of changed features and fixed issues for Visual Studio 2008 Express Editions SP1 Beta, see the following articles in the Microsoft Knowledge Base:

â€¢	950263 (/Feedback.aspx?kbNumber=950263/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual C#
â€¢	950264 (/Feedback.aspx?kbNumber=950264/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual Basic
â€¢	950262 (/Feedback.aspx?kbNumber=950262/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual C++
â€¢	950261 (/Feedback.aspx?kbNumber=950261/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual Web Developer 2008
â€¢	951847 (/Feedback.aspx?kbNumber=951847/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for the .NET Framework 3.5

This service pack adds the following new features:

â€¢

SQL Server 2008 Community Technology Preview (CTP) support is added to Visual Studio 2008.

â€¢

In Visual C++, the Libraries support for Technical Report 1 (TR1) is added.

â€¢

In Visual C++, the Microsoft Foundation Class (MFC) is improved to support the Office Look and Feel feature.

â€¢

In Visual Web Developer, SQL Server 2008 support for Web projects is added.

â€¢

In Visual Web Developer Express Edition, Web application projects support and Class Library support are added.

â€¢

In Visual Web Developer, JScript formatting support is added.

â€¢

In Visual Web Developer, WCF Service Rename Experience is improved.

â€¢

Debugging improvements are made to improve the support for inspecting the results of in-memory Language-Integrated Query (LINQ) queries.

â€¢

A new Visual C# feature is added to provide richer error information about your code.

â€¢

The following debugging features for managed properties and managed operators are changed:

â€¢	Step into Specific
â€¢	Step Filtering

â€¢

The debugger now can cancel symbol and source downloading from Microsoft Public Symbol Servers.

â€¢

Streamlined support for Reference Source is added to the debugger.

â€¢

To ease data access, the ADO.NET Entity Designer is added.

â€¢

The ability to add Local Database Cache to device projects is added.

â€¢

ASP.NET Dynamic Data templates and toolbox controls are added.

â€¢

Internet Information Services (IIS) 7.0 Managed Module and Handler templates are added.

â€¢

Support for starting the WCF Test client debugging of a WCF service (.svc) by pressing F5 is added.

Back to the top

Supported languages and operating systems

Supported languages

â€¢	English (United States)
â€¢	Japanese

Supported operating systems

â€¢	Windows Server 2008
â€¢	Windows Vista
â€¢	Windows XP SP2
â€¢	Windows Server 2003 SP2 or a later version of Windows Server 2003

Back to the top

Installation requirements

â€¢	A licensed copy of one of the supported Visual Studio 2008 Express editions must be installed on the destination computer.
â€¢	Microsoft Windows Installer 3.1 or a later version of Windows Installer must be installed on the destination computer. For more information, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/Aa372866.aspx (http://msdn2.microsoft.com/en-us/library/Aa372866.aspx)
â€¢	We recommend 512 megabytes (MB) or more of RAM.

Back to the top

Visual Studio 2008 Express Editions SP1 Beta support

Formal support is available through Microsoft Connect. For more information, visit the following Microsoft Web site:

http://connect.microsoft.com (http://connect.microsoft.com)

Informal community support is available through the MSDN forums. For more information, visit the following Microsoft Web site:

http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=6&SiteID=1 (http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=6&SiteID=1)

Back to the top

Installation issues for all platforms

Visual Studio 2008 Express Editions SP1 Beta does not install immediately after a Visual Studio compilation

You cannot install Visual Studio 2008 Express Editions SP1 Beta until the debugger service closes.

To resolve this issue, take one of the following actions:

â€¢	Finish compilations that are in progress, and then wait for the debugger service to close. This may take ten minutes.
â€¢	Use Task Manager to end all instances of the Mspdbsrv.exe service.

Back to the top

Removal issues for all platforms

Mixed mode

For multiple editions of Visual Studio 2008, Microsoft supports only those scenarios in which all editions are at the same service pack level. If there are multiple language versions or multiple editions of Visual Studio 2008 on a computer, all must be at the same level to be supported by Microsoft. For example, all versions or editions must be at the release level or at the SP1 level.

How to remove Visual Studio 2008 Express SP1 Beta

Visual Studio 2008 Express SP1 Beta is a complete update of the earlier version of Visual Studio 2008 Express editions. To remove each language edition of Visual Studio 2008 Express SP1 Beta, follow these steps, depending on the version of Windows that you have installed.

Windows Vista

1.	In Control Panel, open the Programs and Features item.
2.	Click Visual Studio 2008 Express SP1 Beta, and then click Uninstall
3.	In the setup wizard, select the option to uninstall the product, and then follow the setup wizard.

Versions of Windows earlier than Windows Vista

1.	In Control Panel, open the Add or Remove Programs item.
2.	Click Visual Studio 2008 Express SP1 Beta, and then click Remove
3.	In the setup wizard, select the option to uninstall the product, and then follow the setup wizard.

How to restore to the release version of Visual Studio 2008

After you completely remove all Visual Studio 2008 SP1 Beta editions, you must repair the remaining Visual Studio 2008 release version to restore all the features that were replaced during the Visual Studio 2008 SP1 Beta update. The Microsoft .NET Framework 3.5 SP1 Beta remains on the operating system after you uninstall Visual Studio 2008 SP1 Beta. We recommend that you do not remove the .NET Framework 3.5 SP1 Beta from the operating system. The .NET Framework 3.5 SP1 Beta is backward compatible with earlier versions of Visual Studio.

To restore Visual Studio 2008 to a supported release-version state, follow these steps:

If any Visual Studio 2008 Express SP1 Beta editions were installed, remove them by following the steps in the How to remove Visual Studio 2008 Express SP1 Beta subsection of the Removal issues for all platforms section.

If Visual Studio 2008 Express SP1 Beta was applied to any Visual Studio 2008 non-Express editions, remove the Visual Studio 2008 Express SP1 Beta updates by following the steps in the How to remove Visual Studio 2008 Express SP1 Beta subsection of the Removal issues for all platforms section..

Follow these steps, depending on the version of Windows that you have installed.

Windows Vista

a.	In Control Panel, open the Programs and Features item.
b.	Click each instance of Visual Studio 2008, and then click Uninstall/Change to start Visual Studio Setup in maintenance mode.

Versions of Windows earlier than Windows Vista

a.	In Control Panel, open the Add or Remove Programs item.
b.	Click each instance of Visual Studio 2008, and then click Change/Remove to start Visual Studio Setup in maintenance mode.

Click to select the Repair/Reinstall option on the maintenance mode window, and then let Setup repair the existing features.

Repeat step 3.

Click to select the Add or Remove Features option on the maintenance mode window.

Take one of the following actions:

â€¢	Click to select one of the feature check boxes in the productâ€™s feature tree, and then click to clear the check box.
â€¢	Add or remove any feature components that you want to modify.

Click Update, and then let Setup update the Visual Studio components that are installed on the operating system.

Reinstall any edition of Visual Studio 2008 Express.

Back to the top

Known issues with the service pack

The Visual Studio 2008 Express Editions SP1 Beta installation fails if the .NET Framework 3.5 Client Beta 1 is already installed on the computer

To work around this issue, follow these steps:

1.	Uninstall the Microsoft .NET Framework 3.5 Client Beta 1.
2.	Uninstall the Microsoft .NET Framework 3.0 Client Beta 1.
3.	Uninstall the Microsoft .NET Framework 2.0 Client Beta 1.
4.	Reinstall Visual Studio 2008 Express Editions SP1 Beta.

Visual Studio 2008 Express Editions SP1 Beta is incompatible with SQL Server 2008 Express Edition, and you cannot connect to SQL Server databases after you upgrade to SQL Server 2008 Express Edition

When you upgrade to SQL Server 2008 Express Edition, the named instance of the database is overwritten, and any Visual Studio 2008 Express editions can no longer target the default instance in SQL Server 2008 Express Edition.

Sixty-four-bit debugger components are not updated on computers that have the release version of Visual Studio 2008 Express editions installed

The Remote Debugger Light component lets you debug 64-bit applications in Visual Studio 2008 Express editions. If a release version of a Visual Studio 2008 Express edition is already installed on the computer, the installation of Visual Studio 2008 Express Editions SP1 Beta does not upgrade the Remote Debugger Light component to the SP1 level. Therefore, some new features in Visual Studio 2008 Express Editions SP1 Beta do not function correctly or are not available when you debug 64-bit applications. Additionally, if you repair the Visual Studio 2008 Express editions, the repair procedure fails at the step at which the repair procedure tries to repair the Remote Debugger Light component. Then, additional repairs of components are canceled.

To work around this issue, uninstall the Remote Debugger Light component in a 64-bit of version of Windows, and then install Visual Studio 2008 Express Editions SP1 Beta.

The .NET Framework Setup program may fail in Visual Studio 2008 Express Editions SP1 Beta

The .NET Framework Setup program fails if one of the following conditions is true:

â€¢	On a Windows XP-based computer, you have no version of the .NET Framework installed.
â€¢	On a Windows XP-based computer, you have only the .NET Framework 2.0 or an earlier version of the .NET Framework installed.

The Setup program fails because an IIS metabase lock is held for longer than expected.

To work around this issue, follow these steps:

1.	Click Start, click run, type eventvwr.msc, and then click OK.
2.	Click to select Application.
3.	Check whether the following error exists in the event log: Type: Error Source: System.ServiceModel.Install 3.0.0.0 Description: System.Runtime.InteropServices.COMException (0×80070094): The path specified cannot be used at this time.
4.	If this error exists, reinstall Visual Studio 2008 Express Editions SP1 Beta.

Entity Designer may display the safe mode watermark when you rename the entity data model namespace

If the entity data model contains a type that has the same name as the last part of the storage model, Entity Designer displays the safe mode watermark when you rename the conceptual model namespace. This makes the .edmx file editable only in the XML editor.

For example, if the entity data model contains a type that is named Store and the storage model namespace is AdventureWorksModel.Store, this issue will occur if you rename the entity data model namespace.

To work around this issue, follow these steps:

1.	In the Visual Studio 2008 IDE, double-click the related error in the error list. The error number is 34. For example: Error 34: Unknown namespace or alias (AdventureWorksModel)
2.	In the XML editor, rename the namespace to the new namespace name, and then save and close the model.

Entity Designer displays the safe mode watermark when the parameters of a stored procedure that is mapped to a function import are modified

If the parameters of a stored procedure that has a corresponding function import are added, removed, or changed, Entity Designer displays the safe mode watermark. This causes the .edmx file to be editable only in the XML editor.

To work around this issue, follow these steps:

Open the .edmx file in the XML editor.

Delete the FunctionImport element and the corresponding FunctionImportMapping element. (These elements exist at two positions in the .edmx file.) If you do not want to delete the elements, you can change the parameters of the Function Import element to correctly map the stored procedure that will be displayed as a function element in the store schema definition language (SSDL) section.

You may receive a System.OutofMemoryException exception on a model that has several hundred tables

There is no known workaround for this issue now.

Undo operations are slow for a model that contains more than 100 types

There is no known workaround for this issue now.

Entity data models that have the same SSDL schema names cause errors in Web site projects

If a Web site project contains entity data models that have the same SSDL schema names, an error that indicates that the project contains conflicting storage namespace names occurs at run time.

To work around this issue, change the metadata part of the connection string in the Web.config file as follows.

The original version is as follows:

res://*

The changed version should be as follows:

res://*/virtual_root.path-to-file.file_name.csdl|res://*/virtual_root.path-to-file.file_name.ssdl|res://*/virtual_root.path-to-file.file_name.msl

For example, if you have a model in the App_Code folder (App_Code Model.edmx) in WebSite1, the connection string should resemble the following:

res://*/WebSite1.App_Code.Model.csdl| res://*/WebSite1.App_Code.Model.ssdl| res://*/WebSite1.App_Code.Model.msl

Visual Studio 2008 Express Editions SP1 Beta may not upgrade SQL Server to the February 2008 Community Technology Preview (CTP) release of SQL Server 2008

After you install Visual Studio 2008 Express SP1 Beta on a computer that has an earlier service pack level of SQL Server 2008 installed, SQL Server 2008 is not upgraded to the February 2008 CTP release (CTP6). SQL Server 2008 CTP6 supports upgrades only from the following earlier versions:

â€¢	SQL Server 2005 SP2 or a later service pack
â€¢	SQL Server 2000 SP4 or a later service pack

To work around this issue, follow these steps:

1.	Uninstall earlier versions of SQL Server.
2.	Run Visual Studio 2008 Express Editions SP1 Beta Setup in maintenance mode.
3.	Click to select the Add Optional Components option, and then select SQL Server 2008 Express Edition.
4.	Click Next to continue the setup.

References to SQL Server 2008 and to SQL Server 2005 appear on the computer after you install Visual Studio 2008 Express Editions SP1 Beta

After you install Visual Studio 2008 Express Editions SP1 Beta on a computer that has SQL Server 2005 Express Edition installed, references to the 2008 and 2005 versions of SQL Server appear on the Start menu and in the Add or Remove Programs item in Control Panel.In this case, SQL Server 2005 Express Edition has been upgraded to SQL Server 2008 Express Edition. Any additional references that represent SQL Server 2005 Express Edition support files do not affect Visual Studio 2008 or SQL Server 2008.

To work around this issue, use the Add or Remove Programs item in Control Panel to remove SQL Server 2005 Express Edition.

Visual Studio 2008 Express Editions SP1 Beta requires Windows Server 2003 SP2

Visual Studio 2008 Express Editions SP1 Beta Setup installs SQL Server 2008 Express Edition. SQL Server 2008 Express Edition does not support Windows Server 2003 SP1.

Visual Studio 2008 Express Editions SP1 Beta Setup does not run when a non-Express edition of Visual Studio 2008 is installed on the computer

Visual Studio 2008 Express Editions SP1 Beta Setup reports a Visual Studio servicing issue that does not let you continue. Visual Studio 2008 Express Editions SP1 Beta is not supported when it is installed on a computer that has a non-Express edition of Visual Studio 2008 installed.

To work around this issue, uninstall any non-Express edition of Visual Studio 2008 before you install Visual Studio 2008 Express Editions SP1 Beta.

Visual Studio 2008 Express Editions SP1 Beta upgrades SQL Server to SQL Server 2008 only on specific versions of Windows

SQL Server 2008 supports only the following versions of Windows:

â€¢	Windows Server 2008or a later version
â€¢	Windows Vista Service Pack 1 or a later version
â€¢	Windows XP Service Pack 2 or a later version
â€¢	Windows Server 2003 Service Pack 2 or a later version

For more information about the SQL Server 2008 CTP release, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=100093 (http://go.microsoft.com/fwlink/?LinkId=100093)

By default, ClickOnce deployment uses SQL Server Express 2005 as a prerequisite

By default, Visual Studio 2008 Express Editions SP1 Beta selects SQL Server Express 2005 as a prerequisite when you use ClickOnce to deploy applications that require SQL Server Express 2008.

To work around this issue, manually change the prerequisite in the application from SQL Server Express 2005 to SQL Server Express 2008. To do this, follow these steps:

1.	Start Visual Studio 2008.
2.	Open your application.
3.	In Solution Explorer, click a project node.
4.	On the Project menu, click a project name, and then click Properties.
5.	In Project Designer, click the Publish tab, and then click Prerequisite.
6.	Click to clear the SQL Server 2005 Express Edition check box, and then click to select the SQL Server 2008 Express Edition check box.

Back to the top

REFERENCES

For more information, see the Visual Studio 2008 Express Editions Readme file. To do this, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkID=111607 (http://go.microsoft.com/fwlink/?LinkID=111607)

For more information about Visual Studio 2008 SP1 Beta for Standard, Professional, and Team editions, click the following article number to view the article in the Microsoft Knowledge Base:

945140 (/Feedback.aspx?kbNumber=945140/) Visual Studio 2008 Service Pack 1 Beta release notes and a list of fixed issues

Back to the top

APPLIES TO

â€¢	Microsoft Visual Web Developer 2008 Express Edition
â€¢	Microsoft Visual Basic 2008 Express Edition
â€¢	Microsoft Visual C# 2008 Express Edition
â€¢	Microsoft Visual C++ 2008 Express Edition

Back to the top

kbexpertiseadvanced kbhowto kbinfo KB952283

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Access violation when class method is called via pointer-to-member-function for forward-declared class

admin — Mon, 09 Aug 2010 12:59:09 +0000

A method is called through pointer and respective class is only forward declared.
For example:

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:

•	Inheritance Keywords (http://msdn2.microsoft.com/en-us/library/ck561bfk.aspx)
•	#pragma pointers_to_members (http://msdn2.microsoft.com/en-us/library/83cch5a6.aspx)
•	Representation Method compiler options (/vmb or /vmg) (http://msdn2.microsoft.com/en-us/library/yad46a6z.aspx)

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

APPLIES TO

•	Microsoft Visual Studio 2005 Express Edition
•	Microsoft Visual Studio 2005 Professional Edition
•	Microsoft Visual Studio 2005 Service Pack 1
•	Microsoft Visual Studio 2005 Standard Edition
•	Microsoft Visual Studio 2005 Team Suite
•	Microsoft Visual Studio 2008 Academic Edition
•	Microsoft Visual Studio 2008 Professional Edition
•	Microsoft Visual Studio 2008 Standard Edition
•	Microsoft Visual Studio Team System 2008 Team Suite

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

Microsoft Knowledge Base Article

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

Related Articles or Pages

FIX: The Microsoft Software License Terms that are attached to the English version of the Visual C++ Redistributable Package in Visual Studio 2008 are incorrect

admin — Mon, 09 Aug 2010 00:33:09 +0000

FIX: The Microsoft Software License Terms that are attached to the English version of the Visual C++ Redistributable Package in Visual Studio 2008 are incorrect

View products that this article applies to.

Article ID	:	956414
Last Review	:	August 11, 2008
Revision	:	1.0

SYMPTOMS

The Microsoft Software License Terms that are attached to the English version of the Microsoft Visual C++ Redistributable Package (VCRedist_x86.exe, VCRedist_x64.exe, and VCRedist_ia64.exe) in Microsoft Visual Studio 2008 do not let you redistribute these files. The incorrect license terms specify that you may install and use only one copy of the software. However, the correct license terms specify that you may install and use any number of copies of the software.

Back to the top

CAUSE

This problem occurs when Visual Studio 2008 Service Pack (SP1) installs Visual C++ Redistributable Package files that have the incorrect license terms.

Back to the top

RESOLUTION

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

Back to the top

Method 1

Download Visual C++ Redistributable Package Service Pack (SP1), and then replace the Visual C++ Redistributable Package files on the disk.

Back to the top

Method 2

Use this hotfix to replace the Visual C++ Redistributable Package files on the disk.

Hotfix information

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB956414 (http://code.msdn.microsoft.com/KB956414)

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

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

x86-based version

File name	File version	File size	Date	Time	Platform
Atl90.dll	9.0.30729.1	161,784	29-Jul-08	00:05	x86
Mfc90.dll	9.0.30729.1	3,768,312	29-Jul-08	00:05	x86
Mfc90chs.dll	9.0.30729.1	38,912	29-Jul-08	00:05	x86
Mfc90cht.dll	9.0.30729.1	39,936	29-Jul-08	00:05	x86
Mfc90deu.dll	9.0.30729.1	66,560	29-Jul-08	00:05	x86
Mfc90enu.dll	9.0.30729.1	56,832	29-Jul-08	00:05	x86
Mfc90esn.dll	9.0.30729.1	65,024	29-Jul-08	00:05	x86
Mfc90esp.dll	9.0.30729.1	65,024	29-Jul-08	00:05	x86
Mfc90fra.dll	9.0.30729.1	66,048	29-Jul-08	00:05	x86
Mfc90ita.dll	9.0.30729.1	64,512	29-Jul-08	00:05	x86
Mfc90jpn.dll	9.0.30729.1	46,592	29-Jul-08	00:05	x86
Mfc90kor.dll	9.0.30729.1	46,080	29-Jul-08	00:05	x86
Mfc90rus.dll	9.0.30729.1	62,976	29-Jul-08	00:05	x86
Mfc90u.dll	9.0.30729.1	3,783,672	29-Jul-08	00:05	x86
Mfcm90.dll	9.0.30729.1	59,904	28-Jul-08	22:07	x86
Mfcm90u.dll	9.0.30729.1	59,904	28-Jul-08	22:07	x86
Msvcm90.dll	9.0.30729.1	225,280	28-Jul-08	19:54	x86
Msvcp90.dll	9.0.30729.1	572,928	29-Jul-08	00:05	x86
Msvcr90.dll	9.0.30729.1	655,872	29-Jul-08	00:05	x86
Vcomp90.dll	9.0.21022.8	54,272	6-Nov-07	18:19	x86

x64-based version

File name	File version	File size	Date	Time	Platform
Atl90.dll	9.0.30729.1	179,704	28-Jul-08	21:23	x64
Mfc90.dll	9.0.30729.1	5,086,712	28-Jul-08	21:23	x64
Mfc90chs.dll	9.0.30729.1	38,912	28-Jul-08	21:23	x64
Mfc90cht.dll	9.0.30729.1	39,936	28-Jul-08	21:23	x64
Mfc90deu.dll	9.0.30729.1	66,560	28-Jul-08	21:23	x64
Mfc90enu.dll	9.0.30729.1	56,832	28-Jul-08	21:23	x64
Mfc90esn.dll	9.0.30729.1	65,024	28-Jul-08	21:23	x64
Mfc90esp.dll	9.0.30729.1	65,024	28-Jul-08	21:23	x64
Mfc90fra.dll	9.0.30729.1	66,048	28-Jul-08	21:23	x64
Mfc90ita.dll	9.0.30729.1	64,512	28-Jul-08	21:23	x64
Mfc90jpn.dll	9.0.30729.1	46,592	28-Jul-08	21:23	x64
Mfc90kor.dll	9.0.30729.1	46,080	28-Jul-08	21:23	x64
Mfc90rus.dll	9.0.30729.1	62,976	28-Jul-08	21:23	x64
Mfc90u.dll	9.0.30729.1	5,105,656	28-Jul-08	21:23	x64
Mfcm90.dll	9.0.30729.1	67,072	28-Jul-08	20:59	x64
Mfcm90u.dll	9.0.30729.1	67,072	28-Jul-08	20:59	x64
Msdia90.dll	9.0.30729.1	853,504	29-Jul-08	04:49	x64
Msvcm90.dll	9.0.30729.1	245,760	28-Jul-08	19:51	x64
Msvcp90.dll	9.0.30729.1	856,576	28-Jul-08	21:23	x64
Msvcr90.dll	9.0.30729.1	626,688	28-Jul-08	21:23	x64
Vcomp90.dll	9.0.21022.8	59,904	6-Nov-07	15:02	x64

IA-64-based version

File name	File version	File size	Date	Time	Platform
Atl90.dll	9.0.30729.1	418,808	28-Jul-08	21:37	IA-64
Mfc90.dll	9.0.21022.8	3,624,440	6-Nov-07	14:53	IA-64
Mfc90chs.dll	9.0.21022.8	41,472	6-Nov-07	14:53	IA-64
Mfc90cht.dll	9.0.21022.8	41,984	6-Nov-07	14:53	IA-64
Mfc90deu.dll	9.0.21022.8	60,928	6-Nov-07	14:53	IA-64
Mfc90enu.dll	9.0.21022.8	54,272	6-Nov-07	14:53	IA-64
Mfc90esn.dll	9.0.21022.8	59,392	6-Nov-07	14:53	IA-64
Mfc90esp.dll	9.0.21022.8	59,392	6-Nov-07	14:53	IA-64
Mfc90fra.dll	9.0.21022.8	60,416	6-Nov-07	14:53	IA-64
Mfc90ita.dll	9.0.21022.8	59,392	6-Nov-07	14:53	IA-64
Mfc90jpn.dll	9.0.21022.8	47,104	6-Nov-07	14:53	IA-64
Mfc90kor.dll	9.0.21022.8	46,592	6-Nov-07	14:53	IA-64
Mfc90u.dll	9.0.21022.8	3,631,096	6-Nov-07	14:53	IA-64
Mfcm90.dll	9.0.21022.8	93,184	6-Nov-07	14:16	IA-64
Mfcm90u.dll	9.0.21022.8	93,184	6-Nov-07	14:16	IA-64
Msdia90.dll	9.0.30729.1	2,139,648	29-Jul-08	04:37	IA-64
Msvcm90.dll	9.0.30729.1	324,096	28-Jul-08	20:09	IA-64
Msvcp90.dll	9.0.30729.1	1,469,440	28-Jul-08	21:37	IA-64
Msvcr90.dll	9.0.30729.1	1,506,816	28-Jul-08	21:37	IA-64
Vcomp90.dll	9.0.21022.8	144,896	6-Nov-07	14:53	IA-64

Back to the top

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Team Suite
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Team Foundation Server
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Test Load Agent
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Database Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Architecture Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Development Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Test Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Standard Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Professional Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Academic Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Tools for Applications Software Development Kit

Back to the top

kbexpertiseadvanced kbqfe KB956414

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

FIX: Live semantic analysis incorrectly reports error messages on a computer that has Visual Studio 2008 SP1 installed

admin — Fri, 06 Aug 2010 11:56:26 +0000

Article ID: 957259 – Last Review: November 21, 2008 – Revision: 1.0

FIX: Live semantic analysis incorrectly reports error messages on a computer that has Visual Studio 2008 SP1 installed

View products that this article applies to.

SYMPTOMS

On a computer that has Micrososft Visual Studio 2008 Service Pack 1 (SP1) installed, live semantic analysis incorrectly reports error messages when you perform one of the following actions:

You open a solution that contains breakpoints in the .aspx.cs files.

Note If you double-click any error message or open the corresponding .aspx files, the error message disappears.
You run a project that uses a constant that requires a conversion. When this occurs, the error message resembles the following:

The operation overflows at compile time in checked mode

This problem may occur if your code contains the following code:
class Program {static void Main(string[] args){ ulong x = ulong.MaxValue - 2;}}
You reference certain constructs that are defined in metadata. This issue occurs if the metadata is produced by a compiler other than the C# compiler.

Back to the top

RESOLUTION

Hotfix information

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB957259 (http://code.msdn.microsoft.com/KB957259)

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

Note This hotfix can be applied to both x86 versions and x64 versions of Visual Studio 2008.

Prerequisites

You must have Visual Studio 2008 SP1 installed to apply this hotfix.

Restart requirement

You have to restart the computer, if Visual Studio is being used when you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

Collapse this tableExpand this table

File name	File version	File size	Date	Time
Cslangsvc.dll	9.0.30729.162	5,306,696	21-Oct-2008	14:44

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

Microsoft Visual Studio Team System 2008 Team Suite
Microsoft Visual Studio 2008 Professional Edition
Microsoft Visual Studio 2008 Standard Edition
Microsoft Visual C# 2008 Express Edition

Back to the top

kbexpertiseadvanced kbfix kbqfe kbhotfixserver KB957259

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Detection and deployment guidance for the March 11, 2008 security release

admin — Wed, 04 Aug 2010 00:28:57 +0000

Detection and deployment guidance for the March 11, 2008 security release

View products that this article applies to.

Article ID	:	950137
Last Review	:	March 11, 2008
Revision	:	1.3

INTRODUCTION

As part of an ongoing commitment to provide detection tools and deployment recommendations for security updates, Microsoft is delivering this detection and deployment guidance for all updates that are released during a Microsoft Security Response Center (MSRC) release cycle.

This guidance contains recommendations that are based on the types of scenarios that may exist in various Microsoft operating system environments. This guidance includes how to use tools such as the following tools:

â€¢	Windows Update
â€¢	Microsoft Update
â€¢	Office Update
â€¢	The Microsoft Baseline Security Analyzer (MBSA)
â€¢	Windows Server Update Services (WSUS)
â€¢	Microsoft System Center Configuration Manager
â€¢	Microsoft Systems Management Server (SMS)
â€¢	The Extended Security Update Inventory Tool

This article describes the detection and deployment guidance for the security release that is dated March 11, 2008.

Back to the top

MORE INFORMATION

Detection and deployment

Environments that detect and deploy security updates by using Windows Update, Microsoft Update, Office Update, and Mactopia

Security updates that were released on March 11, 2008 are available through the following Web sites. Any exceptions are described in each Web site section. The products that are supported by each Web site are also listed.

Note Not every update is available on every Web site that is listed here.

Windows Update

http://update.microsoft.com/windowsupdate (http://update.microsoft.com/windowsupdate)

The products that are supported by this Web site are as follows:

â€¢	Microsoft Windows 2000
â€¢	Windows XP
â€¢	Windows Server 2003
â€¢	Windows Vista
â€¢	Windows Server 2008

Microsoft Update

http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate)

The products that are supported by this Web site are as follows:

â€¢	Microsoft Internet Security and Acceleration Server 2004
â€¢	Microsoft Internet Security and Acceleration Server 2006
â€¢	Microsoft Exchange 2000 Server
â€¢	Microsoft Exchange Server 2003
â€¢	Microsoft Exchange Server 2007
â€¢	Microsoft Office 2002
â€¢	Microsoft Office 2003
â€¢	The 2007 Microsoft Office system
â€¢	Windows 2000
â€¢	Windows XP
â€¢	Windows Server 2003
â€¢	Windows Vista
â€¢	Windows Server 2008
â€¢	Microsoft SQL Server 2005
â€¢	Microsoft Forefront Client Security
â€¢	Microsoft Visual Studio 2005

General exceptions

â€¢	Microsoft Update does not support Office 2000 components.
â€¢	Microsoft Update does not support any Apple Macintosh products.

Specific exceptionsMicrosoft Update does not support the part of security update 933103 that involves the following products:

â€¢	Microsoft Visual Studio 2002
â€¢	Microsoft Visual Studio 2003
â€¢	Microsoft BizTalk Server 2000
â€¢	Microsoft BizTalk Server 2002
â€¢	Microsoft Commerce Server 2000
â€¢	Microsoft Internet Security and Acceleration (ISA) Server 2000

For more information about security update 933103, click the following article number to view the article in the Microsoft Knowledge Base:

933103 (/Feedback.aspx?kbNumber=933103/) MS08-017: Vulnerabilities in Microsoft Office Web Components could allow remote code execution

Office Update

http://office.microsoft.com (http://office.microsoft.com)

The products that are supported by this Web site are as follows:

â€¢	Office 2000
â€¢	Office 2002
â€¢	Office 2003
â€¢	The 2007 Office system

General Exceptions

â€¢	Office Update does not support 2007 Office components when they are installed on computers that are running Windows Vista or Windows Server 2008. You must use Microsoft Update instead.
â€¢	Office Update does not support any Macintosh products.

Mactopia

http://www.microsoft.com/mac/ (http://www.microsoft.com/mac/)

The products that are supported by this Web site are as follows:

â€¢	Microsoft Office 2001 for Mac
â€¢	Microsoft Office 2004 for Mac
â€¢	Microsoft Office X for Mac
â€¢	Microsoft Office 2008 for Mac

Environments that detect security updates by using Microsoft Baseline Security Analyzer (MBSA) version 2.0.1

You can detect security updates that were released on March 11, 2008 if you use MBSA version 2.0.1.

General Exceptions

â€¢	MBSA version 2.0.1 does not support any Office 2000 components.
â€¢	MBSA version 2.0.1 does not support any Macintosh products.
â€¢	MBSA version 2.0.1 is not supported on Windows Vista. However, MBSA version 2.0.1 supports remote scans of computers that are running Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 931943 (/Feedback.aspx?kbNumber=931943/)Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista
â€¢	MBSA version 1.2.1 is no longer supported. It will not detect security updates that were released after October 2007.

Specific exceptionsMBSA version 2.0.1 does not support the part of security update 933103 that involves the following products:

â€¢	Visual Studio 2002
â€¢	Visual Studio 2003
â€¢	BizTalk Server 2000
â€¢	BizTalk Server 2002
â€¢	Commerce Server 2000
â€¢	ISA Server 2000

For more information about security update 933103, click the following article number to view the article in the Microsoft Knowledge Base:

933103 (/Feedback.aspx?kbNumber=933103/) MS08-017: Vulnerabilities in Microsoft Office Web Components could allow remote code execution

Environments that detect and deploy security updates by using Windows Server Update Services (WSUS)

You can detect and deploy security updates that were released on March 11, 2008 if you use any of the following items:

â€¢	WSUS 2.0 Service Pack 1 (SP1)
â€¢	WSUS 3.0
â€¢	WSUS 3.0 Service Pack 1 (SP1)

General Exceptions

â€¢	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Office 2000 components.
â€¢	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Macintosh products.
â€¢	SUS 1.0 Service Pack 1 (SP1) is no longer supported. It will not receive security updates.

Specific exceptionsWSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

â€¢	Visual Studio 2002
â€¢	Visual Studio 2003
â€¢	BizTalk Server 2000
â€¢	BizTalk Server 2002
â€¢	Commerce Server 2000
â€¢	ISA Server 2000

For more information about security update 933103, click the following article number to view the article in the Microsoft Knowledge Base:

933103 (/Feedback.aspx?kbNumber=933103/) MS08-017: Vulnerabilities in Microsoft Office Web Components could allow remote code execution

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or System Center Configuration Manager 2007

You can detect and deploy all security updates that were released on March 11, 2008 if you use any of the following items:

â€¢	Systems Management Server (SMS) 2.0 together with the SUS Feature Pack
â€¢	Systems Management Server (SMS) 2003 together with the SUS Feature Pack
â€¢	Systems Management Server (SMS) 2003 together with Inventory Tool for Microsoft Updates (ITMU)
â€¢	System Center Configuration Manager 2007

General Exceptions

â€¢

SMS ITMU and System Center Configuration Manager do not support any Office 2000 components.

â€¢

SMS together with the SUS Feature Pack does not support the following products:

â€¢	The 2007 Office system
â€¢	Windows Internet Explorer 7
â€¢	Windows Vista
â€¢	Windows Server 2008
â€¢	Any x64-based versions of Windows
â€¢	Any Itanium-based versions of Windows

â€¢

The SMS SUS Feature Pack, SMS ITMU, and System Center Configuration Manager do not support any Macintosh products.

Specific exceptionsWSUS 2.0, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

â€¢	Visual Studio 2002
â€¢	Visual Studio 2003
â€¢	BizTalk Server 2000
â€¢	BizTalk Server 2002
â€¢	Commerce Server 2000
â€¢	ISA Server 2000

For more information about security update 933103, click the following article number to view the article in the Microsoft Knowledge Base:

933103 (/Feedback.aspx?kbNumber=933103/) MS08-017: Vulnerabilities in Microsoft Office Web Components could allow remote code execution

Note The SMS SUS Feature Pack requires the Extended Security Update Inventory Tool to detect all the security updates.

To obtain the Extended Security Update Inventory Tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=2C93DA1D-48A0-4E5C-991F-87E08954F61B&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=2C93DA1D-48A0-4E5C-991F-87E08954F61B&displaylang=en)

Summary of detection and deployment guidance

The following table summarizes the detection and deployment guidance for each new security update.

Note To simplify this table, items that were listed under the General Exceptions heading for each detection and deployment technology are not included.

For example, the Microsoft Update column in this table may include a Yes. However, the security bulletin lists an Office 2000 component as affected. Previously, we would have stated in the table that Microsoft Update partially supported deployment of the security update. However, no Office 2000 components are supported by Microsoft Update. Therefore, we no longer account for that product in the table because it is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.0.1	WSUS 2.0 and WSUS 3.0	SMS SUS Feature Pack	SMS Inventory Tool for Microsoft Updates	System Center Configuration Manager 2007
			Detect and deploy	Detect and deploy	Detect and deploy	Detect only	Detect and deploy	Detect and deploy	Detect and deploy	Detect and deploy
949029	MS08-014	Microsoft Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949031	MS08-015	Microsoft Outlook	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949030	MS08-016	Office	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
933103	MS08-017	Microsoft Office Web Components	Partially. See Office Update section.	Not applicable	Partially. See Microsoft Update section.	Partially. See MBSA section.	Partially. See WSUS section.	Yes	Partially. See SMS section.	Partially. See System Center Configuration Manager section.

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

What is Microsoft doing to provide guidance about how to deploy these updates?

We encourage system administrators to join the monthly technical Webcast to learn more about security updates. The Webcast for this security update airs on Thursday, March 13, 2008 12:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032373597 (http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032373597)

What other information should I know about MBSA?

For more information about the programs that MBSA currently does not detect, click the following article number to view the article in the Microsoft Knowledge Base:

895660 (/Feedback.aspx?kbNumber=895660/)Microsoft Baseline Security Analyzer (MBSA) 2.0 is available

If you installed a program that is listed in the Affected software section of a security bulletin, you may have to manually determine whether you must install the required security update. For more information about MBSA, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=21134 (http://go.microsoft.com/fwlink/?LinkId=21134)

Can I use SMS or System Center Configuration Manager to determine whether the updates are required?

Yes. SMS helps detect and deploy these security updates. SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with SUSFP use MBSA version 1.2.1 technology for detection. Therefore, SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack have limitations that resemble the limitations of MBSA version 1.2.1.

For more information about SMS, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=21158 (http://go.microsoft.com/fwlink/?LinkId=21158)

The SUS Feature Pack together with the Extended Security Update Inventory Tool is required to detect all the security updates on Microsoft Windows and on other affected Microsoft products.

For more informationabout the limitations of the SUS Feature Pack, click the following article number to view the article in the Microsoft Knowledge Base:

306460 (/Feedback.aspx?kbNumber=306460/) Microsoft Baseline Security Analyzer (MBSA) returns note messages for some updates

SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack also use the Microsoft Office Inventory Tool to detect the required security updates for Microsoft Office programs such as Microsoft Word.

SMS 2003 customers can also use ITMU to detect and to deploy security updates. ITMU uses technology from Microsoft Updates. For more information about ITMU, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/sms/bb676783.aspx (http://technet.microsoft.com/en-us/sms/bb676783.aspx)

System Center Configuration Manager 2007 uses WSUS 3.0 for detection and deployment of these security updates. Therefore, anything that is supported by WSUS 3.0 is also supported by System Center Configuration Manager 2007.

Back to the top

APPLIES TO

â€¢

Windows Vista Business

â€¢

Windows Vista Enterprise

â€¢

Windows Vista Home Basic

â€¢

Windows Vista Home Premium

â€¢

Windows Vista Ultimate

â€¢

Windows Vista Business 64-bit Edition

â€¢

Microsoft Windows Server 2003 Service Pack 2, when used with:

Â	Â	Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Web Edition
Â	Â	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Datacenter x64 Edition
Â	Â	Microsoft Windows Server 2003, Enterprise x64 Edition
Â	Â	Microsoft Windows Server 2003, Standard x64 Edition
Â	Â	Microsoft Windows XP Professional x64 Edition
Â	Â	Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Â	Â	Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

â€¢

Microsoft Windows Server 2003 Service Pack 1, when used with:

Â	Â	Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Web Edition
Â	Â	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Â	Â	Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Â	Â	Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

â€¢

Microsoft Windows XP Service Pack 2, when used with:

Â	Â	Microsoft Windows XP Professional
Â	Â	Microsoft Windows XP Home Edition

â€¢

Microsoft Windows 2000 Service Pack 4, when used with:

Â	Â	Microsoft Windows 2000 Advanced Server
Â	Â	Microsoft Windows 2000 Datacenter Server
Â	Â	Microsoft Windows 2000 Professional Edition
Â	Â	Microsoft Windows 2000 Server

â€¢

Microsoft Windows Small Business Server 2003 Premium Edition

â€¢

Microsoft Windows Small Business Server 2003 Standard Edition

â€¢

Microsoft Small Business Server 2000 Standard Edition

â€¢

Windows Server 2008 Datacenter without Hyper-V

â€¢

Windows Server 2008 Enterprise without Hyper-V

â€¢

Windows Server 2008 for Itanium-Based Systems

â€¢

Windows Server 2008 Standard without Hyper-V

â€¢

Windows Server 2008 Datacenter

â€¢

Windows Server 2008 Enterprise

â€¢

Windows Server 2008 Standard

â€¢

Windows Web Server 2008

â€¢

Microsoft Office 2000 Standard Edition

â€¢

Microsoft Office XP Standard Edition

â€¢

Microsoft Office Standard Edition 2003

â€¢

Microsoft Office Professional 2007

â€¢

Microsoft Office Professional Plus 2007

â€¢

Microsoft Office Standard 2007

â€¢

Microsoft Office Ultimate 2007

â€¢

Microsoft Office 2004 for Mac Professional Edition

â€¢

Microsoft Office 2004 for Mac Standard Edition

â€¢

Microsoft Office 2004 for Mac Student and Teacher Edition

â€¢

Microsoft Office X for Mac Standard Edition

â€¢

Microsoft Office 2008 for Mac

â€¢

Microsoft Office 2008 for Mac Home and Student Edition

â€¢

Microsoft Office 2008 for Mac Special Media Edition

Back to the top

kbhowto kbsecurity kbsecbulletin kbinfo KB950137

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Sort function of STL Gives Unexpected Output when Vector is a Type Derived from _com_ptr_t

admin — Mon, 02 Aug 2010 11:56:23 +0000

Article ID: 967759 – Last Review: February 10, 2009 – Revision: 1.0

Sort function of STL Gives Unexpected Output when Vector is a Type Derived from _com_ptr_t

View products that this article applies to.

Expand all | Collapse all

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Action

C++ code which contains an STL vector containing types derived Ã‚Â fromÃ‚Â the_com_ptr_t Ã‚Â COM smart pointer class and using the std:sort() function to sort interface pointers may give unexpected sort output._com_ptr_t COM smart pointer derived types are commonly created when using the ‘#import’ keyword in C++ to import a COM type library. For example:Ã‚Â

#import msxml4.dll

Ã‚Â

Back to the top

Cause

Cause:

The _com_ptr_t class implementation overrides the reference (&) operator and returns a null interface pointer. This is in conflict with STL reference operator rules and may result in incorrect sorting order when std::sort () is called.Ã‚Â

Ã‚Â

Sample Code:

Ã‚Â

#include stdafx.h

#include

Ã‚Â

// Create smart pointer wrappers for msxml com object

#import msxml4.dll

Ã‚Â

// Helper Function to create XML

_bstr_t CreateXML()

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nums[] = {1,10,11,12,13,14,15,16,17,18,19,2,20,21,22,23,24,25,26,27,28,29,3,30,31,32,33,34,4,5,6,7,8,9};

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::stringstream tempstr;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for(int i=0; i<34 ;i++)

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << t << nums[i] << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return static_cast<_bstr_t>(tempstr.str().c_str());

}

Ã‚Â

// Compare Function for std::swap

bool myCompare(MSXML2::IXMLDOMNodePtr& node1, MSXML2::IXMLDOMNodePtr& node2)

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nNode1No(-1),nNode2No(-1);

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if( ( NULL == node1.GetInterfacePtr() ) || ( NULL == node2.GetInterfacePtr() ) )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return false;

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _stscanf_s( node1->text, _T(%d), &nNode1No );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _stscanf_s( node2->text, _T(%d), &nNode2No );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if( nNode1No < nNode2No )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return true;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return false;

};

Ã‚Â

int _tmain(int argc, _TCHAR* argv[])

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // A vector of IXMLDOMNode smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::vector vecNodesList;

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â CoInitialize( NULL );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Create and Load the XML document

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â MSXML2::IXMLDOMDocumentPtr docPtr;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr.CreateInstance(__uuidof(MSXML2::DOMDocument40));Ã‚Â Ã‚Â Ã‚Â Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr->loadXML(CreateXML());

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â MSXML2::IXMLDOMNodeListPtr nodes = docPtr->selectNodes( _T(NodesCol/Node/NodeNum) );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << Before Sorting Nodes << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Initialize the vector of smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for( int i = 0; i < nodes->length; i++ )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â {

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nNodeNo = -1;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â vecNodesList.push_back( nodes->item[i] );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << nodes->item[i]->text << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â }

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Sort the vector of smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::sort( vecNodesList.begin(), vecNodesList.end(), myCompare );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Display sorted results

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << nAfter Sorting Nodes n << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::vector::iterator iter;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for(iter = vecNodesList.begin(); iter!=vecNodesList.end();iter++)

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â {

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if(NULL != (*iter).GetInterfacePtr())

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << (*iter)->text << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â else

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << -1 << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â *iter = NULL; // Release smart pointer before destroying vector;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â }

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Release smart pointers before CoUninitialize

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â nodes = NULL;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr = NULL;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â CoUninitialize( );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return 0;

}

Ã‚Â

The sort() method uses the utility function std::swap():

Ã‚Â

template inlineÃ‚Â Ã‚Â Ã‚Â

void swap(_Ty& _Left, _Ty& _Right)Ã‚Â

{Ã‚Â

Ã‚Â // exchange values stored at _Left and _RightÃ‚Â Ã‚Â Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â if (&_Left != &_Right)Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â {Ã‚Â Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // different, worth swappingÃ‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _Ty _Tmp = _Left;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _Left = _Right;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _Right = _Tmp;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â }

}

Ã‚Â

The if (&_Left != &_Right) line of code calls the overloaded operator & from _com_ptr_t comip.h header file, which returns a NULL interface pointer:

Ã‚Â

Interface** operator&() throw()Ã‚Â Ã‚Â

{

_Release();

m_pInterface = NULL;

return &m_pInterface;Ã‚Â Ã‚Â

}

Back to the top

Resolution

This is a known issue.

All STL containers, including vector, forbid their elements from overloading operator&().Ã‚Â (This is C++ Specification 03 23.1/3 The type of objects stored in these components must meet the requirements of CopyConstructible types (20.1.3) and the additional requirements of Assignable types, and 20.1.3/1 requires &t to have type T * and denote the address of t.)

The best solution is to never overload operator&() when using STL containers. If that is not possible (e.g. because the operator overload is coming from code that you don’t control), an alternative is to wrap the class in another wrapper class that doesn’t overload operator&() which you can then add to the vector or other container class.Ã‚Â CAdapt is one example of such a class.Ã‚Â

Fixed Sample Code example using CAdapt

Ã‚Â

#include stdafx.h

#include

#include atlcomcli.h

Ã‚Â

// Create smart pointer wrappers for msxml com object

#import msxml4.dll

Ã‚Â

// Helper Function to create XML

_bstr_t CreateXML()

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nums[] = {1,10,11,12,13,14,15,16,17,18,19,2,20,21,22,23,24,25,26,27,28,29,3,30,31,32,33,34,4,5,6,7,8,9};

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::stringstream tempstr;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for(int i=0; i<34 ;i++)

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << t << nums[i] << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â tempstr << << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return static_cast<_bstr_t>(tempstr.str().c_str());

}

Ã‚Â

// Compare Function for std::swap

bool myCompare(MSXML2::IXMLDOMNodePtr& node1, MSXML2::IXMLDOMNodePtr& node2)

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nNode1No(-1),nNode2No(-1);

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if( ( NULL == node1.GetInterfacePtr() ) || ( NULL == node2.GetInterfacePtr() ) )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return false;

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _stscanf_s( node1->text, _T(%d), &nNode1No );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â _stscanf_s( node2->text, _T(%d), &nNode2No );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if( nNode1No < nNode2No )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return true;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return false;

};

Ã‚Â

int _tmain(int argc, _TCHAR* argv[])

{

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // A vector of IXMLDOMNode smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::vector> vecNodesList;

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â CoInitialize( NULL );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Create and Load the XML document

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â MSXML2::IXMLDOMDocumentPtr docPtr;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr.CreateInstance(__uuidof(MSXML2::DOMDocument40));Ã‚Â Ã‚Â Ã‚Â Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr->loadXML(CreateXML());

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â MSXML2::IXMLDOMNodeListPtr nodes = docPtr->selectNodes( _T(NodesCol/Node/NodeNum) );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << Before Sorting Nodes << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Initialize the vector of smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for( int i = 0; i < nodes->length; i++ )

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â {

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â int nNodeNo = -1;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â vecNodesList.push_back( nodes->item[i] );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << nodes->item[i]->text << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â }

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Sort the vector of smart pointers

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::sort( vecNodesList.begin(), vecNodesList.end(), myCompare );

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Display sorted results

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << nAfter Sorting Nodes n << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::vector>::iterator iter;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â for(iter = vecNodesList.begin(); iter!=vecNodesList.end();iter++)

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â {

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â if(NULL != (*iter).m_T.GetInterfacePtr())

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << (*iter).m_T->text << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â else

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â std::cout << -1 << std::endl;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â *iter = NULL; // Release smart pointer before destroying vector;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â }

Ã‚Â

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â // Release smart pointers before CoUninitialize

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â nodes = NULL;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â docPtr = NULL;

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â CoUninitialize( );

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â return 0;

}

Back to the top

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.

Back to the top

APPLIES TO

Microsoft Visual C++ 2008 Express Edition

Back to the top

kbnomt kbrapidpub KB967759

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Calling A .NET Managed Method from Native Code

admin — Sat, 31 Jul 2010 12:42:51 +0000

Calling A .NET Managed Method from Native Code

View products that this article applies to.

Article ID	:	953836
Last Review	:	May 31, 2008
Revision	:	1.0

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Action

This is a sample native console application which will query the registry to verify if a specific version of the .NET Framework is installed. It will then use the CorBindToRuntimeEx API to load a specific version of the Common Language Runtime (CLR). Finally, it uses the Interfaces and methods exposed in mscorlib.tlb to load an assembly and type and execute methods.

Create a new C++ Console application named CheckCLR and replace the code in CheckCLR.cpp with the following code:

/*
Â Â Â Â CheckCLR.cpp – A Native Code CLR Host Sample

Â Â Â CheckCLR is a native console application which queries the registry to
Â Â Â determine if a specific version of the .NET runtime is installed on the
Â Â Â machine. It then loads the specific CLR required.

Â Â Â It will then load a managed console app and execute the Main method.
Â Â Â It then loads a managed assembly and executes a method.
*/
#include stdafx.h
#include
#include
#include
#include
#include

// Import mscorlib typelib. Using 1.0 for maximum backwards compatibility
#import C: windows Microsoft.NET Framework v1.0.3705 mscorlib.tlb auto_rename
// Link with mscoree.dll import lib.
#pragma comment(lib,mscoree.lib)

using namespace mscorlib;

int _tmain(int argc, _TCHAR* argv[])
{
Â Â Â Â //
Â Â Â Â // Query ‘HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5 Install’ DWORD value
Â Â Â Â // See /Feedback.aspx?kbNumber=318785/ (/Feedback.aspx?kbNumber=318785/) for more information on .NET runtime versioning information
Â Â Â Â //
Â Â Â Â HKEY key = NULL;
Â Â Â Â DWORD lastError = 0;
Â Â Â Â lastError = RegOpenKeyEx(HKEY_LOCAL_MACHINE,TEXT(SOFTWARE Microsoft NET Framework Setup NDP v3.5),0,KEY_QUERY_VALUE,&key);
Â Â Â Â if(lastError!=ERROR_SUCCESS) {
Â Â Â Â Â Â Â Â _putts(TEXT(Error opening HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5));
Â Â Â Â Â Â Â Â return 1;
Â Â Â Â }

Â Â Â Â DWORD type;
Â Â Â Â BYTE data[4];
Â Â Â Â DWORD len = sizeof(data);
Â Â Â Â lastError = RegQueryValueEx(key,TEXT(Install),NULL,&type,data,&len);
Â
Â Â Â Â if(lastError!=ERROR_SUCCESS) {
Â Â Â Â Â Â Â Â RegCloseKey(key);
Â Â Â Â Â Â Â Â _putts(TEXT(Error querying HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5 Install));
Â Â Â Â Â Â Â Â return 2;
Â Â Â Â }

Â Â Â Â RegCloseKey(key);

Â Â Â Â // Was Install DWORD key value == 1 ??
Â Â Â Â if(data[0]==1)
Â Â Â Â Â Â Â Â _putts(TEXT(.NET Framework 3.5 is installed));
Â Â Â Â else {
Â Â Â Â Â Â Â Â _putts(TEXT(.NET Framework 3.5 is NOT installed));
Â Â Â Â Â Â Â Â return 3;
Â Â Â Â }

Â Â Â Â //Â
Â Â Â Â // Load the runtime the 3.5 Runtime (CLR version 2.0)
Â Â Â Â //
Â Â Â Â LPWSTR pszVer = Lv2.0.50727;Â // .NET Fx 3.5 needs CLR 2.0
Â Â Â Â LPWSTR pszFlavor = Lwks;
Â Â Â Â ICorRuntimeHost *pHost = NULL;

Â Â Â Â HRESULT hr = CorBindToRuntimeEx( pszVer,Â Â Â Â Â Â Â
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â pszFlavor,Â Â Â Â
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â STARTUP_LOADER_OPTIMIZATION_SINGLE_DOMAIN | STARTUP_CONCURRENT_GC,Â
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â CLSID_CorRuntimeHost,Â
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â IID_ICorRuntimeHost,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (void **)&pHost);

Â Â Â if (!SUCCEEDED(hr)) {
Â Â Â Â Â Â Â _tprintf(TEXT(CorBindToRuntimeEx failed 0x%x n),hr);
Â Â Â Â Â Â Â return 1;
Â Â Â }
Â
Â Â Â Â _putts(TEXT(Loaded version 2.0.50727 of the CLR n));
Â
Â Â Â Â pHost->Start(); // Start the CLR

Â Â Â Â //
Â Â Â Â // Get a pointer to the default domain in the CLR
Â Â Â Â //
Â Â Â Â _AppDomainPtr pDefaultDomain = NULL;
Â Â Â Â IUnknownPtrÂ Â pAppDomainPunk = NULL;

Â Â Â Â hr = pHost->GetDefaultDomain(&pAppDomainPunk);
Â Â Â Â assert(pAppDomainPunk);Â
Â
Â Â Â Â hr = pAppDomainPunk->QueryInterface(__uuidof(_AppDomain),(void**) &pDefaultDomain);
Â Â Â Â assert(pDefaultDomain);

Â Â Â Â //
Â Â Â Â // Load an Exe Assembly and call Main()
Â Â Â Â //
Â Â Â Â _bstr_t bstrExeName = LConsoleApplication1.exe;
Â Â Â Â try {
Â Â Â Â Â Â Â Â hr = pDefaultDomain->ExecuteAssembly_2(bstrExeName);
Â Â Â Â }
Â Â Â Â catch(_com_error& error) {
Â Â Â Â Â Â Â Â _tprintf(TEXT(ERROR: %s n),(_TCHAR*)error.Description());
Â Â Â Â Â Â Â Â goto exit;
Â Â Â Â }

Â Â Â Â /*
Â Â Â Â Â Â Â Â Load a type from a DLL Assembly and call it

Â Â Â Â Â Â Â Doing the same thing from native code as this C# code:

Â Â Â Â Â Â Â Â Â Â Â Â System.Runtime.Remoting.ObjectHandle objptr;
Â Â Â Â Â Â Â Â Â Â Â objptr = AppDomain.CurrentDomain.CreateInstanceFrom(ClassLibrary1.dll,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ClassLibrary1.Class1);
Â Â Â Â Â Â Â Â Â Â Â object obj = objptr.Unwrap();
Â Â Â Â Â Â Â Â Â Â Â Type t = obj.GetType();
Â Â Â Â Â Â Â Â Â Â Â t.InvokeMember(Test,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â BindingFlags.InvokeMethod,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â null,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â obj,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â new object[0]);
Â Â Â Â */
Â Â Â Â try {
Â Â Â Â Â Â Â Â _ObjectHandlePtr pObjectHandle;Â
Â Â Â Â Â Â Â Â _ObjectPtr pObject;Â
Â Â Â Â Â Â Â Â _TypePtr pType;
Â Â Â Â Â Â Â Â SAFEARRAY* psa;

Â Â Â Â Â Â Â Â // Create an instance of a type from an assembly
Â Â Â Â Â Â Â Â pObjectHandle = pDefaultDomain->CreateInstanceFrom(LClassLibrary1.dll,Â Â Â Â // no path — local directory
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â LClassLibrary1.Class1);
Â Â
Â Â Â Â Â Â Â Â variant_t vtobj = pObjectHandle->Unwrap();Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â // Get an _Object (as variant) from the _ObjectHandle
Â Â Â Â Â Â Â Â vtobj.pdispVal->QueryInterface(__uuidof(_Object),(void**)&pObject);Â Â // QI the variant for the Object iface
Â Â Â Â Â Â Â Â pType = pObject->GetType();Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â // Get the _Type iface
Â Â Â Â Â Â Â Â psa = SafeArrayCreateVector(VT_VARIANT,0,0);Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â // Create a safearray (0 length)
Â Â Â Â Â Â Â Â pType->InvokeMember_3(Test,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â // Invoke Test method on pType
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â BindingFlags_InvokeMethod,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â NULL,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â vtobj,
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â psa );
Â Â Â Â Â Â Â Â SafeArrayDestroy(psa);Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â // Destroy safearray
Â Â Â Â }
Â Â Â Â catch(_com_error& error) {
Â Â Â Â Â Â Â Â _tprintf(TEXT(ERROR: %s n),(_TCHAR*)error.Description());
Â Â Â Â Â Â Â Â goto exit;
Â Â Â Â }

exit:
Â Â Â Â pHost->Stop();
Â Â Â Â pHost->Release();

Â Â Â Â return 0;
}

/*** End of file CheckCLR.cpp ***/

Create a C# Console Application namedÂ ConsoleApplication1. Add a Console.WriteLine call in the Main method andÂ output a simple string message. Build ConsoleApplication1. Copy the ConsoleApplication1.exe build target to the ouput directory where CheckCLR.exe is built. Alternatively, you can change the code above to have the full path name to where ConsoleApplication1.exe is built.

Create a C# Class Library named ClassLibrary1. In the Class1 class, add a public method named Test. In Test, add a Console.WriteLine call and output a simple string message. Build ClassLibrary1.dll. Copy the ClassLibrary1.dll build target to the outut directory where CheckCLR.exe is built. Alternatively, you can change the code above to have the full path name to where ClassLibrary1.dll is built.

After building CheckCLR, you should should be able to run CheckCLR.exe from a command prompt and see the output of the Console.WriteLine calls:

Â Â Â Â .NET Framework 3.5 is installed
Â Â Â Â Loaded version 2.0.50727 of the CLR

Â Â Â Â Hello World from ConsoleApplication1.Main
Â Â Â Â Hello World from ClassLibrary1.Class1

If running CheckCLR.exe under the debugger from your Visual C++ project, you may get could not load file or assembly error messages. In that case, copy ConsoleApplication1.exe and ClassLibrary1.dll to the folder containing the CheckCLR.sln solution file. The debugger uses that folder as the application default directory.

Back to the top

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.

Back to the top

APPLIES TO

â€¢	Microsoft Visual C++ 2008 Express Edition
â€¢	Microsoft Visual C++ 2005 Express Edition
â€¢	Microsoft Visual C# 2008 Express Edition
â€¢	Microsoft Visual C# 2005 Express Edition

Back to the top

kbnomt kbrapidpub KB953836

Back to the top

Microsoft Knowledge Base Article

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

Related Articles or Pages

Static, identifiers , missing ,from , ClassView ,Globals, folder , Visual ,C++

admin — Sun, 25 Jul 2010 12:27:41 +0000

The Globals folder in the ClassView of Developer’s Studio is used to display and provide quick access to global identifiers in the current project. Identifiers declared as static that have file scope are missing from the ClassView Globals folder.

Note In Microsoft Visual C++ .NET and in Microsoft Visual C++ 2005, the nonstatic identifiers do not appear either.

STATUS

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

MORE INFORMATION

Sample Code to Demonstrate Problem

   // Main.cpp

   #include

...

   static int nGlobalStaticInt;  // Will not show up in Globals Folder

   int        nGlobalInt;        // Will show up in Globals Folder

...

   void main(void)

Related Articles or Pages

Visual Studio 2008 IDE may crash while building a VC++ Project after modifying Linker properties

admin — Sun, 25 Jul 2010 00:33:10 +0000

Visual Studio 2008 IDE may crash while building a VC++ Project after modifying Linker properties

View products that this article applies to.

Article ID	:	956322
Last Review	:	July 29, 2008
Revision	:	1.0

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Action

You createÃ‚Â a VC++ project and, in the linker options of the Project Properties, you have accidentallyÃ‚Â included an extra period(‘.’) in the

Project Properties->Configuration Properties->Linker->Input->Additional Dependencies

For example this may be something like :

kernel32.lib
user32.lib
gdi32.lib
winspool.lib
comdlg32.lib
advapi32.lib.
shell32.lib
ole32.lib
oleaut32.lib
uuid.lib
odbc32.lib
odbccp32.lib

Back to the top

Result

Visual Studio IDE may crash with an Access Violation.Ã‚Â You may get a Microsoft Visual Studio 2008 has encountered a problem and needs to close. message.

In the Event Viewer, you may see the following Application error log:

Event Type:Ã‚Â Error
Event Source:Ã‚Â .NET Runtime 2.0 Error Reporting
Event Category:Ã‚Â None
Event ID:Ã‚Â 1000
Date:Ã‚Â Ã‚Â 7/29/2008
Time:Ã‚Â Ã‚Â 7:28:48 PM
User:Ã‚Â Ã‚Â N/A
Computer:Ã‚Â
Description:
Faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vcprojectengine.dll, version 9.0.21022.8, stamp 47318038, debug? 0, fault address 0×0008c7c1.

Back to the top

Cause

TheÃ‚Â VC project engine doesn’t properly handleÃ‚Â the extra period when determining project dependencies the first time after the list is modified. We are currently investigating the issue.

Back to the top

Resolution

Remove the extra period(‘.’) from

Project Properties->Configuration Properties->Linker->Input->Additional Dependencies.

Back to the top

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.

Back to the top

APPLIES TO

Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Professional Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio 2008 Standard Edition
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Team Suite

Back to the top

kbnomt kbrapidpub KB956322

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

The Visual Basic compiler (Vbc.exe) may use 100 percent of the CPU resources when you build a .NET Framework 3.5-based application that has many assemblies and references

admin — Sat, 24 Jul 2010 05:03:27 +0000

The Visual Basic compiler (Vbc.exe) may use 100 percent of the CPU resources when you build a .NET Framework 3.5-based application that has many assemblies and references

View products that this article applies to.

Article ID	:	953595
Last Review	:	July 1, 2008
Revision	:	1.0

SYMPTOMS

Consider the following scenario:

â€¢	You build a Microsoft .NET Framework 3.5-based application in debug mode. For example, in the Web.config file for a .NET Framework 3.5-based Web application, you set the debug option as follows: debug=true
â€¢	You use Microsoft Visual Basic 2008 as the programming language.
â€¢	The application depends on many assemblies and references.

In this scenario, the Visual Basic compiler (Vbc.exe) may use 100 percent of the CPU resources. Additionally, you may receive an error message that resembles the following:

Object ‘/32eba493_7a69_40af_bfe6_52887ab07396/jdkqqpvt_pufe5n+ogossdnv_258.rem’ has been disconnected or does not exist at the server.

Back to the top

CAUSE

This issue may occur because the CPU computes lots of debug data when you build the application in debug mode. How much debug data is computed depends on the size of the project and on the number of references. In some cases, the debug data is computed multiple times.

Back to the top

RESOLUTION

Hotfix information

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.
Note After you install this hotfix, the CPU computes the debug data only one time. This change minimizes the workload for the compiler and resolves the issue that is mentioned in the Symptoms section. To completely resolve the problem, we recommend that you also install the Visual Basic 2008 hotfix that is provided in the following Microsoft Knowledge Base article:

951708 (/Feedback.aspx?kbNumber=951708/) The Visual Basic compiler (VBC.exe) may use 100 percent of the CPU resources when you build a Visual Basic 2008 application that has a lot of assemblies and references

Prerequisites

To apply this hotfix, you must have the .NET Framework 3.5 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

File name	File version	File size	Date	Time	Platform
Vbc.exe	9.0.21022.113	1,710,584	03-Jun-2008	06:50	x86
Vbc.exe	9.0.21022.113	2,346,488	03-Jun-2008	07:02	x64
Vbc.exe	9.0.21022.113	4,620,280	03-Jun-2008	07:02	IA-64

Back to the top

WORKAROUND

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

Back to the top

Method 1

Build the application in release mode.

Back to the top

Method 2

If you are trying to build a Web application, set the debug option as follows in the Web.config file:

debug=false

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

â€¢	Microsoft .NET Framework 3.5
â€¢	Microsoft Visual Studio 2008 Professional Edition
â€¢	Microsoft Visual Studio 2008 Standard Edition
â€¢	Microsoft Visual Studio Team System 2008 Database Edition
â€¢	Microsoft Visual Studio Team System 2008 Architecture Edition
â€¢	Microsoft Visual Studio Team System 2008 Development Edition
â€¢	Microsoft Visual Studio Team System 2008 Test Edition
â€¢	Microsoft Visual Studio Team System 2008 Team Suite
â€¢	Microsoft Visual Basic 2008 Express Edition

Back to the top

kbexpertiseadvanced kbpubtypekc kbqfe kbhotfixserver KB953595

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

Stack Size Monitoring Tools

admin — Thu, 22 Jul 2010 15:55:49 +0000

Monitor stack size to prevent, predict or debug the StackOverflowException.

Result

The following tools can be used to view the current stack size for threads:
1) Visual studio debugger.
2) WinDBG
3) Process Explorer

Cause

The need to monitor and diagnose potential stack overflow problems during the software development and testing stage is due to the catastrophic nature of the stack overflow condition. This exception or state can rarely be handled intelligently and often cannot be handled at all. For these reasons, it can be desirable to detect or monitor thread stack size during application development and testing, or debugging, when the potential for too-little stack space exists, or stack overflow errors are detected.

Resolution

See the windbg help documentation under the heading, Debugging a Stack Overflow, for a detailed example of debugging thread stack size issues on a native debugger.

More Information

Debugging Tools for Windows
http://www.microsoft.com/whdc/devtools/debugging/default.mspx (http://www.microsoft.com/whdc/devtools/debugging/default.mspx)

Managed StackOverflowException Class:
http://msdn2.microsoft.com/en-us/library/system.stackoverflowexception.aspx (http://msdn2.microsoft.com/en-us/library/system.stackoverflowexception.aspx)

DISCLAIMER

APPLIES TO

•	Microsoft Visual Studio .NET 2002 Professional Edition
•	Microsoft Visual Studio .NET 2003 Professional Edition
•	Microsoft Visual Studio 2005 Standard Edition
•	Microsoft Visual Studio 6.0 Enterprise Edition
•	Microsoft Visual Studio 2008 Professional Edition
•	Microsoft Visual Studio 2005 Team Edition for Software Developers

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

Microsoft Knowledge Base Article

Related Articles or Pages

Description of the Word 2007 hotfix package: June 20, 2008

admin — Fri, 16 Jul 2010 03:19:18 +0000

Description of the Word 2007 hotfix package: June 20, 2008

View products that this article applies to.

Article ID	:	954576
Last Review	:	July 17, 2008
Revision	:	1.0

SUMMARY

This article describes the Microsoft Office Word 2007 issue that is fixed in the Word 2007 hotfix package that is dated June 20, 2008.

This article describes the following items about the hotfix package:

Ã¢â‚¬Â¢	The issues that the hotfix package fixes.
Ã¢â‚¬Â¢	The prerequisites for installing the hotfix package.
Ã¢â‚¬Â¢	Whether you must restart the computer after you install the hotfix package.
Ã¢â‚¬Â¢	Whether the hotfix package is replaced by any other hotfix package.
Ã¢â‚¬Â¢	Whether you must make any registry changes.
Ã¢â‚¬Â¢	The files that the hotfix package contains.

Back to the top

INTRODUCTION

Issues that the hotfix package fixes

List of issues that are fixed

This hotfix fixes the following issues:

Ã¢â‚¬Â¢	954540 (/Feedback.aspx?kbNumber=954540/) The changes in the TOC and PageRef fields do not appear when you compare Word 2007 documents
Ã¢â‚¬Â¢	954541 (/Feedback.aspx?kbNumber=954541/) The Ref field is updated incorrectly when you print a Word 2007 document

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

Ã¢â‚¬Â¢

When you compare and merge documents that are written in Chinese characters or in Japanese characters in Word 2007, the text that is marked as deleted and inserted is much larger than the text that is actually changed. For example, if you delete only one character or one word, a large chunk of text around this character or word is marked as deleted. Additionally, the chunk of text is marked as reinserted, except for the character or for the word that is actually deleted.

Note The issue occurs for both character-level comparison and word-level comparison. However, this issue does not occur if you delete the word or the character at the end of the sentence.

Ã¢â‚¬Â¢

Consider the following scenario. You create and then save a new document from a template on a trusted network share. This template contains Microsoft Visual Basic for Application (VBA) code. Then, you open the document again.

In this scenario, you cannot save the document again. Additionally, you receive the following error message:

The save failed due to out of memory or disk space.

Ã¢â‚¬Â¢

Consider the following scenario. You create and then save a document that contains a table. You delete one row, and you modify the content in the following row. Then, you save the document as a different name.

In this scenario, if you compare the revised document to the original document, the result is incorrect.

Ã¢â‚¬Â¢

Consider the following scenario. You create a Microsoft Office Word 2003 document, and you apply a new style such as Style1 to some paragraphs that have outline numbering enabled. Then, you change the number format of Style1. To change this number format, you add text before the number in that document.

In this scenario, when you use the Compare Documents functionality to compare the revised document to the original document, the comparison document shows the formatting as the formatting in the original document. However, the comparison document should show the formatting as the formatting in the revised document.

Ã¢â‚¬Â¢

You create a document that is based on a template that has customized Ribbons. When you open the document, Word 2007 may not display the Ribbon customizations. This issue can occur if the following conditions are true:

Ã¢â‚¬Â¢

The template uses the editing restriction, Filling in forms.

Note This issue does not occur if the template is unprotected or if the template uses one of the following editing restrictions:

Ã¢â‚¬Â¢	Comments
Ã¢â‚¬Â¢	No changes (Read only)
Ã¢â‚¬Â¢	Tracked changes

Ã¢â‚¬Â¢

The document is saved in one of the following file formats:

Ã¢â‚¬Â¢	Word 2003 XML Document (*.xml)
Ã¢â‚¬Â¢	Word XML Document (*.xml)
Ã¢â‚¬Â¢	Word Document (*.docx)
Ã¢â‚¬Â¢	Word Macro-Enabled Document (*.docm)

Note This issue does not occur if the document is saved in a rich text format (RTF) or in a binary document file format.

However, the template is still correctly loaded as a base template.

Ã¢â‚¬Â¢

When you add one or more letters at the beginning or at the end of a word, a word-level comparison only marks the inserted letters as an insertion, as if the inserted characters are a separate word. The expected behavior is that the original word should be marked as deleted, and the new word should be marked as an insertion.

Ã¢â‚¬Â¢

If you click to clear the White space check box in the Compare Documents dialog box, the closing paragraph mark of an insertion is ignored. The expected behavior is that the closing paragraph mark should be displayed as part of the insertion, and the closing paragraph mark should not be ignored.

Ã¢â‚¬Â¢

When you insert or delete a text box in the revised document, and then you compare this document to the original document, there is a revision bar next to the border of the text box. However, there is no revision markup in the text box.

Ã¢â‚¬Â¢

If two plain text content controls are grouped, you may experience the following issues when you run the Spelling and Grammar check:

Ã¢â‚¬Â¢

The last word in the first content control is selected together with part of the first word of the second content control. This behavior occurs when the following conditions are true:

Ã¢â‚¬Â¢	There is no space after the last word in the first content control.
Ã¢â‚¬Â¢	The last word of the first content control is proofed in the Spelling and Grammar dialog box.

This issue occurs whether the last word of the first content control is spelled correctly.

Ã¢â‚¬Â¢

After the last word of the first content control is proofed, the Spelling and Grammar check is complete. However, misspelled words are not checked in the second content control.

Back to the top

MORE INFORMATION

Hotfix information

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

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

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace any other hotfix packages.

Registry information

You do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The Global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb954576-fullfile-x86-glb.exe	12.0.6320.5000	15,929,040	19-Jun-2008	14:28	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,252,608	19-Jun-2008	18:33	Not Applicable
Wordconv.msp	Not Applicable	6,301,696	19-Jun-2008	18:33	Not Applicable

Word.msp file information

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	06-Dec-2007	17:05	Not Applicable
Winword.exe	12.0.6320.5000	349,720	19-Jun-2008	15:00	x86
Wwlib.dll	12.0.6320.5000	17,491,480	19-Jun-2008	15:00	x86

Wordconv.msp file information

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6320.5000	4,281,368	19-Jun-2008	22:42	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

Ã¢â‚¬Â¢

Microsoft Office Word 2007

Back to the top

kbautohotfix kbhotfixrollup kbexpertiseinter kbfix kbqfe kbhotfixserver KB954576

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

Hang When Reading StdErr/StdOut Properties of WshScriptExec Object

admin — Tue, 13 Jul 2010 11:56:30 +0000

Article ID: 960246 – Last Review: November 18, 2008 – Revision: 1.0

Hang When Reading StdErr/StdOut Properties of WshScriptExec Object

View products that this article applies to.

Expand all | Collapse all

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Symptoms

The Windows Script Host object model provides the WshShell.Exec method, which allows script to run an application in a child command-shell. The Exec method returns a WshScriptExec object, which exposes the StdOut andÃ‚Â StdErr properties. These properties provide access toÃ‚Â informationÃ‚Â the child process has written to its standard output or standard error streams.

Back to the top

When reading the StdErr or StdOut properties of the WshScriptExec object, the script may hang (deadlock).

Back to the top

Cause

A console application’s StdOut and StdErr streams share the same internal 4KB buffer. In addition,Ã‚Â the WshScriptExec object only providesÃ‚Â synchronous read operations on these streams. Synchronous read operationsÃ‚Â introduce a dependency between the calling scriptÃ‚Â reading from theseÃ‚Â streams and the child process writing to those streams, which can resultÃ‚Â in deadlock conditions.

When the caller reads from the redirected stream of a child process, it is dependent on the child. The caller waits on the read operation until the child writes to the stream or closes the stream. When the child process writes enough data to fill its redirected stream, it is dependent on the parent. The child process waits on the next write operation until the parent reads from the full stream or closes the stream. The deadlock condition results when the caller and child process wait on each other to complete an operation, and neither can proceed. Generally, this occurs if the spawned application is writing to both the StdOut and StdErr streams, whileÃ‚Â the calling script is architected so that it reads only from one of them.

Back to the top

Resolution

These are severalÃ‚Â possible workarounds.

1. Architect the script so that it reads from both StdOut and StdErr, which prevents the buffer from filling up.

2. Redirect the console program output to a disk file (or files), and then read the file(s). When spawning the console application, you can use the > operator to output the results of the operation to a file. You could then use the FileSystemObject to read the output files back in for processing.

FileSystemObject Object
http://msdn.microsoft.com/en-us/library/z9ty6h50(VS.85).aspx (http://msdn.microsoft.com/en-us/library/z9ty6h50(VS.85).aspx)

3. Instead of using the WScriptÃ‚Â object model for reading the StdOut/StdErr streams, write a COM component that implementsÃ‚Â asynchronous reads of these streams; and then call the COM component from your script. For example, theÃ‚Â System.Diagnostics.Process class in the Microsoft .NET Framework exposes anÃ‚Â asynchronous model for reading the StdOut/StdErr streams. Therefore;Ã‚Â it is possible to write aÃ‚Â COM callable component which utilizes the Microsoft .NET Framework whichÃ‚Â could raiseÃ‚Â event back to the script on read operations.

Process.StandardOutput Property
http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standardoutput.aspx (http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standardoutput.aspx)

Process.StandardError Property
http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standarderror.aspx (http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standarderror.aspx)

Ã‚Â

Back to the top

Advanced Steps

Steps to Reproduce Problem
=====================

1. Create a new text file with the following script.

‘This script will simulate the work done by a console application.
‘This just iterates 500 times, writing data to both the StdOut and StdErr streams.
Dim i
For i = 1 toÃ‚Â 500
Ã‚Â Ã‚Â WScript.StdOut.WriteLine StdOut: & i
Ã‚Â Ã‚Â WScript.StdErr.WriteLine StdErr: & i
Next

2. Save the file as scriptworker.vbs.
3. Create a new text file with the following script.

Dim WSHShell
Dim oExec

4. Save this file as scriptspawn.vbs, and place it in the same folder with scriptworker.vbs.
5. Start a new command prompt (cmd.exe).
6. Navigate to the folder where you copied scriptworker.vbs and scriptspawn.vbs.
7. Run the following command:

cscript.exe scriptspawn.vbs

Note that the script hangs after outputting just over 300 items, and you have to manually kill the process by pressing CTRL+C or CTRL+BREAK.

Steps to Work Around Problem
=======================

This example demonstrates how toÃ‚Â changeÃ‚Â the scriptÃ‚Â to read from both StdOut and StdErr, whichÃ‚Â prevents the buffer from filling up.

1. Follow the steps in the Steps to Reproduce Problem section above.
2. Use the following script for scriptspawn.vbs, rather than the script shown in the Steps to Reproduce Problem section.

Dim WSHShell
Dim oExec

Set WSHShell = CreateObject(WScript.Shell)
Set oExec = WSHShell.Exec(cscript scriptworker.vbs)
With oExec
Ã‚Â Ã‚Â Do While .Status = 0
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â WScript.Sleep 10
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Do While Not .StdOut.AtEndOfStream
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â WScript.Echo .StdOut.ReadLine
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â ‘Check the .StdErr to see if it is at the end of its
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â ’stream. If not, call ReadLine on it
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â If Not .StdErr.AtEndOfStream Then
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .StdErr.ReadLine
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â End If
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Loop
Ã‚Â Ã‚Â Loop
End With

Note that when running this script, it does not hang and successfully reads all data from the StdOut property.

Back to the top

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.

Back to the top

APPLIES TO

Microsoft Windows 2000
Microsoft Windows XP Professional
Windows Server 2008 Enterprise
Microsoft Windows Server 2003, Standard Edition (32-bit x86)

Back to the top

kbnomt kbrapidpub KB960246

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

A hotfix rollup is available for WPF Designer

admin — Fri, 09 Jul 2010 11:56:31 +0000

Article ID: 958017 – Last Review: November 11, 2008 – Revision: 2.0

A hotfix rollup is available for WPF Designer

View products that this article applies to.

MORE INFORMATION

This hotfix rollup fixes several issues in the WPF Designer. This hotfix rollup applies only to the computer that has Visual Studio 2008 Service Pack 1 installed.

When a resource in an external resource dictionary is updated, Visual Studio 2008 crashes.
WPF Designer cannot load read-only attached properties, such as the VisualStateManager.VisualStateGroups property.
If users or codes set a data binding locally, and then the users or codes clear the data binding, WPF designer reports the following error message:

‘System.Windows.Data.Binding’ is not a valid value for property
If a Win32 project is set as the startup project, WPF Designer cannot load solutions in Visual Studio 2008 or in Visual Studio 2008 Service Pack 1.
When you set and then delete the Source property of a WPF WebBrowser control, Visual Studio crashes.
When you move a control that uses the MultiTrigger class or the DataTrigger class in the Style class, WPF Designer may generate an InvalidCastException exception.

Back to the top

Hotfix information

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

If you already have the latest version of Silverlight Tools for Visual Studio 2008 SP1 installed, do not apply this hotfix rollup. All the fixes in this hotfix rollup are already included in Silverlight Tools for Visual Studio 2008 SP1.

Prerequisites

You must have Visual Studio 2008 Service Pack 1 installed to apply this hotfix. To download Visual Studio 2008 Service Pack 1, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=27673c47-b3b5-4c67-bd99-84e525b5ce61&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=27673c47-b3b5-4c67-bd99-84e525b5ce61&displaylang=en)

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Microsoft.visualstudio.xaml.dll	9.0.30729.166	1,355,776	20-Oct-2008	22:21	x86
Microsoft.windows.design.developer.dll	9.0.30729.166	991,232	20-Oct-2008	22:21	x86
Microsoft.windows.design.markup.dll	9.0.30729.166	782,336	20-Oct-2008	22:21	x86

Back to the top

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

APPLIES TO

Microsoft Visual Studio Team System 2008 Team Suite
Microsoft Visual Studio 2008 Standard Edition
Microsoft Visual Studio 2008 Professional Edition
Microsoft Visual Basic 2008 Express Edition
Microsoft Visual C# 2008 Express Edition

Back to the top

kbfix kbexpertiseadvanced kbqfe kbhotfixserver KB958017

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

How to locate a value or closest match in a Visual FoxPro table from VB .NET using the VFP OLE DB Provider

admin — Wed, 07 Jul 2010 00:33:10 +0000

How to locate a value or closest match in a Visual FoxPro table from VB .NET using the VFP OLE DB Provider

View products that this article applies to.

Article ID	:	956277
Last Review	:	July 28, 2008
Revision	:	1.0

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Action

You have a Microsoft Visual FoxPro (VFP) table you are accessing from Microsoft Visual Basic .NET via the VFP OLE DB Provider. You wish to locate a particular value in a column, or the nearest match.

Back to the top

Resolution

The VFP SET NEAR command controls what happens to the record pointer in a VFP table after an unsuccessful SEEK (or FIND) operation (SEEK uses an index on a VFP column to locate a value). When NEAR is on, the record pointer in the VFP table is positioned at the closest matching recordÃ‚Â after an unsuccessful SEEK.

The following VB .NET code demonstrates how to SEEK a record or the closest match thereto via the VFP OLE DB Provider.Ã‚Â To use this code…

1. Create a sample VFP table and index using the following VFP code:

Ã‚Â Ã‚Â Ã‚Â Ã‚Â CLOSE DATA ALLÃ‚Â
Ã‚Â Ã‚Â Ã‚Â Ã‚Â DELETE FILE C: CUSTS.DBF RECYCLE
Ã‚Â Ã‚Â Ã‚Â Ã‚Â DELETE FILE C: CUSTS.CDX RECYCLE
Ã‚Â Ã‚Â Ã‚Â Ã‚Â CREATE TABLE C: CUSTS (NAMES VarChar(30))
Ã‚Â Ã‚Â Ã‚Â Ã‚Â INDEX ON UPPER(NAMES) TAG NAMES
Ã‚Â Ã‚Â Ã‚Â Ã‚Â INSERT INTO CUSTS VALUES(‘FRED’)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â INSERT INTO CUSTS VALUES(‘JOHN’)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â INSERT INTO CUSTS VALUES(‘MARY’)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â CLOSE DATA ALL

2.Ã‚Â Create a new Visual Studio VB .NET Windows application. Drop a TextBox, a CheckBox and a Button on the form.
3. Double-click the form surface to open the code editor (form1.vb)Ã‚Â and then paste the code below into it, replacing the current contents.

The code does the following…

Ã‚Â - Sets near ON / OFF depending on the state of the CheckBox on the VB form (checked = ON).
Ã‚Â - OpensÃ‚Â the free VFP table (C: CUSTS) and SEEKs theÃ‚Â customer name.
Ã‚Â - In the VFP OLE DB Provider, creates a cursor to be returned to the .NET session.
Ã‚Â - Populates the return cursor with the values of FOUND(), RECNO(‘CUSTS’) and RECCOUNT(‘CUSTS’).
Ã‚Â - Uses the VFP SETRESULTSET() function to return the VFP cursor to .NET.
Ã‚Â - VB .NET uses a OleDbDataReader object to read the returned cursor and display the results of the SEEK in a MSGBOX.

**NOTES**

Ã‚Â - When the VFP SEEK finds an exact match, FOUND() (first column in the result set) is True. Other columns can be ignored.
Ã‚Â - When the VFP SEEK *does not* find an exact match and NEAR is ON, FOUND() (first column in the result set) is False and RECNO() (2nd column in result set) will either be a valid number or will be RECCOUNT() (3rd column in result set) +1 (indicating EOF in the VFP table).
Ã‚Â - When the VFP SEEK *does not* find an exact match and NEAR is OFF, FOUND() will be .F., RECNO() will be RECCOUNT() + 1.
Ã‚Â - Third column in result set is constant: RECCOUNT(‘CUSTS’). Use this to determine if you are on the nearest record when NEAR is on (i.e, column 2 is *not* column 3 +1).

Imports System.Data.OleDb
Imports System.Text

Public Class Form1

Ã‚Â Ã‚Â Ã‚Â Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â TextBox1.Focus()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â TextBox1.Text = JOHN
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â TextBox1.CharacterCasing = CharacterCasing.Upper
Ã‚Â Ã‚Â Ã‚Â End Sub

Ã‚Â Ã‚Â Ã‚Â Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â FindOperator(TextBox1.Text, CheckBox1.Checked)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â TextBox1.Focus()
Ã‚Â Ã‚Â Ã‚Â End Sub

Ã‚Â Ã‚Â Ã‚Â Function FindOperator(ByVal Name2Find As String, ByVal Near As Boolean) As VariantType
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Dim oConn As New OleDbConnection( _
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Provider=VFPOLEDB;Data Source=C: )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Dim oCmd As New OleDbCommand(, oConn)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Dim oStrBldr As New StringBuilder
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Dim oReader As OleDbDataReader
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Dim lcNear As String = IIf(Near, ON, OFF)

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â With oStrBldr
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append(EXECS()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([SET NEAR & lcNear & ] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([USE CUSTS ORDER NAMES SHARED AGAIN IN 0] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([SEEK ' & Name2Find & ' IN CUSTS] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([SELECT 0] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([CREATE CURSOR SeekResults(lFound L, nRecno I, nReccount I)] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([INSERT INTO SeekResults VALUES ( FOUND('CUSTS'), RECNO('CUSTS'), RECCOUNT('CUSTS') )]+ CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([USE IN SELECT('CUSTS')] + CHR(13) + )
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append([RETURN SETRESULTSET( 'SeekResults' )])
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â .Append())
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oCmd.CommandText = .ToString
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â End With

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oConn.Open()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oReader = oCmd.ExecuteReader()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â While oReader.Read
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â MsgBox(Found: & oReader.GetBoolean(0).ToString & vbCrLf & _
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â RECNO(): & oReader.GetInt32(1).ToString & vbCrLf & _
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â RECCOUNT(): & oReader.GetInt32(2).ToString)
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â End While

Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oConn.Close()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oConn.Dispose()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oCmd.Dispose()
Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â Ã‚Â oReader.Close()
Ã‚Â Ã‚Â Ã‚Â End Function

End Class

Back to the top

More Information

For more information about the VFP functions and commands used in this article (SEEK, SET NEAR, RECNO(), RECCOUNT(), SELECT(), SETRESULTSET(), etc.), please refer to the Visual FoxPro 9.0 SP2 online help here:
http://msdn.microsoft.com/en-us/library/724fd5h9(VS.80).aspx (http://msdn.microsoft.com/en-us/library/724fd5h9(VS.80).aspx)

You can also download the entire VFP9 SP2 help file here (.CHM):
http://www.microsoft.com/downloads/details.aspx?FamilyID=842ACEC8-F79C-41CD-AB1A-AE4F184387C2&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=842ACEC8-F79C-41CD-AB1A-AE4F184387C2&displaylang=en)

The VFP OLE DB Provider is available as a free download and is the preferred way to access VFP data from non-VFP applications. It is available here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en)

Back to the top

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.

Back to the top

APPLIES TO

Ã¢â‚¬Â¢	Microsoft Visual FoxPro 9.0 Service Pack 2
Ã¢â‚¬Â¢	Microsoft Visual Studio Team System 2008 Team Suite
Ã¢â‚¬Â¢	Microsoft Visual Basic 2008 Express Edition
Ã¢â‚¬Â¢	Microsoft Visual Basic 2005 Express Edition
Ã¢â‚¬Â¢	Microsoft Visual Basic 2005
Ã¢â‚¬Â¢	Microsoft Visual Basic .NET 2003 Standard Edition
Ã¢â‚¬Â¢	Microsoft Visual Basic .NET 2002 Standard Edition

Back to the top

kbnomt kbrapidpub KB956277

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual C#

admin — Sat, 03 Jul 2010 12:50:57 +0000

List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual C#

View products that this article applies to.

Article ID	:	950263
Last Review	:	April 29, 2008
Revision	:	1.1

Beta Information

This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

INTRODUCTION

This article describes the following aspects of Microsoft Visual Studio 2008 Service Pack 1 (SP1) Beta for Microsoft Visual C#:

â€¢	The known issues in this service pack and how to work around the known issues
â€¢	The issues that may occur when you uninstall this service pack and how to roll back to the release version of Visual Studio 2008
â€¢	The hotfixes that are included in this service pack
â€¢	The features and the functionalities that are new, changed, or improved

Back to the top

MORE INFORMATION

Known issues in this service pack and how to work around the known issues

â€¢	For multiple editions of Visual Studio 2008, Microsoft supports only the scenarios in which all the editions are at the same service pack level. If multiple languages or multiple editions of Visual Studio 2008 are installed on a computer, all the languages or all the editions must be the release version or must have Visual Studio 2008 SP1 Beta installed to be supported by Microsoft.
â€¢	This beta release is not installed if you have a beta version of Microsoft Silverlight installed on the operating system.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

945140 (/Feedback.aspx?kbNumber=945140/) Visual Studio 2008 Service Pack 1 Beta release notes and a list of fixed issues

Back to the top

Issues that may occur when you uninstall this service pack and how to roll back to the release version of Visual Studio 2008

For more information about the issues that may occur when you uninstall this service pack and about how to roll back to the release version of Visual Studio 2008, see the Removal issues for all platforms section in Microsoft Knowledge Base article 945140. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

945140 (/Feedback.aspx?kbNumber=945140/) Visual Studio 2008 Service Pack 1 Beta release notes and a list of fixed issues

Back to the top

Hotfixes that are included in this service pack

No hotfixes are included in this service pack.

Back to the top

Features and functionalities that are new, changed, or improved

New features and new functionalities

â€¢

This service pack adds debugging support for the following items:

â€¢	Range variables in queries
â€¢	Anonymous types
â€¢	Generic type arguments

â€¢

This service pack adds a new Visual C# IDE feature that provides a richer set of error information about your code. Specifically, this feature presents the expression-level errors that occur in open files to you according to your code. These expression-level errors were previously reported only after a build operation.

Changed features and changed functionalities

â€¢	In earlier versions of Visual Studio, the task list is populated by using the ToDo tasks that are specified in open files. In this service pack, the Visual C# IDE extends this functionality. The Visual C# IDE populates the task list by using the ToDo tasks that are specified in the whole solution.

Improved features and improved functionalities

â€¢	This service pack improves the performance of the Enumerable.Cast method by disabling the primitive value conversions and the explicitly defined user conversions. An example of a primitive value conversion is a conversion from the int data type to the long data type.
â€¢	This service pack improves the performance of the Where standard query operator and of the Select standard query operator.

Back to the top

Fixed issues for which hotfixes were not released

The following table lists some issues that this service pack fixes. No hotfixes were released for these issues.

Connect ID	Description
307131	IntelliSense does not show the extension methods that apply to generic type parameters.
304804	The Using directive is not applied to both parts of a partial method if the Using directive is defined in different scopes.
154722	The == operator and the != operator do not work correctly when the operators compare a nullable value type with itself and when the value is null.
315853	Two lock statements in the same block may cause the compiler to crash.
319387	When you call a generic interface method in expression trees, value types are boxed.
319429	Object initializers for value types do not work correctly in expression trees.
319454	Expression trees that have user-defined conversions do not work correctly.
321448	Rename refactoring may cause Visual C# 2008 Express Edition to stop responding (hang).
329326	Multiple issues occur when you compile the following code: default(T) ?? t
319465	The true operator and the false operator do not work correctly in expression trees when these operators are overloaded.
294736	IntelliSense proposes read-only properties in object initializers.
295945	The Remove Unused Usings command does not remove unbound using Language-Integrated Query (LINQ) statements.
316127	When you press CTRL+ENTER or SHIFT+CTRL+ENTER in an XML comment, Visual Studio 2008 crashes.
317256	The Debugger Visualizer template references the wrong version of the Microsoft.VisualStudio.DebuggerVisualizers assembly when an earlier version of Visual Studio is installed.

Back to the top

REFERENCES

For more information about Visual Studio 2008 Service Pack 1 Beta, click the following article number to view the article in the Microsoft Knowledge Base:

945140 (/Feedback.aspx?kbNumber=945140/) Visual Studio 2008 Service Pack 1 Beta release notes and a list of fixed issues

Back to the top

APPLIES TO

â€¢	Microsoft Visual Studio Team System 2008 Team Suite
â€¢	Microsoft Visual Studio Team System 2008 Database Edition
â€¢	Microsoft Visual Studio Team System 2008 Architecture Edition
â€¢	Microsoft Visual Studio Team System 2008 Development Edition
â€¢	Microsoft Visual Studio Team System 2008 Test Edition
â€¢	Microsoft Visual Studio 2008 Standard Edition
â€¢	Microsoft Visual Studio 2008 Professional Edition
â€¢	Microsoft Visual C# 2008 Express Edition

Back to the top

kbexpertiseadvanced kbhowto kbinfo KB950263

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

Visual Studio 2008 Crashes After Installing PowerCommands Add-In

admin — Thu, 01 Jul 2010 11:56:23 +0000

Article ID: 967679 – Last Review: February 9, 2009 – Revision: 1.0

Visual Studio 2008 Crashes After Installing PowerCommands Add-In

View products that this article applies to.

Expand all | Collapse all

Source: Microsoft Support

Back to the top

RAPID PUBLISHING

Back to the top

Action

You are using Visual Studio 2008 with the Visual Studio PowerCommands Add-In installed.

Back to the top

Result

When working with Visual Studio, it crashes unexpectedly and you see information similar to the following in the Windows Application event log.

Log Name: Application
Source: .NET Runtime
Event ID: 1023

.NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (000007FEF671203F) (0)

Back to the top

Cause

This is due to a bug in the Common Language Runtime (CLR) when loading assemblies.Ã‚Â In some scenarios, the CLR might rejectÃ‚Â a native image for a particular assembly based on the context it was requested to load in, rather than the context it actually belongs to. This can cause the native image for the assembly to be lost at some point while the process is running. When the CLR detects this condition, it purposely throws the ExecutionEngineException (Fatal Execution Engine Error), which terminates the process.Ã‚Â

In this scenario, System.Core.dll is reuqested by Microsoft.PowerCommands.dll. In certain scenarios,Ã‚Â System.Core.dll loses its native image and is loaded in the wrong context, which results in the crash.

Back to the top

Resolution

You can resolve the issue by adding a entry for Microsoft.PowerCommands in the Devenv.exe.config file.

1.Ã‚Â Using Notepad, open the devenv.exe.config file which is situated under Program Files Visual Studio 9 Common7 IDE folder.
2. Locate the element underneath the element. You should see a number of elements listed under this.
3. Add the following entry at the bottom of the entries.

Ã‚Â Ã‚Â
Ã‚Â Ã‚Â

4. Be sure to place the path to Microsoft.PowerCommands.dll with the path to it on your computer.
5. Save the file and close it.
6. Restart Visual Studio 2008.

Back to the top

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.

Back to the top

APPLIES TO

Microsoft Visual Studio Team System 2008 Team Suite
Microsoft Visual Studio 2008 Professional Edition
Microsoft Visual Studio 2008 Standard Edition

Back to the top

kbnomt kbrapidpub KB967679

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

FIX: The Visual C++ 2008 Libraries Extension Feature Pack is available

admin — Tue, 29 Jun 2010 12:43:46 +0000

FIX: The Visual C++ 2008 Libraries Extension Feature Pack is available

View products that this article applies to.

Article ID	:	945273
Last Review	:	April 15, 2008
Revision	:	1.0

INTRODUCTION

This article describes the Microsoft Visual C++ 2008 Libraries Extension Feature Pack that is available.

Back to the top

MORE INFORMATION

This package installs the Visual C++ 2008 Feature Pack. This feature pack extends the Visual C++ Libraries that are included with Visual Studio 2008.

The Visual C++ 2008 MFC libraries have been extended to enable you to create applications that have features such as the following:

â€¢	A Microsoft Office Ribbon-style interface
â€¢	The appearance and behavior of 2007 Office, Office 2003, and Office XP
â€¢	Modern Visual Studio-style docking toolbars and panes
â€¢	Fully customizable toolbars and menus
â€¢	A rich set of advanced GUI controls
â€¢	Advanced multiple document interface (MDI) tabs and groups

Back to the top

Hotfix information

How to obtain the Visual C++ 2008 Libraries Extension Feature Pack

The following file is available for download from the Microsoft Download Center:
Download the VC2008FeaturePack.exe package now. (http://www.microsoft.com/downloads/details.aspx?familyid=D466226B-8DAB-445F-A7B4-448B326C48E7&displaylang=en)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (/Feedback.aspx?kbNumber=119591/) How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

You must have the Visual Studio 2008 installed to apply this hotfix.

Restart requirement

You have to restart the computer after you apply this hotfix.

File information

File name	File version	File size	Date	Time	Platform
Dhtmlheader.html	Not Applicable	15,942	04-Mar-2008	13:02	Not Applicable
Parameterinfo.xml	Not Applicable	248,856	04-Mar-2008	13:02	Not Applicable
Spinstaller.exe	9.0.30219.0	78,344	04-Mar-2008	13:08	x86
Spinstallerengine.dll	9.0.30219.0	488,464	04-Mar-2008	13:08	x86
Spinstallerui.dll	9.0.30219.0	208,392	04-Mar-2008	13:08	x86
Sqmapi.dll	6.0.6000.16386	143,352	04-Mar-2008	13:08	x86
Uiinfo.xml	Not Applicable	2,190	04-Mar-2008	13:02	Not Applicable
Vc90fp-kb945273-x86-enu.msp	Not Applicable	170,636,288	04-Mar-2008	13:08	Not Applicable
Vc90fp-kb947886-x86_x64-enu.msp	Not Applicable	156,362,240	04-Mar-2008	13:08	Not Applicable
Vc_x64runtime.exe	9.0.30304.0	9,410,568	04-Mar-2008	01:38	x86
Vc_x86runtime.exe	9.0.30304.0	8,427,528	04-Mar-2008	01:32	x86
Eula.rtf	Not Applicable	160,254	04-Mar-2008	10:51	Not Applicable
Spinstallerresources.dll	9.0.30219.0	23,576	04-Mar-2008	13:08	x86
Spinstallerresources.dll	9.0.30219.0	24,600	04-Mar-2008	13:08	x86
Spinstallerresources.dll	9.0.30219.0	24,088	04-Mar-2008	13:08	x86

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

APPLIES TO

â€¢	Microsoft Visual Studio 2008 Academic Edition
â€¢	Microsoft Visual Studio 2008 Professional Edition
â€¢	Microsoft Visual Studio 2008 Standard Edition

Back to the top

kbexpertiseinter kbfix kbinfo KB945273

Back to the top

Microsoft Knowledge Base Article

Related Articles or Pages

Open Software Solutions » MS Visual Studio

FIX: A Stop error or a crash occurs on the operating system when you profile an application by using Visual Studio 2008 Service Pack 1

Hotfix information

Prerequisites

Restart requirement

Hotfix replacement information

File information

APPLIES TO

Keywords:Ã‚Â

Microsoft Knowledge Base Article

Problems when trying to setup remote debug across network domains

Action

Result

Cause

Resolution

More Information

DISCLAIMER

APPLIES TO

Microsoft Knowledge Base Article

Possible Reasons for OLE Control Registration Failure

SUMMARY

MORE INFORMATION

Reasons Why the Registration of a Control May Fail

Troubleshooting Techniques

APPLIES TO

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

Microsoft Knowledge Base Article

FIX: You may experience performance issues in the IDE after you use Visual Studio 2008 to build a Visual Basic project

CAUSE

RESOLUTION

Download information

Hotfix information

WORKAROUND

Method 1: Disable XML comment generation

Visual Studio 2008

Visual Basic 2008 Express Edition

Method 2: Remove the XML comments

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

STATUS

MORE INFORMATION

APPLIES TO

Microsoft Knowledge Base Article

You cannot host a Visual SourceSafe 2005 Web service on a computer that is running Windows Vista

SYMPTOMS

CAUSE

WORKAROUND

REFERENCES

APPLIES TO

Keywords:Â

Microsoft Knowledge Base Article

The DataSet designer does not allow custom data types to be used on the columns of data tables inside the data set.

APPLIES TO

Keywords:Ã‚Â

Microsoft Knowledge Base Article

After you use the ReportResult method to customize the error icon when a logon failure occurs in Windows Vista, the general error icon (CPSI_ERROR) is displayed unexpectedly

On This Page

SYMPTOMS

RESOLUTION

Hotfix information

Prerequisites

Restart requirement

Hotfix replacement information

Registry information

File information

Windows Vista with SP1, x86-based versions

Windows Vista with SP1, x64-based versions

Windows Vista with SP1, Itanium-based versions

STATUS

MORE INFORMATION

APPLIES TO

Keywords:Â

Microsoft Knowledge Base Article

Visual Studio 2008 Express Editions Service Pack 1 Beta release notes and a list of fixed issues

Notice

Beta Information

On This Page

SUMMARY

MORE INFORMATION

Products to which Visual Studio 2008 Express Editions SP1 Beta applies

How to obtain Visual Studio 2008 Express Editions SP1 Beta