Release Notes

Microsoft Surface SDK 1.0 SP1

Microsoft Surface Runtime 1.0 SP1

Version: March 30, 2009

Copyright
This document is provided for informational purposes only, and Microsoft makes no warranties, either express or
implied, in this document. Information in this document, including URL and other Internet Web site references, is
subject to change without notice. The entire risk of the use or the results from the use of this document remains with
the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses,
logos, people, places, financial and other data, and events depicted herein, are fictitious. No association with any real
company, organization, product, domain name, e-mail address, logo, person, places, financial or other data, or events
is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced
into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording,
or otherwise), or for any purpose, without the express written permission of Microsoft.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering
subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the
furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, DirectX, Expression Blend, Microsoft Surface, Windows, Windows Vista, Visual C#, Visual Studio, and XNA
are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

2
Contents
Introduction __________________________________________________________________________________________________ 4
What’s New ___________________________________________________________________________________________________ 4
Runtime Platform Upgrades _______________________________________________________________________________ 4
Microsoft Surface APIs and Controls _______________________________________________________________________ 4
API Enhancements _________________________________________________________________________________________ 5
Developer Tools ____________________________________________________________________________________________ 6
System-Wide Functionality _________________________________________________________________________________ 6
Vision System ______________________________________________________________________________________________ 8
Shell ________________________________________________________________________________________________________ 8
SDK Documentation________________________________________________________________________________________ 8
Known Issues _________________________________________________________________________________________________ 9
General _____________________________________________________________________________________________________ 9
Setup ______________________________________________________________________________________________________ 10
APIs and Controls _________________________________________________________________________________________ 11
Vision System _____________________________________________________________________________________________ 12
Shell _______________________________________________________________________________________________________ 13
Surface Simulator _________________________________________________________________________________________ 15
Surface Stress _____________________________________________________________________________________________ 16
SDK Samples ______________________________________________________________________________________________ 16
Related Documents __________________________________________________________________________________________ 16

3
Introduction
This document describes the current features and known issues for Microsoft Surface™ SDK 1.0 SP1 and
Microsoft Surface Runtime 1.0 SP1.

What’s New
This section lists new features and modifications in Microsoft Surface SDK 1.0 SP1 and Microsoft Surface
Runtime 1.0 SP1.

Runtime Platform Upgrades

Microsoft Surface 1.0 SP1 now includes the following platform upgrades:
 Required. Windows Vista® Service Pack 1 (SP1).
 Required. Microsoft® Visual Studio® 2008 SP1 or Microsoft Visual C#® 2008 Express Edition SP1.
 Required. .NET Framework version 3.5 SP1 (includes WPF).
 Support for Microsoft XNA® 3.0 and XNA 2.0. Microsoft Surface SDK 1.0 SP1 includes project
templates for building applications with the XNA 3.0 Content Pipeline.

Microsoft Surface APIs and Controls

The following list describes the high-level changes in the Microsoft Surface APIs and controls:
 Added the ElementMenu control (a context menu that is associated with specific pieces of
content) to enable users to perform simple gestures to quickly execute commands on any
interface element.
 Added the LibraryBar control to enable users to quickly scroll through large collections of items.
 Added the LibraryStack control to enable users to browse a collection of items one at a time.
 Added the LibraryContainer control to enable users to dynamically switch between viewing a
collection of elements as a LibraryBar control or a LibraryStack control.
 Added the drag-and-drop framework to enable developers to customize hit-testing rules, visual
cues on the containers, and graphics for the object that is being dragged. The drag-and-drop
framework is enabled by default on the library controls, and it is demonstrated in the updated
Shopping Cart sample.
Microsoft Surface 1.0 SP1 includes the new ContactVisualizer control with the following features:
 Added contact visualizations that provide users with instant and consistent visual feedback when
