Visual Studio 2010 Service Pack 1 Release Notes

License Terms | Visual Studio Blog | Developer Community


This is not the latest version of Visual Studio. To download the latest release, please visit the current release notes for Visual Studio 2019.

Download Visual Studio 2010 Service Pack 1

You can download Visual Studio 2010 from requires a free Dev Essentials subscription, or a Visual Studio Subscription.

Release Notes Icon Visual Studio 2017 2010 Service Pack 1 Release Notes

released on August 18, 2011

What's New in this Release

About Visual Studio 2010 Service Pack 1

Summary: Improvements in this Release

Summary: Issues Fixed in this Release

About Visual Studio 2010 Service Pack 1

Supported Operating Systems

  • Windows Server 2008 R2 (x64-based)
  • Windows 7 (x86-based and x64-based)
  • Windows Server 2008 (all x86-based and x64-based editions) together with Service Pack 2
  • Windows Vista (all x86-based and x64-based editions except Starter Edition) together with Service Pack 2
  • Windows Server 2003 R2 (all x86-based and x64-based editions)
  • Windows Server 2003 (all x86-based and all x64-based editions) together with Service Pack 2


You must have MSXML 6.0 installed to apply this service pack on a computer that is running Windows Server 2003. For more information about how to obtain MSXML 6.0, visit the Microsoft Core XML Services (MSXML) 6.0 website.

  • Windows XP Service Pack 2 (SP2) or a later version of Windows XP
  • Windows XP (all x86-based editions except the Starter edition) together with Service Pack 3

Supported Architectures

  • 32-bit (x86)
  • 64-bit (x64) (WOW)

Hardware Requirements

  • 1.6 gigahertz (GHz) or faster processor
  • 1,024 MB RAM (1.5 GB if running in a virtual machine)
  • 5.5 GB of available hard-disk space
  • 5,400 RPM hard disk drive
  • DirectX 9-capable video card that is running at 1,024 × 768 or higher-resolution display
  • DVD drive

Software Requirements

You must have one of the supported Visual Studio 2010 programs that are listed in the "Applies to" section installed to apply this service pack.

Details: Improvements in this Release

Visual Studio 2010 SP1 includes an update to the Microsoft .NET Framework 4. For more information about the update, read the Microsoft Knowledge Base article 2468871 Update for Microsoft .NET Framework 4.

Debugging Improvements

Visual Studio 2010 SP1 adds the following improvements:

  • Improvements when mini dump files and debugging mini dump files are opened.
  • Improvements to reduce hangs when attaching a process.
  • Reliability improvements in message passing interface (MPI) debugging.
  • Thread slipping improvements during function evaluation.

MFC-based GPU-accelerated Graphics and Animations

Visual Studio 2010 SP1 enables the following two technologies for MFC:

  • Direct2D, a hardware-accelerated, immediate-mode, 2-D graphics API that provides high performance and high-quality rendering for 2-D geometry, bitmaps, and text. For more information, read the Direct2D article.
  • Windows Animation Manager, which enables rich animation of user interface elements. For more information, visit Windows Animation Manager. You can take advantage of these two technologies without breaking the MFC programming model. Additionally, you can find demos in the following directory: drive:\Program Files\Microsoft Visual Studio 10.0\Samples\1033\ For more information about the technology improvements in Visual Studio 2010 SP1, see MFC Additions for Visual Studio 2010 SP1.

New AMD and Intel instruction Set Support

Visual Studio 2010 SP1 adds intrinsic functions or intrinsics to enable the extensions on the AMD and Intel new microprocessors that will be released next year. The intrinsic functions allow for highly efficient computing without the overhead of a function call. For more information about the intrinsics function, see the Compiler Intrinsics article. For more information about the extensions, visit the Intel AVX third-party website.

SQL Updates

Data-Tier Application Project: Data-Tier Application Framework Version 1.1

Visual Studio 2010 SP1 contains the following improvements:

  • DAC upgrades are supported on SQL Azure and on SQL Server.
  • DAC upgrades are now in-place instead of side-by-side.

Technology Improvements

Help Viewer 1.1

To support developer productivity, a stand-alone application for viewing locally is installed in Visual Studio 2010 SP1. The following technology improvements are added in the new local Help viewer:

  • Quick access menu bar icons: Quickly access other high-usage technology improvements or tools. This includes Help Library Manager, Print, Options, and Synchronize topic to table of contents (TOC).
  • Search locally installed content.
  • Search for matching strings within topic.
  • Console views (TOC, Index, Favorite, and Results from Search)
    • Keyword Index topic list
    • TOC view
    • Favorites
    • History
    • Search Results list view
  • Shortcut menus
  • Content window Print topic
  • Options: Change display font size, number of topics in history, and which side the console view is displayed on.

