文件列表:

description.html (45185, 2015-08-10)
description\Galleries.css (10457, 2015-08-10)
description\Layout.css (1727, 2015-08-10)
description\Brand.css (71808, 2015-08-10)
license.rtf (4684, 2015-08-10)
Accelerometer sensor sample\description.html (12663, 2015-08-10)
Accelerometer sensor sample\description\offline.js (1670, 2015-08-10)
Accelerometer sensor sample\description\Combined.css (0, 2015-08-10)
Accelerometer sensor sample\description\dd546e0f-90c9-4aaf-977b-0a48b1324ebaCombined.css (0, 2015-08-10)
Accelerometer sensor sample\description\Galleries.css (10457, 2015-08-10)
Accelerometer sensor sample\description\Layout.css (1727, 2015-08-10)
Accelerometer sensor sample\description\Brand.css (71647, 2015-08-10)
Accelerometer sensor sample\description\iframedescription.css (3369, 2015-08-10)
Accelerometer sensor sample\license.rtf (4688, 2015-08-10)
Accelerometer sensor sample\C#\AccelerometerCS.sln (2860, 2015-08-10)
Accelerometer sensor sample\C#\Shared\AccelerometerCS.Shared.shproj (1059, 2015-08-10)
Accelerometer sensor sample\C#\Shared\App.xaml (877, 2015-08-10)
Accelerometer sensor sample\C#\Shared\App.xaml.cs (4146, 2015-08-10)
Accelerometer sensor sample\C#\Shared\SampleConfiguration.cs (1348, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Scenario1_DataEvents.xaml (3028, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Scenario1_DataEvents.xaml.cs (7260, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Scenario3_Polling.xaml (3003, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Scenario3_Polling.xaml.cs (7123, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Shared.projitems (2361, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\mediumtile-sdk.png (619, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\microsoft-sdk.png (3405, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\smalltile-Phone-sdk.png (428, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\smalltile-Windows-sdk.png (363, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\splash-Phone-sdk.png (10774, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\splash-Windows-sdk.png (9274, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\squaretile-sdk.png (1054, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\storelogo-sdk.png (442, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\tile-sdk.png (4852, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Assets\windows-sdk.png (2997, 2015-08-10)
Accelerometer sensor sample\C#\Shared\Common\SuspensionManager.cs (13316, 2015-08-10)
Accelerometer sensor sample\C#\Windows\AccelerometerCS.Windows.csproj (6335, 2015-08-10)
Accelerometer sensor sample\C#\Windows\MainPage.xaml (4440, 2015-08-10)
Accelerometer sensor sample\C#\Windows\MainPage.xaml.cs (4804, 2015-08-10)
Accelerometer sensor sample\C#\Windows\Package.appxmanifest (1600, 2015-08-10)
Accelerometer sensor sample\C#\Windows\Scenario2_ShakeEvents.xaml (2319, 2015-08-10)
... ...

This Hotspot Authentication Sample demonstrates how to use the Hotspot Authentication API on both Windows and Windows Phone clients. The sample consists of 4 projects: Windows Phone, Windows, Shared and a Background Task. The code in the shared and background task is common to both platforms. Even though a large part of the API is converged, and the code is shared between both the projects, there are few key differences that a developer should be aware of: 1.WISPr requirement for access points: a. On Windows clients: In order to invoke the hotspot authentication flow (background task), the access point being connected to must provide a captive portal response with WISPr support claimed in the XML blob being returned to the client. b. On Windows Phone clients: There is no requirement for captive portal or WISPr support on the Access Point. In this case, the background task is launched as soon as the Wi-Fi connection to the access point is completed and an IP address is acquired – regardless of whether the access point claims WISPr support or not. 2. Authentication using WISPr: a. On Windows client, the Hotspot Authentication API supports two ways of completing authentication i.Issuing WISPr credentials using IssueCredentialsAsync API, which uses the native WISPr implementation of Windows. ii.Perform a custom WISPr authentication using the information obtained through HotspotAuthenticationContext.TryGetAuthenticationContext. In this case, you must call HotspotAuthenticationContext.SkipAuthentication API to skip the Native WISPr authentication process once the custom authentication is complete b. On Windows Phone platform, there is no Native WISPr support. As a result, the IssueCredentialsAsync API is not supported (throws NotImplementedException). The only way to perform WISPr authentication on phone platform is to implement it within the app and then call HotspotAuthenticationContext.SkipAuthentication API. 3. Contents of HostpotAuthenticationContext class: a. On Windows client, a HotspotAuthenticationContext object contain a set of properties documented at http://msdn.microsoft.com/en-us/library/windows/apps/windows.networking.networkoperators.hotspotauthenticationcontext.aspx b. On Windows phone, the only valid Properties of HotspotAuthenticationContext are WirelessNetworkId (SSID) and NetworkAdapter. This is because the remaining properties are obtained from the native WISPr implementation of Windows, which is not supported on phone. If your supported list of Access Points are all WISPr-based, and your app implements WISPr authentication itself, it will result in 100% sharing of Hotspot Authentication API code between Windows Phone and Windows.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：