they touch the Microsoft Surface screen. These visualizations increase user accuracy by showing
users how their touches are recognized, increases playfulness by making all of the screen
interactive, and minimizes confusion when direct manipulations are not possible (such as when
users try to enlarge content that is at its maximum size or when users try to rotate content that
cannot rotate).
 Enabled developers to customize the colors, placement, and other aspects of the contact
visualizations, and enabled administrators to disable the effects by using configuration files.
Microsoft Surface 1.0 SP1 includes a sample XNA interface framework (Core Interface Framework) with the
following features:

4
  Added a flexible XNA interface framework to enable applications to manage input routing and
multi-capture.
 Included state machines (Button, ListBox, ScrollViewer, and ScrollBar) for common controls to
provide a consistent interaction model across all applications with any interface framework.
 Added APIs for improved flexibility that are independent of how the applications perform hit
testing and interface rendering.

API Enhancements
Microsoft Surface 1.0 SP1 also includes a variety of API enhancements that improve developer usability
and productivity. For more information, see the Microsoft Surface SDK documentation.
ScatterView class:
 Added the CanMove property to enable applications to lock items in place while still allowing
users to rotate, scale, and interact with the content.
 Added the IsTopmostOnActivation property to enable applications to override the ScatterView
control’s automatic z-order management behaviors.

TagVisualizer class:
 Added the TagVisualizationDefinition.Matches property as a virtual method that enables you to
create custom definitions to support scenarios such as value ranges.
 Added the TagVisualizer and ScatterView interop to enable an item to seamlessly switch
between tracking a tag or being manipulated by a finger.
 Added the TagVisualizer and ManipulationProcessor interop to enable a manipulation to be
based on the smoothed and offset position of a TagVisualization object rather than the exact
position of the tag.
 Added the TrackedContact property to expose the contact that a tag visualization is currently
using.
 Added the OffsetOrigin property to simplify the task of aligning visualizations with the edge of
an object rather than with the center of an object.

Contact class:
 Added the IsCapturedWithinElementBounds property to quickly determine whether a contact is
physically inside the element it is captured to.

SurfaceSlider class:
 Added the SnappedValue property to report the nearest tick value in addition to the thumb’s
intermediate value while a thumb is being moved.

GlobalizationSettings class:
 Added the read-only CurrentCulture and CurrentUICulture properties.
 Added the ApplyToThread( ) and ApplyToCurrentThread( ) properties.

SurfaceKeyboard class:
 Added the read-only IsNativeInputAllowed property.

5
SimulatedContactScript class:
 Added this class to automate the playback of a recorded Surface Simulator script.

Microsoft Surface 1.0 SP1 includes the following new base classes to derive controls from:
 SurfaceSelector
 SurfaceHeaderedItemsControl

Developer Tools
Developer tools are computer applications and samples that help you develop Microsoft Surface
applications. These tools include the following changes for Microsoft Surface SDK 1.0 SP1.
Microsoft Surface SDK, Workstation Edition installer:
 Included a separate, smaller Microsoft Surface SDK package to use on developer workstations.
 Enabled installation on additional versions of the Windows Vista operating system and the
Windows 7 operating system. (However, Windows 7 is unsupported with the Microsoft Surface
SDK.)
Surface Simulator:
 Added the SimulatedContactScript class, which automates the playback of a recorded Surface
Simulator script.
Samples:
 Added the Item Compare sample application.
 Added the tag-tracking and hit-testing technical sample.
 Added the Cloth sample to demonstrate the Core Interaction Framework state machines.
 Updated the XNA Scatter sample to demonstrate the multi-capture APIs.
 Updated the Shopping Cart sample to demonstrate the new drag-and-drop framework.
Stress test tool:
 Added a command-line tool to send simulated input to applications until they break.
 Enabled options to set the input to random and to specify seed values for reproducibility
purposes.
 Enabled input to be parameterized by types, sizes, velocities of contacts, regions where the
contacts should appear, the rate of appearance, the contact density, and whether the simulated
contacts can touch the Surface Shell access points.
 Enabled input to come from pre-recorded Surface Simulator scripts.