Silverlight 4 Support

Microsoft Silverlight 4 Tools for Visual Studio 2010 is included in Visual Studio 2010 SP1. This adds support for targeting Silverlight 4 in the Silverlight designer and project system. This also provides support for the new Silverlight 4 technology improvements. This new technology includes working with implicit styles and Silverlight 4 Out-of-Browser (OOB) applications. You can automatically start and debug your OOB application from inside the IDE, specify XAP signing for trusted OOB applications, and set the OOB window characteristics.

Basic Unit Testing Support for the .NET Framework 3.5

In Visual Studio 2010 SP1, you now have the functionality to test your applications that target the .NET Framework 3.5.

Performance Wizard for Silverlight

Visual Studio 2010 SP1 enables you to tune the Silverlight application performance by profiling the code. A traditional code profiler cannot tune the rendering performance for Silverlight applications. Many higher-level profilers are added to Visual Studio 2010 SP1 so that you can better determine which parts of the application consume time.

Software Rendering

By default, software rendering is enabled on Windows XP and on Windows Server 2003 to help improve the performance and stability of Visual Studio 2010.

Detecting Mixed-mode Installations

If you install multiple versions of Visual Studio 2010 on the same computer, a combination of program binaries may run in the same instance of Visual Studio. For example, this issue occurs when you have the release version of Visual Studio 2010 Ultimate installed on the same computer where you have Microsoft Visual Basic Express Service Pack 1 installed. This kind of installation may cause stability or functional issues. Visual Studio 2010 SP1 detects whether the installation of SP1 is complete and may prompt you to update it if the installation is incomplete. This makes sure that the installation is in a known, stable state.

Visual Basic Runtime Embedding

A new Visual Basic compiler feature is added that enables Visual Basic developers to target their applications and libraries at platforms where the full Visual Basic Runtime is unavailable. For more information, visit the VB Core – New compilation mode in Visual Studio 2010 SP1 blog post.

Web Development

IIS Express Support

Visual Studio 2010 SP1 enables you to use the Internet Information Services (IIS) 7.5 Express as the local hosting server for the website and Web Application Projects.


IIS 7.5 Express is not included in SP1, and you must download it separately. For more information, visit the VS 2010 SP1 (Beta) and IIS Express blog post.

SQL Server CE 4 Support

Visual Studio 2010 SP1 enables you to manage Microsoft SQL Server Compact 4.0 SDF files in Solution Explorer and in Server Explorer in the context of web projects. Additionally, Visual Studio 2010 SP1 enables you to use SQL Server Compact 4.0 together with the Microsoft ASP.NET Web Forms in a SQL data source control.


SQL Server Compact 4.0 is not included in Visual Studio 2010 SP1, and you must download it separately. For more information, visit the VS 2010 SP1 and SQL CE. blog post.

Razor Support

Changes are made to the web project systems and to the HTML editor to support the new Razor syntax. This new syntax is used by ASP.NET Web Pages and by ASP.NET MVC 3.


Razor is not included in SP1, and you must download it separately. For more information, visit the following blogs:

Web PI Integration

Support for the Microsoft Web Platform Installer (PI) is added in Visual Studio 2010 SP1 as follows:

  • A new toolbar is added that allows for quick access to start the latest version of Web PI. Additionally, if the Web PI was not installed, it is downloaded first.
  • When you open web projects that use IIS 7.5 Express, SQL Server Compact 4.0, or ASP.NET Razor syntax, a dialog box appears that offers to download and install these components by using Web PI if the components are not already installed.

Deployable Dependencies

Some new technology components that are added in Visual Studio 2010 SP1 can be bin-deployed together with an application. Then, you can use the components even when you deploy the application to a server on which those components are not installed. A new dialog box is added in Visual Studio 2010 SP1 that makes it easier to add these deployable dependencies to the web project. To access the dialog box, right-click the project in Solution Explorer, and then select Add Deployable Dependencies. The following components are supported:

  • ASP.NET Web Pages that use Razor Syntax.
  • SQL Server Compact 4.0

For more information, visit the following blogs:

HTML5 and CSS3 Support

Preliminary support is added for HTML5 to the HTML editor so that you can obtain IntelliSense and validation for HTML elements and attributes. A complete version that brings a fuller HTML5 experience will be provided in a future version of Visual Studio. For more information, visit the HTML5 & CSS3 in Visual Studio 2010 SP1 blog.

WCF RIA Services V1 SP1 Included

