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

Installing the Visual C++ 2008 Redistributable Package (VCRedist_x86.exe, VCRedist_x64.exe, VCRedist_ia64.exe) for Visual Studio 2008 RTM.

Back to the top

Following files are generated on the system root directory :

install.exe
install.res.1028.dll
install.res.1031.dll
install.res.1033.dll
install.res.1036.dll
install.res.1040.dll
install.res.1041.dll
install.res.1042.dll
install.res.2052.dll
install.res.3082.dll
vcredist.bmp
globdata.ini
install.ini
eula.1028.txt
eula.1031.txt
eula.1033.txt
eula.1036.txt
eula.1040.txt
eula.1041.txt
eula.1042.txt
eula.2052.txt
eula.3082.txt
vc_redist.msi
vc_redist.cab

Back to the top

These temporary files are erroneously generated by the installer into the system root directory instead of the temp directory.

Back to the top

These files are unnecessary and can be safely deleted from the system. The functioning of the runtime library will not be affected by this.
Its a known bug and is planned to be fixed in VS2008 SP1.

Back to the top

Redistributing Visual C++ Files (http://msdn2.microsoft.com/en-us/library/ms235299.aspx)
Please visit the Visual Studio home page on MSDN (http://msdn2.microsoft.com/en-us/vstudio/default.aspx) for the latest updates

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 are using Visual SourceSafe 6.0 or 2005.  You attempt to edit a file from within Visual Studio that has not been checked out.

Back to the top

You are able to edit the file without being prompted and without the file being automatically checked out.

Back to the top

Files in the working directory do not have the read only attribute even though they are not checked out from Visual SourceSafe.

Several scenarios can cause this behavior:

1. You may have selected make writable option when getting files from SourceSafe.

2.  You may not have Tools> Options> Local Files tab  Use Read-only Flag for files not checked out selected.

3. You may be sharing a working directory with another user that does have the file checked out.

4. You may have intentionally uncheck the read only attribute in order to do testing on the file without checking the file out.

5. You may not have NTFS permissions to set the read only in the working directory. 

6. In the dialog Tools> Options> expand Source Control and choose Environment, you set the On Edit option to do nothing and you have checked the box in the same dialogue to Allow checked in items to be edited.

Back to the top

Make sure the user has full permissions to their working folder.

In VSS  Explorer:

Open the Tools> Options> Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

or

In Visual Studio:

 Go to Tools> Options> expand Source Control and choose Plug-in Settings.  Click on the advance button and select the Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

In Visual Studio you have the option to be prompted when editing or to automatically check the file out.

In the dialog Tools> Options> expand Source Control and choose Environment.

Set the On Edit option to Prompt for Check out or Automatically check out depending on preference.

Move all the files from the working folder and re-issue the Get Latest (making sure you do not select make writable) and try to edit the file.

Back to the top

If you do a Get Latest, typically the files should be marked with a read only attribute.  However, sometimes the attribute is not set for some reason. Please review the cause section for most common reasons.

Sharing of working directories is not recommend because it can easily lead to the problem described in this article.

If you are editing directly from the SourceSafe Explorer

Open the Tools> Options> General tab and make sure that the Double-click on a file option is set to Ask.

You are prompted by a dialog that contains the following question in a option group:

Do you want to:

View SourceSafe’s copy of this file

Check out this file and edit it in your working folder.

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

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

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

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

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

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:

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:

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:

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:

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:

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:

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

Source: Microsoft Support

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.

You attempt to use a 64-bit component within the Microsoft Visual Studio Integrated Development Environment (IDE).

1. When adding control contained within an external 64-bit assembly to to the Visual Studio Toolbox, you receive the following error message.

<Control Name.dll> is not a valid .NET module.

2. When dragging and dropping a UserControl defined in a 64-bit assembly to a Form in another project within the same solution, you receive the error:

Failed to load toolbox item <UserControl Name>.  It will be removed from the toolbox.

3. When opening the Visual Studio Windows Form Designer for a form that attempts to instantiate a control in a 64-bit assembly, you receive the following errors in the Windows Form designer.

Could not find type <typename>. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built.

The variable <variable name> is either undeclared or was never assigned.

Call Stack:

at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.Error(IDesignerSerializationManager manager, String exceptionText, String helpLink)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeExpression(IDesignerSerializationManager manager, String name, CodeExpression expression)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeExpression(IDesignerSerializationManager manager, String name, CodeExpression expression)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeStatement(IDesignerSerializationManager manager, CodeStatement statement)

This behavior is by design. Visual Studio is a 32-bit process, and therefore can only execute 32-bit modules. While Visual Studio allows you to add a reference to a 64-bit assembly, it cannot actually JIT compile it to 64-bit and execute it in process.

1. Rebuild the assembly using the AnyCPU setting. This would allow the component to run within a 32-bit process (such as Visual Studio), or in a 64-bit process.

Advanced Compiler Settings Dialog Box (Visual Basic)
http://msdn.microsoft.com/en-us/library/07bysfz2.aspx (http://msdn.microsoft.com/en-us/library/07bysfz2.aspx)

 /platform (Specify Output Platform) (C# Compiler Options)
http://msdn.microsoft.com/en-us/library/zekwfyz4.aspx (http://msdn.microsoft.com/en-us/library/zekwfyz4.aspx)

If you are using a third party component and cannot rebuild it yourself, contact the component vendor to see if an AnyCPU version of the assembly is possible to obtain. This will allow the component to Just-In-Time (JIT) compile to run as either a 32-bit or 64-bit module, depending on the machine architecture the operating system and host process are targeting.

2. Add the assembly as a reference and load the control dynamically at run-time. Although you still would be unable to use the control within any designer inside Visual Studio, you can still write the code needed to instantiate the control and set it’s properties accordingly.

Is there a 64-bit version of Visual Studio 2005 or Visual Studio 2008?
http://support.microsoft.com/default.aspx/kb/951801 (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fdefault.aspx%2fkb%2f951801)

 

Process Interoperability

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

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.

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

So we recently came across an issue where Visual Studio 2005 and 2008 Designers were not respecting assembly binding redirection.

Example

We have a file which is now version 2 and stored in the GAC (http://msdn2.microsoft.com/en-us/library/yf1d93sz.aspx).  So the assembly version is 2.0.0.0.  We have some existing customers using version 1 so we want to be able to use Assembly Binding Redirection (http://msdn2.microsoft.com/en-us/library/2fc472t2.aspx) to point them to the new version of the assembly.

For more information on configuring this, check out Configuring Assembly Binding Redirection (http://msdn2.microsoft.com/en-us/library/433ysdt1.aspx).

The web page has code like:<tc:TestContacts ID=QuickContacts1 runat=server> <tc:AContact Name=Test Tester Email=test@test.com Phone=(999) 555-1212 /> <tc:AContact Email=no@spam.thx Name=Mr. A. Nonymous Phone=(999) 555-1234 /></tc:TestContacts>.csharpcode, .csharpcode pre{font-size:small;color:black;font-family:consolas, Courier New, courier, monospace;background-color:#ffffff;}.csharpcode pre{margin:0em;}.csharpcode .rem{color:#008000;}.csharpcode .kwrd{color:#0000ff;}.csharpcode .str{color:#006080;}.csharpcode .op{color:#0000c0;}.csharpcode .preproc{color:#cc6633;}.csharpcode .asp{background-color:#ffff00;}.csharpcode .html{color:#800000;}.csharpcode .attr{color:#ff0000;}.csharpcode .alt{background-color:#f4f4f4;width:100%;margin:0em;}.csharpcode .lnum{color:#606060;}

We also have a Register Assembly line at the top that points to the 1.0.0.0 version of the file.  And we have an entry in our web.config that looks like this:<runtime> <assemblyBinding xmlns=urn:schemas-microsoft-com:asm.v1> <dependentAssembly> <assemblyIdentity name=Tester1 publicKeyToken=6ace53ab3256c766/> <bindingRedirect oldVersion=1.0.0.0-1.1.0.0 newVersion=2.0.0.0/> </dependentAssembly> </assemblyBinding></runtime>.csharpcode, .csharpcode pre{font-size:small;color:black;font-family:consolas, Courier New, courier, monospace;background-color:#ffffff;}.csharpcode pre{margin:0em;}.csharpcode .rem{color:#008000;}.csharpcode .kwrd{color:#0000ff;}.csharpcode .str{color:#006080;}.csharpcode .op{color:#0000c0;}.csharpcode .preproc{color:#cc6633;}.csharpcode .asp{background-color:#ffff00;}.csharpcode .html{color:#800000;}.csharpcode .attr{color:#ff0000;}.csharpcode .alt{background-color:#f4f4f4;width:100%;margin:0em;}.csharpcode .lnum{color:#606060;}

We could have done this in a policy file and got the same results.  So now we open this file in Design view inside Visual Studio and change a property of the TestContacts control.  For instance, adding an AccessKey.  Switching back to the Source view, we will now see:<tc:TestContacts ID=QuickContacts1 runat=server> <samples.aspnet.cs.controls.acontact Name=Test Tester Email=test@test.com Phone=(999) 555-1212 /> <samples.aspnet.cs.controls.acontact Email=no@spam.thx Name=Mr. A. Nonymous Phone=(999) 555-1234 /></tc:TestContacts>.csharpcode, .csharpcode pre{font-size:small;color:black;font-family:consolas, Courier New, courier, monospace;background-color:#ffffff;}.csharpcode pre{margin:0em;}.csharpcode .rem{color:#008000;}.csharpcode .kwrd{color:#0000ff;}.csharpcode .str{color:#006080;}.csharpcode .op{color:#0000c0;}.csharpcode .preproc{color:#cc6633;}.csharpcode .asp{background-color:#ffff00;}.csharpcode .html{color:#800000;}.csharpcode .attr{color:#ff0000;}.csharpcode .alt{background-color:#f4f4f4;width:100%;margin:0em;}.csharpcode .lnum{color:#606060;}

Back to the top

This breaks the site and it no longer works.

Note: Assembly Binding Redirection works find in other scenarios, it just doesn’t work right inside the Designer.

Back to the top

Bug in the Designer

Back to the top

This is fixed in Visual Studio 2008 Server pack 1

Other work arounds for Visual Studio 2005

•	Don’t use Assembly Binding Redirection at all and just leave the 1.0.0.0 version of the file in the GAC.  You will see a lot of .NET files do this, there are versions for .NET 1.0, 1.1, 2.0, etc all inside the GAC at the same time.
•	Change the existing files so that the Register Assembly line at the top of the web page points to the 2.0.0.0 version of the file.

Keep in mind that this is only a problem if you are actively changing the older files already, if you don’t touch the file it will be fine since this issue is only with the Designer.  So since you are already updating the file, it is trivial to update this line also.

Back to the top

Global Assembly Cache

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

Assembly Binding Redirection

http://msdn.microsoft.com/en-us/library/2fc472t2.aspx (http://msdn.microsoft.com/en-us/library/2fc472t2.aspx)
Configuring Assembly Binding Redirection
http://msdn.microsoft.com/en-us/library/433ysdt1.aspx (http://msdn.microsoft.com/en-us/library/433ysdt1.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

This article lists known issues with the setup and the removal of Visual Studio 2008 SP1 Beta. Additionally, this article discusses the Visual Studio 2008 SP1 Beta features.

The release notes for Visual Studio 2008 SP1 Beta for Express editions are included in the following Microsoft Knowledge Base (KB) article:

Back to the top

Products to which Visual Studio 2008 SP1 Beta applies

•	The Microsoft .NET Framework 3.5
•	The Microsoft Windows SDK
•	Visual Studio 2008 Standard Edition
•	Visual Studio 2008 Professional Edition
•	Visual Studio 2008 Team Edition for Database Professionals
•	Visual Studio 2008 Team Edition for Software Architects
•	Visual Studio 2008 Team Edition for Software Developers
•	Visual Studio 2008 Team Edition for Software Testers
•	Visual Studio 2008 Team Suite

Back to the top

How to obtain Visual Studio 2008 SP1 Beta

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

This package installs the service pack for Microsoft Visual Studio 2008 Standard, Professional, and Team Editions.

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

Back to the top

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

For more information about the changed features and fixed issues for Visual Studio 2008 SP1 Beta, visit the following Microsoft Knowledge Base (KB) articles:

•	949258 (/Feedback.aspx?kbNumber=949258/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for the Visual Studio Tools for Office System 3.0 Runtime
•	951845 (/Feedback.aspx?kbNumber=951845/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for team editions
•	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
•	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 .NET Framework 3.5
•	951846 (/Feedback.aspx?kbNumber=951846/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Data Projects
•	950262 (/Feedback.aspx?kbNumber=950262/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Visual C++
•	950265 (/Feedback.aspx?kbNumber=950265/) List of changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Windows Presentation Foundation Designer

For more information about the changes and fixed issues for Visual Studio 2008 Service Pack 1 Beta for Windows SDK, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This service pack adds the following new features:

•	SQL Server 2008 Community Technology Preview (CTP) support is added to Visual Studio 2008.
•	The following Visual Basic PowerPack controls have been added: • Line • Shape • Data Repeater
•	In Visual Basic, the Windows Communication Foundation (WCF) Service renaming process is improved.
•	Document level features are included for application level add-ins in Visual Studio Tools for Office.
•	Design-time support has been added in the ClickOnce application for file name extensions and Start menu customization.
•	You can send mail from work items in Team Foundation Server.
•	Version control usability improvements and Microsoft Visual SourceSafe (VSS) converter improvements have been made in Team Foundation Server.
•	Improved Team System Web access integration with notifications has been added in Team Foundation Server.
•	In Visual Studio Team Edition for Developers, support has improved for Internet Information Services (IIS) 7 in the Visual Studio Performance Tools (Profiler).
•	In Visual Studio Team Edition for Developers, 64-bit mixed mode (native/managed) instrumentation support has been added in the Profiler.
•	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 appearance and behavior of Microsoft Office.
•	In Visual Web Developer, SQL Server 2008 support for Web projects is added.
•	In Visual Web Developer, JavaScript formatting support is added.
•	In Visual Web Developer, the WCF Service renaming process is improved.
•	Debugging changes improve support for inspecting the results of in-memory Language-Integrated Query (LINQ) queries.
•	A new Visual C# feature is added to provide a richer set of error information about code.
•	Visual Studio Industry Partners (VSIP) partners are enabled to install one copy of files for a package that can be used by multiple isolated applications.
•	In Windows Presentation Foundation (WPF) Designer, snaplines are now implemented for margins. This behavior enables the designer to control a fixed distance from other controls, container edges, or gridlines.
•	Visual Studio Tools for Office System (VSTO) is improved to support add-in error logging.
•	XSD Schema Explorer is improved.
•	The Step Into Specific debugging feature and the Step Filtering debugging feature for managed properties and managed operators are changed.
•	The debugger now can cancel symbol and source downloading from Microsoft Public Symbol Servers.
•	Streamlined support for Reference Source is added to the debugger.
•	The ADO.NET Entity Designer is added to ease data access.
•	You can now add “Local Database Cache” to device projects.
•	ASP.NET Dynamic Data templates and toolbox controls are added.
•	IIS 7.0 Managed Module and Handler templates are added.
•	Support for starting the WCF Test client debug of a WCF Service file (.svc) by pressing F5 is added.

Back to the top

Supported languages and operating systems

Supported languages

Visual Studio 2008 SP1 Beta provides updates for the following versions of Visual Studio 2008:

•	English (United States)
•	Japanese

Supported operating systems

•	Windows XP Service Pack 2 (SP2)
•	Windows Server 2003 SP1 or a later version of Windows Server 2003 Note If you must have support for Microsoft SQL Server 2008 Community Technology Preview (CTP), you must have Windows Server 2003 SP2 installed.
•	Windows Vista
•	Windows Server 2008

Back to the top

Installation requirements

•	A licensed copy of one of the supported Visual Studio 2008 products 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 MB or more RAM.

Back to the top

Visual Studio 2008 SP1 Beta support

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

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

Back to the top

Administrator deployment of Visual Studio 2008 SP1 Beta

The Visual Studio 2008 SP1 Beta is a conditional download manager and update installer. Visual Studio 2008 SP1 Beta detects and installs only relevant updates applicable to the computer on which it is running. For administrator deployment, create a full package layout on the server computer. To create a full package layout of Visual Studio 2008 SP1 Beta, follow these steps:

1.	Download the VS90sp1_KB945140.exe file to a temporary folder on an computer that connects to the Internet. For example, save the file in the C: VS90SP1 folder.
2.	Click Start, click Run, type cmd, and then click OK. Note In Windows Vista, if you are prompted for an administrator password or confirmation, type your password or click Continue.
3.	Type the following command to download all Visual Studio 2008 SP1 Beta packages: VS90sp1-KB945140-ENU.exe /createlayout FullTargetFolderPath /passive Note FullTargetFolderPath represents the target folder for the package layout. For example, type the following command: VS90sp1-KB945140-ENU.exe /createlayout c: VS90SP1 Layout /passive

When you follow these steps, you download the complete Visual Studio 2008 SP1 Beta packages, you store the packages in the folder that you specify, and you do not install Visual Studio 2008 SP1 Beta. These packages include the SP1 Beta Setup program (SPInstaller.exe).

Then, to deploy the update to the client computers, follow these steps:

1.	Copy the created Layout folder to a shared network location.
2.	Run SPInstaller.exe from the client computers by using the following command: FullNetworkPathSPInstaller.exe /q /log %temp% VS90SP1.htm /promptrestart For example, you type the following command: Server VS90SP1 Layout SPInstaller.exe /q /log %temp% VS90SP1.htm /promptrestart

Back to the top

Installation issues for all platforms

Service pack installation takes longer than the original product installation

Installing Visual Studio 2008 SP1 Beta takes longer than when you install Visual Studio 2008. The Visual Studio 2008 SP1 Beta installation resembles a product installation. However, the Visual Studio 2008 SP1 Beta installation involves more installation tasks. Installation time depends on which product is installed and the computer configuration.

Installation requires significant disk space

You may have to have disk space that is equal to the disk space that the original product installation used when you install a service pack. If you have more than one Visual Studio product installed, you must have disk space for each service pack installation. You can find an estimate of the required disk space on the download page for the service pack.

Visual Studio 2008 SP1 Beta is language specific

If you have more than one language instance of Visual Studio 2008 on a computer, you must install a separate service pack for each language.

Visual Studio 2008 SP1 Beta will not install immediately after a Visual Studio compilation

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

To resolve this issue, use one of the following methods:

•	Finish compilations that are in progress, and wait for the debugger service to close. You may have to wait up to 10 minutes.
•	Use Windows Task Manager to end all instances of the Mspdbsrv.exe service.

You receive a Visual Studio 2008 SP1 Beta error message during the setup process

During the Visual Studio 2008 SP1 Beta setup process, the progress window reports an Install failed – rolling back error message. However, the progress window then reports success on a finish page.

This is a Beta release issue. This issue occurs because incorrect progress reporting for one of the setup packages. This issue does not represent the result of an operation. You can safely ignore this error message in the progress window. If the finish page reports success, all updates have been installed successfully.

Back to the top

Removal issues for all platforms

Mixed-mode configurations

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

How to remove the Visual Studio 2008 SP1 Beta

The Visual Studio 2008 SP1 Beta is a set of updates and upgrades that should be uninstalled individually. To uninstall the SP1 Beta updates, follow these steps:

1.

Depending on the version of Windows, use one of the following methods. If you are running a version of Windows that is earlier than Windows Vista, follow these steps: a. In Control Panel, open the Add or Remove Programs item. b. Click to select the Show updates check box. If you are running Windows Vista, follow these steps: a. In Control Panel, open the Programs and Features item. b. Click to select the Show updates check box.

2.

Uninstall the following updates if they are listed: • Microsoft Visual Studio Team System 2008 Team Suite – Service Pack 1 (KB945140) • Microsoft Visual Studio Team System 2008 Team Suite – Service Pack 1 (KB948560) • Microsoft Visual Studio Team System 2008 Team Suite – Service Pack 1 (KB947888) • Microsoft Visual Studio Team System 2008 Team Suite – Service Pack 1 (KB948484) • Microsoft Visual Studio 2008 Remote Debugger – Service Pack 1 (KB945140) • KB945140 under Visual Studio .NET Prerequisites • Update for WebDesigner 2007 (KB945140) • Windows SDK for Visual Studio 2008 SP1 KB946729 • Windows SDK for Visual Studio 2008 KB946733 • Microsoft SQL Server Compact 3.5 SP1 Design Tools English • Microsoft SQL Server Compact 3.5 SP1 English • Microsoft SQL Server Database Publishing Wizard • Visual Studio Tools for the Office system 3.0 Runtime Service Pack 1 Language Pack (KB949258) • Visual Studio Tools for the Office system 3.0 Runtime Service Pack 1 (KB949258) • Visual C++ 2008 IA64 Runtime – (v9.0.304xx) • Visual C++ 2008 x64 Runtime – (v9.0.304xx) • Visual C++ 2008 x86 Runtime – (v9.0.304xx)

Restoring to the release version of Visual Studio 2008

After the complete removal of 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 SP1 Beta update.

The .NET Framework 3.5 SP1 Beta will remain on the operating system after you uninstall Visual Studio 2008 SP1 Beta. We recommend that you do not remove this product 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.

Note If any Visual Studio 2008 SP1 Beta Express editions were installed, uninstall them all by following the steps that are listed in the How to remove Visual Studio 2008 Express SP1 Beta section in the following Microsoft KB article:

Back to the top

1.	If Visual Studio 2008 SP1 Beta was applied to any non-Express editions of Visual Studio 2008, follow the steps in the How to remove the Visual Studio 2008 SP1 Beta section.
2.	Follow these steps: a. In versions of Windows earlier than Windows Vista, follow these steps: 1. In Control Panel, open the Add or Remove Programs item. 2. Click each instance of Visual Studio 2008, and then click Change/Remove to start the Visual Studio Setup program in maintenance mode. In Windows Vista, follow these steps: 1. In Control Panel, open the Programs and Features item. 2. Click each instance of Visual Studio 2008, and then click Uninstall/Change to start the Visual Studio Setup program in maintenance mode. b. Select the Repair/Reinstall option on the maintenance mode window, and then let the Setup program repair the existing Visual Studio 2008 features.
3.	a. In versions of Windows earlier than Windows Vista, follow these steps: 1. In Control Panel, open the Add or Remove Programs item. 2. Click each instance of Visual Studio 2008, and then click Change/Remove to start the Visual Studio Setup program in maintenance mode. In Windows Vista, follow these steps: 1. In Control Panel, open the Programs and Features item. 2. Click each instance of Visual Studio 2008, and then click Uninstall/Change to start the Visual Studio Setup program in maintenance mode. b. Select the Add or Remove Features option on the maintenance mode window. c. Click to clear and then click to select one of the feature check boxes in the feature tree of the product. Or, add or remove any feature components that you want to modify. d. Click Update, and then wait for the Setup program to update the Visual Studio components that are installed on the computer.
4.	Reinstall any desired Visual Studio 2008 Express edition.

Back to the top

Known issues with the service pack

Visual Studio Team Edition for Software Developers

The Beta release will not update the remote debugger components or the stand-alone profiler unless Visual Studio 2008 is installed on the local computer. After you update Visual Studio 2008 to the SP1 Beta, you can manually copy the updated version of these components to computers that do not have Visual Studio 2008 installed.

Back to the top

For more information, visit the following Microsoft Web site:

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

Back to the top

This article lists the following aspects of Microsoft Visual Studio 2008 Service Pack 1 (SP1) Beta for the Visual Studio Tools for Office System (VSTO) 3.0 Runtime:

•	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

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

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

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

Back to the top

Hotfixes that are included in this service pack

No hotfixes which are included in this service pack.

Back to the top

Features and functionalities that are new, changed, or improved

New features or functionalities

Document-level features are enabled for VSTO add-ins. For example, the ListObject control and managed controls are enabled.

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
301392	The VSTO and Visual Basic for Applications Interop does not work. This behavior causes the EnableVBACallers property to force a VBA error in Visual Studio 2008.
306900	You add a TextBox control in a Microsoft Outlook Form region. Then, you try to copy, cut, or paste from the control by using the keyboard. When you do this, the TextBox control does not work.
311397	The release version of VSTO 3.0 does not release the allocated memory by itself.
328329	The data cache is corrupted when protected word customizations exist.

Back to the top

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:

Back to the top

You may experience one of the following problems when you use Microsoft Visual Studio 2008:

• In Visual Studio 2008 IDE, when you open and edit a segment of relative HTML text that is big and complex, an HTML tag may become distorted. For example, </i> becomes /i>, or </h4> becomes /h4>. Additionally, some HTML fragments may be moved to other locations.
• You open an ASP.NET Web application in Visual Studio 2008 IDE. In the Design view, you select a part of the content, you delete it, and then you paste a segment of text from Microsoft Word or Notepad. When you do this, a random segment of code appears near the previously selected text in the Source view.

This problem occurs because the HTMLed feature ignores the first set of changes from Fpac.msp for the relative page.

To resolve these problems, install Microsoft Visual Studio 2008 Service Pack 1 (SP1). For more information about Visual Studio 2008 SP1, visit the following Microsoft Web site:

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

After you install Visual Studio 2008 SP1, the META tag in FPAC will be changed from <meta name=GENERATOR content=Microsoft FrontPage 6.0> to <meta name=GENERATOR content=Microsoft FrontPage 12.0>. The HTMLed feature will then cover all the changes for the relative page.

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

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 <windows.h>
#include <mscoree.h>
#include <assert.h>
#include <stdio.h>
#include <tchar.h>

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

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

In Microsoft Visual Studio 2005, the following behavior occurs:

•	You perform one of the following actions: • You double-click a Microsoft SQL Server Reporting Services 2005 RDLC file. • You right-click the RDLC file, click Open With, and then click Microsoft Visual Studio 2005.
•	The report design window and the DataSets panel appear. The DataSets panel enables you to drag-and-drop the fields onto the report design surface.

If the DataSets panel is closed in Visual Studio 2005, you can reopen it by using one of the following methods:

•	Press ALT+SHIFT+D.
•	Click Show Data Sources on the Data Design toolbar.
•	On the Data menu, click Show Data Sources.

In Visual Studio 2008, the DataSets panel is not available, and you experience the following behavior:

•	When you press ALT-SHIFT-D, the hotkey sequence does not work.
•	The Show Data Sources button is unavailable on the Data Design toolbar.
•	The Show Data Sources item is not on the Data menu.

Note You can still access the field names by using the expression editor.

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

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

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

File name	File version	File size	Date	Time
Microsoft.reportdesigner.dll	9.0.21022.40	6,094,848	16-Jan-2008	11:38

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, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Source: Microsoft Support

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.

When restoring a maximized or minimized MDI parent form, the height of the restored MDI parent form shrinks.

This behavior occurs when the MDI parent form does not contain a menu, and if it contains a maximized MDI child form. Under these circumstances, the MDI parent window calculates the window size incorrectly when trying to restore from a maximized or minimized window. This is a bug in Windows Forms (System.Windows.Forms.dll) within the Microsoft .NET Framework.

If possible, add a MenuStrip control to the MDI parent form. This is the easiest workaround. Alternatively, you can override the form’s WndProc procedure, and reset the appropriate height of the form when it is restored. The following sample code demonstrates how to do this.

Sample Code in Visual Basic .NET
============================
 
Public Class Form1
    Inherits System.Windows.Forms.Form

    Private currentHeight As Integer
    Const WM_SYSCOMMAND As Integer = &H112
    Const SC_RESTORE As Integer = &HF120

    Protected Overrides Sub WndProc(ByRef m As System.Windows.Forms.Message)
       If m.Msg = WM_SYSCOMMAND Then
          ’Check to see if the window state is being restored.
          ’If so, reset the Height to the value we cached
          If IsRestoring(m.WParam) Then
             Me.Height = currentHeight
          End If
       End If

       ’If the current state is normal (restored), then cache the height
       If Me.WindowState = FormWindowState.Normal Then
          currentHeight = Me.Size.Height
       End If
       MyBase.WndProc(m)
    End Sub

    Function IsRestoring(ByVal WParam As IntPtr) As Boolean
       ‘Used to determine the state of the WParam to see if it is SC_RESTORE
       ’RETURNS: True or False depending on if SC_RESTORE is set

       ’We must determine the size of the pointer from the OS we are using.
       ’If using 32-bit pointers, we need to cast WParam to Int32. If using
       ’64-bit pointers, we cast to Int64. Then we assign to our UInt32 variable.

       ’Note that when processing WM_SYSCOMMAND, we must use the AND operator to combine with &HFFF0 as
       ‘documented on MSDN at http://msdn.microsoft.com/en-us/library/ms646360.aspx

       Dim param As UInt32
       If IntPtr.Size = 4 Then ’32-bit
          param = CUInt(WParam.ToInt32)
       Else
          param = CUInt(WParam.ToInt64) ’64-bit
       End If
       Return ((param And &HFFF0) = SC_RESTORE)
    End Function
End Class

Sample Code in Visual C#
======================
public partial class Form1 : Form
{
   public Form1()
   {
      InitializeComponent();
   }

   private int currentHeight;
   private const int WM_SYSCOMMAND = 0×112;
   private const int SC_RESTORE = 0xF120;

   protected override void WndProc(ref Message m)
   {
      if (m.Msg == WM_SYSCOMMAND)
      {
         //Check to see if the window state is being restored.
         //If so, reset the Height to the value we cached
         if (IsRestoring(m.WParam))
         {
            this.Height = currentHeight;
         }
      }

      //If the current state is normal (restored), then cache the height
      if (this.WindowState == FormWindowState.Normal)
      {
         currentHeight = this.Size.Height;
      }
      base.WndProc(ref m);
   }

   bool IsRestoring(IntPtr WParam)
   {
      //Used to determine the state of the WParam to see if it is SC_RESTORE
      //RETURNS: True or False depending on if SC_RESTORE is set

      //We must determine the size of the pointer from the OS we are using.
      //If using 32-bit pointers, we need to cast WParam to Int32. If using
      //64-bit pointers, we cast to Int64. Then we assign to our UInt32 variable.

      //Note that when processing WM_SYSCOMMAND, we must use the AND operator to combine with 0xHFFF0 as
      //documented on MSDN at http://msdn.microsoft.com/en-us/library/ms646360.aspx 

      UInt32 param;
      if(IntPtr.Size == 4)// 32-bit
      {
         param = (UInt32)(WParam.ToInt32());
      }
      else // 64-bit
      {
         param = (UInt32)(WParam.ToInt64());
      }
      return ((param & 0xFFF0) == SC_RESTORE);
   }
}

Steps To Reproduce Problem
========================
1. Create a new Windows Forms application using Visual Basic 2005 or 2008.
2. For the default form (Form1), set the IsMDIContainer property to True in the Windows Form Designer.
3. On the Project menu, select Add Windows Form.
4. Keep the default name (Form2), and click Add.
5. Save Form2 and close it.
6. Add the following code to the Load event handler in Form1.

Private Sub Form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
   Me.StartPosition = FormStartPosition.Manual
   Dim f2 As New Form2
   f2.MdiParent = Me
   f2.WindowState = FormWindowState.Maximized
   f2.Show()
End Sub

7. On the Debug menu, click Start Debugging. Note that the MDI Parent form is displayed in a restored window, with a maximized child window.
8. Maximize or minimize the MDI Parent form.
9. Restore the MDI Parent form. Note the bottom edge of MDI Parent form has crept up slightly.
10. Repeat steps 8-9 as needed to see the effect occur over time.

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.