System-Wide Functionality
Microsoft Surface 1.0 SP1 includes new features that benefit the entire Microsoft Surface platform.
Service applications:
 Added support for Microsoft Surface service applications that do not have interfaces and that
persist across user sessions.

6
  Enabled the Microsoft Surface Loader to automatically restart the service applications if they fail
(that is, crash).
 Enabled service applications to initiate user notifications and to start other Microsoft Surface
applications.
 Added notification APIs to enable developers to specify which application to start and which
custom icon to display.
 Enabled service applications to register for end-session events.
Manageability improvements:
 Added the Microsoft Surface 1.0 Management Pack for Microsoft System Center Operations
Manager 2007 that you can download to help monitor the health of your Microsoft Surface units.
The pack monitors critical processes and services, automatically recovers stopped services,
monitors the unit’s fans and temperatures, collects and provides graphs for temperature
performance counters, alerts you when units are not in user mode, and collects and provides
graphs for the vision system’s frame rate performance.
Note: The pack is available from the Microsoft Surface Community Web site, separate from
Microsoft Surface 1.0 SP1.
 Integrated Microsoft Update and Windows Update so you can be notified when updates are
available for the Microsoft Surface platform.
 Added the Microsoft Surface Customer Experience Improvement Program (SCEIP) so you can
automatically send software usage data that helps improve future releases. This data does not
intentionally include any information that could be used to identify you.
International support:
 Localized the user and administrative interface text into nine languages, including Danish, Dutch,
English, French, German, Italian, Korean, Norwegian, Spanish, and Swedish.
 Included support for Microsoft Surface to automatically display interface text in any language or
locale that is supported by Windows Vista. (The interface displays English if the appropriate
language isn’t found.)
 Enabled application descriptions and out-of-order text to be customized into any language.
 Customized the on-screen keyboard to support 19 international layouts.
 Added Microsoft Surface interface language, locale, and keyboard layouts that you can configure
independently from equivalent Windows settings.
 Set up Microsoft Surface localization settings to automatically apply to all Microsoft Surface
applications.
 Enabled developers to follow standard .NET localization guidelines in most applications, and
included new APIs to retrieve and apply globalization settings.
 Included an updated Controls Box sample application with English and Spanish versions to
demonstrate the localization process.
 Enabled testing of multi-language applications on any version of Windows Vista.

7
Vision System
The Vision System tracks all the interactions on a Microsoft Surface unit. The Vision System includes the
following changes for Microsoft Surface 1.0 SP1:
 Improved tag detection and tracking.
 Added new tools to help you generate and print identity tags, including a Windows tool, a
command-line tool, and APIs to build custom tools.
 Simplified the calibration process by adding calibration guides so you do not have to use an
external monitor.

Shell
Surface Shell hosts all Microsoft Surface applications. It includes the following changes for Microsoft
Surface 1.0 SP1:
 Improved the discoverability of the access points.
 Added contact visualizations to the Launcher menu, loading screens, and out-of-order screen.
These visualizations provide users with instant and consistent visual feedback when they touch
anywhere on the screen. The visualizations also increase user accuracy by showing users how their
touches are recognized and increase playfulness by making the out-of-order screen, loading
screens, and other non-content elements interactive, and the visualizations minimize confusion
when direct manipulations are not possible (such as on the loading screens).
 Added a branding animation to the first session use of the access points.
 Added a new audio scheme based on the Microsoft Surface brand.
 Added object routing so users can open an application whenever a tagged object that is
configured to work with the application is placed on the Microsoft Surface screen. (For example, a
user could place a card that includes a tag on the screen to open a trivia game.)
Microsoft Surface 1.0 SP1 also introduces single-application mode, which includes the following features:
 Added the ability to run only one application on a Microsoft Surface unit in a way so that users do
not need to start the application.
 Designed the mode so the Launcher menu is hidden and access points are inactive. (Smaller, non-
interactive Microsoft Surface branding is still present in the corners.)
 Made the error interface text bi-directional for users to view it on either side of the Microsoft