The WCF RIA service is now localized in 10 different languages that are supported by Visual Studio 2010 SP1. An entity may now contain members of a complex type. For example, you can use the Customer.Address type where Customer is an entity, but Address is not an entity. An entity type may now be used in multiple DomainService classes in the same application. The restriction on how to use a given entity type inside at most one DomainService is lifted. A code generation extensibility point is now publicly available. It may be used for T4-based and other code-generators that are external to the product. Additionally, DataForm Add/Remove operations are now enabled for the EntitySet class and the EntityCollection class.

More Information about Web Development

For more information about other technology improvements in Visual Studio 2010 SP1 for web developers, visit the HTML5 & CSS3 in Visual Studio 2010 SP1 blog post.

XAML Editor/Designer

Go To Value Definition

Lets you navigate directly from controls on a page to the styles that are applied to the controls. This means that you can quickly and easily understand and work with the style and resource structures in the application and finally understand for sure "why that button on your application is red."

Style IntelliSense

Lets you easily modify styles that you already have in XAML. Now you get IntelliSense for properties and their values in a style that is based on the TargetType.

Data Source Selector

Lets you easily select and modify the data source information directly from the design surface.

Advanced Grid Commands

Lets you easily add, remove, and reorder grid rows and columns.

New Thickness Editor

Lets you bulk edit specific items such as margins or padding on multiple controls.

Sample Data Support

Lets you add sample data to see your item templates and bindings light up at design time. Not only does this make hooking up data bindings easier through the Data Binding Picker, it also means that you can design size-to-content and auto layouts much more smoothly. Also, the design time data will flow cleanly between Visual Studio and Expression Blend.

Increased Stability

Many stability improvements were made to Visual Studio 2010 SP1.

Details: Issues Fixed in this Release


ASP.NET Editor

  • The BACKSPACE key and the ARROW keys do not work.
  • Devenv.exe crashes, and an Access Violation error occurs, during *.js auto-formatting.
  • Problems in the "Format Document" command in the JScript Code Editor.
  • The JScript object member is not listed in IntelliSense when the object member contains a $ character.
  • The "Inner" function does not parse correctly. The function returns the "Undefined" command incorrectly when a JScript file is referenced.
  • JScript function formatting problems occur.
  • JScript IntelliSense does not work as expected when it augments an object that is defined by the "Reference" tab.
  • XML comments do not appear in JScript IntelliSense.

Architecture Tools

  • The sequencing of diagrams, the rearrange of the layout, and Lifelines are not resized as expected.
  • You receive the "Item with same key already added" message in a Sequence diagram.
  • Interaction use is missed after the Lifeline group is expanded.
  • You cannot open a diagram if you change an interface's fully qualified name, and the Hide qualified name option is set to True. In this case, a realization to the interface is displayed as a lollipop.
  • Validation is broken for generic parameter references inside a method body.
  • Modeling project allows users to create duplicate named references. This problem can lead to project corruption.
  • A null reference error occurs for explicit interface implementations and transient diagrams when you generate a sequence diagram.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Interaction Messages are now sorted.
  • Backlinks to layer diagram elements from Team Foundation Server work items are now supported.


C Runtime (CRT)

  • MSPDB100.dll is dynamically loaded, but the DLL does not specify a fully qualified path in the CRT.
  • When the the WEOF constant is passed to the "swprintf_s" function, the buffer does not receive a NULL termination.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Performance and stability improvements.
  • More efficient memory management.
  • Other IDE improvements to prevent user interface (UI) freezes and crashes.
  • Performance improvement for the F12 (Goto Definition) function key on large projects.

C# Compiler

  • An Access Violation occurs when you debug a C# structure that has about 500 fields.
  • Designers may not correctly qualify types in code that is emitted.

C# Editor

  • Visual Studio 2010 crashes when it writes code at design time.
  • The MVC3 Razor release candidate may cause an invalid code block indention when the release candidate autoformats a document.
  • In WPF projects, the C# IntelliSense service may crash on shutdown.
  • If the Multi-targeting Pack is not installed, the C# language service crashes when you try to load a project.
  • The "Highlight References" command causes a crash in some cases when a file is being closed.
  • Generate type can cause a crash report when you open the generated file.
  • Smart tags can cause a crash report in some web scenarios.
  • A crash report occurs when you change the Public field to Property.
  • When you pause the pointer over a named argument, QuickInfo crashes if the method name matches the local class name.
  • C# IntelliSense crashes when the Solution Navigator extension is installed, and an "aspx\web" page is opened as an extra file.
  • The BACKSPACE key does not work correctly for Korean characters in the Text Editor.

