•	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

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

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.

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.

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:

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:

Back to the top

The Microsoft ADO.NET Entity Designer is included in the Microsoft Visual Studio 2008 Service Pack 1 (SP1) Shell (isolated mode). However, when you run the Visual Studio Shell (isolated mode), the ADO.NET Entity Designer is not supported. This article describes how to disable the ADO.NET Entity Designer.

When you browse to an .edmx file in the Visual Studio 2008 SP1 Shell (isolated mode), and then you open the file, Visual Studio starts the ADO.NET Entity Designer. However, the ADO.NET Entity Designer may fail or stop responding.

To disable the ADO.NET Entity Designer when you build an isolated shell application, add the following GUID to the project.pkgundef file:

Note The project placeholder represents the name of your isolated shell application.

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

•	Known issues in this service pack and how to work around those issues
•	Issues that may occur when you uninstall this service pack and how to roll back to the release version of Visual Studio 2008
•	Hotfixes that are included in this service pack
•	Features and functionalities that are added, changed, or improved
•	Fixed issues for which hotfixes were not released

Back to the top

Known issues in this service pack and how to work around those issues

•	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 RTM level or at the SP1 level.
•	You cannot install this service pack if you have the beta version of Silverlight installed on your computer.

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

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 information about 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 the following article in the Microsoft Knowledge Base:

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 added, changed, or improved

No added, changed, or improved features or functionalities are included in this service pack.

Back to the top

Fixed issues for which hotfixes were not released

•

946729 (/Feedback.aspx?kbNumber=946729/) FIX: Visual Studio 2008 IDE access violation occurs when you open an .rc file that is generated by the file fuzzer Category Visual Studio 2008 SP1 Updates from Windows SDK Content. Description FIX: Manifest Tool for generating signed files and catalogs can occasionally corrupt a binary file’s header when embedding the manifest. Related DevDiv bugs

•

946733 (/Feedback.aspx?kbNumber=946733/) Installation fixes and updates that are included Visual Studio 2008 S946733 Beta for WinSDK Category Visual Studio 2008 SP1 Updates from Windows SDK built in Visual Studio Setup Description Improve and repair development tools that are provided by the .NET Framework team for managed code. Extend native C# and Visual Basic language, integrated data access syntax with class libraries to improve query, set, and transform operations. Related DevDiv bugs

Back to the top

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

Back to the top

Source: Microsoft Support

Back to the top

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

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

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 0x0008c7c1.

Back to the top

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

Remove the extra period(‘.’) from

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

Back to the top

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.

Back to the top

You create a Visual C++ project on a computer that has Microsoft Visual Studio 2008 Service Pack 1 (SP1) installed. You use a function that contains the try-catch block but no brace for the function body. When you compile the project, you will receive the C2590 and C2533 errors that resembles following:

When you compile a Visual C++ project on a computer that has Microsoft Visual Studio 2008 Service Pack 1 (SP1) installed, you receive error messages that resemble the following:

This problem occurs if the following conditions are true:

• You use a function that contains the try-catch block.
• The project does not contain a brace for the function body.

This problem occurs because the compiler assumes the try-catch block can only be associated with constructors.

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 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:

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.

Prerequisites

You must have Visual Studio 2008 SP1 installed 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.

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

This article describes a hotfix that provides the IntelliSense flavor for Microsoft Visual Studio 2008 JavaScript files. This flavor is an addition to the existing JavaScript file flavors, which are the Release flavor and the Debug flavor.

When you open IntelliSense-friendly JavaScript files, some semantic code changes are required. For example, dynamically declared functions must be de-normalized into statically declared functions. After you add the new flavor, you can modify semantic code for IntelliSense. The IntelliSense flavor works as an IntelliSense helper file. However, this flavor does not make any statements about the core code. Additionally, this flavor is not intended for running or debugging.

Visual Studio 2008 and ASP.NET 3.5 provide optimizations that let you reference runtime-optimized JavaScript files by using one of the following methods:

• Script Manager
• XML Comments
• HTML Script Tag

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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:

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.

Prerequisites

You must have Visual Studio 2008 SP1 installed before you apply the 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 global 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.

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

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

When you link a Visual C++ project by using the /INCREMENTAL build option in Microsoft Visual Studio 2008, you may receive the following error message:

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. But the hotfix is intended only to correct the problem that is described in this article. Apply this hotfix 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, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

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.

File name	File version	File size	Date	Time	Platform
Link.exe	9.0.21022.58	1,044,984	07-	11:14	x64
Link.exe	9.0.21022.58	790,520	07-	11:14	x86

Back to the top

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

Back to the top

Source: Microsoft Support

Back to the top

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

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

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

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

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.

Back to the top

Source: Microsoft Support

Back to the top

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