Surface unit.
 Added the ability to set up the initial orientation through the registry.

SDK Documentation
The Microsoft Surface SDK documentation is the Help file that features expandable topics. It is integrated
with Microsoft Visual C# 2008 and Microsoft Visual Studio 2008. The documentation includes the
following changes and additions for Microsoft Surface SDK 1.0 SP1:
 Added the Programmer’s Guide section that covers the following topics:
o The ScatterView control

8
 o The manipulations and inertia processors in XNA and WPF
o Microsoft Surface service applications
o Localization of Microsoft Surface applications
o Designing tag-driven applications
o Using tag visualizations
o The drag-and-drop framework
o The ElementMenu control
o The LibraryContainer, LibraryBar, and LibraryStack controls
 Expanded the How Do I…? section with step-by-step instructions for implementing specific
solutions.
 Added information about setting up a Microsoft Surface unit to run in single-application mode.
 Added information about deploying object routing for starting applications from tagged objects.
 Added information about customizing contact visualizations for user feedback.
 Added more information about deploying Microsoft Surface applications, including localized
applications (recommended for anyone developing a setup program for a Microsoft Surface
application).
 Added detailed information about the Core Interaction Framework, which enables developers to
implement WPF-like controls in XNA applications. (For more information, see the "Core
Interaction Framework" section under Samples in the Microsoft Surface SDK Help file and see the
CoreFramework.chm file in the samples ZIP file.)
 Added information about the Surface Stress tool.
 Added more information about tagged objects, including how to print your own identity tags and
how to use them in your applications.
 Added information about three new samples to the Samples section.
 Added complete API coverage for all the new classes in the Class Library Reference section.
 Added new code examples in the Class Library Reference section.
 Updated the screen shots throughout the Microsoft Surface SDK documentation to reflect the
final release visuals.

Known Issues
This section lists known issues in Microsoft Surface SDK 1.0 SP1 and Microsoft Surface Runtime 1.0 SP1.

General

Not all desktop shortcuts are translated [31359]

Some desktop shortcuts are not translated in administrator mode for localized Microsoft Surface versions.

9
Internal card reader [17870]
Older Microsoft Surface units might include an internal card reader. This internal card reader is not
supported and currently deployed Microsoft Surface units do not include it.

SurfaceShell and WPF applications might take over 30 seconds to load [13367]
WPF applications might take over 30 seconds to load. For more information, see FIX: A .NET Framework
2.0 managed application that has an Authenticode signature takes longer than usual to start in the
Microsoft Knowledge Base.

Setup

Setup can fail when switching between elevated and non-elevated Command Prompt windows
[17870]
If you start to run Microsoft Surface Setup from a non-administrator Command Prompt window and then
change to an administrator Command Prompt window, an error message displays, “The system cannot
open the device or the file specified.”
Workaround:
1. Delete the files from the \ProgramData\Applications\Cache folder.
2. Run Microsoft Surface Setup again from the elevated Command Prompt window.

Microsoft Surface SDK 1.0 SP1 Software Requirements

Microsoft Surface SDK 1.0 SP1 installs only on a Microsoft Surface unit. To develop applications by using
Microsoft Surface SDK 1.0 SP1, you need the following software:
 A 32-bit version of Windows Vista Business
 Windows Vista Service Pack 1 (SP1)
 Microsoft XNA 2.0 Redistributable
 Either Microsoft Visual C# 2008 Express Edition SP1 or Microsoft Visual Studio 2008 SP1. (You
must install C# project support to install Microsoft Surface SDK 1.0 SP1.)
 .NET Framework version 3.5 SP1

Microsoft Surface Runtime 1.0 SP1 Software Requirements

Microsoft Surface Runtime 1.0 SP1 installs only on a Microsoft Surface unit. To run Microsoft Surface
Runtime 1.0 SP1, you need the following software:
 A 32-bit version of Windows Vista Business
 Windows Vista Service Pack 1 (SP1)
 Microsoft XNA 2.0 Redistributable
 .NET Framework version 3.5

