Symptoms
Consider the following scenario:
-
You have an independent hardware vendor (IHV) Extension that is loaded on a Windows Embedded Compact 7-based device.
-
You try to use an IHV Native Wi-Fi Extension for Windows Embedded Compact 7.
-
You use CmAddConnectionConfig() to add a profile that will use the IHV Extension.
-
You add an <IHV> tag in the XAML file.
-
You build the IHV Extension DLL.
In this situation, the build fails.
The expected behavior is that the IHV Extension DLL configuration entry points will be called by using QueryUIRequest(DOT11EXTIHV_QUERY_UI_REQUEST), ProcessUIResponse(DOT11EXTIHV_PROCESS_UI_RESPONSE), and IsUIRequestPending(DOT11EXTIHV_IS_UI_REQUEST_PENDING).
Resolution
Download information
The Windows Embedded Compact 7 Monthly Update (December 2014) 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.
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 |
---|---|---|---|---|
Nwifi.lib |
1,534,184 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\X86\Retail |
Nwifi.lib |
1,800,902 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\X86\Debug |
Nwifi.lib |
1,732,568 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\X86\Checked |
Nwifi.lib |
1,664,234 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Armv5\Retail |
Nwifi.lib |
2,101,484 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\Armv5\Debug |
Nwifi.lib |
1,889,146 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Armv5\Checked |
Nwifi.lib |
1,663,934 |
06-Nov-2014 |
10:19 |
Public\Common\Oak\Lib\Armv6\Retail |
Nwifi.lib |
2,100,600 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\Armv6\Debug |
Nwifi.lib |
1,888,724 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Armv6\Checked |
Nwifi.lib |
1,655,946 |
06-Nov-2014 |
10:19 |
Public\Common\Oak\Lib\Armv7\Retail |
Nwifi.lib |
2,091,522 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\Armv7\Debug |
Nwifi.lib |
1,881,858 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Armv7\Checked |
Nwifi.lib |
1,654,694 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Mipsii\Retail |
Nwifi.lib |
2,034,618 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\Mipsii\Debug |
Nwifi.lib |
1,859,434 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Mipsii\Checked |
Nwifi.lib |
1,656,568 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Mipsii_fp\Retail |
Nwifi.lib |
2,036,582 |
06-Nov-2014 |
10:17 |
Public\Common\Oak\Lib\Mipsii_fp\Debug |
Nwifi.lib |
1,861,342 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Mipsii_fp\Checked |
Nwifi.lib |
1,563,866 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Sh4\Retail |
Nwifi.lib |
1,856,582 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Sh4\Debug |
Nwifi.lib |
1,735,358 |
06-Nov-2014 |
10:18 |
Public\Common\Oak\Lib\Sh4\Checked |
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.