You try to do one of the following:
Remove Microsoft Visual C++ Redist from the Add/Remove Programs Control Panel applet, or
Install Microsoft Visual C++ Redist on a machine.

Back to the top

You get the following error :
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2203.

Back to the top

It may be an incorrect value of TEMP/TMP environment variable.

Back to the top

1. Goto My Computer->Properties->Advanced->Environment Variables.

2. Select TEMP System Variable and Click Edit.

3. Validate the path. Set it to a valid folder on the local machine.

Back to the top

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.

Back to the top

Source: Microsoft Support

Back to the top

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

The question has been asked: Is there a 64-bit version of Visual Studio 2005 or Visual Studio 2008?

Back to the top

No.  Unfortunately, we do not have a 64-bit version of Visual Studio 2005 or Visual Studio 2008.  However we do support development and debugging of 64-bit application.  See below for more information:

With the introduction of the Visual Studio 2005, we are able to built applications for both 32-bit and 64-bit systems. The major advantage with the managed applications is that you do not need a separate version for each architecture as the Framework compiles that assembly to run on architecture of the operating system.

There is a requirement for building 64-bit managed assemblies and that is that all components utilized by the managed assembly must be capable of running on the 64-bit system.  For example, if an assembly need to call into a 32-bit COM component, that assembly must be compiled to target x86 CPU so that it runs under the WOW64 layer.

Visual Studio Development Environment 64-Bit Support:
 2005 – http://msdn2.microsoft.com/en-us/library/ms241066(VS.80).aspx (http://msdn2.microsoft.com/en-us/library/ms241066(VS.80).aspx)
 2008 – http://msdn2.microsoft.com/en-us/library/ms241066.aspx (http://msdn2.microsoft.com/en-us/library/ms241066.aspx)

Debugging of your 64-bit application is also possible from Visual Studio 2005 or Visual Studio 2008:

 How to: Debug 64-bit Applications:
 2005 – http://msdn2.microsoft.com/en-us/library/ms184681.aspx (http://msdn2.microsoft.com/en-us/library/ms184681.aspx)
 2008 – http://msdn2.microsoft.com/en-us/library/ms184681(VS.80).aspx (http://msdn2.microsoft.com/en-us/library/ms184681(VS.80).aspx)
 

Back to the top

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.

Back to the top

When you run a C++ application that contains an uninitialized floating-point variable in Microsoft Visual Studio 2008, a floating-point exception occurs. Additionally, you may receive the following error message:

This problem occurs if the following conditions are true:

•	You add the /fp:except option to the compiler option list to disable the floating-point exception.
•	The source code contains an uninitialized floating-point variable.
•	The uninitialized floating-point variable is located in a memory that contains a signaling not-a-number (NaN) value.

Back to the top

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 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:

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.

Prerequisites

You must have Visual Studio 2008 installed 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.

File name	File version	File size	Date	Time	Platform
C2.dll	15.0.21022.162	2,360,304	28-Aug-2008	11:08	x86
Cl.exe	15.0.21022.162	130,032	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	195,576	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	212,984	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	280,568	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	283,128	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	394,744	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	395,256	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	460,792	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	467,448	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	470,520	28-Aug-2008	11:08	x86
Clui.dll	15.0.21022.162	475,640	28-Aug-2008	11:08	x86

Back to the top

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

Back to the top

For more information about the /fp compiler options, visit the following Microsoft Web site:

Back to the top

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 kinds 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 May 13, 2008.

Back to the top

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 May 13, 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.

NoteNot every update is available on every Web site that is listed here.

Windows Update

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

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 exceptions

•	Security update 952044 (security bulletin MS08-029) Microsoft Update supports only the Forefront Client Security and Windows Defender parts of this update. The other products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

Office Update

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

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.1

You can detect security updates that were released on May 13, 2008 if you use MBSA version 2.1.

Note MBSA version 2.1 is now released and fully supports security and vulnerability assessment scans on Windows Vista and Windows Server 2008.General exceptions

•	MBSA version 2.1 does not support any Office 2000 components.
•	MBSA version 2.1 does not support any Macintosh products.
•	MBSA version 1.2.1 and 2.0.1 are no longer supported.

Specific exceptions

•	Security update 952044 (security bulletin MS08-029) MBSA version 2.1 does not support the Malware Protection Engine update. The products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 May 13, 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 exceptions

•	Security update 952044 (security bulletin MS08-029) WSUS 2.0 and WSUS 3.0 support only the Forefront Client Security and Windows Defender parts of this update. The other products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 May 13, 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 exceptions

•

Security update 952044 (security bulletin MS08-029) SMS ITMU and SUS Feature Pack do not support the Malware Protection Engine update. System Center Configuration Manager 2007 supports only the Forefront Client Security and Windows Defender parts of this update. The products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