10
Microsoft Surface SDK 1.0 SP1, Workstation Edition Software Requirements
Microsoft Surface SDK 1.0 SP1, Workstation Edition installs only on a workstation computer (not on a
Microsoft Surface unit). To develop applications by using Microsoft Surface SDK 1.0 SP1, Workstation
Edition, you need the following software:
 A 32-bit version of Windows Vista Home Premium, Windows Vista Business, Windows Vista
Enterprise, or Windows Vista Ultimate
 Windows Vista Service Pack 1 (SP1)
 Microsoft XNA 2.0 Redistributable
 Either Microsoft Visual C# 2008 Express Edition SP1 or Microsoft Visual Studio 2008 SP1. (You
must install C# project support to install Microsoft Surface SDK 1.0 SP1.)
 .NET Framework version 3.5 SP1

DirectX
The Microsoft Surface software requires Microsoft DirectX 9.0c and installs the necessary components
during setup.

Do not interrupt uninstallation

When you are uninstalling Microsoft Surface SDK, you must not interrupt the uninstallation. Do not
unplug the Microsoft Surface unit’s power cable during uninstallation. If you click Cancel during the
uninstallation, the software rolls back to its previously installed state and should work correctly.

APIs and Controls

ElementMenu renders incorrectly when a group style is applied to it [31184]

If you set the GroupStyle property of an ElementMenu control, the control's items render in an
overlapping and unusable manner.
Workaround:
 Rather than using a group style, you should explicitly define the hierarchy of menu items.

Editing an ElementMenu template in Expression Blend is not supported [30131]

If you right-click an ElementMenuItem control in Microsoft Expression Blend™ and click Edit Control
Parts (Template), you might experience unexpected behavior. Editing an ElementMenu template in a
similar way is not supported.

NotSupportedException exception thrown by Viewport3DVisual.HitTestCore [25245]

Applications that perform hit-testing by using GeometryHitTestParameters without filtering out
elements with IsHitTestVisible=False will see a NotSupportedException exception because of the
ViewPort3D that contact visualizations use.
Workaround:

11
  Filter out IsHitTestVisible=False elements or disable contact visualizations. You can disable
visualizations by setting the ContactVisualizations.ShowsVisualizations attached property to
False on the window or by using an XML configuration file. For more information, see the
"Disabling Contact Visualizations for Microsoft Surface Applications" topic in the Microsoft
Surface SDK Help documentation.

Touch contact on hWnd can cause a nearby UI element to be obscured, and the obscured element
might fire an event when the contact is lifted [8597]
For applications that include a UI control that might be obscured by a separate hWnd, the underlying
control might register an event while it is still obscured.
Consider the following scenario. A WPF application includes a menu and a button below the menu. User A
touches and then maintains contact with the button while User B touches and activates the menu. The
menu appears and obscures the button. User A lifts the contact, but a button Click event is sent anyway.
Workaround:
 Design your applications so that pop-up windows do not obscure other UI elements or call the
ReleaseContactCapture method for obscured controls.

Inadvertent zooming occurs when you rotate an item by using a hand [8047]
If you rotate a ScatterViewItem control by using your whole hand, you might experience accidental
zooming.

Controls in Expression Blend do not match how Microsoft Surface controls appear at run time
[6386]
If you load a project that is based on the Microsoft Surface WPF template in Microsoft Expression Blend,
WPF controls do not reflect the styles that are defined in the Microsoft Surface SDK. This problem is a
known issue with how Expression Blend handles Merged Dictionaries.

An error appears when App.xaml is opened [6386]

The Expression Blend application shows an error message when you open the App.xaml file. You can
safely ignore this error because it does not affect the build. This problem is a known issue with how
Expression Blend handles Merged Dictionaries.

Pop-up window won't accept a contact event [5389]