C++ Compiler

  • C++ compiler generates incorrect movups instructions instead of movss instructions.
  • There is a specific problem with the /Og option in the 64-bit version of Visual Studio 2010 Beta 2 compiler.
  • SSE2 instructions are generated when the /arch:SSE option is specified.
  • There are specific problems in the x64 version of the C++ compiler (optimizer).
  • Destructor calls are missing when optimization is enabled.
  • The compiler crashes with the "decltype(*this)" type specifier.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Optimizations and fixes in several code generation areas.
  • Managed Incremental Build parity with Visual Studio 2008. Previously, the Enable Managed Incremental Build property did not exist when you opened the Project Properties pages for a Visual C++ 2010 project.

C++ Debugging

  • Mixed call stacks are broken when you debug C++ code.
  • When you try to inspect local variables while you are debugging in Visual Studio 2010, you receive a "CXX0017 "Symbol not found" error message.
  • The Watch window displays incorrect values.

C++ Editor

  • Visual Studio 2010 crashes in a C/C++ project when hiding or showing all files of solution.
  • Class member auto-completion forces wrong member (case-sensitive).
  • Go to Declaration is slow in some cases.
  • The C++ Editor may crash when you insert comments.
  • A crash occurs while declaring C++ enumuneration.
  • Issues occurred in native IntelliSense, such as with indexes and reporting.
  • The NavigateTo method in C++ occasionally becomes unresponsive.

Standard C++ Library

  • The "vector::erase" constraint returns an incompatible iterator in the debug build.
  • The * of the "tr1:regex" constraint differs in Visual Studio 2008 and in Visual Studio 2010 when some regular expressions are used.
  • When you use the “std::vector" statement, a memory leak occurs when you run your program.

Concurrency Runtime

  • Fixed concurrent queue access violations.
  • Visual C++ concurrent runtime libraries leak memory in Visual Studio 2010.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Incorrect positive memory leaks are no longer reported when you use Concurrency Runtime (ConcRT).
  • The "__stdcall" calling convention is now supported by all PPL, ConcRT, and concurrent containers.
  • An access violation does not occur on "concurrent_queue" with "std::string."
  • Associated containers can be used with the "parallel_for_each" function.

Code Analysis

  • 538887: Visual Studio crashes occur when you view Code Analysis Settings for Solution that has an IIS site.
  • The Static Code Analyzer reports valid code.
  • Frequent crashes occur when you change Code Analysis settings in Visual Studio Team Server 2010.

Additionally, Visual Studio 2010 SP1 contains the following improvement:

  • Managed Code Analysis (FxCop) now installs on x64 TeamBuild servers.

Code Discovery and Validation

  • Crashes that occur with graph navigation are fixed.
  • A scroll-bar UX issue inside the Architecture Explorer’s advanced selection menu is fixed.
  • Temporary files remain after layer validation is run.
  • The "Contained By" action on a C++ folder may cause Architecture Explorer to crash.

Entity Framework (Code Generation)

  • Problems occur when you use Entity Framework Self Tracking Entities together with AppFabric CACHE (‘Velocity’) and the .NET Framework 4.0 release version.
  • When you use an Edmx file together with ADO.NET, the Self-Tracking Entity Generator causes generated files that cannot be compiled because of a missing HandleCascadeDelete event handler.
  • A Self-Tracking Entity Template does not generate code for function imports that do not have a return value.
  • An Entity does not get marked as modified when an FK association that uses the EntityReference.EntityKey property is nulled.
  • A Self-Tracking Entities Template generates incompatible code for dot-separated namespaces.
  • A Self-Tracking Entities Template does not generate default values for scalar properties on complex types.
  • Miscellaneous code-generation changes to comply with Visual Basic pretty-lister guidelines.


Visual Studio 2010 SP1 fixes issues with stability of the compiler and code correctness for generated code. For example, this service pack fixes calling convention correctness for platform invoke and emitting XML document comments for extension methods. Additionally, this service pack improves the performance of generating an event hook up.

JScript Editor

  • Extra space is added under the code when the Keep tabs option is selected.
  • Indentation is incorrect for empty object literals.
  • The JScript function formatting option Parens does not function as "worded parentheses."
  • The keyboard shortcut ALT+A is used incorrectly for the Insert space after function keyword for anonymous functions command.
  • Atlas IntelliSense is not present when script manager has a ServiceReference http path.
  • The memory of the Visual Studio process increases to 300 MB when you open another project, you leave the current project open, and the current project has lots of JScript files that are opened.
  • No IntelliSense exists inside a ForIn condition.
  • Very large memory growth occurs when you comment or uncomment large JScript files.
  • Typing is very slow in a JScript file that has long content on one line.
  • Global members that come from external files cannot find IntelliSense.
  • Loss of colorization and IntelliSense occurs after you update IntelliSense to reference a remote or non-existing service.

