FIX: WM_ACTIVATE message is not sent when a window is first displayed in Windows Embedded Compact 2013

This article describes an issue that occurs when a .NET Compact Framework application’s window is first displayed on a Windows Embedded Compact 2013-based device. An update is available to resolve this issue. Before you install this update, all previously issued updates for this product must be installed.

Symptoms

When a .NET Compact Framework application’s window is first displayed on a Windows Embedded Compact 2013-based device, the WM_ACTIVATE message is not sent. The WM_ACTIVATE messages are sent as expected when you activate or deactivate the window subsequently.

Resolution

Download information

Windows Embedded Compact 2013 Monthly Update (October 2014) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.

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, 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 hotfix package

File name

File size

Date

Time

Path

Netcfagl3_9.dll

199,680

04-Sep-2014

09:31

Public\Netcf\Oak\Target\X86\Checked

Netcfagl3_9.map

176,629

04-Sep-2014

09:31

Public\Netcf\Oak\Target\X86\Checked

Netcfagl3_9.rel

71,736

04-Sep-2014

09:31

Public\Netcf\Oak\Target\X86\Checked

Netcfagl3_9.dll

539,648

04-Sep-2014

09:29

Public\Netcf\Oak\Target\X86\Debug

Netcfagl3_9.map

558,839

04-Sep-2014

09:29

Public\Netcf\Oak\Target\X86\Debug

Netcfagl3_9.rel

245,098

04-Sep-2014

09:29

Public\Netcf\Oak\Target\X86\Debug

Netcfagl3_9.dll

199,168

04-Sep-2014

09:30

Public\Netcf\Oak\Target\X86\Retail

Netcfagl3_9.map

174,942

04-Sep-2014

09:30

Public\Netcf\Oak\Target\X86\Retail

Netcfagl3_9.rel

70,866

04-Sep-2014

09:30

Public\Netcf\Oak\Target\X86\Retail

Netcfagl3_9.dll

174,592

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Checked

Netcfagl3_9.map

305,081

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Checked

Netcfagl3_9.rel

47,260

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Checked

Netcfagl3_9.dll

519,680

04-Sep-2014

09:30

Public\Netcf\Oak\Target\Armv7\Debug

Netcfagl3_9.map

1,088,827

04-Sep-2014

09:30

Public\Netcf\Oak\Target\Armv7\Debug

Netcfagl3_9.rel

145,657

04-Sep-2014

09:30

Public\Netcf\Oak\Target\Armv7\Debug

Netcfagl3_9.dll

174,080

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Retail

Netcfagl3_9.map

301,710

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Retail

Netcfagl3_9.rel

46,825

04-Sep-2014

09:31

Public\Netcf\Oak\Target\Armv7\Retail



Status

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

References

For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×