If you create a pop-up window with a button that opens a second pop-up window, and if a user touches a
button in the second pop-up window that is designed to open a third pop-up window, the button does
not respond.

Vision System

Byte tag backgrounds [16104]

12
You must place tags on a solid, consistent background (for example, with no patterns or stripes). Use a
dark-colored or non-IR reflective background instead of a light background.
Place tags on flat surfaces that help the tag maintain flush contact with the tabletop. Also, tags work
better on physical objects that do not easily tip over while they move.

Input detection is lost [8073]

The current developer version of the Microsoft Surface unit might lose input detection.
Workaround:
 If you lose input detection for longer than 30 seconds, restart Surface Input or the Microsoft
Surface application that is running.

Surface Shell appears off screen if you remove a monitor and don't reset [7791]
If you set up an external monitor as the primary monitor, start Surface Shell, and then disconnect the
external monitor, Surface Shell is off screen.
Workaround:
 Close Surface Shell, exit Surface Input, and recalibrate the Microsoft Surface unit.

SurfaceInput.exe fails if you update video drivers while it's running [7573]
Do not update the video driver while you are running the SurfaceInput.exe file.

Changing the Windows properties will cause Surface Input to fail [5987]
If you are running Surface Input and you change the color depth from 16-bit color to 32-bit color (in the
Display Settings item in Control Panel), Surface Input fails with an error.
Workaround:
 Close Surface Shell, exit Surface Input, and recalibrate the Microsoft Surface unit.

Shell

"0xC0000005" error message occurs when an application displays a lot of text at different sizes or
has a long process lifetime [28222]
On Microsoft Surface SDK 1.0 SP1, Workstation Edition (or any edition of Microsoft Surface 1.0 with .NET
Framework 3.5 SP1 installed), if you run a WPF application that displays a lot of text at different sizes or
only some text for a long process lifetime, the application might fail (crash). If you run the Surface Stress
tool against the application, the application is more likely to crash.
You might receive the following access violation exception error message:
0xC0000005
This crash occurs because of an issue in .NET Framework 3.5 SP1. For more information and instructions,
see FIX: Error message when a .NET Framework 3.5-based application displays lots of text at different sizes
or has a very long process lifetime: "0xC0000005" in the Microsoft Knowledge Base.

13
Projector blanking issue [17666]
On Microsoft Surface units with Microsoft Surface Runtime 1.0 SP1 where projector blanking is enabled,
the screen might turn blank, and the status, side lights might appear. This situation could happen when:
 You are on the Windows logon screen (for example, entering credentials).
 You attach a keyboard and try to operate in user mode (for example, pressing ALT+TAB to switch
between applications).
Workaround:
1. Wait until the status lights turn off; it can take up to 1 minute. Do not touch any keys or move
your mouse; this action prevents the out-of-order screen from loading so the projector is not un-
blanked.
2. After the status lights turn off, if you don't see the Windows logon screen, do the following:
a. Move your mouse. You should see the cursor.
b. Press any key at least twice.
c. If it does not work, wait a few more seconds, and then try again.
Note: Do not press CTRL+ALT+DEL. Otherwise, the Microsoft Surface unit’s screen turns blank
again, and the status lights come on.

Using large video files might cause a delay in the Launcher preview pane [14333]
If you use a large video file for the preview movie of an application, there might be a delay before the
preview shows in Launcher. This delay is particularly noticeable when the Microsoft Surface unit is under a
heavy load. To avoid this issue, reduce the file sizes of your videos.

Only applications that display in 1024 × 768 are supported

Surface Shell supports only applications that display in 1024 × 768 dimensions. Any applications that
display in alternate dimensions (such as 5120 × 768) are not supported and might display incorrectly on
the Microsoft Surface screen.

Surface Shell rejects your application’s connection [7580]