Microsoft Foundation Classes (MFC) and Active Template Library (ATL)

  • In the CDatabase/Crecordset MFC, the "DoFieldExchange" variable does not work correctly in Visual Studio 2010.

Additionally, Visual Studio 2010 SP1 improves security and performance and provides other improvements in ATL/MFC.

Visual Basic Compiler

  • A crash may occur when you type near the ReadOnly property, and multiple field declarations are present.
  • When any local's type comes from a signed assembly, Visual Basic does not show values in the Locals window.
  • In large projects that contain many XML doc comments, you may experience delays in the editor when you type.
  • When you switch the focus between expression fields, you may experience delays in large Workflow Foundation projects.

Visual Basic Editor

  • Mandatory ByVal is displayed in Visual Basic .NET.
  • IntelliSense Enum values are not shown.
  • A large Visual Basic project may crash when it is closed.
  • The Visual Studio IDE becomes unresponsive when it parses XMLDOC comments in a complex project.
  • The Visual Basic Language Service crashes when you open a web project.

Windows Forms Designer

  • You use the Visual Studio 2010 IDE to open a project that is in an earlier version. For example, you open a Visual Studio 2008 project. After a debug session, you cannot rebuild or debug the project again, and you receive an error message that resembles the following:

Unable to copy file obj\Debug\assembly_name to bin\Debug\assembly_name. The process cannot access the file bin\Debug\assembly_name because it is being used by another process.

  • If you rename or undo a paste of Windows Forms controls in the designer, the designer file leaks during the Visual Studio 2010 instance.
  • You upgrade a Visual Studio 2005 project to Visual Studio 2010, and you retarget the project to the .NET Framework 4. When you close the Visual Studio instance, a supported language version of Visual Studio may crash.

Database Projects

  • Database Project deployment fails when you try to revoke permissions by using the GRANT OPTION permission.
  • Customized .dbschema files that contain nonprintable characters cause Visual Studio to crash when you try to upgrade a model.
  • The "Schema Compare" feature ignores composing children when the Only compare elements that exist in the source item is enabled.
  • An Incremental Database Project deployment becomes unresponsive when the project contains long check constraints that have to be normalized.
  • Index Hints do not resolve across database references in a database project build.


  • Debugger randomly treats "step-into" and "step-over" procedures as a "run to completion" procedure.
  • Visual Studio 2010 hangs after several debugging sessions, and a blank Windows Internet Explorer window appears.
  • Pinned debug values.
  • Visual Studio crashes when it imports the same Data Tip that was previously exported.
  • When you perform client-side debugging, you receive the following error message:


Error: The breakpoint will not currently be hit. This location could not be mapped to client side script.

  • Only 100 "std::map" elements are allowed in the debugger.
  • Using Source Server tagged PDBs causes Visual Studio 2010 to hang and then crash.
  • Some issues on event tracing in Windows Presentation Foundation (WPF) are fixed.


  • Log files are removed for the Disk Cleanup operation.
  • Crashes that were introduced in customer's application are fixed.
  • A crash that occurs when you switch to the Disassembly window you enter Historic Mode is fixed.
  • Crash-on-exit because of putting a trace file in Run mode is fixed. ####IntelliTrace for 64-bit and SharePoint IntelliTrace is the revolutionary new debugging technology in Visual Studio 2010 that enables you to move forward and backward through a debug session. However, because of time constraints and because it is a completely new feature, this technology does not work in all scenarios. Visual Studio 2010 SP1 enables the IntelliTrace debugging technology on 64-bit solutions and for Microsoft SharePoint farm solutions.


  • The Performance Explorer does not load when multiple Visual Studio instances are started.
  • JScript profiling does not work on Russian and other European and Latin American language operating systems.
  • JScript profiling does not work with Windows Internet Explorer 9.
  • Visual Studio crashes when you profile a Web Application project by using a customer web server setting.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • More accurate sampling in Hyper-V.
  • Improved JavaScript profiling to enable profiling of multiple processes.
  • Improved stability it performs 64-bit profiling.

Setup Projects

  • The Registry Capture Utility crashes on a computer that is running Windows 7.
  • Visual Studio may crash when you configure prerequisites.
  • A Setup project compilation fails when you run it from the command line.
  • Migrating Setup projects from Visual Studio 2008 to Visual Studio 2010 changes component GUIDs, and this causes the upgrades to fail.
  • The Devenv.exe command in Visual Studio 2010 hangs randomly while a Setup project is built from a command line.
  • The IDE crashes when you close a Setup project or a Deployment Projects Setup project.
  • The RestartWWWService=false command incorrectly restarts the WWW service on a computer that is running Windows Server 2003 when projects are built by using Visual Studio 2010.


