Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: List box control issues in a Silverlight for Windows Embedded application

FIX: List box control issues in a Silverlight for Windows Embedded application

View products that this article applies to.

Introduction

This article describes several list box control issues that may occur in Silverlight for Windows Embedded applications in Windows Embedded Compact 2013. An update is available to resolve these issues. Before you install this update, all previously issued updates for this product must be installed.

↑ Back to the top

Symptoms

When you run a Silverlight for Windows Embedded application on a device that's running Windows Embedded Compact 2013, you may experience one or more of the following issues:
  • You add two list box controls to an application and then add several items in the list boxes. When you select any item in one of the two lists and then select an item in the other list, the first selected item does not remain selected.
  • You register a dependency property by using VT_BSTR or VT_READONLY_STRING and then call the SetDependencyProperty function to set a zero-length string. However, when you call the GetDependencyProperty function to obtain the value, an incorrect value is returned.
  • The GetValue function is called multiple times on each DataBinding or PropertyChanged event. This may trigger a performance issue on the application.
  • The application has a list box control that uses the ItemsPanelTemplate default value of VirtualizingStackPanel. If you move the scroll bar from left to right or from top to bottom, and then you select a new item in the list, the scroll bar jumps back to the leftmost item or to the topmost item, regardless of whether vertical or horizontal orientation for the StackPanel is selected.
  • In an application that contains two list box controls, there's about a one-second lag between when you tap on a new item in the bottom list and when the UI is updated.
  • When you unload an application that contains a control, and then you reload the application, the text in the control is displayed incorrectly.

↑ Back to the top

Software update information

Download information

Windows Embedded Compact 2013 Monthly Update (October 2015) 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.

File information
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 nameFile sizeDateTimePath
Xamlruntime_dt.dll1,137,33630-Oct-201509:11Public\Common\Oak\Bin\I386
Xamlruntimecore_dt.dll2,415,28830-Oct-201509:11Public\Common\Oak\Bin\I386
Xamlruntime.map2,417,29530-Oct-201515:19Public\Common\Oak\Target\X86\Checked
Xamlruntimecore.map5,330,38130-Oct-201515:18Public\Common\Oak\Target\X86\Checked
Xamlruntimecore.rel5,787,20130-Oct-201515:18Public\Common\Oak\Target\X86\Checked
Xamlruntime.rel2,127,11130-Oct-201515:19Public\Common\Oak\Target\X86\Checked
Xamlruntimecore.dll6,316,03230-Oct-201515:18Public\Common\Oak\Target\X86\Checked
Xamlruntime.dll1,167,36030-Oct-201515:19Public\Common\Oak\Target\X86\Checked
Xamlruntime.map1,373,99530-Oct-201515:19Public\Common\Oak\Target\X86\Retail
Xamlruntimecore.map1,811,27030-Oct-201515:18Public\Common\Oak\Target\X86\Retail
Xamlruntimecore.rel1,843,92630-Oct-201515:18Public\Common\Oak\Target\X86\Retail
Xamlruntime.rel1,679,29330-Oct-201515:19Public\Common\Oak\Target\X86\Retail
Xamlruntimecore.dll2,879,48830-Oct-201515:18Public\Common\Oak\Target\X86\Retail
Xamlruntime.dll806,91230-Oct-201515:19Public\Common\Oak\Target\X86\Retail
Xamlruntime.map2,585,40430-Oct-201515:18Public\Common\Oak\Target\X86\Debug
Xamlruntimecore.map5,373,36430-Oct-201515:17Public\Common\Oak\Target\X86\Debug
Xamlruntimecore.rel4,079,01430-Oct-201515:17Public\Common\Oak\Target\X86\Debug
Xamlruntime.rel2,339,47830-Oct-201515:18Public\Common\Oak\Target\X86\Debug
Xamlruntimecore.dll7,512,06430-Oct-201515:17Public\Common\Oak\Target\X86\Debug
Xamlruntime.dll1,687,55230-Oct-201515:18Public\Common\Oak\Target\X86\Debug
Xamlruntime.map5,668,97330-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntimecore.map14,902,82830-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntimecore.rel2,826,62030-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.rel2,126,06730-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntimecore.dll6,107,13630-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.dll1,228,80030-Oct-201515:19Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.map2,422,35830-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntimecore.map3,969,49830-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntimecore.rel1,639,12830-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.rel1,444,04530-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntimecore.dll2,789,37630-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.dll765,95230-Oct-201515:19Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.map9,821,63930-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntimecore.map20,736,12030-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntimecore.rel2,572,89930-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntime.rel2,121,89130-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntimecore.dll7,462,91230-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntime.dll1,773,56830-Oct-201515:18Public\Common\Oak\Target\Armv7\Debug
Xamlruntime_dt.dll1,137,33630-Oct-201509:11Program files\Microsoft visual studio 11.0\Vc\Vcwizards\Windowsembeddedsilverlighttools
Xamlruntimecore_dt.dll2,415,28830-Oct-201509:11Program files\Microsoft visual studio 11.0\Vc\Vcwizards\Windowsembeddedsilverlighttools

↑ Back to the top

Status

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

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3107410
Revision : 1
Created on : 1/7/2017
Published on : 11/17/2015
Exists online : False
Views : 162