If Surface Shell rejects your application's connection, a TypeInitializationException exception is thrown
when your application makes its first Shell API call. The Message property on the innermost exception
within the TypeInitializationException exception includes details about why Surface Shell rejected the
application. There are currently two scenarios where this exception occurs:
 You use Surface Simulator, and your application is started before Surface Simulator is started.
 Your application is not registered with Surface Shell, and you start it in user mode.

Text box receives no input [7422]

If your application uses the Microsoft Surface on-screen keyboard (for example, by including a WPF text
box control), it does not receive text input in the following situation:

14
  The application is running with elevated privileges (for example, you open it from a Visual Studio
instance that is elevated), and Surface Simulator or Surface Shell is running without elevated
privileges.
In this situation, close Surface Simulator (or Surface Shell if you are running the application on a Microsoft
Surface unit), and restart it with elevated privileges.

Changing desktop settings requires a restart [5990]

If you are logged on an administrator account and if you start Surface Shell, right-click the Windows
desktop, and then change your desktop settings, the Surface Shell access points are missing when you
return to Surface Shell. You must restart the Microsoft Surface software.
Workaround:
 Close Surface Shell, exit Surface Input, and recalibrate the Microsoft Surface unit.

Surface Simulator

XNA applications render incorrectly [4511]

XNA applications render incorrectly in Surface Simulator when you change the resolution.
Workaround:
 Set the resolution before you open applications in Surface Simulator.

Surface Simulator stops the screen saver from starting [17953]

If the Surface Simulator is running on your computer, the Windows screen saver will not start, unless the
Water attract application is active in the Surface Simulator.

SimulatorAutomation component name in reference dialog box [17640]

The Microsoft.Surface.Simulation.Automation DLL displays with the SimulatorAutomation component
name.

Surface Simulator does not change the cursor to a finger [14462]

Surface Simulator does not change its cursor to the finger icon when it is partially covered by a topmost
window, such as a taskbar or assert dialog box. Move the topmost window away.

When logged in as a non-administrator, Surface Simulator cannot be run with elevated privileges
[12112]
You cannot run Surface Simulator as a user other than the logged-on user. When you are logged on a
Microsoft Surface unit as a non-administrator, you cannot run Surface Simulator with elevated privileges.
Workaround:
 Run Surface Simulator without elevated privileges or from an administrator account.

15
MenuItems are rendered over Surface Simulator’s border [6343]
By default, SurfaceMenuItem controls are rendered over Surface Simulator’s border. This situation
applies to any controls that might use the SurfacePopup class.

Microsoft Surface applications must run with the same permissions as Surface Simulator [4682,
7821]
If you open Microsoft Surface applications by using administrator permissions, Surface Simulator must
also run with administrator permissions.

Surface Stress

Surface Stress does not supply data while the screen saver is active [28553]
Surface Stress does not supply contact data while the screen saver is active.
Workaround:
 To run Surface Stress over prolonged periods of time, disable the Windows screen saver for the
duration of the run.

Surface Stress requires .NET Framework 3.5 SP1 [28222]

If you run Surface Stress without .NET Framework 3.5 SP1 installed, Surface Stress fails (crashes).

SDK Samples

Placing a tag on the Shopping Cart sample opens a shopping pod

The Shopping Cart sample responds to a specific tag, 0xc0, to open the shopping pod. It uses the
TagVisualizer control.

Raw Image Visualizer crashes when it is closed on the Microsoft Surface SDK, Workstation Edition
[31853]
If you use the Raw Image Visualizer sample on a workstation computer that is running the Microsoft
Surface SDK, the sample fails (that is, crashes) with a NullReferenceException message when it exits.
Workaround:
 Avoid running the Raw Image Visualizer sample on a workstation computer that is running
Microsoft Surface SDK 1.0 SP1, Workstation Edition.

Related Documents
All Microsoft Surface documentation is available on the Microsoft Surface Community Web site, including
information about administering, calibrating, and upgrading Microsoft Surface units.

16
Important
The Microsoft Surface documentation is regularly reviewed and updated, so please
check the Microsoft Surface Community Web site periodically for new information.

17