Visual Studio 2010 SP1 contains the following improvements:

  • Customize or extend T4 templates by using template inheritance.
  • Use helper libraries with T4 much more easily because T4 no longer locks referenced assemblies in memory.
  • Deploy T4 to your build server for build-time generation.


  • In the Release Candidate for Visual Studio 2010, the "DataContext" field is not visible when the "Show only DataContext objects" check box is selected.

Web Development

Web Projects

  • The ASP.NET App_Themes folder does not allow for adding a new CSS style sheet.
  • The .designer.cs style sheet does not work as expected with nested web application projects.
  • SCC glyphs are not displayed in Solution Explorer.

HTML Designer

  • Style sheets that are external to a web application are not applied in Visual Studio .NET 2010 IDE design view.
  • HTML Designer cannot be used as expected to design web pages.

Windows Phone Developer Tools

The deployment of XAP files over 64 MB may fail for testing and debugging on physical telephone devices.

General WPF and Silverlight Designer

  • When you use the "Choose Toolbox Items" dialog box, you must manually kill the process, the application becomes unresponsive, and data loss and GUI corruption occur.
  • The IDE locks completely when you try to add Silverlight items to the toolbox.
  • Upgrading Silverlight while Visual Studio is running causes Visual Studio to crash.
  • Deleting controls that have a background thread running causes Visual Studio to crash.
  • The error list is not displayed when XAML files that contain errors are opened.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Performance improvements when you select a different color profile are added.
  • The Save dialog box appears when you close a solution after an event in Visual Basic is generated.
  • Support for portable assemblies is added.


XAML Designer Design Surface

  • The Binding feature in WPF does not work as expected.
  • An "inherit and overwrite" pattern in XAML is reported as "detected loop."
  • The Visibility property is now respected at design time.
  • A memory leak occurs when you drag controls from the toolbox to the design surface.
  • A System.InvalidOperationException exception occurs when you start the design surface after you add an event.
  • An error message dialog box appears when you move parent controls into an expander.
  • Control creation when the root element’s child is an expander.
  • Controls may move in a container that has the FlowDirection property set to RightToLeft.
  • You cannot open the designer for files that use Silverlight Toolkit Data Visualization components.
  • Expander stays expanded during design time when it should be collapsed.
  • Controls snap to minor gridlines.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • The snapping of controls is reduced in a ScrollViewer control.
  • The user code that may cause an unhandled exception on the gold bar is now displayed.

XAML Refactoring

  • When you rename a type, properties of the type are not renamed in the XAML files for Visual Basic.
  • Workflow files that are XAML-based pick up refactoring events from the code that is behind the workflow files.
  • Refactoring and “Go to Definition” do not work as expected when you interact with XAML files, and the XAML file is not open.
  • After you rename a class, event handler does not generate the events for the renamed class.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Support for refactoring types in the TypeArguments attribute is added.
  • Support for refactoring namespaces that include assembly in definition is added.

XAML Property Inspector

  • The StyleTypedProperty property is not supported by the Style Chooser.
  • The XAML StringFormat editor does not support double-escaped characters.
  • When the XAML editor is pinned, and you set bindings or resources, keyboard focus may be lost.
  • The “Go to value” definition displays an error message dialog box when the definition points to an Application XAML file.
  • Attached properties in the Property Inspector disappear after you build the solution.
  • When the brush editor is pinned, it can cause the same property to appear multiple times within the property inspector.
  • The Content property cannot be displayed when the property inspector is sorted by source.
  • An error occurs if you open the Databinding Picker when the DataContext is set to CollectionViewSource.
  • An error occurs if you apply a style that is loaded from another project by using the resource picker.
  • Excess attached properties are displayed unexpectedly.
  • The Expand or Collapse state of the Property category is not persisted after build and run.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • Support for setting attached properties that have the same name but different namespaces in the property inspector is added.
  • Support to add inheritance as a possible source indication for the property marker in the property inspector is added for Silverlight project.

XAML Editor

  • An AppDomainUnloaded exception may occur in the Visual Studio 2010 XAML editor. This problem may be caused by obtaining IntelliSense on a Grid's x:Name.
  • Visual Studio 2010 XAML IntelliSense may fail unexpectedly.
  • At design time in the Design pane, you cannot see applied custom Styles for controls. However, everything looks fine at run time.
  • Visual Studio 2010 Premium edition may crash when you select an IntelliSense item.
  • The XAML editor may become unresponsive when you edit a VisualStateGroup object.
  • An error may not be cleared after the XAML is temporarily put in an invalid state.
  • Erroneous squiggles may appear for attached properties, and this prevents the design surface from working.
  • An incorrect error may occur when you set the StrokeThickness property to 0 on Rectangles.
  • When you use by using CTRL+M to collapse XAML, Visual Studio may crash.
  • Style IntelliSense for Silverlight does not show classes in the same namespace as the application.