NoteThe 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:

Summary of detection and deployment guidance

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

NoteTo 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 partly 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.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
951207	MS08-026	Word	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
951208	MS08-027	Publisher	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
950749	MS08-028	Jet	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
952044	MS08-029	Malware Protection Engine	Not applicable	Not applicable	Yes	No	Partly, see the WSUS section	No	No	Yes

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 May 14, 2008 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

What other information should I know about MBSA?

For more information about the programs that MBSA currently supports, visit the following Microsoft TechNet Web page:

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:

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 information about the limitations of the SUS Feature Pack, click the following article number to view the article in the Microsoft Knowledge Base:

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:

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

In the Windows Presentation Foundation (WPF) Designer for Microsoft Visual Studio 2008, you can use Microsoft IntelliSense for Extensible Application Markup Language (XAML). However, IntelliSense for XAML may stop working after you install the Microsoft Windows Software Development Kit (SDK) or Microsoft Developer Network (MSDN). When this problem occurs, the (Default) registry value in one of the following registry keys is empty:

• On an x86-based computer:
  HKEY_CLASSES_ROOT CLSID {73B7DC00-F498-4ABD-AB79-D07AFD52F395} InProcServer32
• On an x64-based computer:
  HKEY_CLASSES_ROOT Wow6432Node CLSID {73B7DC00-F498-4ABD-AB79-D07AFD52F395} InProcServer32

This problem occurs because the (Default) registry value in the InProcServer32 registry key is reset incorrectly after you install Document Explorer.

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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:

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.

Prerequisites

There are no prerequisites.

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.

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

Method 1: Repair Visual Studio 2008

Windows Vista and Windows Server 2008

1. Click Start
   Collapse this imageExpand this image

   

   , and then type appwiz.cplin the Start Searchbox.

2. In the Programslist,right-click appwiz.cpl, and then click Run as administrator.
   Collapse this imageExpand this image

   

   If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

3. In the list of installed programs, locate Visual Studio 2008, and then click Change.
4. Click Repair.

Windows XP and Windows Server 2003

1. Click Start, click Run, type appwiz.cplin the Openbox, and then click OK.
2. In the list of installed programs, locate Visual Studio 2008, and then click Change.
3. Click Repair.

Method 2: Register the TextMgrP.dll file manually

Windows Vista and Windows Server 2008

1. Click Start
   Collapse this imageExpand this image

   

   , and then type cmdin the Start Searchbox.

2. In the Programslist,right-click cmd, and then click Run as administrator.
   Collapse this imageExpand this image

   

   If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

3. At the command prompt, type the appropriate command, and then press ENTER:
   • On an x86-based computer, type the following command:
     regsvr32 %CommonProgramFiles% Microsoft Shared MSEnv TextMgrP.dll
   • On an x64-based computer, type the following command:
     regsvr32 %CommonProgramFiles(X86)% Microsoft Shared MSEnv TextMgrP.dll

Windows XP and Windows Server 2003

1. Click Start, click Run, type cmdin the Openbox, and then click OK.
2. At the command prompt, type the appropriate command, and then press ENTER:
   • On an x86-based computer, type the following command:
     regsvr32 %CommonProgramFiles% Microsoft Shared MSEnv TextMgrP.dll
   • On an x64-based computer, type the following command:
     regsvr32 %CommonProgramFiles(X86)% Microsoft Shared MSEnv TextMgrP.dll

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

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

Source: Microsoft Support

Back to the top

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

Create a VC++ console-based application that links statically with MFC and execute it on the Windows Server 2000 (or earlier) operating system.

Back to the top

You get a fatal error message:
The procedure entry point getaddrinfo could not be located in the dynamic link library WS2_32.dll

Back to the top

The getaddrinfo (http://msdn.microsoft.com/en-us/library/ms738520.aspx) function was added to the Ws2_32.dll on Windows XP and later.

Back to the top

To execute an application using this function on earlier versions of Windows (Windows 2000, Windows NT, and Windows Me/98/95), then it is mandatary to #include Ws2tcpip.h and also Wspiapi.h. When the Wspiapi.h header file is included, the ‘getaddrinfo’ function is #defined to the ‘WspiapiGetAddrInfo’ inline function in Wspiapi.h. At runtime, the ‘WspiapiGetAddrInfo’ function is implemented in such a way that if the Ws2_32.dll or the Wship6.dll (the file containing getaddrinfo in the IPv6 Technology Preview for Windows 2000) does not include ‘getaddrinfo’, then a version of ‘getaddrinfo’ is implemented inline based on code in the Wspiapi.h header file. This inline code will be used on older Windows platforms that do not natively support the ‘getaddrinfo’ function.

Back to the top

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.

Back to the top