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.

FIX: Text in a control isn't displayed correctly on an SWE application in WEC 7


View products that this article applies to.

Symptoms

Assume that you have a Silverlight for Windows Embedded (SWE) application that contains a control on a Windows Embedded Compact 7 (WEC 7) device, and you have applied WEC 7 July Update on this device. When you unload this control and then reload it, the text of this control is displayed incorrectly.


↑ Back to the top


Cause

This issue occurs because the GetValue function from end-users returns E_FAIL and then framework on SWE encounters an access violation. Therefore, the bound control can't display the correct content.

↑ Back to the top


Resolution

Download information

The Windows Embedded Compact 7 Monthly Update (September 2015) is now available from Microsoft. To download this Windows Embedded Compact 7 monthly update, see Windows Embedded Compact 7 updates in the Microsoft Download Center website.

The kind of processor that each file applies to is visible in the name of each file in the "File information" section.

↑ Back to the top


More Information

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, select Clean Solution, and then select Build Solution.
  • On the Build menu, select Rebuild Solution.
You don't have to restart the computer after you apply this software update.

Update replacement information

This update doesn't 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's 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 hotfix package


File nameFile sizeDateTimePath
Xamlruntime.map1,840,84509-Oct-201505:15Public\Common\Oak\Target\Mipsii\Checked
Xamlruntime.rel2,848,52409-Oct-201505:15Public\Common\Oak\Target\Mipsii\Checked
Xamlruntime.dll1,712,12809-Oct-201505:15Public\Common\Oak\Target\Mipsii\Checked
Xamlruntime.map1,435,89609-Oct-201505:16Public\Common\Oak\Target\Mipsii\Retail
Xamlruntime.rel2,322,20309-Oct-201505:16Public\Common\Oak\Target\Mipsii\Retail
Xamlruntime.dll1,236,99209-Oct-201505:16Public\Common\Oak\Target\Mipsii\Retail
Xamlruntime.map2,462,69109-Oct-201505:15Public\Common\Oak\Target\Mipsii\Debug
Xamlruntime.rel3,905,74809-Oct-201505:15Public\Common\Oak\Target\Mipsii\Debug
Xamlruntime.dll2,523,13609-Oct-201505:15Public\Common\Oak\Target\Mipsii\Debug
Xamlruntime.map1,833,76709-Oct-201505:16Public\Common\Oak\Target\Armv6\Checked
Xamlruntime.rel1,763,66309-Oct-201505:16Public\Common\Oak\Target\Armv6\Checked
Xamlruntime.dll1,359,87209-Oct-201505:16Public\Common\Oak\Target\Armv6\Checked
Xamlruntime.map1,264,19109-Oct-201505:17Public\Common\Oak\Target\Armv6\Retail
Xamlruntime.rel1,577,83109-Oct-201505:17Public\Common\Oak\Target\Armv6\Retail
Xamlruntime.dll970,75209-Oct-201505:17Public\Common\Oak\Target\Armv6\Retail
Xamlruntime.map2,485,40209-Oct-201505:15Public\Common\Oak\Target\Armv6\Debug
Xamlruntime.rel2,317,38909-Oct-201505:15Public\Common\Oak\Target\Armv6\Debug
Xamlruntime.dll2,232,32009-Oct-201505:15Public\Common\Oak\Target\Armv6\Debug
Xamlruntime.map1,787,87009-Oct-201505:15Public\Common\Oak\Target\X86\Checked
Xamlruntime.rel1,731,15409-Oct-201505:15Public\Common\Oak\Target\X86\Checked
Xamlruntime.dll1,060,86409-Oct-201505:15Public\Common\Oak\Target\X86\Checked
Xamlruntime.map1,428,73509-Oct-201505:15Public\Common\Oak\Target\X86\Retail
Xamlruntime.rel1,626,05809-Oct-201505:15Public\Common\Oak\Target\X86\Retail
Xamlruntime.dll778,24009-Oct-201505:15Public\Common\Oak\Target\X86\Retail
Xamlruntime.map2,282,55109-Oct-201505:15Public\Common\Oak\Target\X86\Debug
Xamlruntime.rel2,140,46009-Oct-201505:15Public\Common\Oak\Target\X86\Debug
Xamlruntime.dll1,601,53609-Oct-201505:15Public\Common\Oak\Target\X86\Debug
Xamlruntime.map1,803,80209-Oct-201505:16Public\Common\Oak\Target\Sh4\Checked
Xamlruntime.rel2,186,48309-Oct-201505:15Public\Common\Oak\Target\Sh4\Checked
Xamlruntime.dll1,265,66409-Oct-201505:15Public\Common\Oak\Target\Sh4\Checked
Xamlruntime.map1,425,76509-Oct-201505:15Public\Common\Oak\Target\Sh4\Retail
Xamlruntime.rel1,955,23709-Oct-201505:15Public\Common\Oak\Target\Sh4\Retail
Xamlruntime.dll925,69609-Oct-201505:15Public\Common\Oak\Target\Sh4\Retail
Xamlruntime.map2,461,84909-Oct-201505:16Public\Common\Oak\Target\Sh4\Debug
Xamlruntime.rel2,928,18709-Oct-201505:16Public\Common\Oak\Target\Sh4\Debug
Xamlruntime.dll2,019,32809-Oct-201505:16Public\Common\Oak\Target\Sh4\Debug
Xamlruntime.map1,839,32809-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Checked
Xamlruntime.rel2,820,19109-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Checked
Xamlruntime.dll1,703,93609-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Checked
Xamlruntime.map1,434,68409-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Retail
Xamlruntime.rel2,301,61309-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Retail
Xamlruntime.dll1,236,99209-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Retail
Xamlruntime.map2,460,85609-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Debug
Xamlruntime.rel3,879,35809-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Debug
Xamlruntime.dll2,514,94409-Oct-201505:15Public\Common\Oak\Target\Mipsii_fp\Debug
Xamlruntime.map1,833,76109-Oct-201505:16Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.rel1,763,66309-Oct-201505:16Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.dll1,355,77609-Oct-201505:16Public\Common\Oak\Target\Armv7\Checked
Xamlruntime.map1,264,09209-Oct-201505:16Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.rel1,577,80209-Oct-201505:16Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.dll966,65609-Oct-201505:16Public\Common\Oak\Target\Armv7\Retail
Xamlruntime.map2,485,41109-Oct-201505:15Public\Common\Oak\Target\Armv7\Debug
Xamlruntime.rel2,317,36009-Oct-201505:15Public\Common\Oak\Target\Armv7\Debug
Xamlruntime.dll2,228,22409-Oct-201505:15Public\Common\Oak\Target\Armv7\Debug
Xamlruntime.map1,834,22109-Oct-201505:16Public\Common\Oak\Target\Armv5\Checked
Xamlruntime.rel1,769,26009-Oct-201505:16Public\Common\Oak\Target\Armv5\Checked
Xamlruntime.dll1,372,16009-Oct-201505:16Public\Common\Oak\Target\Armv5\Checked
Xamlruntime.map1,264,57109-Oct-201505:16Public\Common\Oak\Target\Armv5\Retail
Xamlruntime.rel1,582,44209-Oct-201505:16Public\Common\Oak\Target\Armv5\Retail
Xamlruntime.dll983,04009-Oct-201505:16Public\Common\Oak\Target\Armv5\Retail
Xamlruntime.map2,485,06609-Oct-201505:15Public\Common\Oak\Target\Armv5\Debug
Xamlruntime.rel2,325,01609-Oct-201505:15Public\Common\Oak\Target\Armv5\Debug
Xamlruntime.dll2,240,51209-Oct-201505:15Public\Common\Oak\Target\Armv5\Debug


↑ 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


Keywords: kbsurveynew, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3099207
Revision : 1
Created on : 1/7/2017
Published on : 11/11/2015
Exists online : False
Views : 143