Visual Studio Editor

  • CTRL+BACKSPACE deletes too much text.
  • The "Find and Replace" window is moved off-screen after text is replaced.
  • Visual Studio 2010 crashes when the source file contains non-Unicode characters.
  • Viewing a "List" command at debug-time no longer enables you to see the Items property.
  • Selection navigation does not work as expected.
  • Caret is off-screen during CTRL+ARROW word selection.
  • Horizontal auto-scrolling does not work with CTRL+SHIFT.
  • The CTRL+SHIFT+ARROW key combination to select text goes out of view.
  • The Visual Studio 2010 Copy command generates RTF that causes an error to occur.
  • Garbled code occurs when you copy Visual Studio 2010 code that contains Chinese characters to Word 2010.
  • You cannot copy and paste Korean characters by using the Visual Studio 2010 Code Editor.
  • When you copy source code that contains Japanese characters, the source code cannot be pasted to Microsoft Word 2010 correctly.
  • Garbled characters occur when the source code is copied and pasted to Microsoft PowerPoint 2010.
  • The Visual Studio 2010 IDE may crash when you expand regions that were already expanded.
  • The Visual Studio 2010 IDE may crash when you change the color settings.
  • Visual Studio 2010 may crash when you start the WPF Editor.
  • An Out-Of-Memory issue occurs when you copy by using statements.
  • After you perform a Cut action for text, you cannot paste the text.
  • When you stop doing extra layouts during the statement completion, the pop-up time can be shorten by 30 to 40 percent.
  • The Replace in Files action reports incorrect results.

Visual Studio Extensibility

  • The "Solution/Project Loading" dialog box does not show the Isolated Shell application name as the title.

Visual Studio Shell

  • Context menus scroll even if there is room to show them.
  • The "Find and Replace" window grows wider every time that it is opened.
  • Visual Studio crashes when you click a menu separator.
  • Visual Studio crashes with a COM Exception every time that you close it.
  • Visual Studio crashes when it closes.
  • Visual Studio crashes when you use AMD CodeAnalyst.
  • Visual Studio restarts every time that you try to close it.
  • Loading a solution by double-clicking its file causes unnecessary DLLs to be loaded.
  • Idle time processing inside Visual Studio causes unnecessary thread context switching.
  • The progress dialog box that appears for certain scenarios. For example, the Go To Definition for C++ projects takes longer than expected to finish.
  • LightSwitch does not load when you run "devenv /safemode" mode.
  • The Editor stops responding when you open .aspx and .js files by using Telerik.
  • Removed For evaluation only from the Express splash screen.
  • Screen readers and tablets cause Visual Studio to crash when the pointer is pausing over the Undo button.
  • Visual Studio crashes when you close a floating group of multi-instance tool windows.
  • Visual Studio crashes when you undo a file checkout.

Visual Studio Test

Web/Load Test

  • WebTest Results viewer may crash when a test is executing.
  • An OutOfMemory exception is thrown when you perform the Find/Replace action in a request.
  • The Devenv.exe process crashes after you click the "threshold violations" hyperlink in the test result status bar.
  • Counters on the "Page Response Time" graph disappear after the run is finished.
  • Writing results to the LoadTest DB takes longer than expected to finish.
  • Performance Counters are dropped during load test execution.

Visual Studio Tools

Visual Studio Tools for Office (VSTO)

  • Marking Form Region as localizable breaks Visual Studio editor.
  • Additionally, Visual Studio 2010 SP1 improves performance on the VSTO Runtime.

Visual Studio Tools for SharePoint

  • Adding a CAS permission set to a package manifest template causes F5 deployment to fail.
  • Visual Web Part code generation that is sandboxed fails if the ASCX file exceeds a certain length.

Visual Studio Data Tools

  • The Auto-Generated Code of TableAdapterManager class of the Dataset Designer differs in Visual Studio 2008 and in Visual Studio 2010.
  • Data Repeater cannot bind to image in the data sources window.

Unit Test/Test Execution

  • A race condition exists in the test controller that causes tests to go into the "Not Executed" state.
  • A test run stops responding when the QTAgent fails to start or the test run stops responding in the Main() function.
  • The TestContext output is incorrect for inner tests that are contained inside an Ordered test.
  • A performance issue occurs when a test is loaded in test controller.
  • Running large amount of tests on a lab environment leaves some tests in the "Not Executed" state.
  • Code coloring for code coverage is not working for unmanaged C++ code.
  • The TestCaseId property comes out to be the same for all test cases that are associated with the same test method.

