Introduction
This article describes an issue that prevents you from moving a slider control after it's re-enabled in a Silverlight for Windows Embedded (SWE) application in Windows Embedded Compact 2013. An update is available to resolve this issue. Before you install this update, all previously issued updates for this product must be installed.
Symptoms
In a Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013 device, you disable a slider control in the application. After you re-enable the control, you can't move the slider as expected.
Software update information
Download information
Windows Embedded Compact 2013 Monthly Update (June 2016) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.
Prerequisites
This update is supported only if all previously issued updates for this product have also been installed.
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package 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.
Files that are included in this update package
|
File name |
File size |
Date |
Time |
Path |
|---|---|---|---|---|
|
Xamlruntime_dt.dll |
1,137,336 |
16-Jun-2016 |
10:38 |
Public\Common\Oak\Bin\I386 |
|
Xamlruntime.map |
2,417,370 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Checked |
|
Xamlruntime.rel |
2,127,140 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Checked |
|
Xamlruntime.dll |
1,167,360 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Checked |
|
Xamlruntime.map |
1,374,086 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Retail |
|
Xamlruntime.rel |
1,679,322 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Retail |
|
Xamlruntime.dll |
806,912 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\X86\Retail |
|
Xamlruntime.map |
2,585,482 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\X86\Debug |
|
Xamlruntime.rel |
2,339,536 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\X86\Debug |
|
Xamlruntime.dll |
1,687,552 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\X86\Debug |
|
Xamlruntime.map |
5,669,264 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Checked |
|
Xamlruntime.rel |
2,126,096 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Checked |
|
Xamlruntime.dll |
1,228,800 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Checked |
|
Xamlruntime.map |
2,422,633 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Retail |
|
Xamlruntime.rel |
1,444,074 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Retail |
|
Xamlruntime.dll |
765,952 |
16-Jun-2016 |
10:48 |
Public\Common\Oak\Target\Armv7\Retail |
|
Xamlruntime.map |
9,818,827 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\Armv7\Debug |
|
Xamlruntime.rel |
2,121,920 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\Armv7\Debug |
|
Xamlruntime.dll |
1,773,568 |
16-Jun-2016 |
10:47 |
Public\Common\Oak\Target\Armv7\Debug |
|
Xamlruntime_dt.dll |
1,137,336 |
16-Jun-2016 |
10:38 |
Program files\Microsoft visual studio 11.0\Vc\Vcwizards\Windowsembeddedxamltools |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