TCM Server

  • The warehouse rebuild takes longer than expected to finish.
  • Resetting automated test results can cause two changes of a point to appear in the warehouse as the current version.

Microsoft Test Manager

  • The "Configure Diagnostic Data Adapter-Event Log" page is truncated in different language versions of Microsoft Test Manager.
  • Analyzing test results causes the result to become the most recent result in the test point trend.
  • The Right-To-Left language settings do not persist across MTM sessions.
  • Query-based test suite repopulation takes longer than expected for large suites.
  • A crash may occur you select the browser type for Firefox playback in the Microsoft Test Runner.
  • You cannot collect Intellitrace data if the application that is being tested is started as a part of action recording for the test case.
  • The attachment count for test results returns 0 when iterating through large amounts of test results.
  • You cannot bind the "parameter to password" field when you create action recording.

Additionally, Visual Studio 2010 SP1 contains the following improvements:

  • The test case description can be shown in Microsoft Test Manager.
  • Performance improvements for Microsoft Test Manager are provided.
  • Support for Expression Encoder 4.0 in manual testing is added.

Lab Manager

  • Cannot change the Microsoft System Center Virtual Machine Manager (SCVMM) server that is configured for a TFS Application Tier.
  • A Build deploy/test workflow cannot use drop locations on DFS or on WebDav shares.
  • You cannot select a configuration for existing builds that have more than one configuration in a Build deploy/test workflow.
  • The Build Service Host crashes if it is running in "Lab Mode," and the service account does not have administrative credentials.
  • When the build agent and the lab agent are installed on a non-lab managed virtual machine, the build agent does not start.

Fast Forward/Coded UITest

  • Coded UI test projects are incompatible with Setup and Deployment projects in the same solution.
  • A UITestException exception is thrown in the BrowserWindow.FindMatchingControls method.
  • UI Test controls that are added to UIMap are case-insensitive.
  • Creating a Coded UI Test from an existing action recording do not display in the alternative credentials dialog box.

Additionally, support for recording and playback of code UITest is added for Internet Explorer 9 Beta in Compatibility View.

Known Issues

Help Library Manager

  • Issue:

    The Help Library Manager does not support multiple concurrent sessions.

  • Workaround:

    There is no workaround.

Help Library Agent

  • Issue:

    The Help Library Agent does not restart after content update. The Help Library Agent may crash when you first start it without content. When you navigate to invalid URLs, the agent does not show the Content Not Found page.

  • Workaround:

    There is no workaround.

Installation Can Cause the Installed Update List to Erroneously List Hotfixes

  • Issue:

    Visual Studio 2010 Service Pack 1 can cause several entries to be created in the Installed Updates list. The entries are labeled “Hotfix for Visual C++ Standard 2010 Beta 1” along with a KB number. Microsoft has confirmed that no Beta fixes were installed with Visual Studio 2010 Service Pack 1, and that the fix for each of the hotfixes listed was included in Visual Studio 2010 Service Pack 1.

  • Workaround:

    There is no workaround for this issue. No "Beta 1" hotfixes are installed on your system. You cannot uninstall the updates or remove the entries from the Installed Updates list because no files are actually installed on your system.

Known Issues with Using Microsoft Update

  • Issue:

    When you install this service pack, the installation process may continue and finish successfully if you try to stop the installation. This issue may occur when the installation process is over half complete. If you start the installation process by selecting the "Download updates but let me choose whether to install them" option, and then select the "install update then shutdown" option, the service pack installation may fail. After the computer restarts, you will be offered this service pack again, and installation will complete successfully. If you uninstall the service pack from a non-English version of Visual Studio 2010Ultimate, Visual Studio 2010 Premium, or Visual Studio 2010Professional users, you will be offered to install the service pack again. However, the installation process will fail because components of this service pack are in an unexpected state. To successfully reinstall this service pack, follow these steps:

  • Workaround:

    1. Start Visual Studio setup in Maintenance Mode from the Programs and Features item in Control Panel, or by running Setup.exe.
    2. Select Add or Remove Features.
    3. Select Microsoft Office Developer Tools, and then click Update. When the setup is complete, reinstall the service pack.


  • The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
  • Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


Article ID: 983509 - Last Review: Jul 10, 2017 - Revision: 2 Applies to:

  • Microsoft Visual Studio 2010 Premium
  • Microsoft Visual Studio 2010 Professional
  • Microsoft Visual Studio 2010 Ultimate
  • Microsoft Visual Studio Lab Management 2010
  • Microsoft Visual Studio Team Agents 2010
  • Microsoft Visual Studio Test Professional 2010
  • Visual Studio 2010 Tools for Microsoft Office Runtime

Top of Page