diff --git a/README.md b/README.md
index ed383d94d..b80b5ff89 100644
--- a/README.md
+++ b/README.md
@@ -1,126 +1,126 @@
-
-
- ██╗ ██╗ ██╗ ███╗ ██╗ ██████╗ █████╗ ██╗ ██╗ ██████╗ ██╗ ████████╗
- ██║ ██╗ ██║ ██║ ████╗ ██║ ██╔══██╗ ██╔══██╗ ██║ ██╗ ██║ ██╔════╝ ██║ ╚══██╔══╝
- ╚██╗████╗██╔╝ ██║ ██╔██╗██║ ██║ ██║ ██║ ██║ ╚██╗████╗██╔╝ ╚█████╗ ██║ █████╗ ██║
- ████╔═████║ ██║ ██║╚████║ ██║ ██║ ██║ ██║ ████╔═████║ ╚═══██╗ ██║ ██╔══██║ ██║
- ╚██╔╝ ╚██╔╝ ██║ ██║ ╚███║ ██████╔╝ ╚█████╔╝ ╚██╔╝ ╚██╔╝ ██████╔╝ ██║ ╚█████╔╝ ██║
- ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚══╝ ╚═════╝ ╚════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚════╝ ╚═╝
-
-# Windows Internet of Things (IoT) Samples
-
-This repo contains samples that demonstrate usage patterns for Microsoft's Windows 10 IoT. These code samples were created with templates available in Visual Studio and are designed, but not limited to, run on devices using Windows IoT Enterprise.
-
-> **Note:** If you are unfamiliar with Git and GitHub, you can download the entire collection as a
-> [ZIP file](https://github.com/Microsoft/Windows-universal-samples/archive/master.zip), but be
-> sure to unzip everything to access shared dependencies. For more info on working with the ZIP file,
-> the samples collection, and GitHub, see [Get the UWP samples from GitHub](https://aka.ms/ovu2uq).
-> For more samples, see the [Samples portal](https://aka.ms/winsamples) on the Windows Dev Center.
-
-## Windows 10 IoT development
-These samples require Visual Studio and the Windows Software Development Kit (SDK) for Windows 10.
-
- [Get a free copy of Visual Studio Community Edition with support for building Universal Windows Platform apps](http://go.microsoft.com/fwlink/p/?LinkID=280676)
-
-Additionally, to stay on top of the latest updates to Windows and the development tools, become a Windows Insider by joining the Windows Insider Program.
-
- [Become a Windows Insider](https://insider.windows.com/)
-
- ## Using the samples
-
-The easiest way to use these samples without using Git is to download the zip file containing the current version (using the following link or by clicking the "Download ZIP" button on the repo page). You can then unzip the entire archive and use the samples in Visual Studio.
-
- [Download the samples ZIP](../../archive/master.zip)
-
- **Notes:**
- * Before you unzip the archive, right-click it, select **Properties**, and then select **Unblock**.
- * Be sure to unzip the entire archive, and not just individual samples. The samples all depend on the SharedContent folder in the archive.
- * In Visual Studio, the platform target defaults to ARM, so be sure to change that to x64 or x86 if you want to test on a non-ARM device.
-
-The samples use Linked files in Visual Studio to reduce duplication of common files, including sample template files and image assets. These common files are stored in the SharedContent folder at the root of the repository and are referred to in the project files using links.
-
-**Reminder:** If you unzip individual samples, they will not build due to references to other portions of the ZIP file that were not unzipped. You must unzip the entire archive if you intend to build the samples.
-
-For more info about the programming models, platforms, languages, and APIs demonstrated in these samples, please refer to the guidance, tutorials, and reference topics provided in the Windows 10 documentation available in the [Windows Developer Center](http://go.microsoft.com/fwlink/p/?LinkID=532421). These samples are provided as-is in order to indicate or demonstrate the functionality of the programming models and feature APIs for Windows.
-
-## Contributing
-These samples are direct from the feature teams and we welcome your input on issues and suggestions for new samples. If you would like to see new coverage or have feedback, please consider contributing. You can edit the existing content, add new content, or simply create new issues. We’ll take a look at your suggestions and will work together to incorporate them into the docs.
-
-This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
-
-**Note**:
-* When contributing, make sure you are contributing from the **develop** branch and not the master branch. Your contribution will not be accepted if your PR is coming from the master branch.
-
-When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
-
-
-## See also
-
-For additional Windows samples, see:
-* [Windows on GitHub](http://microsoft.github.io/windows/)
-* [Windows IoT Core](https://github.com/microsoft/Windows-iotcore-samples/tree/develop/Samples)
-* [Azure IoT Edge for Linux on Windows (EFLOW)](https://github.com/Azure/iotedge-eflow)
-* [.NET IoT Libraries](https://github.com/dotnet/iot)
-
-## Samples by category
-
-### Azure IoT Edge
-
-| Name | Description |
-|----------------|------------------|
-| [interop-textmsg-consoleapp](https://aka.ms/WinIoTSamples-interop-textmsg-consoleapp) | Basic interop sample demonstrating text messaging between a Windows console app and an Edge module. |
-| [interop-customvision-textmsg-uwpapp](https://aka.ms/WinIoTSamples-interop-customvision-textmsg-uwpapp) |
Two more advanced interop samples which demonstrate bidirectional communication between a Windows application and an Edge module.
Text messaging between a UWP application and an Edge module.
A 'Custom vision' machine learning interop sample with a fruit classifier which uses a Windows UWP app to send camera frames to an Edge module for identification.
|
-
-### Windows 10 IoT Enterprise
-
-| Name | Description |
-|----------------|------------------|
-| [Accelerometer](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/Accelerometer) | Sample app that reads data over either I2C or SPI from an attached ADXL345 accelerometer |
-| [AppServiceBlinky](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/AppServiceBlinky) | Two part sample. 1. Create a simple Blinky app service and connect a LED to your Windows IoT Enterprise device (Up-Board). 2. Create a simple app service client that blinks the LED |
-| [AppServiceSharedNotepad](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/AppServiceSharedNotepad) | This app creates a simple notepad app service, and two simple app service clients. One app will write to the notepad service and the other one reads from the notepad service. |
-| [CustomDeviceAccessor](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/CustomDeviceAccessor) | This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIOControl(). |
-| [DMMockPortal](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/DMMocKPortal) | This sample shows what an operator's flow might look like when it comes to updating devices in bulk or individually. |
-| [DeviceIOContoller](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/DeviceIOContoller) | This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). |
-| [DualOperator](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/DualOperator) | This sample demonstrates Dual Operator demonstrates routing input from 2 physical keyboards to specific applications. |
-| [ExternalProcessLauncher](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/ExternalProcessLauncher) | We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using Windows.System.ProcessLauncher API. |
-| [FlowVolume](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/FlowVolume) | This sample show how to launch an external process (exe) from a Universal Windows Platform (UWP) app using Windows.System.ProcessLauncher API. |
-| [ForegroundAppWithBackgroundApp](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/ForegroundAppWithBackgroundApp) | This sample will showcase how to create a foreground application with a background application. |
-| [GPIOKmdfDemo](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/GPIOKmdfDemo) | This sample will demonstrate how to deploy a GPIO Kernel driver to a Windows 10 IoT Device. |
-| [GPIOOneWire](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/GPIOOneWire) | This sample shows how to read a temperature and humidity sensor from a Universal Windows Application. |
-| [HIDInjector](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/HIDInjector) | This sample will allow you to deploy a driver to perform low level injection of touch, keyboard and mouse events. |
-| [Hello Blinky](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/Hello%20Blinky) | This sample is a simple blinking LED app. |
-| [HelloBlinkyBackground](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/HelloBlinkyBackground) | This sample showcases how to set up and use a background service. |
-| [I2CCompass](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/I2CCompass) | This sample uses I2C on Windows IoT Enterprise to communicate with an magnetometer device.|
-| [I2CPortExpander](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/I2CPortExpander) | This sample app uses the port expander to read the status of a tactile switch and control an LED. |
-| [IoTEnterpriseDefault](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/IoTEnterpriseDefault) | This sample app provides an overview of the various features that can be enabled in Windows 10 IoT Enterprise. |
-| [IoTHubClients](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/IoTHubClients) | This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes. |
-| [MemoryStatus](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/MemoryStatus) | This sample is intended to show how to create a console application that can be used to query the memory usage on your Windows 10 IoT Enterprise device. |
-| [NTServiceRpc](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/NTServiceRpc) | This sample demonstrates the use of a NT service with an UWP app. |
-| [Potentiometer](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/Potentiometer) | This sample shows how to connect a rotary potentiometer and LED to a Windows IoT Enterprise compatible board. |
-| [PushButtton](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/PushButtton) | This sample shows how to use a push button to control an LED. |
-| [RFIDForIoT](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/RFIDForIoT) | This sample demonstrates how to read an RFID tag and beep the buzzer when the card scans. |
-| [RGBLED](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/RGBLED) | This sample demonstrates how a tri-color LED will blink and cycle through red, blue and green. |
-| [SPIDisplay](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/SPIDisplay) | This sample interfaces a SPI based OLED display to a Windows 10 IoT Enterprise device. |
-| [SerialNumber](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/SerialNumber) | This sample demonstrates how to get the device serial number. |
-| [SerialUART](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/SerialUART) | This sample creates an app that allows communication between a PC and an IoT device over a serial interface. |
-| [ShellLauncher](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/ShellLauncher) | This is a UWP app sample for Shell Launcher V2, see how to configure UWP app for Shell Launcher V2 in the samples. |
-| [SpeechTranslator](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/SpeechTranslator) | This sample will translate speech to different languages. |
-| [TempForceSensor](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/TempForceSensor) | This sample showcases how to use a temperature and force sensor. |
-| [VideoCaptureSample](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/VideoCaptureSample) | This sample initializes a video capture device, record video to a file, preview video feed, and playback the recorded video. |
-| [VirtualMicrophoneArrayDriver](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/VirtualMicrophoneArrayDriver) | This sample illustrates how to construct a virtual microphone array at runtime using monoaural audio devices present on the system. |
-| [WebcamApp](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/WebcamApp) | This sample will initialize a webcam, take pictures, and record video and audio. |
-| [WifiConnector](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/WifiConnector) | This sample will find and connect to WiFi networks using a Universal Windows Platform (UWP) app that makes use of the Windows.Devices.WiFi.WiFiAdapter API. |
-
-
-#### Bus Tools
-| Name | Description |
-|----------------|------------------|
-| [GPIOTestTool](https://github.com/microsoft/Windows-IoT-Samples/tree/master/BusTools) | Utility to manipulate GPIO pins from the command line. Demonstrates how to use the GPIO WinRT APIs from standard C++ with WRL. |
-| [I2CTestTool](https://github.com/microsoft/Windows-IoT-Samples/tree/master/BusTools) | Utility to read and write I2C devices from the command line. Shows how to use C++/CX in console applications. |
-| [MinComm (UART)](https://github.com/microsoft/Windows-IoT-Samples/tree/master/BusTools) | Demonstrates how to use UART. |
-| [PWMTestTool](https://github.com/microsoft/Windows-IoT-Samples/tree/master/BusTools) | Utility to read and write PWM devices from the command line. Shows how to use C++/CX in console applications. |
-| [SPITestTool](https://github.com/microsoft/Windows-IoT-Samples/tree/master/BusTools) | Utility to read and write SPI devices from the command line. |
+
+
+ ██╗ ██╗ ██╗ ███╗ ██╗ ██████╗ █████╗ ██╗ ██╗ ██████╗ ██╗ ████████╗
+ ██║ ██╗ ██║ ██║ ████╗ ██║ ██╔══██╗ ██╔══██╗ ██║ ██╗ ██║ ██╔════╝ ██║ ╚══██╔══╝
+ ╚██╗████╗██╔╝ ██║ ██╔██╗██║ ██║ ██║ ██║ ██║ ╚██╗████╗██╔╝ ╚█████╗ ██║ █████╗ ██║
+ ████╔═████║ ██║ ██║╚████║ ██║ ██║ ██║ ██║ ████╔═████║ ╚═══██╗ ██║ ██╔══██║ ██║
+ ╚██╔╝ ╚██╔╝ ██║ ██║ ╚███║ ██████╔╝ ╚█████╔╝ ╚██╔╝ ╚██╔╝ ██████╔╝ ██║ ╚█████╔╝ ██║
+ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚══╝ ╚═════╝ ╚════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚════╝ ╚═╝
+
+# Windows Internet of Things (IoT) Samples
+
+This repo contains samples that demonstrate usage patterns for Microsoft's Windows 10 IoT. These code samples were created with templates available in Visual Studio and are designed, but not limited to, run on devices using Windows IoT Enterprise.
+
+> **Note:** If you are unfamiliar with Git and GitHub, you can download the entire collection as a
+> [ZIP file](https://github.com/Microsoft/Windows-universal-samples/archive/master.zip), but be
+> sure to unzip everything to access shared dependencies. For more info on working with the ZIP file,
+> the samples collection, and GitHub, see [Get the UWP samples from GitHub](https://aka.ms/ovu2uq).
+> For more samples, see the [Samples portal](https://aka.ms/winsamples) on the Windows Dev Center.
+
+## Windows 10 IoT development
+These samples require Visual Studio and the Windows Software Development Kit (SDK) for Windows 10.
+
+ [Get a free copy of Visual Studio Community Edition with support for building Universal Windows Platform apps](http://go.microsoft.com/fwlink/p/?LinkID=280676)
+
+Additionally, to stay on top of the latest updates to Windows and the development tools, become a Windows Insider by joining the Windows Insider Program.
+
+ [Become a Windows Insider](https://insider.windows.com/)
+
+ ## Using the samples
+
+The easiest way to use these samples without using Git is to download the zip file containing the current version (using the following link or by clicking the "Download ZIP" button on the repo page). You can then unzip the entire archive and use the samples in Visual Studio.
+
+ [Download the samples ZIP](../../archive/master.zip)
+
+ **Notes:**
+ * Before you unzip the archive, right-click it, select **Properties**, and then select **Unblock**.
+ * Be sure to unzip the entire archive, and not just individual samples. The samples all depend on the SharedContent folder in the archive.
+ * In Visual Studio, the platform target defaults to ARM, so be sure to change that to x64 or x86 if you want to test on a non-ARM device.
+
+The samples use Linked files in Visual Studio to reduce duplication of common files, including sample template files and image assets. These common files are stored in the SharedContent folder at the root of the repository and are referred to in the project files using links.
+
+**Reminder:** If you unzip individual samples, they will not build due to references to other portions of the ZIP file that were not unzipped. You must unzip the entire archive if you intend to build the samples.
+
+For more info about the programming models, platforms, languages, and APIs demonstrated in these samples, please refer to the guidance, tutorials, and reference topics provided in the Windows 10 documentation available in the [Windows Developer Center](http://go.microsoft.com/fwlink/p/?LinkID=532421). These samples are provided as-is in order to indicate or demonstrate the functionality of the programming models and feature APIs for Windows.
+
+## Contributing
+These samples are direct from the feature teams and we welcome your input on issues and suggestions for new samples. If you would like to see new coverage or have feedback, please consider contributing. You can edit the existing content, add new content, or simply create new issues. We’ll take a look at your suggestions and will work together to incorporate them into the docs.
+
+This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
+
+**Note**:
+* When contributing, make sure you are contributing from the **develop** branch and not the master branch. Your contribution will not be accepted if your PR is coming from the master branch.
+
+When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
+
+
+## See also
+
+For additional Windows samples, see:
+* [Windows on GitHub](http://microsoft.github.io/windows/)
+* [Windows IoT Core](https://github.com/microsoft/Windows-iotcore-samples/tree/develop/Samples)
+* [Azure IoT Edge for Linux on Windows (EFLOW)](https://github.com/Azure/iotedge-eflow)
+* [.NET IoT Libraries](https://github.com/dotnet/iot)
+
+## Samples by category
+
+### Azure IoT Edge
+
+| Name | Description |
+|----------------|------------------|
+| [interop-textmsg-consoleapp](https://aka.ms/WinIoTSamples-interop-textmsg-consoleapp) | Basic interop sample demonstrating text messaging between a Windows console app and an Edge module. |
+| [interop-customvision-textmsg-uwpapp](https://aka.ms/WinIoTSamples-interop-customvision-textmsg-uwpapp) |
Two more advanced interop samples which demonstrate bidirectional communication between a Windows application and an Edge module.
Text messaging between a UWP application and an Edge module.
A 'Custom vision' machine learning interop sample with a fruit classifier which uses a Windows UWP app to send camera frames to an Edge module for identification.
-<PropertyGroup Label="Globals">
- <ProjectGuid>...</ProjectGuid>
- ...
- <!-- Add the following property to make desktop APIs visible at compile time. -->
- <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
-</PropertyGroup>
-
-
-When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
-
- %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
-
-For more information on API families, see winapifamily.h from the SDK.
-
-We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
-
-
-<PropertyGroup>
- <PackageCertificateKeyFile>CustomDeviceAccessorUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
-</PropertyGroup>
-<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
-<ItemDefinitionGroup>
- <Link>
- <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
- </Link>
-</ItemDefinitionGroup>
-
-
-## Use CreateFile/DeviceIoControl in your Application
-
-Add the following code to pch.h:
-
-``` C++
-
- #include
- #include
-
- // Undefine symbols to avoid collision with ntddser.h
- #undef SERIAL_LSRMST_ESCAPE
- #undef SERIAL_LSRMST_LSR_DATA
- #undef SERIAL_LSRMST_LSR_NODATA
- #undef SERIAL_LSRMST_MST
- #undef SERIAL_IOC_FCR_FIFO_ENABLE
- #undef SERIAL_IOC_FCR_RCVR_RESET
- #undef SERIAL_IOC_FCR_XMIT_RESET
- #undef SERIAL_IOC_FCR_DMA_MODE
- #undef SERIAL_IOC_FCR_RES1
- #undef SERIAL_IOC_FCR_RES2
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
- #undef SERIAL_IOC_MCR_DTR
- #undef SERIAL_IOC_MCR_RTS
- #undef SERIAL_IOC_MCR_OUT1
- #undef SERIAL_IOC_MCR_OUT2
- #undef SERIAL_IOC_MCR_LOOP
-
- #include
- #include
-
-```
-
-Add the following code to Mainpage.xaml.cpp:
-
-``` C++
- void AccessComPort ()
- {
- using namespace Microsoft::WRL::Wrappers;
-
- // Open the COM port synchronously for simplicity.
- // You'll almost always want to use FILE_FLAG_OVERLAPPED
- // for COM ports.
- FileHandle fileHandle(CreateFile(
- L"\\\\.\\COM1",
- GENERIC_READ | GENERIC_WRITE,
- 0,
- nullptr,
- OPEN_EXISTING,
- FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
- nullptr));
-
- if (!fileHandle.IsValid()) {
- DWORD lastError = GetLastError();
- throw ref new Exception( // set a breakpoint here
- HRESULT_FROM_WIN32(lastError),
- L"Failed to open COM port.");
- }
-
- DWORD information;
- SERIAL_BAUD_RATE inputBuffer = { 115200 };
- if (!DeviceIoControl(
- fileHandle.Get(),
- IOCTL_SERIAL_SET_BAUD_RATE,
- &inputBuffer,
- sizeof(inputBuffer),
- nullptr,
- 0,
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to set baud rate.");
- }
-
- const char message[] = "Hello serial!\n";
- if (!WriteFile(
- fileHandle.Get(),
- message,
- sizeof(message),
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to write data to COM port.");
- }
- }
-```
-
-Add a call to `AccessComPort()` in the MainPage constructor:
-
-``` C++
- MainPage::MainPage()
- {
- InitializeComponent();
- AccessComPort();
- }
-```
-
-### Deploy your app
-
-* If you're building for [UP Board](https://up-board.org/up/specifications/), select `x64` as the architecture.
-* Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-* Build the project, which should succeed because we made desktop APIs visible at compile time.
-* Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
-* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Granting Access to AppContainer Processes
-
-Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
-
-
-
-
-
SDDL String
-
Description
-
Wdmsec.h constant
-
-
-
-
-
"D:P"
-
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
-
-
-
"D:P(A;;GA;;;SY)"
-
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
-
SDDL_DEVOBJ_SYS_ALL
-
-
-
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
-
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
-
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
-
-
-
-
-A number of common security descriptor strings are defined in wdmsec.h.
-
-To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
-
-If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
-
-If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
-
-First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
-
-```csharp
- $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
- $a -join ','
-```
-
-The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
-
- Windows Registry Editor Version 5.00
-
- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
- "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
-
-Verify that the Security registry value was created by running:
-
- reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
-
-If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
-
- Devcon restart acpi\pnp0501
-
-Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
-
-Congratulations, you have successfully opened a device and sent an IOCTL to it!
-
-## Granting Access to a Specific Application
-
-The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
-
-Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
-
-
-
-You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
-
-SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
-
-For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
+---
+page_type: sample
+urlFragment: custom-device-accessor
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl() with Windows 10 IoT Enterprise.
+---
+
+# Custom Device Accessor
+
+This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
+
+ - You have existing code that uses CreateFile()
+ - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
+ - Your application needs the performance of the win32 APIs
+ - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
+
+While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
+
+The high level steps involved are:
+
+ 1. Create a C++/CX UWP application
+ 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
+ 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
+ 4. Make the device accessible to appcontainer processes
+
+This walkthrough uses the COM port on UP Board as the example device. UP Board has 2 COM ports - one high-speed UARTs on the 40-pin header, and a conventional COM port controlled by serial.sys on a separate header. The oone high speed UARTs are already exposed to UWP applications, but the COM port is not. This walkthrough shows you how to access the COM port from UWP applications.
+
+## Exposing the COM port to usermode
+
+Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
+
+ Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
+ Devcon restart acpi\pnp0501
+
+If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available at [here](https://github.com/ms-iot/samples/tree/develop/MinComm).
+
+## Enabling access to desktop APIs in a C++/CX UWP Application
+
+Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
+
+Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
+
+
+<PropertyGroup Label="Globals">
+ <ProjectGuid>...</ProjectGuid>
+ ...
+ <!-- Add the following property to make desktop APIs visible at compile time. -->
+ <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
+</PropertyGroup>
+
+
+When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
+
+ %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
+
+For more information on API families, see winapifamily.h from the SDK.
+
+We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
+
+
+<PropertyGroup>
+ <PackageCertificateKeyFile>CustomDeviceAccessorUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
+</PropertyGroup>
+<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
+<ItemDefinitionGroup>
+ <Link>
+ <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
+ </Link>
+</ItemDefinitionGroup>
+
+
+## Use CreateFile/DeviceIoControl in your Application
+
+Add the following code to pch.h:
+
+``` C++
+
+ #include
+ #include
+
+ // Undefine symbols to avoid collision with ntddser.h
+ #undef SERIAL_LSRMST_ESCAPE
+ #undef SERIAL_LSRMST_LSR_DATA
+ #undef SERIAL_LSRMST_LSR_NODATA
+ #undef SERIAL_LSRMST_MST
+ #undef SERIAL_IOC_FCR_FIFO_ENABLE
+ #undef SERIAL_IOC_FCR_RCVR_RESET
+ #undef SERIAL_IOC_FCR_XMIT_RESET
+ #undef SERIAL_IOC_FCR_DMA_MODE
+ #undef SERIAL_IOC_FCR_RES1
+ #undef SERIAL_IOC_FCR_RES2
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
+ #undef SERIAL_IOC_MCR_DTR
+ #undef SERIAL_IOC_MCR_RTS
+ #undef SERIAL_IOC_MCR_OUT1
+ #undef SERIAL_IOC_MCR_OUT2
+ #undef SERIAL_IOC_MCR_LOOP
+
+ #include
+ #include
+
+```
+
+Add the following code to Mainpage.xaml.cpp:
+
+``` C++
+ void AccessComPort ()
+ {
+ using namespace Microsoft::WRL::Wrappers;
+
+ // Open the COM port synchronously for simplicity.
+ // You'll almost always want to use FILE_FLAG_OVERLAPPED
+ // for COM ports.
+ FileHandle fileHandle(CreateFile(
+ L"\\\\.\\COM1",
+ GENERIC_READ | GENERIC_WRITE,
+ 0,
+ nullptr,
+ OPEN_EXISTING,
+ FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
+ nullptr));
+
+ if (!fileHandle.IsValid()) {
+ DWORD lastError = GetLastError();
+ throw ref new Exception( // set a breakpoint here
+ HRESULT_FROM_WIN32(lastError),
+ L"Failed to open COM port.");
+ }
+
+ DWORD information;
+ SERIAL_BAUD_RATE inputBuffer = { 115200 };
+ if (!DeviceIoControl(
+ fileHandle.Get(),
+ IOCTL_SERIAL_SET_BAUD_RATE,
+ &inputBuffer,
+ sizeof(inputBuffer),
+ nullptr,
+ 0,
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to set baud rate.");
+ }
+
+ const char message[] = "Hello serial!\n";
+ if (!WriteFile(
+ fileHandle.Get(),
+ message,
+ sizeof(message),
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to write data to COM port.");
+ }
+ }
+```
+
+Add a call to `AccessComPort()` in the MainPage constructor:
+
+``` C++
+ MainPage::MainPage()
+ {
+ InitializeComponent();
+ AccessComPort();
+ }
+```
+
+### Deploy your app
+
+* If you're building for [UP Board](https://up-board.org/up/specifications/), select `x64` as the architecture.
+* Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+* Build the project, which should succeed because we made desktop APIs visible at compile time.
+* Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
+* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Granting Access to AppContainer Processes
+
+Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
+
+
+
+
+
SDDL String
+
Description
+
Wdmsec.h constant
+
+
+
+
+
"D:P"
+
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
+
+
+
"D:P(A;;GA;;;SY)"
+
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
+
SDDL_DEVOBJ_SYS_ALL
+
+
+
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
+
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
+
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
+
+
+
+
+A number of common security descriptor strings are defined in wdmsec.h.
+
+To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
+
+If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
+
+If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
+
+First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
+
+```csharp
+ $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
+ $a -join ','
+```
+
+The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
+
+ Windows Registry Editor Version 5.00
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
+ "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
+
+Verify that the Security registry value was created by running:
+
+ reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
+
+If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
+
+ Devcon restart acpi\pnp0501
+
+Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
+
+Congratulations, you have successfully opened a device and sent an IOCTL to it!
+
+## Granting Access to a Specific Application
+
+The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
+
+Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
+
+
+
+You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
+
+SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
+
+For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
diff --git a/samples/CustomDeviceAccessor/CPP/pch.cpp b/samples/CustomDeviceAccessor/CPP/pch.cpp
index b459044b7..dbd902d13 100644
--- a/samples/CustomDeviceAccessor/CPP/pch.cpp
+++ b/samples/CustomDeviceAccessor/CPP/pch.cpp
@@ -1,8 +1,8 @@
-// Copyright (c) Microsoft. All rights reserved.
-
-//
-// pch.cpp
-// Include the standard header and generate the precompiled header.
-//
-
-#include "pch.h"
+// Copyright (c) Microsoft. All rights reserved.
+
+//
+// pch.cpp
+// Include the standard header and generate the precompiled header.
+//
+
+#include "pch.h"
diff --git a/samples/CustomDeviceAccessor/CPP/pch.h b/samples/CustomDeviceAccessor/CPP/pch.h
index 49b76a6cb..386a38ad8 100644
--- a/samples/CustomDeviceAccessor/CPP/pch.h
+++ b/samples/CustomDeviceAccessor/CPP/pch.h
@@ -1,37 +1,37 @@
-// Copyright (c) Microsoft. All rights reserved.
-
-//
-// pch.h
-// Header for standard system include files.
-//
-
-#pragma once
-
-#include
-#include
-#include
-#include
-
-// Undefine symbols to avoid collision with ntddser.h
-#undef SERIAL_LSRMST_ESCAPE
-#undef SERIAL_LSRMST_LSR_DATA
-#undef SERIAL_LSRMST_LSR_NODATA
-#undef SERIAL_LSRMST_MST
-#undef SERIAL_IOC_FCR_FIFO_ENABLE
-#undef SERIAL_IOC_FCR_RCVR_RESET
-#undef SERIAL_IOC_FCR_XMIT_RESET
-#undef SERIAL_IOC_FCR_DMA_MODE
-#undef SERIAL_IOC_FCR_RES1
-#undef SERIAL_IOC_FCR_RES2
-#undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
-#undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
-#undef SERIAL_IOC_MCR_DTR
-#undef SERIAL_IOC_MCR_RTS
-#undef SERIAL_IOC_MCR_OUT1
-#undef SERIAL_IOC_MCR_OUT2
-#undef SERIAL_IOC_MCR_LOOP
-
-#include
-#include
-
-#include "App.xaml.h"
+// Copyright (c) Microsoft. All rights reserved.
+
+//
+// pch.h
+// Header for standard system include files.
+//
+
+#pragma once
+
+#include
+#include
+#include
+#include
+
+// Undefine symbols to avoid collision with ntddser.h
+#undef SERIAL_LSRMST_ESCAPE
+#undef SERIAL_LSRMST_LSR_DATA
+#undef SERIAL_LSRMST_LSR_NODATA
+#undef SERIAL_LSRMST_MST
+#undef SERIAL_IOC_FCR_FIFO_ENABLE
+#undef SERIAL_IOC_FCR_RCVR_RESET
+#undef SERIAL_IOC_FCR_XMIT_RESET
+#undef SERIAL_IOC_FCR_DMA_MODE
+#undef SERIAL_IOC_FCR_RES1
+#undef SERIAL_IOC_FCR_RES2
+#undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
+#undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
+#undef SERIAL_IOC_MCR_DTR
+#undef SERIAL_IOC_MCR_RTS
+#undef SERIAL_IOC_MCR_OUT1
+#undef SERIAL_IOC_MCR_OUT2
+#undef SERIAL_IOC_MCR_LOOP
+
+#include
+#include
+
+#include "App.xaml.h"
diff --git a/samples/CustomDeviceAccessor/README.md b/samples/CustomDeviceAccessor/README.md
index a2a685b43..48e0c7e0d 100644
--- a/samples/CustomDeviceAccessor/README.md
+++ b/samples/CustomDeviceAccessor/README.md
@@ -1,293 +1,293 @@
----
-page_type: sample
-urlFragment: custom-device-accessor
-languages:
- - cpp
-products:
- - windows
- - windows-iot
- - windows-10-iot-Enterprise
-description: This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl() with Windows 10 IoT Enterprise.
----
-
-# Custom Device Accessor
-
-This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
-
- - You have existing code that uses CreateFile()
- - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
- - Your application needs the performance of the win32 APIs
- - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
-
-While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
-
-The high level steps involved are:
-
- 1. Create a C++/CX UWP application
- 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
- 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
- 4. Make the device accessible to appcontainer processes
-
-This walkthrough uses the COM port on UP Board as the example device. UP Board has 2 COM ports - one high-speed UARTs on the 40-pin header, and a conventional COM port controlled by serial.sys on a separate header. The one high speed UARTs are already exposed to UWP applications, but the COM port is not. This walkthrough shows you how to access the COM port from UWP applications.
-
-## Exposing the COM port to usermode
-
-Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
-
- Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
- Devcon restart acpi\pnp0501
-
-If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available at [here](https://github.com/ms-iot/samples/tree/develop/MinComm).
-
-## Enabling access to desktop APIs in a C++/CX UWP Application
-
-Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
-
-Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
-
-
-<PropertyGroup Label="Globals">
- <ProjectGuid>...</ProjectGuid>
- ...
- <!-- Add the following property to make desktop APIs visible at compile time. -->
- <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
-</PropertyGroup>
-
-
-When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
-
- %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
-
-For more information on API families, see winapifamily.h from the SDK.
-
-We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
-
-
-<PropertyGroup>
- <PackageCertificateKeyFile>CustomDeviceAccessorUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
-</PropertyGroup>
-<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
-<ItemDefinitionGroup>
- <Link>
- <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
- </Link>
-</ItemDefinitionGroup>
-
-
-## Use CreateFile/DeviceIoControl in your Application
-
-Add the following code to pch.h:
-
-``` C++
-
- #include
- #include
-
- // Undefine symbols to avoid collision with ntddser.h
- #undef SERIAL_LSRMST_ESCAPE
- #undef SERIAL_LSRMST_LSR_DATA
- #undef SERIAL_LSRMST_LSR_NODATA
- #undef SERIAL_LSRMST_MST
- #undef SERIAL_IOC_FCR_FIFO_ENABLE
- #undef SERIAL_IOC_FCR_RCVR_RESET
- #undef SERIAL_IOC_FCR_XMIT_RESET
- #undef SERIAL_IOC_FCR_DMA_MODE
- #undef SERIAL_IOC_FCR_RES1
- #undef SERIAL_IOC_FCR_RES2
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
- #undef SERIAL_IOC_MCR_DTR
- #undef SERIAL_IOC_MCR_RTS
- #undef SERIAL_IOC_MCR_OUT1
- #undef SERIAL_IOC_MCR_OUT2
- #undef SERIAL_IOC_MCR_LOOP
-
- #include
- #include
-
-```
-
-Add the following code to Mainpage.xaml.cpp:
-
-``` C++
- void AccessComPort ()
- {
- using namespace Microsoft::WRL::Wrappers;
-
- // Open the COM port synchronously for simplicity.
- // You'll almost always want to use FILE_FLAG_OVERLAPPED
- // for COM ports.
- FileHandle fileHandle(CreateFile(
- L"\\\\.\\COM1",
- GENERIC_READ | GENERIC_WRITE,
- 0,
- nullptr,
- OPEN_EXISTING,
- FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
- nullptr));
-
- if (!fileHandle.IsValid()) {
- DWORD lastError = GetLastError();
- throw ref new Exception( // set a breakpoint here
- HRESULT_FROM_WIN32(lastError),
- L"Failed to open COM port.");
- }
-
- DWORD information;
- SERIAL_BAUD_RATE inputBuffer = { 115200 };
- if (!DeviceIoControl(
- fileHandle.Get(),
- IOCTL_SERIAL_SET_BAUD_RATE,
- &inputBuffer,
- sizeof(inputBuffer),
- nullptr,
- 0,
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to set baud rate.");
- }
-
- const char message[] = "Hello serial!\n";
- if (!WriteFile(
- fileHandle.Get(),
- message,
- sizeof(message),
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to write data to COM port.");
- }
- }
-```
-
-Add a call to `AccessComPort()` in the MainPage constructor:
-
-``` C++
- MainPage::MainPage()
- {
- InitializeComponent();
- AccessComPort();
- }
-```
-
-### Deploy your app
-
-* If you're building for UPBoard, select `x64` as the architecture.
-
-* Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-
-* Build the project, which should succeed because we made desktop APIs visible at compile time.
-
-* Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
-
-* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
-
-### Generate an app package
-
-Steps to follow :
-
- * In Solution Explorer, open the solution for your application project.
- * Right-click the project and choose Publish->Create App Packages (before Visual Studio 2019 version 16.3, the Publish menu is named Store).
- * Select Sideloading in the first page of the wizard and then click Next.
- * On the Select signing method page, select whether to skip packaging signing or select a certificate for signing. You can select a certificate from your local certificate store, select a certificate file, or create a new certificate. For an MSIX package to be installed on an end user's machine, it must be signed with a cert that is trusted on the machine.
- * Complete the Select and configure packages page as described in the Create your app package upload file using Visual Studio section.
-
- If you need guidance click Link: [here](https://docs.microsoft.com/en-us/windows/msix/package/packaging-uwp-apps#generate-an-app-package).
-
-### Install your app package using an install script
-
-Steps to follow :
- * Open the *_Test folder.
- * Right-click on the Add-AppDevPackage.ps1 file. Choose Run with PowerShell and follow the prompts.
- * When the app package has been installed, the PowerShell window displays this message: Your app was successfully installed.
-
- If you need guidance click Link: [here](https://docs.microsoft.com/en-us/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script).
-
- Click the Start button to search for the app by name, and then launch it.
-
-## Granting Access to AppContainer Processes
-
-Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
-
-
-
-
-
SDDL String
-
Description
-
Wdmsec.h constant
-
-
-
-
-
"D:P"
-
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
-
-
-
"D:P(A;;GA;;;SY)"
-
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
-
SDDL_DEVOBJ_SYS_ALL
-
-
-
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
-
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
-
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
-
-
-
-
-A number of common security descriptor strings are defined in wdmsec.h.
-
-To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
-
-If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
-
-If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
-
-First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
-
-```csharp
- $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
- $a -join ','
-```
-
-The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
-
- Windows Registry Editor Version 5.00
-
- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
- "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
-
-Verify that the Security registry value was created by running:
-
- reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
-
-If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
-
- Devcon restart acpi\pnp0501
-
-Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
-
-Congratulations, you have successfully opened a device and sent an IOCTL to it!
-
-## Granting Access to a Specific Application
-
-The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
-
-Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
-
-
-
-You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
-
-SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
-
-For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
+---
+page_type: sample
+urlFragment: custom-device-accessor
+languages:
+ - cpp
+products:
+ - windows
+ - windows-iot
+ - windows-10-iot-Enterprise
+description: This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl() with Windows 10 IoT Enterprise.
+---
+
+# Custom Device Accessor
+
+This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
+
+ - You have existing code that uses CreateFile()
+ - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
+ - Your application needs the performance of the win32 APIs
+ - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
+
+While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
+
+The high level steps involved are:
+
+ 1. Create a C++/CX UWP application
+ 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
+ 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
+ 4. Make the device accessible to appcontainer processes
+
+This walkthrough uses the COM port on UP Board as the example device. UP Board has 2 COM ports - one high-speed UARTs on the 40-pin header, and a conventional COM port controlled by serial.sys on a separate header. The one high speed UARTs are already exposed to UWP applications, but the COM port is not. This walkthrough shows you how to access the COM port from UWP applications.
+
+## Exposing the COM port to usermode
+
+Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
+
+ Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
+ Devcon restart acpi\pnp0501
+
+If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available at [here](https://github.com/ms-iot/samples/tree/develop/MinComm).
+
+## Enabling access to desktop APIs in a C++/CX UWP Application
+
+Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
+
+Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
+
+
+<PropertyGroup Label="Globals">
+ <ProjectGuid>...</ProjectGuid>
+ ...
+ <!-- Add the following property to make desktop APIs visible at compile time. -->
+ <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
+</PropertyGroup>
+
+
+When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
+
+ %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
+
+For more information on API families, see winapifamily.h from the SDK.
+
+We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
+
+
+<PropertyGroup>
+ <PackageCertificateKeyFile>CustomDeviceAccessorUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
+</PropertyGroup>
+<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
+<ItemDefinitionGroup>
+ <Link>
+ <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
+ </Link>
+</ItemDefinitionGroup>
+
+
+## Use CreateFile/DeviceIoControl in your Application
+
+Add the following code to pch.h:
+
+``` C++
+
+ #include
+ #include
+
+ // Undefine symbols to avoid collision with ntddser.h
+ #undef SERIAL_LSRMST_ESCAPE
+ #undef SERIAL_LSRMST_LSR_DATA
+ #undef SERIAL_LSRMST_LSR_NODATA
+ #undef SERIAL_LSRMST_MST
+ #undef SERIAL_IOC_FCR_FIFO_ENABLE
+ #undef SERIAL_IOC_FCR_RCVR_RESET
+ #undef SERIAL_IOC_FCR_XMIT_RESET
+ #undef SERIAL_IOC_FCR_DMA_MODE
+ #undef SERIAL_IOC_FCR_RES1
+ #undef SERIAL_IOC_FCR_RES2
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
+ #undef SERIAL_IOC_MCR_DTR
+ #undef SERIAL_IOC_MCR_RTS
+ #undef SERIAL_IOC_MCR_OUT1
+ #undef SERIAL_IOC_MCR_OUT2
+ #undef SERIAL_IOC_MCR_LOOP
+
+ #include
+ #include
+
+```
+
+Add the following code to Mainpage.xaml.cpp:
+
+``` C++
+ void AccessComPort ()
+ {
+ using namespace Microsoft::WRL::Wrappers;
+
+ // Open the COM port synchronously for simplicity.
+ // You'll almost always want to use FILE_FLAG_OVERLAPPED
+ // for COM ports.
+ FileHandle fileHandle(CreateFile(
+ L"\\\\.\\COM1",
+ GENERIC_READ | GENERIC_WRITE,
+ 0,
+ nullptr,
+ OPEN_EXISTING,
+ FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
+ nullptr));
+
+ if (!fileHandle.IsValid()) {
+ DWORD lastError = GetLastError();
+ throw ref new Exception( // set a breakpoint here
+ HRESULT_FROM_WIN32(lastError),
+ L"Failed to open COM port.");
+ }
+
+ DWORD information;
+ SERIAL_BAUD_RATE inputBuffer = { 115200 };
+ if (!DeviceIoControl(
+ fileHandle.Get(),
+ IOCTL_SERIAL_SET_BAUD_RATE,
+ &inputBuffer,
+ sizeof(inputBuffer),
+ nullptr,
+ 0,
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to set baud rate.");
+ }
+
+ const char message[] = "Hello serial!\n";
+ if (!WriteFile(
+ fileHandle.Get(),
+ message,
+ sizeof(message),
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to write data to COM port.");
+ }
+ }
+```
+
+Add a call to `AccessComPort()` in the MainPage constructor:
+
+``` C++
+ MainPage::MainPage()
+ {
+ InitializeComponent();
+ AccessComPort();
+ }
+```
+
+### Deploy your app
+
+* If you're building for UPBoard, select `x64` as the architecture.
+
+* Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+
+* Build the project, which should succeed because we made desktop APIs visible at compile time.
+
+* Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
+
+* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
+
+### Generate an app package
+
+Steps to follow :
+
+ * In Solution Explorer, open the solution for your application project.
+ * Right-click the project and choose Publish->Create App Packages (before Visual Studio 2019 version 16.3, the Publish menu is named Store).
+ * Select Sideloading in the first page of the wizard and then click Next.
+ * On the Select signing method page, select whether to skip packaging signing or select a certificate for signing. You can select a certificate from your local certificate store, select a certificate file, or create a new certificate. For an MSIX package to be installed on an end user's machine, it must be signed with a cert that is trusted on the machine.
+ * Complete the Select and configure packages page as described in the Create your app package upload file using Visual Studio section.
+
+ If you need guidance click Link: [here](https://docs.microsoft.com/en-us/windows/msix/package/packaging-uwp-apps#generate-an-app-package).
+
+### Install your app package using an install script
+
+Steps to follow :
+ * Open the *_Test folder.
+ * Right-click on the Add-AppDevPackage.ps1 file. Choose Run with PowerShell and follow the prompts.
+ * When the app package has been installed, the PowerShell window displays this message: Your app was successfully installed.
+
+ If you need guidance click Link: [here](https://docs.microsoft.com/en-us/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script).
+
+ Click the Start button to search for the app by name, and then launch it.
+
+## Granting Access to AppContainer Processes
+
+Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
+
+
+
+
+
SDDL String
+
Description
+
Wdmsec.h constant
+
+
+
+
+
"D:P"
+
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
+
+
+
"D:P(A;;GA;;;SY)"
+
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
+
SDDL_DEVOBJ_SYS_ALL
+
+
+
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
+
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
-
-2. Define the criteria a device should satisfy to get either of these configuration snippets. The criteria can be a simple condition or a compound one where device tags and/or properties are checked.
-Deciding which tags/properties to use depends on how you are tagging your devices and what properties your devices are reporting - and which of those can be used to author the condition.
-
- For example, in our example here, we will use the `deviceInfo` `processorArchitecture` values to derive our conditions.
-
- - For x64,
-
-
-3. Lastly, define the criteria a device should satisfy to be considered successful in applying the condition. This has to be based on one or more reported properties as they reflect the state of the device.
-Since we are setting `windowsTelemetry`, the Device Agent will respond after applying such configuration in the reported properties under a section named `WindowsTelemetry`.
-
- - For x64,
-
- properties.reported.windowsTelemetry.__meta.deploymentStatus='succeeded' and properties.reported.deviceInfo.processorArchitecture='0'
-
-
- - For arm
-
- properties.reported.windowsTelemetry.__meta.deploymentStatus='succeeded' and properties.reported.deviceInfo.processorArchitecture='5'
-
-
- Note here that we included the "targeting" condition in the success condition. This is necessary so we scope our success result to the devices that are actually targeted by this deployment.
-
-For the DMMockPortal, it expects three criteria to be defined for each deployment:
-
-1. `successCondition`: defines how to know the deployment has succeeded.
-2. `failureCondition`: defines how to know the deployment has failed.
-3. `pendingCondition`: defines how to know the deployment is still in progress.
-
-Now, typing those in the DMMockPortal can prove to be tricky. An easier way is to craft all these settings in a json file and import it into the DMMockPortal.
-For example, we have [adm.windows_telemetry_x64_v1.json](adm.windows_telemetry_x64_v1.json) and [adm.windows_telemetry_arm_v1.json](adm.windows_telemetry_arm_v1.json) for your convenience.
-
-### Walk-Through
-
-- After inserting the iothubowner connection string, click `Refresh`.
-- To create a deployment, click the `+`.
- - You can fill-in the form and then click `Save`. OR
- - You can import a pre-existing deployment profile by clicking `Import` then `Save`.
- - The repo comes with a set of pre-defined deployment profiles:
-
- - [adm.windows_telemetry_x64_v1.json](adm.windows_telemetry_x64_v1.json)
- - [adm.windows_telemetry_arm_v1.json](adm.windows_telemetry_arm_v1.json)
-
-- Once a deployment is created (saved), the ADM service will pick it at some point (undeterministic) and apply it to the devices that satisfy the target condition.
-- You can monitor their progress by hitting the `Refresh` button.
-
-**Note 1**: Your device(s) must be running to be able to respond to the deployments.
-
-**Note 2**: By default, we have device info and device schemas reported on start-up. This allows deployments to use their reported properties for targeting.
-
-
+---
+page_type: sample
+urlFragment: DMMockPortal
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample tool allows the user to update devices individually or in bulk in Azure ADM service.
+---
+
+# DM Mock Portal
+
+This tool allows the user to update devices individually or in bulk. It utilizes [Azure's ADM](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-auto-device-config) service.
+
+While you may find this tool useful, it was primary developed as a sample to show how an operator's flow might look like - specifically when it comes to bulk updates.
+
+## Individual Update
+
+- After inserting the iothubowner connection string, click `Refresh`.
+- Select the `All` deployment.
+- In the `Deployment Details` pane, click the `Target Devices` button.
+- Select the device of your choice, and paste the JSON you want applied.
+
+## Bulk Update
+
+Bulk update is possible using this tool by specifying three different pieces:
+
+1. The configuration to deploy (a JSON blob).
+2. What criteria a device should satisfy to be a target of that configuration.
+3. What criteria a device should satisfy to be considered successful in applying the configuration.
+
+For example, let's say we want to set the telemetry level to `basic` for arm devices, while we want to set it to `security` for x64 device. To do that we will:
+
+1. Define two configurations,
+
+ - For x64
+
+
+2. Define the criteria a device should satisfy to get either of these configuration snippets. The criteria can be a simple condition or a compound one where device tags and/or properties are checked.
+Deciding which tags/properties to use depends on how you are tagging your devices and what properties your devices are reporting - and which of those can be used to author the condition.
+
+ For example, in our example here, we will use the `deviceInfo` `processorArchitecture` values to derive our conditions.
+
+ - For x64,
+
+
+3. Lastly, define the criteria a device should satisfy to be considered successful in applying the condition. This has to be based on one or more reported properties as they reflect the state of the device.
+Since we are setting `windowsTelemetry`, the Device Agent will respond after applying such configuration in the reported properties under a section named `WindowsTelemetry`.
+
+ - For x64,
+
+ properties.reported.windowsTelemetry.__meta.deploymentStatus='succeeded' and properties.reported.deviceInfo.processorArchitecture='0'
+
+
+ - For arm
+
+ properties.reported.windowsTelemetry.__meta.deploymentStatus='succeeded' and properties.reported.deviceInfo.processorArchitecture='5'
+
+
+ Note here that we included the "targeting" condition in the success condition. This is necessary so we scope our success result to the devices that are actually targeted by this deployment.
+
+For the DMMockPortal, it expects three criteria to be defined for each deployment:
+
+1. `successCondition`: defines how to know the deployment has succeeded.
+2. `failureCondition`: defines how to know the deployment has failed.
+3. `pendingCondition`: defines how to know the deployment is still in progress.
+
+Now, typing those in the DMMockPortal can prove to be tricky. An easier way is to craft all these settings in a json file and import it into the DMMockPortal.
+For example, we have [adm.windows_telemetry_x64_v1.json](adm.windows_telemetry_x64_v1.json) and [adm.windows_telemetry_arm_v1.json](adm.windows_telemetry_arm_v1.json) for your convenience.
+
+### Walk-Through
+
+- After inserting the iothubowner connection string, click `Refresh`.
+- To create a deployment, click the `+`.
+ - You can fill-in the form and then click `Save`. OR
+ - You can import a pre-existing deployment profile by clicking `Import` then `Save`.
+ - The repo comes with a set of pre-defined deployment profiles:
+
+ - [adm.windows_telemetry_x64_v1.json](adm.windows_telemetry_x64_v1.json)
+ - [adm.windows_telemetry_arm_v1.json](adm.windows_telemetry_arm_v1.json)
+
+- Once a deployment is created (saved), the ADM service will pick it at some point (undeterministic) and apply it to the devices that satisfy the target condition.
+- You can monitor their progress by hitting the `Refresh` button.
+
+**Note 1**: Your device(s) must be running to be able to respond to the deployments.
+
+**Note 2**: By default, we have device info and device schemas reported on start-up. This allows deployments to use their reported properties for targeting.
+
+
diff --git a/samples/DMMocKPortal/windows_telemetry_x64_v1.json.txt b/samples/DMMocKPortal/windows_telemetry_x64_v1.json.txt
index 28769d52f..d1ac527ec 100644
--- a/samples/DMMocKPortal/windows_telemetry_x64_v1.json.txt
+++ b/samples/DMMocKPortal/windows_telemetry_x64_v1.json.txt
@@ -1,7 +1,7 @@
- "windowsTelemetry": {
- "__meta": {
- "deploymentId": "windows_telemetry_x64_v1",
- "serviceInterfaceVersion": "1.0.0"
- },
- "level": "security"
+ "windowsTelemetry": {
+ "__meta": {
+ "deploymentId": "windows_telemetry_x64_v1",
+ "serviceInterfaceVersion": "1.0.0"
+ },
+ "level": "security"
}
\ No newline at end of file
diff --git a/samples/DeviceIOContoller/CPP/README.md b/samples/DeviceIOContoller/CPP/README.md
index b5841351e..42ebf16b1 100644
--- a/samples/DeviceIOContoller/CPP/README.md
+++ b/samples/DeviceIOContoller/CPP/README.md
@@ -1,274 +1,274 @@
----
-page_type: sample
-urlFragment: deviceIO-controller
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: Sample for leveraging Device IO Controller.
----
-
-# Device IO Controller
-
-This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
-
- - You have existing code that uses CreateFile()
- - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
- - Your application needs the performance of the win32 APIs
- - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
-
-While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
-
-The high level steps involved are:
-
- 1. Create a C++/CX UWP application
- 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
- 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
- 4. Make the device accessible to appcontainer processes
-
-## Step 1: Exposing the COM port to usermode
-
-Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
-
- Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
- Devcon restart acpi\pnp0501
-
-If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available in the Windows IoT samples repository.
-
-## Step 2: Enabling access to desktop APIs in a C++/CX UWP Application
-
-Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
-
-Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
-
-
-<PropertyGroup Label="Globals">
- <ProjectGuid>...</ProjectGuid>
- ...
- <!-- Add the following property to make desktop APIs visible at compile time. -->
- <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
-</PropertyGroup>
-
-
-When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
-
- %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
-
-For more information on API families, see winapifamily.h from the SDK.
-
-We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
-
-
-<PropertyGroup>
- <PackageCertificateKeyFile>DeviceIOControllerUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
-</PropertyGroup>
-<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
-<ItemDefinitionGroup>
- <Link>
- <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
- </Link>
-</ItemDefinitionGroup>
-
-
-## Step 3: Use CreateFile/DeviceIoControl in your Application
-
-Add the following code to pch.h:
-
-``` C++
-
- #include
- #include
-
- // Undefine symbols to avoid collision with ntddser.h
- #undef SERIAL_LSRMST_ESCAPE
- #undef SERIAL_LSRMST_LSR_DATA
- #undef SERIAL_LSRMST_LSR_NODATA
- #undef SERIAL_LSRMST_MST
- #undef SERIAL_IOC_FCR_FIFO_ENABLE
- #undef SERIAL_IOC_FCR_RCVR_RESET
- #undef SERIAL_IOC_FCR_XMIT_RESET
- #undef SERIAL_IOC_FCR_DMA_MODE
- #undef SERIAL_IOC_FCR_RES1
- #undef SERIAL_IOC_FCR_RES2
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
- #undef SERIAL_IOC_MCR_DTR
- #undef SERIAL_IOC_MCR_RTS
- #undef SERIAL_IOC_MCR_OUT1
- #undef SERIAL_IOC_MCR_OUT2
- #undef SERIAL_IOC_MCR_LOOP
-
- #include
- #include
-
-```
-
-Add the following code to Mainpage.xaml.cpp:
-
-``` C++
- void AccessComPort ()
- {
- using namespace Microsoft::WRL::Wrappers;
-
- // Open the COM port synchronously for simplicity.
- // You'll almost always want to use FILE_FLAG_OVERLAPPED
- // for COM ports.
- FileHandle fileHandle(CreateFile(
- L"\\\\.\\COM1",
- GENERIC_READ | GENERIC_WRITE,
- 0,
- nullptr,
- OPEN_EXISTING,
- FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
- nullptr));
-
- if (!fileHandle.IsValid()) {
- DWORD lastError = GetLastError();
- throw ref new Exception( // set a breakpoint here
- HRESULT_FROM_WIN32(lastError),
- L"Failed to open COM port.");
- }
-
- DWORD information;
- SERIAL_BAUD_RATE inputBuffer = { 115200 };
- if (!DeviceIoControl(
- fileHandle.Get(),
- IOCTL_SERIAL_SET_BAUD_RATE,
- &inputBuffer,
- sizeof(inputBuffer),
- nullptr,
- 0,
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to set baud rate.");
- }
-
- const char message[] = "Hello serial!\n";
- if (!WriteFile(
- fileHandle.Get(),
- message,
- sizeof(message),
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to write data to COM port.");
- }
- }
-```
-
-Add a call to `AccessComPort()` in the MainPage constructor:
-
-``` C++
- MainPage::MainPage()
- {
- InitializeComponent();
- AccessComPort();
- }
-```
-
-## Step 4: Deploy your app
-
-* If you're building for UP Board, select `x64` as the architecture.
-
-* Select **Local Machine** to point to IoT device and select *F5* on your keyboard to deploy to your device.
-
-## Step 5: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 6: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 7: Build the project
-
-This build should succeed since we made desktop APIs visible at compile time.
-
-Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
-
-* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
-
-## Step 8: Granting Access to AppContainer Processes
-
-Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
-
-
-
-
-
SDDL String
-
Description
-
Wdmsec.h constant
-
-
-
-
-
"D:P"
-
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
-
-
-
"D:P(A;;GA;;;SY)"
-
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
-
SDDL_DEVOBJ_SYS_ALL
-
-
-
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
-
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
-
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
-
-
-
-
-A number of common security descriptor strings are defined in wdmsec.h.
-
-To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
-
-If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
-
-If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
-
-First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
-
-```csharp
- $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
- $a -join ','
-```
-
-The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
-
- Windows Registry Editor Version 5.00
-
- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
- "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
-
-Verify that the Security registry value was created by running:
-
- reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
-
-If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
-
- Devcon restart acpi\pnp0501
-
-Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
-
-Congratulations, you have successfully opened a device and sent an IOCTL to it!
-
-## Step 9: Granting Access to a Specific Application
-
-The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
-
-Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
-
-
-
-You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
-
-SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
-
-For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
+---
+page_type: sample
+urlFragment: deviceIO-controller
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: Sample for leveraging Device IO Controller.
+---
+
+# Device IO Controller
+
+This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
+
+ - You have existing code that uses CreateFile()
+ - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
+ - Your application needs the performance of the win32 APIs
+ - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
+
+While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
+
+The high level steps involved are:
+
+ 1. Create a C++/CX UWP application
+ 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
+ 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
+ 4. Make the device accessible to appcontainer processes
+
+## Step 1: Exposing the COM port to usermode
+
+Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
+
+ Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
+ Devcon restart acpi\pnp0501
+
+If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available in the Windows IoT samples repository.
+
+## Step 2: Enabling access to desktop APIs in a C++/CX UWP Application
+
+Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
+
+Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
+
+
+<PropertyGroup Label="Globals">
+ <ProjectGuid>...</ProjectGuid>
+ ...
+ <!-- Add the following property to make desktop APIs visible at compile time. -->
+ <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
+</PropertyGroup>
+
+
+When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
+
+ %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
+
+For more information on API families, see winapifamily.h from the SDK.
+
+We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
+
+
+<PropertyGroup>
+ <PackageCertificateKeyFile>DeviceIOControllerUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
+</PropertyGroup>
+<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
+<ItemDefinitionGroup>
+ <Link>
+ <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
+ </Link>
+</ItemDefinitionGroup>
+
+
+## Step 3: Use CreateFile/DeviceIoControl in your Application
+
+Add the following code to pch.h:
+
+``` C++
+
+ #include
+ #include
+
+ // Undefine symbols to avoid collision with ntddser.h
+ #undef SERIAL_LSRMST_ESCAPE
+ #undef SERIAL_LSRMST_LSR_DATA
+ #undef SERIAL_LSRMST_LSR_NODATA
+ #undef SERIAL_LSRMST_MST
+ #undef SERIAL_IOC_FCR_FIFO_ENABLE
+ #undef SERIAL_IOC_FCR_RCVR_RESET
+ #undef SERIAL_IOC_FCR_XMIT_RESET
+ #undef SERIAL_IOC_FCR_DMA_MODE
+ #undef SERIAL_IOC_FCR_RES1
+ #undef SERIAL_IOC_FCR_RES2
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
+ #undef SERIAL_IOC_MCR_DTR
+ #undef SERIAL_IOC_MCR_RTS
+ #undef SERIAL_IOC_MCR_OUT1
+ #undef SERIAL_IOC_MCR_OUT2
+ #undef SERIAL_IOC_MCR_LOOP
+
+ #include
+ #include
+
+```
+
+Add the following code to Mainpage.xaml.cpp:
+
+``` C++
+ void AccessComPort ()
+ {
+ using namespace Microsoft::WRL::Wrappers;
+
+ // Open the COM port synchronously for simplicity.
+ // You'll almost always want to use FILE_FLAG_OVERLAPPED
+ // for COM ports.
+ FileHandle fileHandle(CreateFile(
+ L"\\\\.\\COM1",
+ GENERIC_READ | GENERIC_WRITE,
+ 0,
+ nullptr,
+ OPEN_EXISTING,
+ FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
+ nullptr));
+
+ if (!fileHandle.IsValid()) {
+ DWORD lastError = GetLastError();
+ throw ref new Exception( // set a breakpoint here
+ HRESULT_FROM_WIN32(lastError),
+ L"Failed to open COM port.");
+ }
+
+ DWORD information;
+ SERIAL_BAUD_RATE inputBuffer = { 115200 };
+ if (!DeviceIoControl(
+ fileHandle.Get(),
+ IOCTL_SERIAL_SET_BAUD_RATE,
+ &inputBuffer,
+ sizeof(inputBuffer),
+ nullptr,
+ 0,
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to set baud rate.");
+ }
+
+ const char message[] = "Hello serial!\n";
+ if (!WriteFile(
+ fileHandle.Get(),
+ message,
+ sizeof(message),
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to write data to COM port.");
+ }
+ }
+```
+
+Add a call to `AccessComPort()` in the MainPage constructor:
+
+``` C++
+ MainPage::MainPage()
+ {
+ InitializeComponent();
+ AccessComPort();
+ }
+```
+
+## Step 4: Deploy your app
+
+* If you're building for UP Board, select `x64` as the architecture.
+
+* Select **Local Machine** to point to IoT device and select *F5* on your keyboard to deploy to your device.
+
+## Step 5: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 6: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 7: Build the project
+
+This build should succeed since we made desktop APIs visible at compile time.
+
+Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
+
+* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
+
+## Step 8: Granting Access to AppContainer Processes
+
+Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
+
+
+
+
+
SDDL String
+
Description
+
Wdmsec.h constant
+
+
+
+
+
"D:P"
+
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
+
+
+
"D:P(A;;GA;;;SY)"
+
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
+
SDDL_DEVOBJ_SYS_ALL
+
+
+
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
+
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
+
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
+
+
+
+
+A number of common security descriptor strings are defined in wdmsec.h.
+
+To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
+
+If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
+
+If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
+
+First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
+
+```csharp
+ $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
+ $a -join ','
+```
+
+The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
+
+ Windows Registry Editor Version 5.00
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
+ "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
+
+Verify that the Security registry value was created by running:
+
+ reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
+
+If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
+
+ Devcon restart acpi\pnp0501
+
+Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
+
+Congratulations, you have successfully opened a device and sent an IOCTL to it!
+
+## Step 9: Granting Access to a Specific Application
+
+The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
+
+Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
+
+
+
+You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
+
+SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
+
+For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
diff --git a/samples/DeviceIOContoller/README.md b/samples/DeviceIOContoller/README.md
index c85918a54..41605619f 100644
--- a/samples/DeviceIOContoller/README.md
+++ b/samples/DeviceIOContoller/README.md
@@ -1,282 +1,282 @@
----
-page_type: sample
-urlFragment: deviceIO-controller
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: Sample for leveraging Device IO Controller.
----
-
-# Device IO Controller
-
-This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
-
- - You have existing code that uses CreateFile()
- - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
- - Your application needs the performance of the win32 APIs
- - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
-
-While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
-
-The high level steps involved are:
-
- 1. Create a C++/CX UWP application
- 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
- 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
- 4. Make the device accessible to appcontainer processes
-
-## Step 1: Exposing the COM port to usermode
-
-Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
-
- Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
- Devcon restart acpi\pnp0501
-
-If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available in the Windows IoT samples repository.
-
-## Step 2: Enabling access to desktop APIs in a C++/CX UWP Application
-
-Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
-
-Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
-
-
-<PropertyGroup Label="Globals">
- <ProjectGuid>...</ProjectGuid>
- ...
- <!-- Add the following property to make desktop APIs visible at compile time. -->
- <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
-</PropertyGroup>
-
-
-When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
-
- %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
-
-For more information on API families, see winapifamily.h from the SDK.
-
-We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
-
-
-<PropertyGroup>
- <PackageCertificateKeyFile>DeviceIOControllerUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
-</PropertyGroup>
-<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
-<ItemDefinitionGroup>
- <Link>
- <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
- </Link>
-</ItemDefinitionGroup>
-
-
-## Step 3: Use CreateFile/DeviceIoControl in your Application
-
-Add the following code to pch.h:
-
-``` C++
-
- #include
- #include
-
- // Undefine symbols to avoid collision with ntddser.h
- #undef SERIAL_LSRMST_ESCAPE
- #undef SERIAL_LSRMST_LSR_DATA
- #undef SERIAL_LSRMST_LSR_NODATA
- #undef SERIAL_LSRMST_MST
- #undef SERIAL_IOC_FCR_FIFO_ENABLE
- #undef SERIAL_IOC_FCR_RCVR_RESET
- #undef SERIAL_IOC_FCR_XMIT_RESET
- #undef SERIAL_IOC_FCR_DMA_MODE
- #undef SERIAL_IOC_FCR_RES1
- #undef SERIAL_IOC_FCR_RES2
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
- #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
- #undef SERIAL_IOC_MCR_DTR
- #undef SERIAL_IOC_MCR_RTS
- #undef SERIAL_IOC_MCR_OUT1
- #undef SERIAL_IOC_MCR_OUT2
- #undef SERIAL_IOC_MCR_LOOP
-
- #include
- #include
-
-```
-
-Add the following code to Mainpage.xaml.cpp:
-
-``` C++
- void AccessComPort ()
- {
- using namespace Microsoft::WRL::Wrappers;
-
- // Open the COM port synchronously for simplicity.
- // You'll almost always want to use FILE_FLAG_OVERLAPPED
- // for COM ports.
- FileHandle fileHandle(CreateFile(
- L"\\\\.\\COM1",
- GENERIC_READ | GENERIC_WRITE,
- 0,
- nullptr,
- OPEN_EXISTING,
- FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
- nullptr));
-
- if (!fileHandle.IsValid()) {
- DWORD lastError = GetLastError();
- throw ref new Exception( // set a breakpoint here
- HRESULT_FROM_WIN32(lastError),
- L"Failed to open COM port.");
- }
-
- DWORD information;
- SERIAL_BAUD_RATE inputBuffer = { 115200 };
- if (!DeviceIoControl(
- fileHandle.Get(),
- IOCTL_SERIAL_SET_BAUD_RATE,
- &inputBuffer,
- sizeof(inputBuffer),
- nullptr,
- 0,
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to set baud rate.");
- }
-
- const char message[] = "Hello serial!\n";
- if (!WriteFile(
- fileHandle.Get(),
- message,
- sizeof(message),
- &information,
- nullptr)) {
-
- throw ref new Exception(
- HRESULT_FROM_WIN32(GetLastError()),
- L"Failed to write data to COM port.");
- }
- }
-```
-
-Add a call to `AccessComPort()` in the MainPage constructor:
-
-``` C++
- MainPage::MainPage()
- {
- InitializeComponent();
- AccessComPort();
- }
-```
-
-## Step 4: Deploy your app
-
-* If you're building for UP Board, select `x64` as the architecture.
-
-* Select **Local Machine** to point to IoT device and select *F5* on your keyboard to deploy to your device.
-
-## Step 5: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 6: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 7: Build the project
-
-This build should succeed since we made desktop APIs visible at compile time.
-
-Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
-
-* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
-
-## Step 8: Granting Access to AppContainer Processes
-
-Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
-
-
-
-
-
SDDL String
-
Description
-
Wdmsec.h constant
-
-
-
-
-
"D:P"
-
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
-
-
-
"D:P(A;;GA;;;SY)"
-
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
-
SDDL_DEVOBJ_SYS_ALL
-
-
-
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
-
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
-
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
-
-
-
-
-A number of common security descriptor strings are defined in wdmsec.h.
-
-To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
-
-If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
-
-If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
-
-First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
-
-```csharp
- $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
- $a -join ','
-```
-
-The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
-
- Windows Registry Editor Version 5.00
-
- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
- "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
-
-Copy this file to c:\data on your MBM and run:
-
- schtasks /create /RU SYSTEM /SC ONCE /TN DeviceAC /TR "reg import c:\data\deviceac.reg" /ST 00:00
- schtasks /run /tn DeviceAC
- schtasks /delete /tn DeviceAC /f
-
-We use schtasks to run the reg import operation as SYSTEM, because only the SYSTEM account has permission to change registry keys under the enum key.
-
-Verify that the Security registry value was created by running:
-
- reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
-
-If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
-
- Devcon restart acpi\pnp0501
-
-Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
-
-Congratulations, you have successfully opened a device and sent an IOCTL to it!
-
-## Step 9: Granting Access to a Specific Application
-
-The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
-
-Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
-
-
-
-You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
-
- "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
-
-SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
-
-For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
+---
+page_type: sample
+urlFragment: deviceIO-controller
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: Sample for leveraging Device IO Controller.
+---
+
+# Device IO Controller
+
+This sample shows how to access devices from UWP applications using familiar win32 APIs like CreateFile(), ReadFile(), WriteFile(), and DeviceIoControl(). Some reasons you may want to do this are:
+
+ - You have existing code that uses CreateFile()
+ - You prefer the programming model of the win32 APIs to Windows.Devices.Custom
+ - Your application needs the performance of the win32 APIs
+ - You need to open the device synchronously, because the device driver requires it, or you need to leverage FastIO
+
+While you will be able to debug and deploy this app on devices you own by sideloading the application, you will not be able to upload an app that uses unsupported APIs to the Windows Store.
+
+The high level steps involved are:
+
+ 1. Create a C++/CX UWP application
+ 2. Set an msbuild property named `_NoWinAPIFamilyApp` to `true` in the vcxproj file
+ 3. Use CreateFile/ReadFile/WriteFile/DeviceIoControl in your code
+ 4. Make the device accessible to appcontainer processes
+
+## Step 1: Exposing the COM port to usermode
+
+Before we can access the COM port, we need to add the `PortName` registry value under the device's hardware key so that serial.sys will create a device interface and symbolic link. On desktop flavors of Windows, this is handled by the ports class coinstaller (msports.dll), but since coinstallers are not supported on onecore-based editions, we need to add this reg key manually.
+
+ Reg add "HKLM\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1\Device Parameters" /v PortName /t REG_SZ /d COM1
+ Devcon restart acpi\pnp0501
+
+If you now run `mincomm -list`, you should see ACPI\PNP0501\1 in the list of COM ports. Mincomm is available in the Windows IoT samples repository.
+
+## Step 2: Enabling access to desktop APIs in a C++/CX UWP Application
+
+Create a new project by going to File -> New -> Project -> Visual C++ -> Windows-> Universal -> Blank App (Universal Windows), and click OK.
+
+Open the .vcxproj file in a text editor and add the `<_NoWinAPIFamilyAPP>` element to the first PropertyGroup element:
+
+
+<PropertyGroup Label="Globals">
+ <ProjectGuid>...</ProjectGuid>
+ ...
+ <!-- Add the following property to make desktop APIs visible at compile time. -->
+ <_NoWinAPIFamilyApp>true</_NoWinAPIFamilyApp>
+</PropertyGroup>
+
+
+When you define `_NoWinAPIFamilyApp`, it causes `WINAPI_FAMILY` to be left undefined, instead of defined to `WINAPI_FAMILY_APP`. If `WINAPI_FAMILY` is not defined, it will default to `WINAPI_FAMILY_DESKTOP_APP`, which makes desktop APIs visible at compile time. The `_NoWinAPIFamilyApp` property is referenced as follows by C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.AppContainerApplication.props:
+
+ %(PreprocessorDefinitions);WINAPI_FAMILY=WINAPI_FAMILY_APP
+
+For more information on API families, see winapifamily.h from the SDK.
+
+We also need to link against onecoreuap.lib, which exports all symbols available on OnecoreUAP-based editions. Add an `AdditionalDependencies` element containing onecoreuap.lib just after the PropertyGroup that contains the `PackageCertificateKeyFile` element.
+
+
+<PropertyGroup>
+ <PackageCertificateKeyFile>DeviceIOControllerUWP_TemporaryKey.pfx</PackageCertificateKeyFile>
+</PropertyGroup>
+<!-- Link against onecoreuap.lib so we can use CreateFile() and friends. -->
+<ItemDefinitionGroup>
+ <Link>
+ <AdditionalDependencies>onecoreuap.lib;%(AdditionalDependencies)</AdditionalDependencies>
+ </Link>
+</ItemDefinitionGroup>
+
+
+## Step 3: Use CreateFile/DeviceIoControl in your Application
+
+Add the following code to pch.h:
+
+``` C++
+
+ #include
+ #include
+
+ // Undefine symbols to avoid collision with ntddser.h
+ #undef SERIAL_LSRMST_ESCAPE
+ #undef SERIAL_LSRMST_LSR_DATA
+ #undef SERIAL_LSRMST_LSR_NODATA
+ #undef SERIAL_LSRMST_MST
+ #undef SERIAL_IOC_FCR_FIFO_ENABLE
+ #undef SERIAL_IOC_FCR_RCVR_RESET
+ #undef SERIAL_IOC_FCR_XMIT_RESET
+ #undef SERIAL_IOC_FCR_DMA_MODE
+ #undef SERIAL_IOC_FCR_RES1
+ #undef SERIAL_IOC_FCR_RES2
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_LSB
+ #undef SERIAL_IOC_FCR_RCVR_TRIGGER_MSB
+ #undef SERIAL_IOC_MCR_DTR
+ #undef SERIAL_IOC_MCR_RTS
+ #undef SERIAL_IOC_MCR_OUT1
+ #undef SERIAL_IOC_MCR_OUT2
+ #undef SERIAL_IOC_MCR_LOOP
+
+ #include
+ #include
+
+```
+
+Add the following code to Mainpage.xaml.cpp:
+
+``` C++
+ void AccessComPort ()
+ {
+ using namespace Microsoft::WRL::Wrappers;
+
+ // Open the COM port synchronously for simplicity.
+ // You'll almost always want to use FILE_FLAG_OVERLAPPED
+ // for COM ports.
+ FileHandle fileHandle(CreateFile(
+ L"\\\\.\\COM1",
+ GENERIC_READ | GENERIC_WRITE,
+ 0,
+ nullptr,
+ OPEN_EXISTING,
+ FILE_ATTRIBUTE_NORMAL /*FILE_FLAG_OVERLAPPED*/,
+ nullptr));
+
+ if (!fileHandle.IsValid()) {
+ DWORD lastError = GetLastError();
+ throw ref new Exception( // set a breakpoint here
+ HRESULT_FROM_WIN32(lastError),
+ L"Failed to open COM port.");
+ }
+
+ DWORD information;
+ SERIAL_BAUD_RATE inputBuffer = { 115200 };
+ if (!DeviceIoControl(
+ fileHandle.Get(),
+ IOCTL_SERIAL_SET_BAUD_RATE,
+ &inputBuffer,
+ sizeof(inputBuffer),
+ nullptr,
+ 0,
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to set baud rate.");
+ }
+
+ const char message[] = "Hello serial!\n";
+ if (!WriteFile(
+ fileHandle.Get(),
+ message,
+ sizeof(message),
+ &information,
+ nullptr)) {
+
+ throw ref new Exception(
+ HRESULT_FROM_WIN32(GetLastError()),
+ L"Failed to write data to COM port.");
+ }
+ }
+```
+
+Add a call to `AccessComPort()` in the MainPage constructor:
+
+``` C++
+ MainPage::MainPage()
+ {
+ InitializeComponent();
+ AccessComPort();
+ }
+```
+
+## Step 4: Deploy your app
+
+* If you're building for UP Board, select `x64` as the architecture.
+
+* Select **Local Machine** to point to IoT device and select *F5* on your keyboard to deploy to your device.
+
+## Step 5: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 6: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 7: Build the project
+
+This build should succeed since we made desktop APIs visible at compile time.
+
+Set a breakpoint on the `throw` statement after the file handle validity check, as indicated in the source code above.
+
+* Debug the application on UP Board. The breakpoint should get hit. Inspect the `lastError` variable in the debugger, which should equal 5 (Access Denied). We need to set a proper security descriptor on the device object so it can be accessed by UWP applications.
+
+## Step 8: Granting Access to AppContainer Processes
+
+Every device object in the system has an associated security descriptor. The security descriptor determines who has what access to a device object. Security descriptors have a binary representation which is used by the system to compute access to objects, and a human readable form called an SDDL string. Some examples of SDDL strings are:
+
+
+
+
+
SDDL String
+
Description
+
Wdmsec.h constant
+
+
+
+
+
"D:P"
+
Denies access to all, except other kernel-mode clients.
SDDL_DEVOBJ_KERNEL_ONLY
+
+
+
"D:P(A;;GA;;;SY)"
+
Denies access to all, except kernel mode code, and usermode clients running under the SYSTEM account.
+
SDDL_DEVOBJ_SYS_ALL
+
+
+
"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GR;;;WD)"
+
Grants full access to kernel mode clients and the SYSTEM account, grants read, write, execute to built-in Administrators, and grants read-only access to everyone else.
+
SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R
+
+
+
+
+A number of common security descriptor strings are defined in wdmsec.h.
+
+To make a device accessible to UWP applications, you need to grant access to the All Application Packages security principle, which is represented by the SID string "AC". The following SDDL will grant GENERIC_ALL permissions to SYSTEM, built-in administrators, authenticated users, and appcontainer applications:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)"
+
+If you control the code of the driver you wish to access, you can programatically assign an SDDL string to a device object using the [IoCreateDeviceObjectSecure()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff548407(v=vs.85).aspx) routine in WDM drivers, or the [WdfDeviceInitAssignSDDLString()](https://msdn.microsoft.com/en-us/library/windows/hardware/ff546035(v=vs.85).aspx) routine in WDF drivers.
+
+If you do not control the driver code for your device, you can override the SDDL for any device using the registry. If a registry value named "Security" is present in the hardware registry key for a device, the system will use the specified security descriptor instead of the one supplied by the driver. We will override the security descriptor for the COM port with one that grants access to all appcontainer applications.
+
+First, we need to convert the SDDL string to its binary representation. We can do this with [PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/09/use-powershell-to-convert-sddl-to-binary-format.aspx). Open a PowerShell prompt and run the following commands:
+
+```csharp
+ $a = ([wmiclass]"Win32_SecurityDescriptorHelper").SDDLToBinarySD("D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;AC)").BinarySD | % { '{0:X}' -f $_ }
+ $a -join ','
+```
+
+The output will be a long string of comma-separated numbers that we will paste into a registry file. Create a file named deviceac.reg with the following contents:
+
+ Windows Registry Editor Version 5.00
+
+ [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1]
+ "Security"=hex:1,0,4,90,0,0,0,0,0,0,0,0,0,0,0,0,14,0,0,0,2,0,60,0,4,0,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,12,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,5,20,0,0,0,20,2,0,0,0,0,14,0,0,0,0,10,1,1,0,0,0,0,0,5,B,0,0,0,0,0,18,0,0,0,0,10,1,2,0,0,0,0,0,F,2,0,0,0,1,0,0,0
+
+Copy this file to c:\data on your MBM and run:
+
+ schtasks /create /RU SYSTEM /SC ONCE /TN DeviceAC /TR "reg import c:\data\deviceac.reg" /ST 00:00
+ schtasks /run /tn DeviceAC
+ schtasks /delete /tn DeviceAC /f
+
+We use schtasks to run the reg import operation as SYSTEM, because only the SYSTEM account has permission to change registry keys under the enum key.
+
+Verify that the Security registry value was created by running:
+
+ reg query HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\PNP0501\1 /v Security
+
+If you don't see the Security value, something went wrong in the previous steps. If the Security value was created successfully, restart the device so the new security settings take effect:
+
+ Devcon restart acpi\pnp0501
+
+Now, debug the universal application again. The COM port should be opened successfully and the breakpoint above should not be hit.
+
+Congratulations, you have successfully opened a device and sent an IOCTL to it!
+
+## Step 9: Granting Access to a Specific Application
+
+The security identifier "AC" identifies all application packages, and will grant all apps access to the device. If you want to grant access to a specific application only, you can replace "AC" in the SDDL above with the app-specific SID of the application you'd like to target. You can inspect the app-specific SID with [process explorer](https://technet.microsoft.com/en-us/sysinternals/bb896653).
+
+Launch the app and launch process explorer. Open the properties dialog box for the process in process explorer and go to the Security tab. There you will see all of the security identifiers associated with the process's token. The SID with the AppContainer flag set is the app-specific SID.
+
+
+
+You can replace "AC" with this SID in the above SDDL to generate an SDDL that grants access to that specific application only. For example, the following SDDL would grant access only to the application shown above:
+
+ "D:P(A;;GA;;;SY)(A;;GA;;;BA)(A;;GA;;;AU)(A;;GA;;;S-1-15-3-2628158189-2540711686-3785793668-522787976-4226511596-526649915-1865015409)"
+
+SIDs are generated at application install time so can only be determined after the application has been installed on the target machine.
+
+For more information about app containers, see [Windows 8 App Container Security Notes - Part 1](http://recxltd.blogspot.com/2012/03/windows-8-app-container-security-notes.html).
diff --git a/samples/DualOperator/DualOperator/DualOperator.csproj.user b/samples/DualOperator/DualOperator/DualOperator.csproj.user
index 23e62fb04..8bdcc031d 100644
--- a/samples/DualOperator/DualOperator/DualOperator.csproj.user
+++ b/samples/DualOperator/DualOperator/DualOperator.csproj.user
@@ -1,11 +1,11 @@
-
-
-
-
- Form
-
-
- Form
-
-
+
+
+
+
+ Form
+
+
+ Form
+
+
\ No newline at end of file
diff --git a/samples/DualOperator/DualOperator/OperatorManager.resx b/samples/DualOperator/DualOperator/OperatorManager.resx
index b5ae26c78..f298a7be8 100644
--- a/samples/DualOperator/DualOperator/OperatorManager.resx
+++ b/samples/DualOperator/DualOperator/OperatorManager.resx
@@ -1,60 +1,60 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
\ No newline at end of file
diff --git a/samples/DualOperator/DualOperator/ScanOperator.resx b/samples/DualOperator/DualOperator/ScanOperator.resx
index b5ae26c78..f298a7be8 100644
--- a/samples/DualOperator/DualOperator/ScanOperator.resx
+++ b/samples/DualOperator/DualOperator/ScanOperator.resx
@@ -1,60 +1,60 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
\ No newline at end of file
diff --git a/samples/DualOperator/README.md b/samples/DualOperator/README.md
index d37b28486..4150f2427 100644
--- a/samples/DualOperator/README.md
+++ b/samples/DualOperator/README.md
@@ -1,117 +1,117 @@
-# Dual Operator
-
-Dual Operator is a conceptual sample application which demonstrates how input from 2 physical keyboards can be routed to specific applications docked full screen to separate display. Dual Operator receives keystrokes from both physical keyboards and routes them to the application to which the keyboard is associated.
-
-Teaser Trailer: http://aka.ms/dualoperatordemo
-MS Build 2022: https://aka.ms/MSBuild2022-DualOperator
-
-## Requirements
-
-- 2 physical keyboards
-- 2 monitors
-
-Dual Operator requires the full device ID as used by Windows for each keyboard registered. It also requires a unique portion of the title bar text to be paired with the keyboard output.
-
-Applications targeted by Dual Operator must have a visible window on any available monitor. This means that Windows services or any application that runs as a background task is not a target candidate because this type of application does not present a handle to the operating system. This handle is a necessity for receiving keystrokes whether they come from the OS or from Dual Operator.
-
-In addition to having a visible window, each application targeted should also be running in full screen mode on its own monitor running on Windows IoT Enterprise edition.
-
-## Devices
-
-Dual Operator demonstrates input isolation using 2 physical keyboards. Dual Operator does not provide input isolation for mouse or touch imput.
-
-## How it works
-In normal operation, on startup Dual Operator will read from a file named OPERATORS.JSON located in the same folder as the executable file for the system. The contents of the file look like this:
-
-```
-[
- {
- "ApplicationTitle": "Document1 - Word",
- "Keyboard": "\\\\?\\HID#VID_046D&PID_C541&MI_01&Col01#b&865bce8&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}"
- },
- {
- "ApplicationTitle": "Untitled - Notepad",
- "Keyboard": "\\\\?\\HID#{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0832_REV&0138_eb5864041ec3&Col01#9&19514786&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}"
- }
-]
-```
-
-The file is an array of application and keyboard objects paired together. The ApplicationTitle element in each object is the unique window text for the application. This value can be as much or little as desired providing the value uniquely identifies a specific window.
-
-The second element is the full device identifier. This is what Dual Operator uses to differentiate between keyboards and application targets. If input is received from any other keyboard attached to the system, Dual Operator will ignore the input and allow Windows to direct the keystroke to another application.
-
-Please note: the device identifier does not always follow the same naming convention across devices and in many cases, even coming from the same device manufacturer. In the example above, the first device is a Logitech G9 keyboard while the second device is a Logitech Bluetooth keyboard. Dual Operator provides a method of learning the various keyboards attached to the system - see the section on Command Line Parameters below.
-
-There can be only 2 array items defined. Dual Operator will ignore any items beyond the first two found.
-
-Dual Operator uses the Raw Input functions contained within the USER32.DLL module contained in Windows 8 and above. Through the use of a custom key mapper, Dual Operator can handle almost all recognizable keys along with their commonly used modifiers like ALT, CONTROL and SHIFT.
-
-Because Windows requires a visible window to receive keystrokes, Dual Operator has been written as a Windows Forms application in C# version 6 and .NET Core 5. Even though the application targets .NET Core, Dual Operator runs solely on the Windows platform because of its use of the native keyboard handling functions built into Windows.
-
-The window the application provides contains a text control that will show the device that produced a keystroke along with the scan code, the key state and other pertinent information about the keypress event. Although KEY DOWN key state events are shown in the text control, Dual Operator does not act on these as it only signifies that a key action has started. If the application responded to the KEY DOWN event, then multiple combinations of keys could be achieved (e.g., CTL-SHIFT-ESC). Only when all key combinations have generated their KEY UP events (signifying that the user is no longer pressing any key) does Dual Operator find the appropriate match for the event and pass the combined keystroke to the target application.
-
-## Command Line Parameters
-
-Dual Operator accepts two different command line parameters and an optional companion parameter for the first (the parameter is not case-sensitive):
-
-/LIST
-This parameter will generate a list of Human Interface Device items connected to the system. If the optional parameter is not used, the /LIST parameter will generate a file named DeviceAudit.txt in the same directory as the Dual Operator application. This list can be opened in any standard text editor and will help guide the selection of the proper keyboard identifiers to use in the OPERATORS.JSON file.
-
-{optional} Full file path and name
-This optional parameter will specify where to place the output from /LIST parameter.
-
-/SCAN
-This parameter will open a form which will allow the user to press any key on an attached keyboard to learn the full name for the device. Once a key has been pressed, the name can be copied to the clipboard or saved directly in the OPERATORS.JSON file as either keyboard 1 or 2.
-
-### Examples
-
-``
-dualoperator.exe /list
-``
-This will create a file in the current directory named DeviceAudit.txt
-
-``
-dualoperator.exe /list "C:\Temp\DeviceList.txt"
-``
-This will create the same output in a file named DeviceList.txt in the C:\Temp directory
-
-``
-dualoperator.exe /scan
-``
-This will open the Scan Operator form and allow identification of any attached keyboard
-
-
-## Demo app
-
-There is a demo target application provided with the Dual Operator code. This application looks very similar to the Dual Operator app but is intended to be a target for Dual Operator to use while testing.
-
-In the demo app directory there is a file named APPTITLE.JSON. This provides a unique title for the demo app making it easy to run 2 instances with different window names. The structure of the file looks like this:
-
-```
-[
- {
- "ApplicationTitle": "Demo App 1"
- }
-]
-```
-
-The ApplicationTitle element defines the text for the app window. It is possible to put a copy of this demo app in separate directories and by changing the ApplicationTitle to be unique values in each directory, two versions of this app can run as targets for Dual Operator.
-
-## Code structure
-
-### Root
-OperatorManager: the form used by Dual Operator to intercept keystrokes and all other associated top-level code and configuration objects
-
-### Enumerations
-Enumerations used throughout the application, such as KeyEvent
-
-### Helpers
-Code that helps drive function within the application (e.g. the custom Key Mapper component)
-
-### Models
-Classes used to serialize/deserialze data between systems (e.g., reading configuration from the OPERATORS.JSON file)
-
-### Structures
-C# STRUCT objects used to pass and receive information from the Raw Input functions (e.g., DeviceInfo which has metadata about the device which generated an event)
-
-
+# Dual Operator
+
+Dual Operator is a conceptual sample application which demonstrates how input from 2 physical keyboards can be routed to specific applications docked full screen to separate display. Dual Operator receives keystrokes from both physical keyboards and routes them to the application to which the keyboard is associated.
+
+Teaser Trailer: http://aka.ms/dualoperatordemo
+MS Build 2022: https://aka.ms/MSBuild2022-DualOperator
+
+## Requirements
+
+- 2 physical keyboards
+- 2 monitors
+
+Dual Operator requires the full device ID as used by Windows for each keyboard registered. It also requires a unique portion of the title bar text to be paired with the keyboard output.
+
+Applications targeted by Dual Operator must have a visible window on any available monitor. This means that Windows services or any application that runs as a background task is not a target candidate because this type of application does not present a handle to the operating system. This handle is a necessity for receiving keystrokes whether they come from the OS or from Dual Operator.
+
+In addition to having a visible window, each application targeted should also be running in full screen mode on its own monitor running on Windows IoT Enterprise edition.
+
+## Devices
+
+Dual Operator demonstrates input isolation using 2 physical keyboards. Dual Operator does not provide input isolation for mouse or touch imput.
+
+## How it works
+In normal operation, on startup Dual Operator will read from a file named OPERATORS.JSON located in the same folder as the executable file for the system. The contents of the file look like this:
+
+```
+[
+ {
+ "ApplicationTitle": "Document1 - Word",
+ "Keyboard": "\\\\?\\HID#VID_046D&PID_C541&MI_01&Col01#b&865bce8&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}"
+ },
+ {
+ "ApplicationTitle": "Untitled - Notepad",
+ "Keyboard": "\\\\?\\HID#{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0832_REV&0138_eb5864041ec3&Col01#9&19514786&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}"
+ }
+]
+```
+
+The file is an array of application and keyboard objects paired together. The ApplicationTitle element in each object is the unique window text for the application. This value can be as much or little as desired providing the value uniquely identifies a specific window.
+
+The second element is the full device identifier. This is what Dual Operator uses to differentiate between keyboards and application targets. If input is received from any other keyboard attached to the system, Dual Operator will ignore the input and allow Windows to direct the keystroke to another application.
+
+Please note: the device identifier does not always follow the same naming convention across devices and in many cases, even coming from the same device manufacturer. In the example above, the first device is a Logitech G9 keyboard while the second device is a Logitech Bluetooth keyboard. Dual Operator provides a method of learning the various keyboards attached to the system - see the section on Command Line Parameters below.
+
+There can be only 2 array items defined. Dual Operator will ignore any items beyond the first two found.
+
+Dual Operator uses the Raw Input functions contained within the USER32.DLL module contained in Windows 8 and above. Through the use of a custom key mapper, Dual Operator can handle almost all recognizable keys along with their commonly used modifiers like ALT, CONTROL and SHIFT.
+
+Because Windows requires a visible window to receive keystrokes, Dual Operator has been written as a Windows Forms application in C# version 6 and .NET Core 5. Even though the application targets .NET Core, Dual Operator runs solely on the Windows platform because of its use of the native keyboard handling functions built into Windows.
+
+The window the application provides contains a text control that will show the device that produced a keystroke along with the scan code, the key state and other pertinent information about the keypress event. Although KEY DOWN key state events are shown in the text control, Dual Operator does not act on these as it only signifies that a key action has started. If the application responded to the KEY DOWN event, then multiple combinations of keys could be achieved (e.g., CTL-SHIFT-ESC). Only when all key combinations have generated their KEY UP events (signifying that the user is no longer pressing any key) does Dual Operator find the appropriate match for the event and pass the combined keystroke to the target application.
+
+## Command Line Parameters
+
+Dual Operator accepts two different command line parameters and an optional companion parameter for the first (the parameter is not case-sensitive):
+
+/LIST
+This parameter will generate a list of Human Interface Device items connected to the system. If the optional parameter is not used, the /LIST parameter will generate a file named DeviceAudit.txt in the same directory as the Dual Operator application. This list can be opened in any standard text editor and will help guide the selection of the proper keyboard identifiers to use in the OPERATORS.JSON file.
+
+{optional} Full file path and name
+This optional parameter will specify where to place the output from /LIST parameter.
+
+/SCAN
+This parameter will open a form which will allow the user to press any key on an attached keyboard to learn the full name for the device. Once a key has been pressed, the name can be copied to the clipboard or saved directly in the OPERATORS.JSON file as either keyboard 1 or 2.
+
+### Examples
+
+``
+dualoperator.exe /list
+``
+This will create a file in the current directory named DeviceAudit.txt
+
+``
+dualoperator.exe /list "C:\Temp\DeviceList.txt"
+``
+This will create the same output in a file named DeviceList.txt in the C:\Temp directory
+
+``
+dualoperator.exe /scan
+``
+This will open the Scan Operator form and allow identification of any attached keyboard
+
+
+## Demo app
+
+There is a demo target application provided with the Dual Operator code. This application looks very similar to the Dual Operator app but is intended to be a target for Dual Operator to use while testing.
+
+In the demo app directory there is a file named APPTITLE.JSON. This provides a unique title for the demo app making it easy to run 2 instances with different window names. The structure of the file looks like this:
+
+```
+[
+ {
+ "ApplicationTitle": "Demo App 1"
+ }
+]
+```
+
+The ApplicationTitle element defines the text for the app window. It is possible to put a copy of this demo app in separate directories and by changing the ApplicationTitle to be unique values in each directory, two versions of this app can run as targets for Dual Operator.
+
+## Code structure
+
+### Root
+OperatorManager: the form used by Dual Operator to intercept keystrokes and all other associated top-level code and configuration objects
+
+### Enumerations
+Enumerations used throughout the application, such as KeyEvent
+
+### Helpers
+Code that helps drive function within the application (e.g. the custom Key Mapper component)
+
+### Models
+Classes used to serialize/deserialze data between systems (e.g., reading configuration from the OPERATORS.JSON file)
+
+### Structures
+C# STRUCT objects used to pass and receive information from the Raw Input functions (e.g., DeviceInfo which has metadata about the device which generated an event)
+
+
diff --git a/samples/DualOperator/TestApp/Form1.resx b/samples/DualOperator/TestApp/Form1.resx
index b5ae26c78..f298a7be8 100644
--- a/samples/DualOperator/TestApp/Form1.resx
+++ b/samples/DualOperator/TestApp/Form1.resx
@@ -1,60 +1,60 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
\ No newline at end of file
diff --git a/samples/DualOperator/TestApp/TestApp.csproj.user b/samples/DualOperator/TestApp/TestApp.csproj.user
index f61322e84..7814ea24e 100644
--- a/samples/DualOperator/TestApp/TestApp.csproj.user
+++ b/samples/DualOperator/TestApp/TestApp.csproj.user
@@ -1,8 +1,8 @@
-
-
-
-
- Form
-
-
-
+
+
+
+
+ Form
+
+
+
diff --git a/samples/ExternalProcessLauncher/CS/ProcessLauncherSample/Properties/Default.rd.xml b/samples/ExternalProcessLauncher/CS/ProcessLauncherSample/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/ExternalProcessLauncher/CS/ProcessLauncherSample/Properties/Default.rd.xml
+++ b/samples/ExternalProcessLauncher/CS/ProcessLauncherSample/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/ExternalProcessLauncher/CS/README.md b/samples/ExternalProcessLauncher/CS/README.md
index a3cef6a4b..df5970963 100644
--- a/samples/ExternalProcessLauncher/CS/README.md
+++ b/samples/ExternalProcessLauncher/CS/README.md
@@ -1,206 +1,206 @@
----
-page_type: sample
-urlFragment: external-process-launcher
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using the Windows.System.ProcessLauncher API with Windows 10 IoT Enterprise.
----
-
-# External process launcher
-
-We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using `Windows.System.ProcessLauncher` API.
-
-## Step 1: Load the project in Visual Studio
-
-You can find the source code for this sample by downloading a zip of all of our samples. Make a copy of the folder on your disk and open the project from [Visual Studio 2019](https://www.visualstudio.com/downloads/).
-
-This is a Universal Windows application.
-
-Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-The code for the ProcessLauncher sample can be found under: \ProcessLauncher\CS
-
-## Step 2: Deploy your app
-
-1. For building on UP Board, select `x64` as the architecture.
-
-1. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 3: Test your app
-
-The sample app when deployed displays a screen similar to this one:
-
-
-
-Go ahead, click the **Run Command** button to launch the application specified in the **Command** edit box, SampleConsoleApplication.exe, which is an executable Win32 application built and deployed from the sample app as well.
-
-When run, the SampleConsoleApplication exe, will send output to both the Standard Output and Standard Error boxes. The return error code of the process, 100, should also be shown.
-
-
-
-## Let's take a look at the code
-
-The code for this sample makes use of the `Windows.System.ProcessLauncher` API, which is part of the system management contract APIs available on Windows IoT Enterprise.
-
-To use the API, we need to do a couple of things.
-
-### Add a reference to the Windows IoT extension SDK
-
-Since the IoT extension SDK is not added to projects by default, we'll need to add a reference to it so its types, including `Windows.System.SystemManagement.ProcessLauncher`, will be available in the project.
-
-To do so, right-click on the References entry under the project, select "Add Reference" then navigate the resulting dialog to `Universal Windows->Extensions->Windows IoT Extensions for the UWP` making sure the right version, 10.0.10586.0 or higher, is selected, then check the box, and click OK.
-
-
-
-
-### Add systemManagement capabiity
-
-Accessing the `Windows.System.ProcessLauncher` API from your code requires the `systemManagement` IOT Capability. So, we need to add it to the AppX manifest, **Package.appxmanifest** file:
-
-**NOTE:** While you can add other capabilities directly by double clicking and opening the **Package.appxmanifest** file in the UI editor, **systemManagement** capability can only be added via the XML editor (Right Click on the file -> Open with -> XML (Text) Editor) and adding the capability below:
-
-``` xml
-
-
-
-
-
-
-
-
-```
-
-### Launching a process
-
-The `ProcessLauncher` API providers a number of static method overloads to launch new apps using the executable file name plus optional arguments and other options.
-
-Here's the part of the sample that launches the new process. After the process is launched, we `await` its return to get the exit code.
-
-```csharp
-var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
-
-ProcessExitCode.Text += "Process Exit Code: " + result.ExitCode;
-```
-
-### Using standard streams
-
-While the exit code is often enough to let us know if an executable has succeeded or not, sometimes we need to read the output from the program; e.g. to log information or to show that text in the app.
-
-The `ProcessLauncherOptions` class allows sharing the standard input, output and error streams between the UWP app and external process.
-
-* `ProcessLauncherOptions.StandardInput` is of type `Windows.Storage.Streams.IInputStream` and is **read from** by the external process
-* Both `ProcessLauncherOptions.StandardOutput` and `ProcessLauncherOptions.StandardError` are `Windows.Storage.Streams.IInputStream` properties and are used by the external process to **write to** standard output or standard error
-
-Now, let's learn how to pass output streams to the executable and then read what was written to it.
-
-To be able to both read and write data to strams, we create the streams as `Windows.Storage.Streams.InMemoryRandomAccessStream` objects. `InMemoryRandomAccessStream` can be casted as both Input or Output streams, which is exactly what we need. We will pass it as `IOutputStream` to the `ProcessLauncherOptions`, and then read data from it as an `IInputStream` after the external exe has completed writing to it.
-
-Here's the relavant code from the sample. First, we initialize the stream objects:
-
-```csharp
-var options = new ProcessLauncherOptions();
-var standardOutput = new InMemoryRandomAccessStream();
-var standardError = new InMemoryRandomAccessStream();
-options.StandardOutput = standardOutput;
-options.StandardError = standardError;
-```
-
-Then, we pass the options to the `RunToCompletionAsync()` method:
-
-```csharp
-var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
-```
-
-Finally, we read the data from the `InMemoryRandomAccessStream` after getting it as an input stream:
-
-```csharp
-using (var outStreamRedirect = standardOutput.GetInputStreamAt(0))
-{
- var size = standardOutput.Size;
- using (var dataReader = new DataReader(outStreamRedirect))
- {
- var bytesLoaded = await dataReader.LoadAsync((uint)size);
- var stringRead = dataReader.ReadString(bytesLoaded);
- StdOutputText.Text += stringRead;
- }
-}
-```
-
-**Note**, while not used in the sample, the standard input stream can be used with the `ProcessLauncher` API as well.
-
-### Including an executable application with the AppX package
-
-The `ProcessLauncher` API can launch executable programs packaged as part of the same AppX. So, a sample Win32 console app, SampleConsoleApplication, is included in the sample.
-
-The program itself is quite simple, but it demonstrates the various aspects of the ProcessLauncher API, including argument passing and sharing standard output and standard error streams.
-
-Here's the main method of the sample console app:
-
-``` c++
-int main(int argc, char **argv)
-{
- std::cout << "Hi there!" << std::endl;
- std::cout << "I'm running in a different process!" << std::endl << std::endl;
-
- std::cout << "There are " << argc << " arguments passed to this application (including the exe name):" << std::endl;
- for (int i = 0; i < argc; i++)
- {
- std::cout << "\t" << i << ") \"" << argv[i] << "\"" << std::endl;
- }
-
- std::cerr << "Nothing is wrong! I just wanted to try writing to the std error stream." << std::endl;
-
- return 100;
-}
-```
-
-The application has been added to the solution as a *console application*.
-
-To be able to find and invoke the SampleConsoleApplication exe at runtime, we need to package the output exe with the AppX. We've already added it to the sample application. However, to do the same in your own application, you can follow these steps:
-
-1. Put the output exe in the same folder as the C# sample. Right click on the C++ console app project, select *Properties*, then open the *General* tab
-1. Change the output directory to the be the same as the C# sample (or a subfolder) and click OK 
-1. Build the console application to create and put the exe in its new location
-1. Add the exe to the UWP projct: Right click on the Project, select *Add -> Existing Item*
-1. Browse to and select the exe just built
-1. After the exe is added to the UWP project, we need to make sure it's added to the AppX package layout, Right click on the exe, select *Properties*
-1. Change *Build Action* to *Content*
-1. Change *Copy to Output Directory* to *Always*
-
-
-
-1. Finaly, to ensure the exe is built every time the main app is deployed, we need to change the project dependency, Right click the solution, select *Project Dependencies* and make the UWP project have a dependency on the console app 
-
-Now, everytime the solution is built or deployed, it'll ensure the console application exe is up-to-date and deployed with the rest of the AppX.
-
-## Run more executables
-
-When a relative path is specified; such as *SampleConsoleApp.exe*, *.\SampleConsoleApp.exe* or a subfolder, *subfolder\SampleConsoleApp.exe*, the `ProcessLauncher` API looks for the exe file starting at the package root of the AppX deployed.
-
-However, the API is also capable of running apps anywhere on the device, by specifying the absolute path; e.g. c:\windows.system32\ipconfig.exe
-
-To use an external exe, that exe must be added to an **allow list**. This is needed to prevent malicious apps from running.
-
-To add an exe to the **allow list**, add to or replace the reg value in the reg command below:
-
-`reg.exe ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\ipconfig.exe\0c:\windows\system32\tlist.exe\0"`
-
-**Note**, `ProcessLauncher` API launches executables under the current user credentials, or **DefautlAccount**, so apps requiring admin priviliges will fail to run properly.
-
-Go ahead, run the command above on your device, using SSH or PowerShell. Then, in the sample app (no need to restart) type the command `c:\windows\system32\ipconfig.exe`. You should get an output similar to the one below:
-
-
-
+---
+page_type: sample
+urlFragment: external-process-launcher
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using the Windows.System.ProcessLauncher API with Windows 10 IoT Enterprise.
+---
+
+# External process launcher
+
+We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using `Windows.System.ProcessLauncher` API.
+
+## Step 1: Load the project in Visual Studio
+
+You can find the source code for this sample by downloading a zip of all of our samples. Make a copy of the folder on your disk and open the project from [Visual Studio 2019](https://www.visualstudio.com/downloads/).
+
+This is a Universal Windows application.
+
+Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+The code for the ProcessLauncher sample can be found under: \ProcessLauncher\CS
+
+## Step 2: Deploy your app
+
+1. For building on UP Board, select `x64` as the architecture.
+
+1. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 3: Test your app
+
+The sample app when deployed displays a screen similar to this one:
+
+
+
+Go ahead, click the **Run Command** button to launch the application specified in the **Command** edit box, SampleConsoleApplication.exe, which is an executable Win32 application built and deployed from the sample app as well.
+
+When run, the SampleConsoleApplication exe, will send output to both the Standard Output and Standard Error boxes. The return error code of the process, 100, should also be shown.
+
+
+
+## Let's take a look at the code
+
+The code for this sample makes use of the `Windows.System.ProcessLauncher` API, which is part of the system management contract APIs available on Windows IoT Enterprise.
+
+To use the API, we need to do a couple of things.
+
+### Add a reference to the Windows IoT extension SDK
+
+Since the IoT extension SDK is not added to projects by default, we'll need to add a reference to it so its types, including `Windows.System.SystemManagement.ProcessLauncher`, will be available in the project.
+
+To do so, right-click on the References entry under the project, select "Add Reference" then navigate the resulting dialog to `Universal Windows->Extensions->Windows IoT Extensions for the UWP` making sure the right version, 10.0.10586.0 or higher, is selected, then check the box, and click OK.
+
+
+
+
+### Add systemManagement capabiity
+
+Accessing the `Windows.System.ProcessLauncher` API from your code requires the `systemManagement` IOT Capability. So, we need to add it to the AppX manifest, **Package.appxmanifest** file:
+
+**NOTE:** While you can add other capabilities directly by double clicking and opening the **Package.appxmanifest** file in the UI editor, **systemManagement** capability can only be added via the XML editor (Right Click on the file -> Open with -> XML (Text) Editor) and adding the capability below:
+
+``` xml
+
+
+
+
+
+
+
+
+```
+
+### Launching a process
+
+The `ProcessLauncher` API providers a number of static method overloads to launch new apps using the executable file name plus optional arguments and other options.
+
+Here's the part of the sample that launches the new process. After the process is launched, we `await` its return to get the exit code.
+
+```csharp
+var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
+
+ProcessExitCode.Text += "Process Exit Code: " + result.ExitCode;
+```
+
+### Using standard streams
+
+While the exit code is often enough to let us know if an executable has succeeded or not, sometimes we need to read the output from the program; e.g. to log information or to show that text in the app.
+
+The `ProcessLauncherOptions` class allows sharing the standard input, output and error streams between the UWP app and external process.
+
+* `ProcessLauncherOptions.StandardInput` is of type `Windows.Storage.Streams.IInputStream` and is **read from** by the external process
+* Both `ProcessLauncherOptions.StandardOutput` and `ProcessLauncherOptions.StandardError` are `Windows.Storage.Streams.IInputStream` properties and are used by the external process to **write to** standard output or standard error
+
+Now, let's learn how to pass output streams to the executable and then read what was written to it.
+
+To be able to both read and write data to strams, we create the streams as `Windows.Storage.Streams.InMemoryRandomAccessStream` objects. `InMemoryRandomAccessStream` can be casted as both Input or Output streams, which is exactly what we need. We will pass it as `IOutputStream` to the `ProcessLauncherOptions`, and then read data from it as an `IInputStream` after the external exe has completed writing to it.
+
+Here's the relavant code from the sample. First, we initialize the stream objects:
+
+```csharp
+var options = new ProcessLauncherOptions();
+var standardOutput = new InMemoryRandomAccessStream();
+var standardError = new InMemoryRandomAccessStream();
+options.StandardOutput = standardOutput;
+options.StandardError = standardError;
+```
+
+Then, we pass the options to the `RunToCompletionAsync()` method:
+
+```csharp
+var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
+```
+
+Finally, we read the data from the `InMemoryRandomAccessStream` after getting it as an input stream:
+
+```csharp
+using (var outStreamRedirect = standardOutput.GetInputStreamAt(0))
+{
+ var size = standardOutput.Size;
+ using (var dataReader = new DataReader(outStreamRedirect))
+ {
+ var bytesLoaded = await dataReader.LoadAsync((uint)size);
+ var stringRead = dataReader.ReadString(bytesLoaded);
+ StdOutputText.Text += stringRead;
+ }
+}
+```
+
+**Note**, while not used in the sample, the standard input stream can be used with the `ProcessLauncher` API as well.
+
+### Including an executable application with the AppX package
+
+The `ProcessLauncher` API can launch executable programs packaged as part of the same AppX. So, a sample Win32 console app, SampleConsoleApplication, is included in the sample.
+
+The program itself is quite simple, but it demonstrates the various aspects of the ProcessLauncher API, including argument passing and sharing standard output and standard error streams.
+
+Here's the main method of the sample console app:
+
+``` c++
+int main(int argc, char **argv)
+{
+ std::cout << "Hi there!" << std::endl;
+ std::cout << "I'm running in a different process!" << std::endl << std::endl;
+
+ std::cout << "There are " << argc << " arguments passed to this application (including the exe name):" << std::endl;
+ for (int i = 0; i < argc; i++)
+ {
+ std::cout << "\t" << i << ") \"" << argv[i] << "\"" << std::endl;
+ }
+
+ std::cerr << "Nothing is wrong! I just wanted to try writing to the std error stream." << std::endl;
+
+ return 100;
+}
+```
+
+The application has been added to the solution as a *console application*.
+
+To be able to find and invoke the SampleConsoleApplication exe at runtime, we need to package the output exe with the AppX. We've already added it to the sample application. However, to do the same in your own application, you can follow these steps:
+
+1. Put the output exe in the same folder as the C# sample. Right click on the C++ console app project, select *Properties*, then open the *General* tab
+1. Change the output directory to the be the same as the C# sample (or a subfolder) and click OK 
+1. Build the console application to create and put the exe in its new location
+1. Add the exe to the UWP projct: Right click on the Project, select *Add -> Existing Item*
+1. Browse to and select the exe just built
+1. After the exe is added to the UWP project, we need to make sure it's added to the AppX package layout, Right click on the exe, select *Properties*
+1. Change *Build Action* to *Content*
+1. Change *Copy to Output Directory* to *Always*
+
+
+
+1. Finaly, to ensure the exe is built every time the main app is deployed, we need to change the project dependency, Right click the solution, select *Project Dependencies* and make the UWP project have a dependency on the console app 
+
+Now, everytime the solution is built or deployed, it'll ensure the console application exe is up-to-date and deployed with the rest of the AppX.
+
+## Run more executables
+
+When a relative path is specified; such as *SampleConsoleApp.exe*, *.\SampleConsoleApp.exe* or a subfolder, *subfolder\SampleConsoleApp.exe*, the `ProcessLauncher` API looks for the exe file starting at the package root of the AppX deployed.
+
+However, the API is also capable of running apps anywhere on the device, by specifying the absolute path; e.g. c:\windows.system32\ipconfig.exe
+
+To use an external exe, that exe must be added to an **allow list**. This is needed to prevent malicious apps from running.
+
+To add an exe to the **allow list**, add to or replace the reg value in the reg command below:
+
+`reg.exe ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\ipconfig.exe\0c:\windows\system32\tlist.exe\0"`
+
+**Note**, `ProcessLauncher` API launches executables under the current user credentials, or **DefautlAccount**, so apps requiring admin priviliges will fail to run properly.
+
+Go ahead, run the command above on your device, using SSH or PowerShell. Then, in the sample app (no need to restart) type the command `c:\windows\system32\ipconfig.exe`. You should get an output similar to the one below:
+
+
+
diff --git a/samples/ExternalProcessLauncher/README.md b/samples/ExternalProcessLauncher/README.md
index 28a7b688b..17643ce98 100644
--- a/samples/ExternalProcessLauncher/README.md
+++ b/samples/ExternalProcessLauncher/README.md
@@ -1,206 +1,206 @@
----
-page_type: sample
-urlFragment: external-process-launcher
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using the Windows.System.ProcessLauncher API with Windows 10 IoT Enterprise.
----
-
-# External process launcher
-
-We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using `Windows.System.ProcessLauncher` API.
-
-## Step 1: Load the project in Visual Studio
-
-You can find the source code for this sample by downloading a zip of all of our samples. Make a copy of the folder on your disk and open the project from [Visual Studio 2019](https://www.visualstudio.com/downloads/).
-
-This is a Universal Windows application.
-
-Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-The code for the ProcessLauncher sample can be found under: \ProcessLauncher\CS
-
-## Step 2: Deploy your app
-
-1. For building on UP Board, select `x64` as the architecture.
-
-1. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 3: Test your app
-
-The sample app when deployed displays a screen similar to this one:
-
-
-
-Go ahead, click the **Run Command** button to launch the application specified in the **Command** edit box, SampleConsoleApplication.exe, which is an executable Win32 application built and deployed from the sample app as well.
-
-When run, the SampleConsoleApplication exe, will send output to both the Standard Output and Standard Error boxes. The return error code of the process, 100, should also be shown.
-
-
-
-## Let's take a look at the code
-
-The code for this sample makes use of the `Windows.System.ProcessLauncher` API, which is part of the system management contract APIs available on Windows IoT Enterprise.
-
-To use the API, we need to do a couple of things.
-
-### Add a reference to the Windows IoT extension SDK
-
-Since the IoT extension SDK is not added to projects by default, we'll need to add a reference to it so its types, including `Windows.System.SystemManagement.ProcessLauncher`, will be available in the project.
-
-To do so, right-click on the References entry under the project, select "Add Reference" then navigate the resulting dialog to `Universal Windows->Extensions->Windows IoT Extensions for the UWP` making sure the right version, 10.0.10586.0 or higher, is selected, then check the box, and click OK.
-
-
-
-
-### Add systemManagement capabiity
-
-Accessing the `Windows.System.ProcessLauncher` API from your code requires the `systemManagement` IOT Capability. So, we need to add it to the AppX manifest, **Package.appxmanifest** file:
-
-**NOTE:** While you can add other capabilities directly by double clicking and opening the **Package.appxmanifest** file in the UI editor, **systemManagement** capability can only be added via the XML editor (Right Click on the file -> Open with -> XML (Text) Editor) and adding the capability below:
-
-``` xml
-
-
-
-
-
-
-
-
-```
-
-### Launching a process
-
-The `ProcessLauncher` API providers a number of static method overloads to launch new apps using the executable file name plus optional arguments and other options.
-
-Here's the part of the sample that launches the new process. After the process is launched, we `await` its return to get the exit code.
-
-```csharp
-var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
-
-ProcessExitCode.Text += "Process Exit Code: " + result.ExitCode;
-```
-
-### Using standard streams
-
-While the exit code is often enough to let us know if an executable has succeeded or not, sometimes we need to read the output from the program; e.g. to log information or to show that text in the app.
-
-The `ProcessLauncherOptions` class allows sharing the standard input, output and error streams between the UWP app and external process.
-
-* `ProcessLauncherOptions.StandardInput` is of type `Windows.Storage.Streams.IInputStream` and is **read from** by the external process
-* Both `ProcessLauncherOptions.StandardOutput` and `ProcessLauncherOptions.StandardError` are `Windows.Storage.Streams.IInputStream` properties and are used by the external process to **write to** standard output or standard error
-
-Now, let's learn how to pass output streams to the executable and then read what was written to it.
-
-To be able to both read and write data to strams, we create the streams as `Windows.Storage.Streams.InMemoryRandomAccessStream` objects. `InMemoryRandomAccessStream` can be casted as both Input or Output streams, which is exactly what we need. We will pass it as `IOutputStream` to the `ProcessLauncherOptions`, and then read data from it as an `IInputStream` after the external exe has completed writing to it.
-
-Here's the relavant code from the sample. First, we initialize the stream objects:
-
-```csharp
-var options = new ProcessLauncherOptions();
-var standardOutput = new InMemoryRandomAccessStream();
-var standardError = new InMemoryRandomAccessStream();
-options.StandardOutput = standardOutput;
-options.StandardError = standardError;
-```
-
-Then, we pass the options to the `RunToCompletionAsync()` method:
-
-```csharp
-var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
-```
-
-Finally, we read the data from the `InMemoryRandomAccessStream` after getting it as an input stream:
-
-```csharp
-using (var outStreamRedirect = standardOutput.GetInputStreamAt(0))
-{
- var size = standardOutput.Size;
- using (var dataReader = new DataReader(outStreamRedirect))
- {
- var bytesLoaded = await dataReader.LoadAsync((uint)size);
- var stringRead = dataReader.ReadString(bytesLoaded);
- StdOutputText.Text += stringRead;
- }
-}
-```
-
-**Note**, while not used in the sample, the standard input stream can be used with the `ProcessLauncher` API as well.
-
-### Including an executable application with the AppX package
-
-The `ProcessLauncher` API can launch executable programs packaged as part of the same AppX. So, a sample Win32 console app, SampleConsoleApplication, is included in the sample.
-
-The program itself is quite simple, but it demonstrates the various aspects of the ProcessLauncher API, including argument passing and sharing standard output and standard error streams.
-
-Here's the main method of the sample console app:
-
-``` c++
-int main(int argc, char **argv)
-{
- std::cout << "Hi there!" << std::endl;
- std::cout << "I'm running in a different process!" << std::endl << std::endl;
-
- std::cout << "There are " << argc << " arguments passed to this application (including the exe name):" << std::endl;
- for (int i = 0; i < argc; i++)
- {
- std::cout << "\t" << i << ") \"" << argv[i] << "\"" << std::endl;
- }
-
- std::cerr << "Nothing is wrong! I just wanted to try writing to the std error stream." << std::endl;
-
- return 100;
-}
-```
-
-The application has been added to the solution as a *console application*.
-
-To be able to find and invoke the SampleConsoleApplication exe at runtime, we need to package the output exe with the AppX. We've already added it to the sample application. However, to do the same in your own application, you can follow these steps:
-
-1. Put the output exe in the same folder as the C# sample. Right click on the C++ console app project, select *Properties*, then open the *General* tab
-1. Change the output directory to the be the same as the C# sample (or a subfolder) and click OK 
-1. Build the console application to create and put the exe in its new location
-1. Add the exe to the UWP projct: Right click on the Project, select *Add -> Existing Item*
-1. Browse to and select the exe just built
-1. After the exe is added to the UWP project, we need to make sure it's added to the AppX package layout, Right click on the exe, select *Properties*
-1. Change *Build Action* to *Content*
-1. Change *Copy to Output Directory* to *Always*
-
-
-
-1. Finaly, to ensure the exe is built every time the main app is deployed, we need to change the project dependency, Right click the solution, select *Project Dependencies* and make the UWP project have a dependency on the console app 
-
-Now, everytime the solution is built or deployed, it'll ensure the console application exe is up-to-date and deployed with the rest of the AppX.
-
-## Run more executables
-
-When a relative path is specified; such as *SampleConsoleApp.exe*, *.\SampleConsoleApp.exe* or a subfolder, *subfolder\SampleConsoleApp.exe*, the `ProcessLauncher` API looks for the exe file starting at the package root of the AppX deployed.
-
-However, the API is also capable of running apps anywhere on the device, by specifying the absolute path; e.g. c:\windows.system32\ipconfig.exe
-
-To use an external exe, that exe must be added to an **allow list**. This is needed to prevent malicious apps from running.
-
-To add an exe to the **allow list**, add to or replace the reg value in the reg command below:
-
-`reg.exe ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\ipconfig.exe\0c:\windows\system32\tlist.exe\0"`
-
-**Note**, `ProcessLauncher` API launches executables under the current user credentials, or **DefautlAccount**, so apps requiring admin priviliges will fail to run properly.
-
-Go ahead, run the command above on your device, using SSH or PowerShell. Then, in the sample app (no need to restart) type the command `c:\windows\system32\ipconfig.exe`. You should get an output similar to the one below:
-
-
-
+---
+page_type: sample
+urlFragment: external-process-launcher
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using the Windows.System.ProcessLauncher API with Windows 10 IoT Enterprise.
+---
+
+# External process launcher
+
+We'll learn how to launch an external process (exe) from a Universal Windows Platform (UWP) app using `Windows.System.ProcessLauncher` API.
+
+## Step 1: Load the project in Visual Studio
+
+You can find the source code for this sample by downloading a zip of all of our samples. Make a copy of the folder on your disk and open the project from [Visual Studio 2019](https://www.visualstudio.com/downloads/).
+
+This is a Universal Windows application.
+
+Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+The code for the ProcessLauncher sample can be found under: \ProcessLauncher\CS
+
+## Step 2: Deploy your app
+
+1. For building on UP Board, select `x64` as the architecture.
+
+1. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 3: Test your app
+
+The sample app when deployed displays a screen similar to this one:
+
+
+
+Go ahead, click the **Run Command** button to launch the application specified in the **Command** edit box, SampleConsoleApplication.exe, which is an executable Win32 application built and deployed from the sample app as well.
+
+When run, the SampleConsoleApplication exe, will send output to both the Standard Output and Standard Error boxes. The return error code of the process, 100, should also be shown.
+
+
+
+## Let's take a look at the code
+
+The code for this sample makes use of the `Windows.System.ProcessLauncher` API, which is part of the system management contract APIs available on Windows IoT Enterprise.
+
+To use the API, we need to do a couple of things.
+
+### Add a reference to the Windows IoT extension SDK
+
+Since the IoT extension SDK is not added to projects by default, we'll need to add a reference to it so its types, including `Windows.System.SystemManagement.ProcessLauncher`, will be available in the project.
+
+To do so, right-click on the References entry under the project, select "Add Reference" then navigate the resulting dialog to `Universal Windows->Extensions->Windows IoT Extensions for the UWP` making sure the right version, 10.0.10586.0 or higher, is selected, then check the box, and click OK.
+
+
+
+
+### Add systemManagement capabiity
+
+Accessing the `Windows.System.ProcessLauncher` API from your code requires the `systemManagement` IOT Capability. So, we need to add it to the AppX manifest, **Package.appxmanifest** file:
+
+**NOTE:** While you can add other capabilities directly by double clicking and opening the **Package.appxmanifest** file in the UI editor, **systemManagement** capability can only be added via the XML editor (Right Click on the file -> Open with -> XML (Text) Editor) and adding the capability below:
+
+``` xml
+
+
+
+
+
+
+
+
+```
+
+### Launching a process
+
+The `ProcessLauncher` API providers a number of static method overloads to launch new apps using the executable file name plus optional arguments and other options.
+
+Here's the part of the sample that launches the new process. After the process is launched, we `await` its return to get the exit code.
+
+```csharp
+var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
+
+ProcessExitCode.Text += "Process Exit Code: " + result.ExitCode;
+```
+
+### Using standard streams
+
+While the exit code is often enough to let us know if an executable has succeeded or not, sometimes we need to read the output from the program; e.g. to log information or to show that text in the app.
+
+The `ProcessLauncherOptions` class allows sharing the standard input, output and error streams between the UWP app and external process.
+
+* `ProcessLauncherOptions.StandardInput` is of type `Windows.Storage.Streams.IInputStream` and is **read from** by the external process
+* Both `ProcessLauncherOptions.StandardOutput` and `ProcessLauncherOptions.StandardError` are `Windows.Storage.Streams.IInputStream` properties and are used by the external process to **write to** standard output or standard error
+
+Now, let's learn how to pass output streams to the executable and then read what was written to it.
+
+To be able to both read and write data to strams, we create the streams as `Windows.Storage.Streams.InMemoryRandomAccessStream` objects. `InMemoryRandomAccessStream` can be casted as both Input or Output streams, which is exactly what we need. We will pass it as `IOutputStream` to the `ProcessLauncherOptions`, and then read data from it as an `IInputStream` after the external exe has completed writing to it.
+
+Here's the relavant code from the sample. First, we initialize the stream objects:
+
+```csharp
+var options = new ProcessLauncherOptions();
+var standardOutput = new InMemoryRandomAccessStream();
+var standardError = new InMemoryRandomAccessStream();
+options.StandardOutput = standardOutput;
+options.StandardError = standardError;
+```
+
+Then, we pass the options to the `RunToCompletionAsync()` method:
+
+```csharp
+var result = await ProcessLauncher.RunToCompletionAsync(cmd.Text, args.Text == null ? string.Empty : args.Text, options);
+```
+
+Finally, we read the data from the `InMemoryRandomAccessStream` after getting it as an input stream:
+
+```csharp
+using (var outStreamRedirect = standardOutput.GetInputStreamAt(0))
+{
+ var size = standardOutput.Size;
+ using (var dataReader = new DataReader(outStreamRedirect))
+ {
+ var bytesLoaded = await dataReader.LoadAsync((uint)size);
+ var stringRead = dataReader.ReadString(bytesLoaded);
+ StdOutputText.Text += stringRead;
+ }
+}
+```
+
+**Note**, while not used in the sample, the standard input stream can be used with the `ProcessLauncher` API as well.
+
+### Including an executable application with the AppX package
+
+The `ProcessLauncher` API can launch executable programs packaged as part of the same AppX. So, a sample Win32 console app, SampleConsoleApplication, is included in the sample.
+
+The program itself is quite simple, but it demonstrates the various aspects of the ProcessLauncher API, including argument passing and sharing standard output and standard error streams.
+
+Here's the main method of the sample console app:
+
+``` c++
+int main(int argc, char **argv)
+{
+ std::cout << "Hi there!" << std::endl;
+ std::cout << "I'm running in a different process!" << std::endl << std::endl;
+
+ std::cout << "There are " << argc << " arguments passed to this application (including the exe name):" << std::endl;
+ for (int i = 0; i < argc; i++)
+ {
+ std::cout << "\t" << i << ") \"" << argv[i] << "\"" << std::endl;
+ }
+
+ std::cerr << "Nothing is wrong! I just wanted to try writing to the std error stream." << std::endl;
+
+ return 100;
+}
+```
+
+The application has been added to the solution as a *console application*.
+
+To be able to find and invoke the SampleConsoleApplication exe at runtime, we need to package the output exe with the AppX. We've already added it to the sample application. However, to do the same in your own application, you can follow these steps:
+
+1. Put the output exe in the same folder as the C# sample. Right click on the C++ console app project, select *Properties*, then open the *General* tab
+1. Change the output directory to the be the same as the C# sample (or a subfolder) and click OK 
+1. Build the console application to create and put the exe in its new location
+1. Add the exe to the UWP projct: Right click on the Project, select *Add -> Existing Item*
+1. Browse to and select the exe just built
+1. After the exe is added to the UWP project, we need to make sure it's added to the AppX package layout, Right click on the exe, select *Properties*
+1. Change *Build Action* to *Content*
+1. Change *Copy to Output Directory* to *Always*
+
+
+
+1. Finaly, to ensure the exe is built every time the main app is deployed, we need to change the project dependency, Right click the solution, select *Project Dependencies* and make the UWP project have a dependency on the console app 
+
+Now, everytime the solution is built or deployed, it'll ensure the console application exe is up-to-date and deployed with the rest of the AppX.
+
+## Run more executables
+
+When a relative path is specified; such as *SampleConsoleApp.exe*, *.\SampleConsoleApp.exe* or a subfolder, *subfolder\SampleConsoleApp.exe*, the `ProcessLauncher` API looks for the exe file starting at the package root of the AppX deployed.
+
+However, the API is also capable of running apps anywhere on the device, by specifying the absolute path; e.g. c:\windows.system32\ipconfig.exe
+
+To use an external exe, that exe must be added to an **allow list**. This is needed to prevent malicious apps from running.
+
+To add an exe to the **allow list**, add to or replace the reg value in the reg command below:
+
+`reg.exe ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\ipconfig.exe\0c:\windows\system32\tlist.exe\0"`
+
+**Note**, `ProcessLauncher` API launches executables under the current user credentials, or **DefautlAccount**, so apps requiring admin priviliges will fail to run properly.
+
+Go ahead, run the command above on your device, using SSH or PowerShell. Then, in the sample app (no need to restart) type the command `c:\windows\system32\ipconfig.exe`. You should get an output similar to the one below:
+
+
+
diff --git a/samples/FlowVolume/CS/FlowVolume/Properties/Default.rd.xml b/samples/FlowVolume/CS/FlowVolume/Properties/Default.rd.xml
index 74b03e3f8..af00722cd 100644
--- a/samples/FlowVolume/CS/FlowVolume/Properties/Default.rd.xml
+++ b/samples/FlowVolume/CS/FlowVolume/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/FlowVolume/CS/README.md b/samples/FlowVolume/CS/README.md
index 7fafeb936..604bf2ed9 100644
--- a/samples/FlowVolume/CS/README.md
+++ b/samples/FlowVolume/CS/README.md
@@ -1,111 +1,111 @@
----
-page_type: sample
-urlFragment: flow-volume
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
----
-
-# Flow Volume
-
-In this sample, we will demonstrate how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
-
-Keep in mind that the GPIO APIs are only available on Windows 10 IoT Enterprise, so this sample cannot run on your desktop.
-
-## Step 1: Set up your hardware
-___
-The hardware setup for this sample is relatively simple.
-
-You’ll need a few components:
-
-* a Hall-effect flow sensor (we used a FL-S402B flow meter by DIGITEN)
-
-
-
-* a microcontroller board running Windows IoT Enterprise (we used an UP Board) with a free GPIO pin
-
-
-
-### For UP Board
-
-1. Connect the red wire to 3.3V (pin 1 on the expansion header) on the UP Board.
-2. Connect the black wire to ground (pin 9).
-3. Connect the yellow wire, the data pin, to the GPIO-2 pin that we will read from (we used pin 7 for convenience, since it is right there between pins 1 and 9).
-4. Connect the monitor to your device (we used an HDMI cable to connect our Upbaord to a standard monitor).
-
-For reference, here is the pinout of the UP Board:
-
-
-
-## Step 2: Deploy your app
-
-1. With the application open in Visual Studio, set the architecture in the toolbar dropdown. We use `x64` since we used the UP Board.
-1. When everything is set up, you should be able to press **F5** from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now.
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-1. If you are using UPBOARD, you have to setup the BIOS GPIO configuration.
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-1. Select **Pin 2** as **INPUT**.
-1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-1. Click the Start button to search for the app by name, and then launch it.
-1. The app will deploy and start on the Windows IoT device, and you should see a gauge control fill the screen.
-
-
-
-The easiest way to test is to gently blow in one end of the flow meter. The application listens for data coming from the device and the gauge should move up and back down as the flow rises and then stops.
-
-Congratulations! You just measured the flow going through the sensor from your Windows IoT device.
-
-## Let’s look at the code
-
-The code for this sample is made easier by using a class to interface with such devices, found in Flow.cs. This, in turn, is dependent upon a reusable class called Measurement, which is found in Models/Measurement.cs.
-
-In order to understand how the code works, an explanation of the sensor device will help. The device is based on the principle that a small wheel spins as there is flow through the sensor, which results in a certain number of pulses generated on the data pin.
-By counting the number of pulses and multiplying by a factor, the volume flowing through the sensor can be calculated. Because of variations in fluid density, and other subtle factors, it is important to calibrate the factor for your application.
-
-### Timer code
-
-Here is how you set up the application to use the Flow object in C#:
-
-```csharp
-public MainPage()
-{
- this.InitializeComponent();
-
- // to change the calibration numbers, do it here to override the defaults within the code
- var calibration = new Dictionary();
- calibration[Flow.FlowCalibrationFactorSetting] = "0.045";
- calibration[Flow.FlowCalibrationOffsetSetting] = "0";
-
- _flow = new Flow(calibration);
- _flow.FlowChanged += OnFlowChange;
- //_flow.Initialize(); // start without a timer, or ...
- _flow.Initialize(1000, 500); // start with a timer
-
- LastMeasurement = new Keg.DAL.Models.Measurement(0, Keg.DAL.Models.Measurement.UnitsOfMeasure.Ounces);
- LastMeasurement.PropertyChanged += OnAmountChange;
-}
-```
-As you can see, we use a Dictionary object and add to it the values we want to use to calibrate the sensor's reported values. Then we pass the Dictionary to the Flow object's constructor. Finally, we call Initialize to allow the object
-to setup internally. Then we simply attach method references to the OnFlowChange event so that we get notified when readings are taken from the sensor. The event provides to us a value that continues to increase that
-represents the cumulative volume measured by the sensor. Since our user interface was implemented to display sort of a rolling average of the value of the sensor, we calculate the amount added since the last event and pass
-that to the radial gauge control for display.
-
-## Note
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
-
-## Additional resources
-* [Documentation for all samples](https://developer.microsoft.com/en-us/windows/iot/samples)
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: flow-volume
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
+---
+
+# Flow Volume
+
+In this sample, we will demonstrate how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
+
+Keep in mind that the GPIO APIs are only available on Windows 10 IoT Enterprise, so this sample cannot run on your desktop.
+
+## Step 1: Set up your hardware
+___
+The hardware setup for this sample is relatively simple.
+
+You’ll need a few components:
+
+* a Hall-effect flow sensor (we used a FL-S402B flow meter by DIGITEN)
+
+
+
+* a microcontroller board running Windows IoT Enterprise (we used an UP Board) with a free GPIO pin
+
+
+
+### For UP Board
+
+1. Connect the red wire to 3.3V (pin 1 on the expansion header) on the UP Board.
+2. Connect the black wire to ground (pin 9).
+3. Connect the yellow wire, the data pin, to the GPIO-2 pin that we will read from (we used pin 7 for convenience, since it is right there between pins 1 and 9).
+4. Connect the monitor to your device (we used an HDMI cable to connect our Upbaord to a standard monitor).
+
+For reference, here is the pinout of the UP Board:
+
+
+
+## Step 2: Deploy your app
+
+1. With the application open in Visual Studio, set the architecture in the toolbar dropdown. We use `x64` since we used the UP Board.
+1. When everything is set up, you should be able to press **F5** from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now.
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+1. If you are using UPBOARD, you have to setup the BIOS GPIO configuration.
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+1. Select **Pin 2** as **INPUT**.
+1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+1. Click the Start button to search for the app by name, and then launch it.
+1. The app will deploy and start on the Windows IoT device, and you should see a gauge control fill the screen.
+
+
+
+The easiest way to test is to gently blow in one end of the flow meter. The application listens for data coming from the device and the gauge should move up and back down as the flow rises and then stops.
+
+Congratulations! You just measured the flow going through the sensor from your Windows IoT device.
+
+## Let’s look at the code
+
+The code for this sample is made easier by using a class to interface with such devices, found in Flow.cs. This, in turn, is dependent upon a reusable class called Measurement, which is found in Models/Measurement.cs.
+
+In order to understand how the code works, an explanation of the sensor device will help. The device is based on the principle that a small wheel spins as there is flow through the sensor, which results in a certain number of pulses generated on the data pin.
+By counting the number of pulses and multiplying by a factor, the volume flowing through the sensor can be calculated. Because of variations in fluid density, and other subtle factors, it is important to calibrate the factor for your application.
+
+### Timer code
+
+Here is how you set up the application to use the Flow object in C#:
+
+```csharp
+public MainPage()
+{
+ this.InitializeComponent();
+
+ // to change the calibration numbers, do it here to override the defaults within the code
+ var calibration = new Dictionary();
+ calibration[Flow.FlowCalibrationFactorSetting] = "0.045";
+ calibration[Flow.FlowCalibrationOffsetSetting] = "0";
+
+ _flow = new Flow(calibration);
+ _flow.FlowChanged += OnFlowChange;
+ //_flow.Initialize(); // start without a timer, or ...
+ _flow.Initialize(1000, 500); // start with a timer
+
+ LastMeasurement = new Keg.DAL.Models.Measurement(0, Keg.DAL.Models.Measurement.UnitsOfMeasure.Ounces);
+ LastMeasurement.PropertyChanged += OnAmountChange;
+}
+```
+As you can see, we use a Dictionary object and add to it the values we want to use to calibrate the sensor's reported values. Then we pass the Dictionary to the Flow object's constructor. Finally, we call Initialize to allow the object
+to setup internally. Then we simply attach method references to the OnFlowChange event so that we get notified when readings are taken from the sensor. The event provides to us a value that continues to increase that
+represents the cumulative volume measured by the sensor. Since our user interface was implemented to display sort of a rolling average of the value of the sensor, we calculate the amount added since the last event and pass
+that to the radial gauge control for display.
+
+## Note
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+
+## Additional resources
+* [Documentation for all samples](https://developer.microsoft.com/en-us/windows/iot/samples)
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/FlowVolume/README.md b/samples/FlowVolume/README.md
index 7f898f344..7bce8284c 100644
--- a/samples/FlowVolume/README.md
+++ b/samples/FlowVolume/README.md
@@ -1,111 +1,111 @@
----
-page_type: sample
-urlFragment: flow-volume
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
----
-
-# Flow Volume
-
-In this sample, we will demonstrate how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
-
-Keep in mind that the GPIO APIs are only available on Windows 10 IoT Enterprise, so this sample cannot run on your desktop.
-
-## Step 1: Set up your hardware
-___
-The hardware setup for this sample is relatively simple.
-
-You’ll need a few components:
-
-* a Hall-effect flow sensor (we used a FL-S402B flow meter by DIGITEN)
-
-
-
-* a microcontroller board running Windows IoT Enterprise (we used an UP Board) with a free GPIO pin
-
-
-
-### For UP Board
-
-1. Connect the red wire to 3.3V (pin 1 on the expansion header) on the UP Board.
-2. Connect the black wire to ground (pin 9).
-3. Connect the yellow wire, the data pin, to the GPIO-2 pin that we will read from (we used pin 7 for convenience, since it is right there between pins 1 and 9).
-4. Connect the monitor to your device (we used an HDMI cable to connect our Upbaord to a standard monitor).
-
-For reference, here is the pinout of the UP Board:
-
-
-
-## Step 2: Deploy your app
-
-1. With the application open in Visual Studio, set the architecture in the toolbar dropdown. We use `x64` since we used the UP Board.
-1. When everything is set up, you should be able to press **F5** from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now.
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-1. If you are using UPBOARD, you have to setup the BIOS GPIO configuration.
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-1. Select **Pin 2** as **INPUT**.
-1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-1. Click the Start button to search for the app by name, and then launch it.
-1. The app will deploy and start on the Windows IoT device, and you should see a gauge control fill the screen.
-
-
-
-The easiest way to test is to gently blow in one end of the flow meter. The application listens for data coming from the device and the gauge should move up and back down as the flow rises and then stops.
-
-Congratulations! You just measured the flow going through the sensor from your Windows IoT device.
-
-## Let’s look at the code
-
-The code for this sample is made easier by using a class to interface with such devices, found in Flow.cs. This, in turn, is dependent upon a reusable class called Measurement, which is found in Models/Measurement.cs.
-
-In order to understand how the code works, an explanation of the sensor device will help. The device is based on the principle that a small wheel spins as there is flow through the sensor, which results in a certain number of pulses generated on the data pin.
-By counting the number of pulses and multiplying by a factor, the volume flowing through the sensor can be calculated. Because of variations in fluid density, and other subtle factors, it is important to calibrate the factor for your application.
-
-### Timer code
-
-Here is how you set up the application to use the Flow object in C#:
-
-```csharp
-public MainPage()
-{
- this.InitializeComponent();
-
- // to change the calibration numbers, do it here to override the defaults within the code
- var calibration = new Dictionary();
- calibration[Flow.FlowCalibrationFactorSetting] = "0.045";
- calibration[Flow.FlowCalibrationOffsetSetting] = "0";
-
- _flow = new Flow(calibration);
- _flow.FlowChanged += OnFlowChange;
- //_flow.Initialize(); // start without a timer, or ...
- _flow.Initialize(1000, 500); // start with a timer
-
- LastMeasurement = new Keg.DAL.Models.Measurement(0, Keg.DAL.Models.Measurement.UnitsOfMeasure.Ounces);
- LastMeasurement.PropertyChanged += OnAmountChange;
-}
-```
-As you can see, we use a Dictionary object and add to it the values we want to use to calibrate the sensor's reported values. Then we pass the Dictionary to the Flow object's constructor. Finally, we call Initialize to allow the object
-to setup internally. Then we simply attach method references to the OnFlowChange event so that we get notified when readings are taken from the sensor. The event provides to us a value that continues to increase that
-represents the cumulative volume measured by the sensor. Since our user interface was implemented to display sort of a rolling average of the value of the sensor, we calculate the amount added since the last event and pass
-that to the radial gauge control for display.
-
-## Note
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
-
-## Additional resources
-* [Documentation for all samples](https://developer.microsoft.com/en-us/windows/iot/samples)
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: flow-volume
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
+---
+
+# Flow Volume
+
+In this sample, we will demonstrate how to use a relatively inexpensive device and an UP Board to measure the volume of liquid flowing through a hose.
+
+Keep in mind that the GPIO APIs are only available on Windows 10 IoT Enterprise, so this sample cannot run on your desktop.
+
+## Step 1: Set up your hardware
+___
+The hardware setup for this sample is relatively simple.
+
+You’ll need a few components:
+
+* a Hall-effect flow sensor (we used a FL-S402B flow meter by DIGITEN)
+
+
+
+* a microcontroller board running Windows IoT Enterprise (we used an UP Board) with a free GPIO pin
+
+
+
+### For UP Board
+
+1. Connect the red wire to 3.3V (pin 1 on the expansion header) on the UP Board.
+2. Connect the black wire to ground (pin 9).
+3. Connect the yellow wire, the data pin, to the GPIO-2 pin that we will read from (we used pin 7 for convenience, since it is right there between pins 1 and 9).
+4. Connect the monitor to your device (we used an HDMI cable to connect our Upbaord to a standard monitor).
+
+For reference, here is the pinout of the UP Board:
+
+
+
+## Step 2: Deploy your app
+
+1. With the application open in Visual Studio, set the architecture in the toolbar dropdown. We use `x64` since we used the UP Board.
+1. When everything is set up, you should be able to press **F5** from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now.
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+1. If you are using UPBOARD, you have to setup the BIOS GPIO configuration.
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+1. Select **Pin 2** as **INPUT**.
+1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+1. Click the Start button to search for the app by name, and then launch it.
+1. The app will deploy and start on the Windows IoT device, and you should see a gauge control fill the screen.
+
+
+
+The easiest way to test is to gently blow in one end of the flow meter. The application listens for data coming from the device and the gauge should move up and back down as the flow rises and then stops.
+
+Congratulations! You just measured the flow going through the sensor from your Windows IoT device.
+
+## Let’s look at the code
+
+The code for this sample is made easier by using a class to interface with such devices, found in Flow.cs. This, in turn, is dependent upon a reusable class called Measurement, which is found in Models/Measurement.cs.
+
+In order to understand how the code works, an explanation of the sensor device will help. The device is based on the principle that a small wheel spins as there is flow through the sensor, which results in a certain number of pulses generated on the data pin.
+By counting the number of pulses and multiplying by a factor, the volume flowing through the sensor can be calculated. Because of variations in fluid density, and other subtle factors, it is important to calibrate the factor for your application.
+
+### Timer code
+
+Here is how you set up the application to use the Flow object in C#:
+
+```csharp
+public MainPage()
+{
+ this.InitializeComponent();
+
+ // to change the calibration numbers, do it here to override the defaults within the code
+ var calibration = new Dictionary();
+ calibration[Flow.FlowCalibrationFactorSetting] = "0.045";
+ calibration[Flow.FlowCalibrationOffsetSetting] = "0";
+
+ _flow = new Flow(calibration);
+ _flow.FlowChanged += OnFlowChange;
+ //_flow.Initialize(); // start without a timer, or ...
+ _flow.Initialize(1000, 500); // start with a timer
+
+ LastMeasurement = new Keg.DAL.Models.Measurement(0, Keg.DAL.Models.Measurement.UnitsOfMeasure.Ounces);
+ LastMeasurement.PropertyChanged += OnAmountChange;
+}
+```
+As you can see, we use a Dictionary object and add to it the values we want to use to calibrate the sensor's reported values. Then we pass the Dictionary to the Flow object's constructor. Finally, we call Initialize to allow the object
+to setup internally. Then we simply attach method references to the OnFlowChange event so that we get notified when readings are taken from the sensor. The event provides to us a value that continues to increase that
+represents the cumulative volume measured by the sensor. Since our user interface was implemented to display sort of a rolling average of the value of the sensor, we calculate the amount added since the last event and pass
+that to the radial gauge control for display.
+
+## Note
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+
+## Additional resources
+* [Documentation for all samples](https://developer.microsoft.com/en-us/windows/iot/samples)
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/ForegroundAppWithBackgroundApp/CPP/README.md b/samples/ForegroundAppWithBackgroundApp/CPP/README.md
index 641241339..3d45b66b5 100644
--- a/samples/ForegroundAppWithBackgroundApp/CPP/README.md
+++ b/samples/ForegroundAppWithBackgroundApp/CPP/README.md
@@ -1,169 +1,169 @@
----
-page_type: sample
-urlFragment: foregroundapp-backgroundapp
-languages:
- - csharp
- - cpp
-products:
- - Windows
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
----
-
-# Foreground App with Background App
-
-In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
-
-## About this sample
-If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
-
-## Step 1: Create a New project
-1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
-1. Navigate to **File** > **New** > Projec
-
-## Step 2: Create a new Blank App
-
-
-
-## Step 3: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
-
-
-
-## Step 5: Create a new Background Application
-
-
-
-## Step 6: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
-
-
-
-## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
-
-
-
-## Step 9: Update App Manifest
-
-At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
-
-
-
-## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
-
-It should look like this:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Step 11: Add References to Foreground Application
-
-In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
-
-
-
-## Step 12: Add References to Background Application
-
-Add a project reference to the Background Application
-
-
-
-## Step 13: Unload Project
-
-In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
-
-
-
-## Step 14: Edit Foreground and Background App
-
-1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
-
-
-
-1. In the background project file comment the following lines:
-
-
-
-
-
-1. In the foreground project file add true to the first PropertyGroup
-
-
-
- MyForegroundApp_TemporaryKey.pfx
- true
-
-
-## Step 15: Reload Project
-
-1. In Solution Explorer right-click on each project and choose Reload Project
-
-
-
-1. In Solution Explorer delete Package.appxmanifest from the background application
-
-
-
-1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
-
-## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 18: BIOS GPIO Configuration
-
->[!NOTE]
->
-> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
-
-1. Configure the BIOS GPIO on the UP Board:
-
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
-For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
-
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: foregroundapp-backgroundapp
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
+---
+
+# Foreground App with Background App
+
+In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
+
+## About this sample
+If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
+
+## Step 1: Create a New project
+1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
+1. Navigate to **File** > **New** > Projec
+
+## Step 2: Create a new Blank App
+
+
+
+## Step 3: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
+
+
+
+## Step 5: Create a new Background Application
+
+
+
+## Step 6: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
+
+
+
+## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
+
+
+
+## Step 9: Update App Manifest
+
+At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
+
+
+
+## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
+
+It should look like this:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Step 11: Add References to Foreground Application
+
+In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
+
+
+
+## Step 12: Add References to Background Application
+
+Add a project reference to the Background Application
+
+
+
+## Step 13: Unload Project
+
+In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
+
+
+
+## Step 14: Edit Foreground and Background App
+
+1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
+
+
+
+1. In the background project file comment the following lines:
+
+
+
+
+
+1. In the foreground project file add true to the first PropertyGroup
+
+
+
+ MyForegroundApp_TemporaryKey.pfx
+ true
+
+
+## Step 15: Reload Project
+
+1. In Solution Explorer right-click on each project and choose Reload Project
+
+
+
+1. In Solution Explorer delete Package.appxmanifest from the background application
+
+
+
+1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
+
+## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 18: BIOS GPIO Configuration
+
+>[!NOTE]
+>
+> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
+
+1. Configure the BIOS GPIO on the UP Board:
+
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
+
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/ForegroundAppWithBackgroundApp/CS/MyBackgroundApplication/Properties/Default.rd.xml b/samples/ForegroundAppWithBackgroundApp/CS/MyBackgroundApplication/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/ForegroundAppWithBackgroundApp/CS/MyBackgroundApplication/Properties/Default.rd.xml
+++ b/samples/ForegroundAppWithBackgroundApp/CS/MyBackgroundApplication/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/ForegroundAppWithBackgroundApp/CS/MyForegroundApp/Properties/Default.rd.xml b/samples/ForegroundAppWithBackgroundApp/CS/MyForegroundApp/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/ForegroundAppWithBackgroundApp/CS/MyForegroundApp/Properties/Default.rd.xml
+++ b/samples/ForegroundAppWithBackgroundApp/CS/MyForegroundApp/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/ForegroundAppWithBackgroundApp/CS/README.md b/samples/ForegroundAppWithBackgroundApp/CS/README.md
index 641241339..3d45b66b5 100644
--- a/samples/ForegroundAppWithBackgroundApp/CS/README.md
+++ b/samples/ForegroundAppWithBackgroundApp/CS/README.md
@@ -1,169 +1,169 @@
----
-page_type: sample
-urlFragment: foregroundapp-backgroundapp
-languages:
- - csharp
- - cpp
-products:
- - Windows
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
----
-
-# Foreground App with Background App
-
-In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
-
-## About this sample
-If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
-
-## Step 1: Create a New project
-1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
-1. Navigate to **File** > **New** > Projec
-
-## Step 2: Create a new Blank App
-
-
-
-## Step 3: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
-
-
-
-## Step 5: Create a new Background Application
-
-
-
-## Step 6: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
-
-
-
-## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
-
-
-
-## Step 9: Update App Manifest
-
-At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
-
-
-
-## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
-
-It should look like this:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Step 11: Add References to Foreground Application
-
-In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
-
-
-
-## Step 12: Add References to Background Application
-
-Add a project reference to the Background Application
-
-
-
-## Step 13: Unload Project
-
-In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
-
-
-
-## Step 14: Edit Foreground and Background App
-
-1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
-
-
-
-1. In the background project file comment the following lines:
-
-
-
-
-
-1. In the foreground project file add true to the first PropertyGroup
-
-
-
- MyForegroundApp_TemporaryKey.pfx
- true
-
-
-## Step 15: Reload Project
-
-1. In Solution Explorer right-click on each project and choose Reload Project
-
-
-
-1. In Solution Explorer delete Package.appxmanifest from the background application
-
-
-
-1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
-
-## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 18: BIOS GPIO Configuration
-
->[!NOTE]
->
-> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
-
-1. Configure the BIOS GPIO on the UP Board:
-
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
-For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
-
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: foregroundapp-backgroundapp
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
+---
+
+# Foreground App with Background App
+
+In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
+
+## About this sample
+If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
+
+## Step 1: Create a New project
+1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
+1. Navigate to **File** > **New** > Projec
+
+## Step 2: Create a new Blank App
+
+
+
+## Step 3: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
+
+
+
+## Step 5: Create a new Background Application
+
+
+
+## Step 6: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
+
+
+
+## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
+
+
+
+## Step 9: Update App Manifest
+
+At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
+
+
+
+## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
+
+It should look like this:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Step 11: Add References to Foreground Application
+
+In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
+
+
+
+## Step 12: Add References to Background Application
+
+Add a project reference to the Background Application
+
+
+
+## Step 13: Unload Project
+
+In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
+
+
+
+## Step 14: Edit Foreground and Background App
+
+1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
+
+
+
+1. In the background project file comment the following lines:
+
+
+
+
+
+1. In the foreground project file add true to the first PropertyGroup
+
+
+
+ MyForegroundApp_TemporaryKey.pfx
+ true
+
+
+## Step 15: Reload Project
+
+1. In Solution Explorer right-click on each project and choose Reload Project
+
+
+
+1. In Solution Explorer delete Package.appxmanifest from the background application
+
+
+
+1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
+
+## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 18: BIOS GPIO Configuration
+
+>[!NOTE]
+>
+> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
+
+1. Configure the BIOS GPIO on the UP Board:
+
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
+
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/ForegroundAppWithBackgroundApp/README.md b/samples/ForegroundAppWithBackgroundApp/README.md
index 205478da6..0e0e9d388 100644
--- a/samples/ForegroundAppWithBackgroundApp/README.md
+++ b/samples/ForegroundAppWithBackgroundApp/README.md
@@ -1,169 +1,169 @@
----
-page_type: sample
-urlFragment: foregroundapp-backgroundapp
-languages:
- - csharp
- - cpp
-products:
- - Windows
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
----
-
-# Foreground App with Background App
-
-In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
-
-## About this sample
-If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
-
-## Step 1: Create a New project
-1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
-1. Navigate to **File** > **New** > Projec
-
-## Step 2: Create a new Blank App
-
-
-
-## Step 3: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
-
-
-
-## Step 5: Create a new Background Application
-
-
-
-## Step 6: Select desired target version and click OK when prompted for target version
-
-
-
-## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
-
-
-
-## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
-
-
-
-## Step 9: Update App Manifest
-
-At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
-
-
-
-## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
-
-It should look like this:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Step 11: Add References to Foreground Application
-
-In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
-
-
-
-## Step 12: Add References to Background Application
-
-Add a project reference to the Background Application
-
-
-
-## Step 13: Unload Project
-
-In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
-
-
-
-## Step 14: Edit Foreground and Background App
-
-1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
-
-
-
-1. In the background project file comment the following lines:
-
-
-
-
-
-1. In the foreground project file add true to the first PropertyGroup
-
-
-
- MyForegroundApp_TemporaryKey.pfx
- true
-
-
-## Step 15: Reload Project
-
-1. In Solution Explorer right-click on each project and choose Reload Project
-
-
-
-1. In Solution Explorer delete Package.appxmanifest from the background application
-
-
-
-1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
-
-## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-## Step 18: BIOS GPIO Configuration
-
->[!NOTE]
->
-> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
-
-1. Configure the BIOS GPIO on the UP Board:
-
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
-For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
-
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+---
+page_type: sample
+urlFragment: foregroundapp-backgroundapp
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: An example of building a foreground app and background app within the same APPX file for Windows 10 IoT Enterprise.
+---
+
+# Foreground App with Background App
+
+In both versions of this sample (C++ or C#), the Background App can toggle a GPIO pin.
+
+## About this sample
+If you want to create a solution that builds the foreground application and the background application into the same .APPX file it will require manual steps to combine the two projects.
+
+## Step 1: Create a New project
+1. Download [Visual Studio 2019](https://www.visualstudio.com/downloads/)
+1. Navigate to **File** > **New** > Projec
+
+## Step 2: Create a new Blank App
+
+
+
+## Step 3: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 4: In Solution Explorer right-click on the solution and choose Add>New Project …
+
+
+
+## Step 5: Create a new Background Application
+
+
+
+## Step 6: Select desired target version and click OK when prompted for target version
+
+
+
+## Step 7: In Solution Explorer right-click on the background application Package.appxmanifest and choose View Code
+
+
+
+## Step 8: In Solution Explorer right-click on the foreground application Package.appxmanifest and choose View Code
+
+
+
+## Step 9: Update App Manifest
+
+At the top of the foreground Package.appxmanifest add xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" and modify IgnorableNamespaces to include IoT.
+
+
+
+## Step 10: Copy the Extensions from Background to Foreground Application Package.appxmanifest
+
+It should look like this:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Step 11: Add References to Foreground Application
+
+In Solution Explorer right-click on the Foreground Application References node and choose Add Reference
+
+
+
+## Step 12: Add References to Background Application
+
+Add a project reference to the Background Application
+
+
+
+## Step 13: Unload Project
+
+In Solution Explorer right-click the foreground application project and choose Unload Project, then right-click the background application project and choose Unload Project.
+
+
+
+## Step 14: Edit Foreground and Background App
+
+1. In Solution Explorer right-click on the foreground application project and choose Edit MyForegroundApp.csproj and then right-click on the background application project and choose Edit MyBackgroundApp.csproj.
+
+
+
+1. In the background project file comment the following lines:
+
+
+
+
+
+1. In the foreground project file add true to the first PropertyGroup
+
+
+
+ MyForegroundApp_TemporaryKey.pfx
+ true
+
+
+## Step 15: Reload Project
+
+1. In Solution Explorer right-click on each project and choose Reload Project
+
+
+
+1. In Solution Explorer delete Package.appxmanifest from the background application
+
+
+
+1. At this point the project should build (and run the implementation you have added to the foreground and background applications).
+
+## Step 16: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 17: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+## Step 18: BIOS GPIO Configuration
+
+>[!NOTE]
+>
+> If you are using the [UP Board](https://up-board.org/up/specifications/), you will have to set up the BIOS GPIO configuration.
+
+1. Configure the BIOS GPIO on the UP Board:
+
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+For more information, please review the [UP Board Firmware Settings.](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf)
+
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
\ No newline at end of file
diff --git a/samples/GPIOKmdfDemo/LICENSE.txt b/samples/GPIOKmdfDemo/LICENSE.txt
index 1b6cef88f..898982967 100644
--- a/samples/GPIOKmdfDemo/LICENSE.txt
+++ b/samples/GPIOKmdfDemo/LICENSE.txt
@@ -1,21 +1,21 @@
-Copyright (c) Microsoft Open Technologies, Inc. All rights reserved.
-
-The MIT License (MIT)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+Copyright (c) Microsoft Open Technologies, Inc. All rights reserved.
+
+The MIT License (MIT)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
diff --git a/samples/GPIOKmdfDemo/asl/dragon.asl b/samples/GPIOKmdfDemo/asl/dragon.asl
index e23759ecb..ce126705d 100644
--- a/samples/GPIOKmdfDemo/asl/dragon.asl
+++ b/samples/GPIOKmdfDemo/asl/dragon.asl
@@ -1,58 +1,58 @@
-//
-// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
-//
-// The MIT License(MIT)
-//
-// Permission is hereby granted, free of charge, to any person obtaining a copy
-// of this software and associated documentation files(the "Software"), to deal
-// in the Software without restriction, including without limitation the rights
-// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
-// copies of the Software, and to permit persons to whom the Software is
-// furnished to do so, subject to the following conditions :
-//
-// The above copyright notice and this permission notice shall be included in
-// all copies or substantial portions of the Software.
-//
-// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
-// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-// THE SOFTWARE.
-//
-
-DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "GPOT", 1)
-{
- Scope (\_SB)
- {
- //
- // Test peripheral device node for the Dragon board
- //
- Device(GPOT)
- {
- Name(_HID, "GPOT0001")
- Name(_CID, "GPOT0001")
- Name(_UID, 1)
- Name(_CRS, ResourceTemplate()
- {
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0024 } // Index: 0 - Pin #23 - GPIO-A - GPIO_36
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x000C } // Index: 1 - Pin #24 - GPIO-B - GPIO_12
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x000D } // Index: 2 - Pin #25 - GPIO-C - GPIO_13
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0045 } // Index: 3 - Pin #26 - GPIO-D - GPIO_69
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0073 } // Index: 4 - Pin #27 - GPIO-E - GPIO_115
- //GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0518 } // Index: X - Pin # - GPIO-F - MPP_4
- //GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0018 } // Index: X - Pin # - GPIO-G - GPIO_24
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0019 } // Index: 5 - Pin #30 - GPIO-H - GPIO_25
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0023 } // Index: 6 - Pin #31 - GPIO-I - GPIO_35
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0022 } // Index: 7 - Pin #32 - GPIO-J - GPIO_34
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x001C } // Index: 8 - Pin #33 - GPIO-K - GPIO_28
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0021 } // Index: 9 - Pin #34 - GPIO-L - GPIO_33
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0015 } // Index: 10 - LED #1 GPIO_21
- GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0078 } // Index: 11 - LED #2 GPIO_120
- GpioIO (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0600 } // Index: 12 - LED #3 GPIO_1
- GpioIO (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0608 } // Index: 13 - LED #4 GPIO_2
- })
- }
- }
+//
+// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
+//
+// The MIT License(MIT)
+//
+// Permission is hereby granted, free of charge, to any person obtaining a copy
+// of this software and associated documentation files(the "Software"), to deal
+// in the Software without restriction, including without limitation the rights
+// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
+// copies of the Software, and to permit persons to whom the Software is
+// furnished to do so, subject to the following conditions :
+//
+// The above copyright notice and this permission notice shall be included in
+// all copies or substantial portions of the Software.
+//
+// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
+// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+// THE SOFTWARE.
+//
+
+DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "GPOT", 1)
+{
+ Scope (\_SB)
+ {
+ //
+ // Test peripheral device node for the Dragon board
+ //
+ Device(GPOT)
+ {
+ Name(_HID, "GPOT0001")
+ Name(_CID, "GPOT0001")
+ Name(_UID, 1)
+ Name(_CRS, ResourceTemplate()
+ {
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0024 } // Index: 0 - Pin #23 - GPIO-A - GPIO_36
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x000C } // Index: 1 - Pin #24 - GPIO-B - GPIO_12
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x000D } // Index: 2 - Pin #25 - GPIO-C - GPIO_13
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0045 } // Index: 3 - Pin #26 - GPIO-D - GPIO_69
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0073 } // Index: 4 - Pin #27 - GPIO-E - GPIO_115
+ //GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0518 } // Index: X - Pin # - GPIO-F - MPP_4
+ //GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0018 } // Index: X - Pin # - GPIO-G - GPIO_24
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0019 } // Index: 5 - Pin #30 - GPIO-H - GPIO_25
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0023 } // Index: 6 - Pin #31 - GPIO-I - GPIO_35
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0022 } // Index: 7 - Pin #32 - GPIO-J - GPIO_34
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x001C } // Index: 8 - Pin #33 - GPIO-K - GPIO_28
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0021 } // Index: 9 - Pin #34 - GPIO-L - GPIO_33
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0015 } // Index: 10 - LED #1 GPIO_21
+ GpioIo (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.GIO0", 0x00, ResourceConsumer, ,){ 0x0078 } // Index: 11 - LED #2 GPIO_120
+ GpioIO (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0600 } // Index: 12 - LED #3 GPIO_1
+ GpioIO (Shared, PullNone, 0x0000, 0x0000, IoRestrictionNoneAndPreserve, "\\_SB.PM01", 0x00, ResourceConsumer, ,){ 0x0608 } // Index: 13 - LED #4 GPIO_2
+ })
+ }
+ }
}
\ No newline at end of file
diff --git a/samples/GPIOKmdfDemo/asl/gpiokmdfdemo.asl b/samples/GPIOKmdfDemo/asl/gpiokmdfdemo.asl
index 5dc4725fe..86db689bc 100644
--- a/samples/GPIOKmdfDemo/asl/gpiokmdfdemo.asl
+++ b/samples/GPIOKmdfDemo/asl/gpiokmdfdemo.asl
@@ -1,56 +1,56 @@
-//
-// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
-//
-// The MIT License(MIT)
-//
-// Permission is hereby granted, free of charge, to any person obtaining a copy
-// of this software and associated documentation files(the "Software"), to deal
-// in the Software without restriction, including without limitation the rights
-// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
-// copies of the Software, and to permit persons to whom the Software is
-// furnished to do so, subject to the following conditions :
-//
-// The above copyright notice and this permission notice shall be included in
-// all copies or substantial portions of the Software.
-//
-// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
-// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-// THE SOFTWARE.
-//
-
-DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "gpiodemo", 1)
-{
- Scope (\_SB)
- {
- //
- // Test peripheral device node for MinnowBoardMax
- //
- Device(GPOT)
- {
- Name(_HID, "GPOT0001")
- Name(_CID, "GPOT0001")
- Name(_UID, 1)
- Name (RBUF, ResourceTemplate ()
- {
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 0 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 1 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 2 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 62 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 63 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 65 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 64 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 94 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 95 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 54 }
- })
- Method(_CRS, 0x0, NotSerialized)
- {
- Return(RBUF)
- }
- }
- }
+//
+// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
+//
+// The MIT License(MIT)
+//
+// Permission is hereby granted, free of charge, to any person obtaining a copy
+// of this software and associated documentation files(the "Software"), to deal
+// in the Software without restriction, including without limitation the rights
+// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
+// copies of the Software, and to permit persons to whom the Software is
+// furnished to do so, subject to the following conditions :
+//
+// The above copyright notice and this permission notice shall be included in
+// all copies or substantial portions of the Software.
+//
+// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
+// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+// THE SOFTWARE.
+//
+
+DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "gpiodemo", 1)
+{
+ Scope (\_SB)
+ {
+ //
+ // Test peripheral device node for MinnowBoardMax
+ //
+ Device(GPOT)
+ {
+ Name(_HID, "GPOT0001")
+ Name(_CID, "GPOT0001")
+ Name(_UID, 1)
+ Name (RBUF, ResourceTemplate ()
+ {
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 0 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 1 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO2", 0, ResourceConsumer, , ) { 2 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 62 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 63 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 65 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 64 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 94 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 95 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNone, "\\_SB.GPO0", 0, ResourceConsumer, , ) { 54 }
+ })
+ Method(_CRS, 0x0, NotSerialized)
+ {
+ Return(RBUF)
+ }
+ }
+ }
}
\ No newline at end of file
diff --git a/samples/GPIOKmdfDemo/asl/rpi2.asl b/samples/GPIOKmdfDemo/asl/rpi2.asl
index 76562cd5f..711ec8c32 100644
--- a/samples/GPIOKmdfDemo/asl/rpi2.asl
+++ b/samples/GPIOKmdfDemo/asl/rpi2.asl
@@ -1,56 +1,56 @@
-//
-// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
-//
-// The MIT License(MIT)
-//
-// Permission is hereby granted, free of charge, to any person obtaining a copy
-// of this software and associated documentation files(the "Software"), to deal
-// in the Software without restriction, including without limitation the rights
-// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
-// copies of the Software, and to permit persons to whom the Software is
-// furnished to do so, subject to the following conditions :
-//
-// The above copyright notice and this permission notice shall be included in
-// all copies or substantial portions of the Software.
-//
-// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
-// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-// THE SOFTWARE.
-//
-DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "GPOT", 1)
-{
- Scope (\_SB)
- {
- //
- // Test peripheral device node for RPi2
- //
- Device(GPOT)
- {
- Name(_HID, "GPOT0001")
- Name(_CID, "GPOT0001")
- Name(_UID, 1)
- Name(_CRS, ResourceTemplate()
- {
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 4 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 5 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 6 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 12 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 13 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 16 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 18 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 22 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 23 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 24 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 25 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 26 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 27 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 35 }
- GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 47 }
- })
- }
- }
-}
+//
+// Copyright(c) Microsoft Open Technologies, Inc. All rights reserved.
+//
+// The MIT License(MIT)
+//
+// Permission is hereby granted, free of charge, to any person obtaining a copy
+// of this software and associated documentation files(the "Software"), to deal
+// in the Software without restriction, including without limitation the rights
+// to use, copy, modify, merge, publish, distribute, sublicense, and / or sell
+// copies of the Software, and to permit persons to whom the Software is
+// furnished to do so, subject to the following conditions :
+//
+// The above copyright notice and this permission notice shall be included in
+// all copies or substantial portions of the Software.
+//
+// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
+// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+// THE SOFTWARE.
+//
+DefinitionBlock ("ACPITABL.dat", "SSDT", 1, "MSFT", "GPOT", 1)
+{
+ Scope (\_SB)
+ {
+ //
+ // Test peripheral device node for RPi2
+ //
+ Device(GPOT)
+ {
+ Name(_HID, "GPOT0001")
+ Name(_CID, "GPOT0001")
+ Name(_UID, 1)
+ Name(_CRS, ResourceTemplate()
+ {
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 4 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 5 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 6 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 12 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 13 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 16 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 18 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 22 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 23 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 24 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 25 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 26 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 27 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 35 }
+ GpioIO(Shared, PullDefault, 0, 0, IoRestrictionNoneAndPreserve, "\\_SB.GPI0", 0, ResourceConsumer, , ) { 47 }
+ })
+ }
+ }
+}
diff --git a/samples/GPIOKmdfDemo/readme.md b/samples/GPIOKmdfDemo/readme.md
index 8adfda538..5137a59e7 100644
--- a/samples/GPIOKmdfDemo/readme.md
+++ b/samples/GPIOKmdfDemo/readme.md
@@ -1,45 +1,45 @@
----
-page_type: sample
-urlFragment: gpio-kmdf-demo
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: Create a simple GPIO demo.
----
-
-# GPIO KMDF Demo
-
-Windows 10 IoT Enterprise GPIO KMDF Demo sample will allow you to deploy a GPIO Kernel driver to IoT Device.
-
-# Prerequisites
-In order to build this driver you will need the following:
-
- * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/).
- * [Windows 10 Driver Development Kit](https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk).
- * [Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk/).
-
-## Building and Deploying the GPIO KMDF
- 1. Be sure you've installed the Visual Studio update and the Windows 10 Driver Development kit before continuing.
- 2. On your development machine, use Windows Explorer to navigate to the folder where you downloaded or cloned samples.
- 3. Open the project located ```Samples\GPIOKMDFDemo\GPIOkmdfdemo.sln```.
- 4. Select the architecture you intend to deploy to: x64 for UP-BOARD.
- 5. You can now build the solution.
-
-### Copying the GPIOKMDF folder to your device
- 1. Under the release folder you will find the .inf and .sys files.
- 2. Copy that folder and send it to IoT Enterprise device
-
-### Installing the GPIO KMDF Drivers
- 1. Install the .inf file in the Windows IoT Enterprise device.
- 2. You will see the dialogue box of "The operation completed successful".
- 3. The GPIO KMDF device drivers installed in IoT device
-
-### Verify installation
-If you've installed the driver, verify the install by navigating to the system32 folder under Windows and looking for the GPIO KMDF Demo file.
-
-
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: gpio-kmdf-demo
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: Create a simple GPIO demo.
+---
+
+# GPIO KMDF Demo
+
+Windows 10 IoT Enterprise GPIO KMDF Demo sample will allow you to deploy a GPIO Kernel driver to IoT Device.
+
+# Prerequisites
+In order to build this driver you will need the following:
+
+ * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/).
+ * [Windows 10 Driver Development Kit](https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk).
+ * [Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk/).
+
+## Building and Deploying the GPIO KMDF
+ 1. Be sure you've installed the Visual Studio update and the Windows 10 Driver Development kit before continuing.
+ 2. On your development machine, use Windows Explorer to navigate to the folder where you downloaded or cloned samples.
+ 3. Open the project located ```Samples\GPIOKMDFDemo\GPIOkmdfdemo.sln```.
+ 4. Select the architecture you intend to deploy to: x64 for UP-BOARD.
+ 5. You can now build the solution.
+
+### Copying the GPIOKMDF folder to your device
+ 1. Under the release folder you will find the .inf and .sys files.
+ 2. Copy that folder and send it to IoT Enterprise device
+
+### Installing the GPIO KMDF Drivers
+ 1. Install the .inf file in the Windows IoT Enterprise device.
+ 2. You will see the dialogue box of "The operation completed successful".
+ 3. The GPIO KMDF device drivers installed in IoT device
+
+### Verify installation
+If you've installed the driver, verify the install by navigating to the system32 folder under Windows and looking for the GPIO KMDF Demo file.
+
+
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/GPIOOneWire/CPP/ReadMe.md b/samples/GPIOOneWire/CPP/ReadMe.md
index 7c31896e1..9f44e90f7 100644
--- a/samples/GPIOOneWire/CPP/ReadMe.md
+++ b/samples/GPIOOneWire/CPP/ReadMe.md
@@ -1,207 +1,207 @@
----
-page_type: sample
-urlFragment: gpio-onewire
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: "This sample shows how to read from the DHT11 from a Universal Windows Application for Windows 10 IoT Enterprise."
----
-
-# GPIO OneWire DHT11/22 reader
-
-| Minimum SDK Version | 19041 |
-|---------------------|-------|
-| Minimum OS Version | 15063 |
-
-This sample has been updated to use the `GpioChangeReader` API which is new as of build 19041. You must install SDK version 19041 or later to build this sample.
-
-The sample has been temporarily modified to use two pins instead of one to drive the DHT22. `GpioChangeReader` requires interrupts to be enabled.
-`GpioPin.SetDriveMode()` currently takes much longer when interrupts are enabled than when they are disabled.
-If you try to change a pin from output to input when interrupts are enabled, you will miss the response from the DHT22.
-As a workaround, two pins are used to interface with the DHT22.
-One pin is configured as an output and is used to assert the data line LOW to request a sample.
-The other pin is configured as input and is used to capture changes on the data line.
-
-Your breadboard should be wired as follows. You can use either a MOSFET(2N700) or BJT transistor(2N3904).
-If you use a BJT(2N3904), be sure to put a resistor in series with the base of the transistor.
-
-
-
-## GPIO OneWire DHT11 reader
-
-Note what follows below is a bit out of date- the latest version on GitHub is a 2 wire operation requiring pin 4 as input and pin 5 as output.
-
-This sample shows how to read from the [DHT11](https://www.adafruit.com/product/386) from a Universal Windows Application.
-The DHT11 is a low cost temperature and humidity sensor that uses a single wire to interface to the host controller.
-This wire is used by the host to request a sample from the DHT11 and by the DHT11 to transmit data back to the host.
-
-The DHT11 is right on the edge performance-wise of what the GPIO APIs can handle.
-If there is background activity such as network, USB, filesystem, or graphics activity, it can prevent the sample from successfully sampling from the DHT11.
-
-For a description of the protocol used by the DHT11, see [this article](http://embedded-lab.com/blog/?p=4333).
-
-The datasheet is [here](http://akizukidenshi.com/download/ds/aosong/DHT11.pdf).
-
-
-
-### Requirements
-
-{:.table.table-bordered}
-| Minimum supported build | 10.0.10556 |
-|-------------------------|---------------------------------|
-| Supported Hardware | UP Board |
-
-### Hardware Setup
-
-You will need the following hardware to run this demo:
-
- * A [DHT11](https://www.adafruit.com/product/386) or [DHT22](http://www.adafruit.com/products/385) sensor
- * A couple of female-to-female connector wires
-
-Connect the components as shown in the following diagram:
-
-
-
-
-### Running the Solution
-
- 1. Clone the Microsoft IoT Enterprise Repository and open GpioOneWire/GpioOneWire.vcxproj in Visual Studio 2019.
- 2. Build the solution in Release x64 mode.
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-### BIOS Settings for UP Board
-If you are using UP Board, you have to setup the BIOS GPIO configuration.
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-1. Select **Pin 4** as **INPUT** and **Pin 5** as **OUTPUT**
-1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-1. Click the Start button to search for the app by name, and then launch it.
-
-### How it works
-
-The logic that interacts with the DHT11 is contained in the Dht11::Sample() method.
-Since the 1s and 0s that the DHT11 sends back are encoded as pulse widths, we need a way to precisely measure the time difference between falling edges.
-We use [QueryPerformanceCounter()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644904(v=vs.85).aspx) for this purpose.
-The units of QueryPerformanceCounter are platform-dependent, so we must call [QueryPerformanceFrequency()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644905(v=vs.85).aspx) to determine the resolution of the counter.
-
-A difference of 76 microseconds between falling edges denotes a '0', while a difference of 120 microseconds between falling edges denotes a '1'.
-We choose 110 microseconds as a reasonable threshold above which we will consider bits to be 1s, while we will consider pulses shorter than this threshold to be 0s. We convert 110 microseconds to QueryPerformanceCounter (QPC) units to be used later.
-
-```cpp
- HRESULT GpioOneWire::Dht11::Sample (GpioOneWire::Dht11Reading& Reading)
- {
- Reading = Dht11Reading();
-
- LARGE_INTEGER qpf;
- QueryPerformanceFrequency(&qpf);
-
- // This is the threshold used to determine whether a bit is a '0' or a '1'.
- // A '0' has a pulse time of 76 microseconds, while a '1' has a
- // pulse time of 120 microseconds. 110 is chosen as a reasonable threshold.
- // We convert the value to QPF units for later use.
- const unsigned int oneThreshold = static_cast(
- 110LL * qpf.QuadPart / 1000000LL);
-```
-
-Next, we send the sequence required to activate the sensor.
-The GPIO signal is normally pulled high while the device is idle, and we must pull it low for 18 milliseconds to request a sample. We latch a low value to the pin and set it as an output, driving the GPIO pin low.
-
-```cpp
- // Latch low value onto pin
- this->pin->Write(GpioPinValue::Low);
-
- // Set pin as output
- this->pin->SetDriveMode(GpioPinDriveMode::Output);
-
- // Wait for at least 18 ms
- Sleep(SAMPLE_HOLD_LOW_MILLIS);
-```
-
-We then revert the pin to an input which causes it to go high, and wait for the DHT11 to pull the pin low, then high again.
-
-```cpp
- // Set pin back to input
- this->pin->SetDriveMode(this->inputDriveMode);
-
- GpioPinValue previousValue = this->pin->Read();
-
- // catch the first rising edge
- const ULONG initialRisingEdgeTimeoutMillis = 1;
- ULONGLONG endTickCount = GetTickCount64() + initialRisingEdgeTimeoutMillis;
- for (;;) {
- if (GetTickCount64() > endTickCount) {
- return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
- }
-
- GpioPinValue value = this->pin->Read();
- if (value != previousValue) {
- // rising edgue?
- if (value == GpioPinValue::High) {
- break;
- }
- previousValue = value;
- }
- }
-```
-
-After receiving the first rising edge, we catch all of the falling edges and measure the time difference between them to determine whether the bit is a 0 or 1.
-
-```cpp
- LARGE_INTEGER prevTime = { 0 };
-
- const ULONG sampleTimeoutMillis = 10;
- endTickCount = GetTickCount64() + sampleTimeoutMillis;
-
- // capture every falling edge until all bits are received or
- // timeout occurs
- for (unsigned int i = 0; i < (Reading.bits.size() + 1);) {
- if (GetTickCount64() > endTickCount) {
- return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
- }
-
- GpioPinValue value = this->pin->Read();
- if ((previousValue == GpioPinValue::High) && (value == GpioPinValue::Low)) {
- // A falling edge was detected
- LARGE_INTEGER now;
- QueryPerformanceCounter(&now);
-
- if (i != 0) {
- unsigned int difference = static_cast(
- now.QuadPart - prevTime.QuadPart);
- Reading.bits[Reading.bits.size() - i] =
- difference > oneThreshold;
- }
-
- prevTime = now;
- ++i;
- }
-
- previousValue = value;
- }
-```
-
-After all bits have been received, we validate the checksum to make sure the received data is valid. The data is returned through the `Reading` reference parameter.
-
-```cpp
- if (!Reading.IsValid()) {
- // checksum mismatch
- return HRESULT_FROM_WIN32(ERROR_INVALID_DATA);
- }
-
- return S_OK;
-```
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: gpio-onewire
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: "This sample shows how to read from the DHT11 from a Universal Windows Application for Windows 10 IoT Enterprise."
+---
+
+# GPIO OneWire DHT11/22 reader
+
+| Minimum SDK Version | 19041 |
+|---------------------|-------|
+| Minimum OS Version | 15063 |
+
+This sample has been updated to use the `GpioChangeReader` API which is new as of build 19041. You must install SDK version 19041 or later to build this sample.
+
+The sample has been temporarily modified to use two pins instead of one to drive the DHT22. `GpioChangeReader` requires interrupts to be enabled.
+`GpioPin.SetDriveMode()` currently takes much longer when interrupts are enabled than when they are disabled.
+If you try to change a pin from output to input when interrupts are enabled, you will miss the response from the DHT22.
+As a workaround, two pins are used to interface with the DHT22.
+One pin is configured as an output and is used to assert the data line LOW to request a sample.
+The other pin is configured as input and is used to capture changes on the data line.
+
+Your breadboard should be wired as follows. You can use either a MOSFET(2N700) or BJT transistor(2N3904).
+If you use a BJT(2N3904), be sure to put a resistor in series with the base of the transistor.
+
+
+
+## GPIO OneWire DHT11 reader
+
+Note what follows below is a bit out of date- the latest version on GitHub is a 2 wire operation requiring pin 4 as input and pin 5 as output.
+
+This sample shows how to read from the [DHT11](https://www.adafruit.com/product/386) from a Universal Windows Application.
+The DHT11 is a low cost temperature and humidity sensor that uses a single wire to interface to the host controller.
+This wire is used by the host to request a sample from the DHT11 and by the DHT11 to transmit data back to the host.
+
+The DHT11 is right on the edge performance-wise of what the GPIO APIs can handle.
+If there is background activity such as network, USB, filesystem, or graphics activity, it can prevent the sample from successfully sampling from the DHT11.
+
+For a description of the protocol used by the DHT11, see [this article](http://embedded-lab.com/blog/?p=4333).
+
+The datasheet is [here](http://akizukidenshi.com/download/ds/aosong/DHT11.pdf).
+
+
+
+### Requirements
+
+{:.table.table-bordered}
+| Minimum supported build | 10.0.10556 |
+|-------------------------|---------------------------------|
+| Supported Hardware | UP Board |
+
+### Hardware Setup
+
+You will need the following hardware to run this demo:
+
+ * A [DHT11](https://www.adafruit.com/product/386) or [DHT22](http://www.adafruit.com/products/385) sensor
+ * A couple of female-to-female connector wires
+
+Connect the components as shown in the following diagram:
+
+
+
+
+### Running the Solution
+
+ 1. Clone the Microsoft IoT Enterprise Repository and open GpioOneWire/GpioOneWire.vcxproj in Visual Studio 2019.
+ 2. Build the solution in Release x64 mode.
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+### BIOS Settings for UP Board
+If you are using UP Board, you have to setup the BIOS GPIO configuration.
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+1. Select **Pin 4** as **INPUT** and **Pin 5** as **OUTPUT**
+1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+1. Click the Start button to search for the app by name, and then launch it.
+
+### How it works
+
+The logic that interacts with the DHT11 is contained in the Dht11::Sample() method.
+Since the 1s and 0s that the DHT11 sends back are encoded as pulse widths, we need a way to precisely measure the time difference between falling edges.
+We use [QueryPerformanceCounter()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644904(v=vs.85).aspx) for this purpose.
+The units of QueryPerformanceCounter are platform-dependent, so we must call [QueryPerformanceFrequency()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644905(v=vs.85).aspx) to determine the resolution of the counter.
+
+A difference of 76 microseconds between falling edges denotes a '0', while a difference of 120 microseconds between falling edges denotes a '1'.
+We choose 110 microseconds as a reasonable threshold above which we will consider bits to be 1s, while we will consider pulses shorter than this threshold to be 0s. We convert 110 microseconds to QueryPerformanceCounter (QPC) units to be used later.
+
+```cpp
+ HRESULT GpioOneWire::Dht11::Sample (GpioOneWire::Dht11Reading& Reading)
+ {
+ Reading = Dht11Reading();
+
+ LARGE_INTEGER qpf;
+ QueryPerformanceFrequency(&qpf);
+
+ // This is the threshold used to determine whether a bit is a '0' or a '1'.
+ // A '0' has a pulse time of 76 microseconds, while a '1' has a
+ // pulse time of 120 microseconds. 110 is chosen as a reasonable threshold.
+ // We convert the value to QPF units for later use.
+ const unsigned int oneThreshold = static_cast(
+ 110LL * qpf.QuadPart / 1000000LL);
+```
+
+Next, we send the sequence required to activate the sensor.
+The GPIO signal is normally pulled high while the device is idle, and we must pull it low for 18 milliseconds to request a sample. We latch a low value to the pin and set it as an output, driving the GPIO pin low.
+
+```cpp
+ // Latch low value onto pin
+ this->pin->Write(GpioPinValue::Low);
+
+ // Set pin as output
+ this->pin->SetDriveMode(GpioPinDriveMode::Output);
+
+ // Wait for at least 18 ms
+ Sleep(SAMPLE_HOLD_LOW_MILLIS);
+```
+
+We then revert the pin to an input which causes it to go high, and wait for the DHT11 to pull the pin low, then high again.
+
+```cpp
+ // Set pin back to input
+ this->pin->SetDriveMode(this->inputDriveMode);
+
+ GpioPinValue previousValue = this->pin->Read();
+
+ // catch the first rising edge
+ const ULONG initialRisingEdgeTimeoutMillis = 1;
+ ULONGLONG endTickCount = GetTickCount64() + initialRisingEdgeTimeoutMillis;
+ for (;;) {
+ if (GetTickCount64() > endTickCount) {
+ return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
+ }
+
+ GpioPinValue value = this->pin->Read();
+ if (value != previousValue) {
+ // rising edgue?
+ if (value == GpioPinValue::High) {
+ break;
+ }
+ previousValue = value;
+ }
+ }
+```
+
+After receiving the first rising edge, we catch all of the falling edges and measure the time difference between them to determine whether the bit is a 0 or 1.
+
+```cpp
+ LARGE_INTEGER prevTime = { 0 };
+
+ const ULONG sampleTimeoutMillis = 10;
+ endTickCount = GetTickCount64() + sampleTimeoutMillis;
+
+ // capture every falling edge until all bits are received or
+ // timeout occurs
+ for (unsigned int i = 0; i < (Reading.bits.size() + 1);) {
+ if (GetTickCount64() > endTickCount) {
+ return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
+ }
+
+ GpioPinValue value = this->pin->Read();
+ if ((previousValue == GpioPinValue::High) && (value == GpioPinValue::Low)) {
+ // A falling edge was detected
+ LARGE_INTEGER now;
+ QueryPerformanceCounter(&now);
+
+ if (i != 0) {
+ unsigned int difference = static_cast(
+ now.QuadPart - prevTime.QuadPart);
+ Reading.bits[Reading.bits.size() - i] =
+ difference > oneThreshold;
+ }
+
+ prevTime = now;
+ ++i;
+ }
+
+ previousValue = value;
+ }
+```
+
+After all bits have been received, we validate the checksum to make sure the received data is valid. The data is returned through the `Reading` reference parameter.
+
+```cpp
+ if (!Reading.IsValid()) {
+ // checksum mismatch
+ return HRESULT_FROM_WIN32(ERROR_INVALID_DATA);
+ }
+
+ return S_OK;
+```
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/GPIOOneWire/CPP/schematic.sch b/samples/GPIOOneWire/CPP/schematic.sch
index 8f1ea2840..0f6885aa6 100644
--- a/samples/GPIOOneWire/CPP/schematic.sch
+++ b/samples/GPIOOneWire/CPP/schematic.sch
@@ -1,408 +1,408 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h1>RHT03 / DHT-22 / AM2302 library</h1>
-<p>
-Library with devices (schematic symbol and packages) for the RHT03 / DHT-22 / AM2302 digital relative humidity and tempearture sensor.<br />
-Warning: Package does not include tKeepout areas so that the part may optionally be placed on a riser with components underneath. Please keep the package outline and bent-pin space in mind.
-</p>
-
-
-<h1>RHT03 / DHT-22</h1>
-<p>
-Package for the RHT03 / DHT-22 relative humidity and temperature sensor.
-</p>
-
-
-
-
-
-
-
-
-
-
-
->NAME
->VALUE
-
-
-<h1>AM2302</h1>
-<p>
-Package for the AM2302 wired variant of the RHT03/DHT-22 relative humidity and temperature sensor.
-</p>
-
-
-
-
->NAME
-
-
-
-
-
->VALUE
-
-
-<h1>RHT03 / DHT-22 - RIGHT ANGLE</h1>
-<p>
-Right angle package for the RHT03 / DHT-22 relative humidity and temperature sensor.
-</p>
-
-
-
-
-
->NAME
-
-
-
-
-
-
-
-
-
-
-
->VALUE
-
-
-
-
-<h1>RHT03 / DHT-22 / AM2302</h1>
-<p>
-Symbol for the RHT03 / DHT-22 / AM2302 relative humidity and temperature sensor.
-</p>
-
-
-
-
-
-
-
-
->NAME
->VALUE
-
-
-
-
-<h1>RHT03 / DHT-22 / AM2302</h1>
-<p>
-Packages and symbol for the RHT03 / DHT-22 relative humidity and temperature sensor.<br />
-Note: The AM2302 is a wired version of the DHT-22 which typically requires less clearance and is thus provided as a separate package.
-</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<b>Field Effect Transistors</b><p>
-<author>Created by librarian@cadsoft.de</author><p>
-<p>
-Symbols changed according to IEC617<p>
-All types, packages and assignment to symbols and pins checked<p>
-Package outlines partly checked<p>
-<p>
-JFET = junction FET<p>
-IGBT-x = insulated gate bipolar transistor<p>
-x=N: NPN; x=P: PNP<p>
-IGFET-mc-nnn; (IGFET=insulated gate field effect transistor)<P>
-m=D: depletion mode (Verdrängungstyp)<p>
-m=E: enhancement mode (Anreicherungstyp)<p>
-c: N=N-channel; P=P-Channel<p>
-GDSB: gate, drain, source, bulk<p>
-<p>
-by R. Vogg 15.March.2002
-
-
-<b>TO 92</b>
-
-
-
-
-
-
-
-
-
-
-
-
-
->NAME
->VALUE
-2
-3
-1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
->VALUE
->NAME
-
-
-
-
-
-
-
-<b>N-Channel Enhancement MOSFET</b> not checked
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<b>Supply Symbols</b><p>
- GND, VCC, 0V, +5V, -5V, etc.<p>
- Please keep in mind, that these devices are necessary for the
- automatic wiring of the supply signals.<p>
- The pin name defined in the symbol is identical to the net which is to be wired automatically.<p>
- In this library the device names are the same as the pin names of the symbols, therefore the correct signal names appear next to the supply symbols in the schematic.<p>
- <author>Created by librarian@cadsoft.de</author>
-
-
-
-
-
-
->VALUE
-
-
-
-
->VALUE
-
-
-
-
-
-<b>SUPPLY SYMBOL</b>
-
-
-
-
-
-
-
-
-
-
-
-
-<b>SUPPLY SYMBOL</b>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<h1>RHT03 / DHT-22 / AM2302 library</h1>
+<p>
+Library with devices (schematic symbol and packages) for the RHT03 / DHT-22 / AM2302 digital relative humidity and tempearture sensor.<br />
+Warning: Package does not include tKeepout areas so that the part may optionally be placed on a riser with components underneath. Please keep the package outline and bent-pin space in mind.
+</p>
+
+
+<h1>RHT03 / DHT-22</h1>
+<p>
+Package for the RHT03 / DHT-22 relative humidity and temperature sensor.
+</p>
+
+
+
+
+
+
+
+
+
+
+
+>NAME
+>VALUE
+
+
+<h1>AM2302</h1>
+<p>
+Package for the AM2302 wired variant of the RHT03/DHT-22 relative humidity and temperature sensor.
+</p>
+
+
+
+
+>NAME
+
+
+
+
+
+>VALUE
+
+
+<h1>RHT03 / DHT-22 - RIGHT ANGLE</h1>
+<p>
+Right angle package for the RHT03 / DHT-22 relative humidity and temperature sensor.
+</p>
+
+
+
+
+
+>NAME
+
+
+
+
+
+
+
+
+
+
+
+>VALUE
+
+
+
+
+<h1>RHT03 / DHT-22 / AM2302</h1>
+<p>
+Symbol for the RHT03 / DHT-22 / AM2302 relative humidity and temperature sensor.
+</p>
+
+
+
+
+
+
+
+
+>NAME
+>VALUE
+
+
+
+
+<h1>RHT03 / DHT-22 / AM2302</h1>
+<p>
+Packages and symbol for the RHT03 / DHT-22 relative humidity and temperature sensor.<br />
+Note: The AM2302 is a wired version of the DHT-22 which typically requires less clearance and is thus provided as a separate package.
+</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<b>Field Effect Transistors</b><p>
+<author>Created by librarian@cadsoft.de</author><p>
+<p>
+Symbols changed according to IEC617<p>
+All types, packages and assignment to symbols and pins checked<p>
+Package outlines partly checked<p>
+<p>
+JFET = junction FET<p>
+IGBT-x = insulated gate bipolar transistor<p>
+x=N: NPN; x=P: PNP<p>
+IGFET-mc-nnn; (IGFET=insulated gate field effect transistor)<P>
+m=D: depletion mode (Verdrängungstyp)<p>
+m=E: enhancement mode (Anreicherungstyp)<p>
+c: N=N-channel; P=P-Channel<p>
+GDSB: gate, drain, source, bulk<p>
+<p>
+by R. Vogg 15.March.2002
+
+
+<b>TO 92</b>
+
+
+
+
+
+
+
+
+
+
+
+
+
+>NAME
+>VALUE
+2
+3
+1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+>VALUE
+>NAME
+
+
+
+
+
+
+
+<b>N-Channel Enhancement MOSFET</b> not checked
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<b>Supply Symbols</b><p>
+ GND, VCC, 0V, +5V, -5V, etc.<p>
+ Please keep in mind, that these devices are necessary for the
+ automatic wiring of the supply signals.<p>
+ The pin name defined in the symbol is identical to the net which is to be wired automatically.<p>
+ In this library the device names are the same as the pin names of the symbols, therefore the correct signal names appear next to the supply symbols in the schematic.<p>
+ <author>Created by librarian@cadsoft.de</author>
+
+
+
+
+
+
+>VALUE
+
+
+
+
+>VALUE
+
+
+
+
+
+<b>SUPPLY SYMBOL</b>
+
+
+
+
+
+
+
+
+
+
+
+
+<b>SUPPLY SYMBOL</b>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/samples/GPIOOneWire/ReadMe.md b/samples/GPIOOneWire/ReadMe.md
index c3624db83..6e38026f9 100644
--- a/samples/GPIOOneWire/ReadMe.md
+++ b/samples/GPIOOneWire/ReadMe.md
@@ -1,207 +1,207 @@
----
-page_type: sample
-urlFragment: gpio-onewire
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: "This sample shows how to read from the DHT11 from a Universal Windows Application for Windows 10 IoT Enterprise."
----
-
-# GPIO OneWire DHT11/22 reader
-
-| Minimum SDK Version | 19041 |
-|---------------------|-------|
-| Minimum OS Version | 15063 |
-
-This sample has been updated to use the `GpioChangeReader` API which is new as of build 19041. You must install SDK version 19041 or later to build this sample.
-
-The sample has been temporarily modified to use two pins instead of one to drive the DHT22. `GpioChangeReader` requires interrupts to be enabled.
-`GpioPin.SetDriveMode()` currently takes much longer when interrupts are enabled than when they are disabled.
-If you try to change a pin from output to input when interrupts are enabled, you will miss the response from the DHT22.
-As a workaround, two pins are used to interface with the DHT22.
-One pin is configured as an output and is used to assert the data line LOW to request a sample.
-The other pin is configured as input and is used to capture changes on the data line.
-
-Your breadboard should be wired as follows. You can use either a MOSFET(2N7000) or BJT transistor(2N3904).
-If you use a BJT(2N3904), be sure to put a resistor in series with the base of the transistor.
-
-
-
-## GPIO OneWire DHT11 reader
-
-Note what follows below is a bit out of date- the latest version on GitHub is a 2 wire operation requiring pin 4 as input and pin 5 as output.
-
-This sample shows how to read from the [DHT11](https://www.adafruit.com/product/386) from a Universal Windows Application.
-The DHT11 is a low cost temperature and humidity sensor that uses a single wire to interface to the host controller.
-This wire is used by the host to request a sample from the DHT11 and by the DHT11 to transmit data back to the host.
-
-The DHT11 is right on the edge performance-wise of what the GPIO APIs can handle.
-If there is background activity such as network, USB, filesystem, or graphics activity, it can prevent the sample from successfully sampling from the DHT11.
-
-For a description of the protocol used by the DHT11, see [this article](http://embedded-lab.com/blog/?p=4333).
-
-The datasheet is [here](http://akizukidenshi.com/download/ds/aosong/DHT11.pdf).
-
-
-
-### Requirements
-
-{:.table.table-bordered}
-| Minimum supported build | 10.0.10556 |
-|-------------------------|---------------------------------|
-| Supported Hardware | UP Board |
-
-### Hardware Setup
-
-You will need the following hardware to run this demo:
-
- * A [DHT11](https://www.adafruit.com/product/386) or [DHT22](http://www.adafruit.com/products/385) sensor
- * A couple of female-to-female connector wires
-
-Connect the components as shown in the following diagram:
-
-
-
-
-### Running the Solution
-
- 1. Clone the Microsoft IoT Enterprise Repository and open GpioOneWire/GpioOneWire.vcxproj in Visual Studio 2019.
- 2. Build the solution in Release x64 mode.
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-### BIOS Settings for UP Board
-If you are using UP Board, you have to setup the BIOS GPIO configuration.
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-1. Select **Pin 4** as **INPUT** and **Pin 5** as **OUTPUT**
-1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-1. Click the Start button to search for the app by name, and then launch it.
-
-### How it works
-
-The logic that interacts with the DHT11 is contained in the Dht11::Sample() method.
-Since the 1s and 0s that the DHT11 sends back are encoded as pulse widths, we need a way to precisely measure the time difference between falling edges.
-We use [QueryPerformanceCounter()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644904(v=vs.85).aspx) for this purpose.
-The units of QueryPerformanceCounter are platform-dependent, so we must call [QueryPerformanceFrequency()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644905(v=vs.85).aspx) to determine the resolution of the counter.
-
-A difference of 76 microseconds between falling edges denotes a '0', while a difference of 120 microseconds between falling edges denotes a '1'.
-We choose 110 microseconds as a reasonable threshold above which we will consider bits to be 1s, while we will consider pulses shorter than this threshold to be 0s. We convert 110 microseconds to QueryPerformanceCounter (QPC) units to be used later.
-
-```cpp
- HRESULT GpioOneWire::Dht11::Sample (GpioOneWire::Dht11Reading& Reading)
- {
- Reading = Dht11Reading();
-
- LARGE_INTEGER qpf;
- QueryPerformanceFrequency(&qpf);
-
- // This is the threshold used to determine whether a bit is a '0' or a '1'.
- // A '0' has a pulse time of 76 microseconds, while a '1' has a
- // pulse time of 120 microseconds. 110 is chosen as a reasonable threshold.
- // We convert the value to QPF units for later use.
- const unsigned int oneThreshold = static_cast(
- 110LL * qpf.QuadPart / 1000000LL);
-```
-
-Next, we send the sequence required to activate the sensor.
-The GPIO signal is normally pulled high while the device is idle, and we must pull it low for 18 milliseconds to request a sample. We latch a low value to the pin and set it as an output, driving the GPIO pin low.
-
-```cpp
- // Latch low value onto pin
- this->pin->Write(GpioPinValue::Low);
-
- // Set pin as output
- this->pin->SetDriveMode(GpioPinDriveMode::Output);
-
- // Wait for at least 18 ms
- Sleep(SAMPLE_HOLD_LOW_MILLIS);
-```
-
-We then revert the pin to an input which causes it to go high, and wait for the DHT11 to pull the pin low, then high again.
-
-```cpp
- // Set pin back to input
- this->pin->SetDriveMode(this->inputDriveMode);
-
- GpioPinValue previousValue = this->pin->Read();
-
- // catch the first rising edge
- const ULONG initialRisingEdgeTimeoutMillis = 1;
- ULONGLONG endTickCount = GetTickCount64() + initialRisingEdgeTimeoutMillis;
- for (;;) {
- if (GetTickCount64() > endTickCount) {
- return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
- }
-
- GpioPinValue value = this->pin->Read();
- if (value != previousValue) {
- // rising edgue?
- if (value == GpioPinValue::High) {
- break;
- }
- previousValue = value;
- }
- }
-```
-
-After receiving the first rising edge, we catch all of the falling edges and measure the time difference between them to determine whether the bit is a 0 or 1.
-
-```cpp
- LARGE_INTEGER prevTime = { 0 };
-
- const ULONG sampleTimeoutMillis = 10;
- endTickCount = GetTickCount64() + sampleTimeoutMillis;
-
- // capture every falling edge until all bits are received or
- // timeout occurs
- for (unsigned int i = 0; i < (Reading.bits.size() + 1);) {
- if (GetTickCount64() > endTickCount) {
- return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
- }
-
- GpioPinValue value = this->pin->Read();
- if ((previousValue == GpioPinValue::High) && (value == GpioPinValue::Low)) {
- // A falling edge was detected
- LARGE_INTEGER now;
- QueryPerformanceCounter(&now);
-
- if (i != 0) {
- unsigned int difference = static_cast(
- now.QuadPart - prevTime.QuadPart);
- Reading.bits[Reading.bits.size() - i] =
- difference > oneThreshold;
- }
-
- prevTime = now;
- ++i;
- }
-
- previousValue = value;
- }
-```
-
-After all bits have been received, we validate the checksum to make sure the received data is valid. The data is returned through the `Reading` reference parameter.
-
-```cpp
- if (!Reading.IsValid()) {
- // checksum mismatch
- return HRESULT_FROM_WIN32(ERROR_INVALID_DATA);
- }
-
- return S_OK;
-```
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: gpio-onewire
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: "This sample shows how to read from the DHT11 from a Universal Windows Application for Windows 10 IoT Enterprise."
+---
+
+# GPIO OneWire DHT11/22 reader
+
+| Minimum SDK Version | 19041 |
+|---------------------|-------|
+| Minimum OS Version | 15063 |
+
+This sample has been updated to use the `GpioChangeReader` API which is new as of build 19041. You must install SDK version 19041 or later to build this sample.
+
+The sample has been temporarily modified to use two pins instead of one to drive the DHT22. `GpioChangeReader` requires interrupts to be enabled.
+`GpioPin.SetDriveMode()` currently takes much longer when interrupts are enabled than when they are disabled.
+If you try to change a pin from output to input when interrupts are enabled, you will miss the response from the DHT22.
+As a workaround, two pins are used to interface with the DHT22.
+One pin is configured as an output and is used to assert the data line LOW to request a sample.
+The other pin is configured as input and is used to capture changes on the data line.
+
+Your breadboard should be wired as follows. You can use either a MOSFET(2N7000) or BJT transistor(2N3904).
+If you use a BJT(2N3904), be sure to put a resistor in series with the base of the transistor.
+
+
+
+## GPIO OneWire DHT11 reader
+
+Note what follows below is a bit out of date- the latest version on GitHub is a 2 wire operation requiring pin 4 as input and pin 5 as output.
+
+This sample shows how to read from the [DHT11](https://www.adafruit.com/product/386) from a Universal Windows Application.
+The DHT11 is a low cost temperature and humidity sensor that uses a single wire to interface to the host controller.
+This wire is used by the host to request a sample from the DHT11 and by the DHT11 to transmit data back to the host.
+
+The DHT11 is right on the edge performance-wise of what the GPIO APIs can handle.
+If there is background activity such as network, USB, filesystem, or graphics activity, it can prevent the sample from successfully sampling from the DHT11.
+
+For a description of the protocol used by the DHT11, see [this article](http://embedded-lab.com/blog/?p=4333).
+
+The datasheet is [here](http://akizukidenshi.com/download/ds/aosong/DHT11.pdf).
+
+
+
+### Requirements
+
+{:.table.table-bordered}
+| Minimum supported build | 10.0.10556 |
+|-------------------------|---------------------------------|
+| Supported Hardware | UP Board |
+
+### Hardware Setup
+
+You will need the following hardware to run this demo:
+
+ * A [DHT11](https://www.adafruit.com/product/386) or [DHT22](http://www.adafruit.com/products/385) sensor
+ * A couple of female-to-female connector wires
+
+Connect the components as shown in the following diagram:
+
+
+
+
+### Running the Solution
+
+ 1. Clone the Microsoft IoT Enterprise Repository and open GpioOneWire/GpioOneWire.vcxproj in Visual Studio 2019.
+ 2. Build the solution in Release x64 mode.
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+### BIOS Settings for UP Board
+If you are using UP Board, you have to setup the BIOS GPIO configuration.
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+1. Select **Pin 4** as **INPUT** and **Pin 5** as **OUTPUT**
+1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+1. Click the Start button to search for the app by name, and then launch it.
+
+### How it works
+
+The logic that interacts with the DHT11 is contained in the Dht11::Sample() method.
+Since the 1s and 0s that the DHT11 sends back are encoded as pulse widths, we need a way to precisely measure the time difference between falling edges.
+We use [QueryPerformanceCounter()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644904(v=vs.85).aspx) for this purpose.
+The units of QueryPerformanceCounter are platform-dependent, so we must call [QueryPerformanceFrequency()](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644905(v=vs.85).aspx) to determine the resolution of the counter.
+
+A difference of 76 microseconds between falling edges denotes a '0', while a difference of 120 microseconds between falling edges denotes a '1'.
+We choose 110 microseconds as a reasonable threshold above which we will consider bits to be 1s, while we will consider pulses shorter than this threshold to be 0s. We convert 110 microseconds to QueryPerformanceCounter (QPC) units to be used later.
+
+```cpp
+ HRESULT GpioOneWire::Dht11::Sample (GpioOneWire::Dht11Reading& Reading)
+ {
+ Reading = Dht11Reading();
+
+ LARGE_INTEGER qpf;
+ QueryPerformanceFrequency(&qpf);
+
+ // This is the threshold used to determine whether a bit is a '0' or a '1'.
+ // A '0' has a pulse time of 76 microseconds, while a '1' has a
+ // pulse time of 120 microseconds. 110 is chosen as a reasonable threshold.
+ // We convert the value to QPF units for later use.
+ const unsigned int oneThreshold = static_cast(
+ 110LL * qpf.QuadPart / 1000000LL);
+```
+
+Next, we send the sequence required to activate the sensor.
+The GPIO signal is normally pulled high while the device is idle, and we must pull it low for 18 milliseconds to request a sample. We latch a low value to the pin and set it as an output, driving the GPIO pin low.
+
+```cpp
+ // Latch low value onto pin
+ this->pin->Write(GpioPinValue::Low);
+
+ // Set pin as output
+ this->pin->SetDriveMode(GpioPinDriveMode::Output);
+
+ // Wait for at least 18 ms
+ Sleep(SAMPLE_HOLD_LOW_MILLIS);
+```
+
+We then revert the pin to an input which causes it to go high, and wait for the DHT11 to pull the pin low, then high again.
+
+```cpp
+ // Set pin back to input
+ this->pin->SetDriveMode(this->inputDriveMode);
+
+ GpioPinValue previousValue = this->pin->Read();
+
+ // catch the first rising edge
+ const ULONG initialRisingEdgeTimeoutMillis = 1;
+ ULONGLONG endTickCount = GetTickCount64() + initialRisingEdgeTimeoutMillis;
+ for (;;) {
+ if (GetTickCount64() > endTickCount) {
+ return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
+ }
+
+ GpioPinValue value = this->pin->Read();
+ if (value != previousValue) {
+ // rising edgue?
+ if (value == GpioPinValue::High) {
+ break;
+ }
+ previousValue = value;
+ }
+ }
+```
+
+After receiving the first rising edge, we catch all of the falling edges and measure the time difference between them to determine whether the bit is a 0 or 1.
+
+```cpp
+ LARGE_INTEGER prevTime = { 0 };
+
+ const ULONG sampleTimeoutMillis = 10;
+ endTickCount = GetTickCount64() + sampleTimeoutMillis;
+
+ // capture every falling edge until all bits are received or
+ // timeout occurs
+ for (unsigned int i = 0; i < (Reading.bits.size() + 1);) {
+ if (GetTickCount64() > endTickCount) {
+ return HRESULT_FROM_WIN32(ERROR_TIMEOUT);
+ }
+
+ GpioPinValue value = this->pin->Read();
+ if ((previousValue == GpioPinValue::High) && (value == GpioPinValue::Low)) {
+ // A falling edge was detected
+ LARGE_INTEGER now;
+ QueryPerformanceCounter(&now);
+
+ if (i != 0) {
+ unsigned int difference = static_cast(
+ now.QuadPart - prevTime.QuadPart);
+ Reading.bits[Reading.bits.size() - i] =
+ difference > oneThreshold;
+ }
+
+ prevTime = now;
+ ++i;
+ }
+
+ previousValue = value;
+ }
+```
+
+After all bits have been received, we validate the checksum to make sure the received data is valid. The data is returned through the `Reading` reference parameter.
+
+```cpp
+ if (!Reading.IsValid()) {
+ // checksum mismatch
+ return HRESULT_FROM_WIN32(ERROR_INVALID_DATA);
+ }
+
+ return S_OK;
+```
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/HIDInjector/README.md b/samples/HIDInjector/README.md
index a693bcee8..efefd9798 100644
--- a/samples/HIDInjector/README.md
+++ b/samples/HIDInjector/README.md
@@ -1,50 +1,50 @@
----
-page_type: sample
-urlFragment: HIDInjector
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that will allow you to deploy a driver to perform low level injection of touch, keyboard and mouse event.
----
-
-# HID Injector
-
-Windows 10 IoT Enterprise HID Injector sample will allow you to deploy a driver to perform low level injection of touch, keyboard and mouse events, and can be used until the SendInput equivalent API is available.
-
-The HID Injection sample leverages the [Virtual HID Framework](https://msdn.microsoft.com/en-us/library/windows/hardware/dn925056(v=vs.85).aspx).
-
-# Prerequisites
-In order to build this driver you will need the following:
-
- * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/).
- * [Windows 10 Driver Development Kit](https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk).
- * [Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk/).
-
-## Building and Deploying the HID Injector
- 1. Be sure you've installed the Visual Studio update and the Windows 10 Driver Development kit before continuing.
- 2. On your development machine, use Windows Explorer to navigate to the folder where you downloaded or cloned samples.
- 3. Open the project located ```Samples\HidInjector\HidInjector.sln```.
- 4. Select the architecture you intend to deploy to: x64 for UP Board.
- 5. You can now build the solution.
-
-### Copying the HID Injector to your device
- 1. Under the driver Directory you will find the .inf and .sys file, copy that folder and send it to Windows 10 IoT Enterprise device
- 2. Copy the testvhid application file from release folder, send this file to the Windows 10 IoT Enterprise device.
-
-### Installing the HID Injector
- 1. Install the inf file in the Windows 10 IoT Enterprise device.
- 2. You will see the dialogue box of "The operation completed successful".
- 3. Run the "Testvhid.exe" file in command prompt under Administrator mode.
- 4. You will see the message ".... sending control to the device". without any error message.
- 5. The HID injector device installed in IoT device.
-
-### Verify installation
-If you've installed the driver, verify the install by navigating to the Device Manager and looking for the HID Injection Sample node.
-
-## Using the HID Injector
-Included in the solution is a C++ console application used to demonstrate communication with the HID injection Driver. The Driver is discovered by class using "CM_Get_Device_Interface_List".
-The sample application will inject Touch, Keyboard and Mouse events by synthesizing a HID block, and calling the driver with that block.
+---
+page_type: sample
+urlFragment: HIDInjector
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that will allow you to deploy a driver to perform low level injection of touch, keyboard and mouse event.
+---
+
+# HID Injector
+
+Windows 10 IoT Enterprise HID Injector sample will allow you to deploy a driver to perform low level injection of touch, keyboard and mouse events, and can be used until the SendInput equivalent API is available.
+
+The HID Injection sample leverages the [Virtual HID Framework](https://msdn.microsoft.com/en-us/library/windows/hardware/dn925056(v=vs.85).aspx).
+
+# Prerequisites
+In order to build this driver you will need the following:
+
+ * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/).
+ * [Windows 10 Driver Development Kit](https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk).
+ * [Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk/).
+
+## Building and Deploying the HID Injector
+ 1. Be sure you've installed the Visual Studio update and the Windows 10 Driver Development kit before continuing.
+ 2. On your development machine, use Windows Explorer to navigate to the folder where you downloaded or cloned samples.
+ 3. Open the project located ```Samples\HidInjector\HidInjector.sln```.
+ 4. Select the architecture you intend to deploy to: x64 for UP Board.
+ 5. You can now build the solution.
+
+### Copying the HID Injector to your device
+ 1. Under the driver Directory you will find the .inf and .sys file, copy that folder and send it to Windows 10 IoT Enterprise device
+ 2. Copy the testvhid application file from release folder, send this file to the Windows 10 IoT Enterprise device.
+
+### Installing the HID Injector
+ 1. Install the inf file in the Windows 10 IoT Enterprise device.
+ 2. You will see the dialogue box of "The operation completed successful".
+ 3. Run the "Testvhid.exe" file in command prompt under Administrator mode.
+ 4. You will see the message ".... sending control to the device". without any error message.
+ 5. The HID injector device installed in IoT device.
+
+### Verify installation
+If you've installed the driver, verify the install by navigating to the Device Manager and looking for the HID Injection Sample node.
+
+## Using the HID Injector
+Included in the solution is a C++ console application used to demonstrate communication with the HID injection Driver. The Driver is discovered by class using "CM_Get_Device_Interface_List".
+The sample application will inject Touch, Keyboard and Mouse events by synthesizing a HID block, and calling the driver with that block.
diff --git a/samples/HIDInjector/driver/CreateDriverPackage.cmd b/samples/HIDInjector/driver/CreateDriverPackage.cmd
index b807b529d..d5161e79d 100644
--- a/samples/HIDInjector/driver/CreateDriverPackage.cmd
+++ b/samples/HIDInjector/driver/CreateDriverPackage.cmd
@@ -1,17 +1,17 @@
-:: Run the following script from “Deployment and Imaging Tools Environment” as Admin.
-SET PATH=%KITSROOT%\tools\bin\i386;%PATH%
-SET PATH=%KITSROOT%\bin\i386;%PATH%
-SET AKROOT=%KITSROOT%
-SET WPDKCONTENTROOT=%KITSROOT%
-SET PKG_CONFIG_XML=%KITSROOT%Tools\bin\i386\pkggen.cfg.xml
-SET BSP_VERSION=10.0.0.0
-SET BSP_ARCH=arm
-SET OUTPUT_DIRECTORY=.
-
-:: The following variables ensure the package is appropriately signed
-SET SIGN_OEM=1
-SET SIGN_WITH_TIMESTAMP=0
-
-echo Creating Driver Package
-"%KITSROOT%Tools\bin\i386\pkggen.exe" HidDriver.%BSP_ARCH%.pkg.xml /config:"%PKG_CONFIG_XML%" /output:"%OUTPUT_DIRECTORY%" /version:%BSP_VERSION% /build:fre /cpu:%BSP_ARCH% /nohives /variables:"_RELEASEDIR=%OUTPUT_DIRECTORY\;"
-
+:: Run the following script from “Deployment and Imaging Tools Environment” as Admin.
+SET PATH=%KITSROOT%\tools\bin\i386;%PATH%
+SET PATH=%KITSROOT%\bin\i386;%PATH%
+SET AKROOT=%KITSROOT%
+SET WPDKCONTENTROOT=%KITSROOT%
+SET PKG_CONFIG_XML=%KITSROOT%Tools\bin\i386\pkggen.cfg.xml
+SET BSP_VERSION=10.0.0.0
+SET BSP_ARCH=arm
+SET OUTPUT_DIRECTORY=.
+
+:: The following variables ensure the package is appropriately signed
+SET SIGN_OEM=1
+SET SIGN_WITH_TIMESTAMP=0
+
+echo Creating Driver Package
+"%KITSROOT%Tools\bin\i386\pkggen.exe" HidDriver.%BSP_ARCH%.pkg.xml /config:"%PKG_CONFIG_XML%" /output:"%OUTPUT_DIRECTORY%" /version:%BSP_VERSION% /build:fre /cpu:%BSP_ARCH% /nohives /variables:"_RELEASEDIR=%OUTPUT_DIRECTORY\;"
+
diff --git a/samples/HIDInjector/driver/HidDriver.arm.pkg.xml b/samples/HIDInjector/driver/HidDriver.arm.pkg.xml
index 937bcdd5d..1dc8ecc16 100644
--- a/samples/HIDInjector/driver/HidDriver.arm.pkg.xml
+++ b/samples/HIDInjector/driver/HidDriver.arm.pkg.xml
@@ -1,22 +1,22 @@
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/Hello Blinky/CS/Properties/Default.rd.xml b/samples/Hello Blinky/CS/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/Hello Blinky/CS/Properties/Default.rd.xml
+++ b/samples/Hello Blinky/CS/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/Hello Blinky/CS/README.md b/samples/Hello Blinky/CS/README.md
index 51ead218a..a6d1cb19a 100644
--- a/samples/Hello Blinky/CS/README.md
+++ b/samples/Hello Blinky/CS/README.md
@@ -1,186 +1,186 @@
----
-page_type: sample
-urlFragment: hello-blinky
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
----
-
-# “Hello, blinky!”
-
-We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
-
-> [!NOTE]
->
-> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
-
-## Step 1: Load the project in Visual Studio 2019
-
-* * *
-
-1. Open the application in Visual Studio 2019
-2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
-
-## Step 2: Connect the LED to your Windows IoT device
-
-* * *
-
-You’ll need a few components:
-
-* a LED (any color you like)
-
-* a 220 Ω resistor for the UP Board
-
-* a breadboard and a couple of connector wires
-
-
-
-### For UP Board
-
-1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
-2. Connect the longer leg of the LED to the resistor.
-3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
-4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
-
-And here is the pinout of the UP Board:
-
-
-
-Here is an example of what your breadboard might look like with the circuit assembled:
-
-
-
-## Step 3: Deploy your app
-
-* * *
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
- 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
- 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
- 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-4. Click the Start button to search for the app by name, and then launch it.
-
-5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
-
-
-
-Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
-
-## Let’s look at the code
-
-* * *
-
-The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
-
-### Timer code
-
-Here is how you set up the timer in C#:
-
-
- public MainPage()
- {
- // ...
-
- timer = new DispatcherTimer();
- timer.Interval = TimeSpan.FromMilliseconds(500);
- timer.Tick += Timer_Tick;
- InitGPIO();
- if (pin != null)
- {
- timer.Start();
- }
-
- // ...
- }
-
- private void Timer_Tick(object sender, object e)
- {
- if (pinValue == GpioPinValue.High)
- {
- pinValue = GpioPinValue.Low;
- pin.Write(pinValue);
- LED.Fill = redBrush;
- }
- else
- {
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- LED.Fill = grayBrush;
- }
- }
-
-### Initialize the GPIO pin
-
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-
- using Windows.Devices.Gpio;
-
- private void InitGPIO()
- {
- var gpio = GpioController.GetDefault();
-
- // Show an error if there is no GPIO controller
- if (gpio == null)
- {
- pin = null;
- GpioStatus.Text = "There is no GPIO controller on this device.";
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-
- GpioStatus.Text = "GPIO pin initialized correctly.";
-
- }
-
-Let’s break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-### Modify the state of the GPIO pin
-
-Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
- pin.Write(GpioPinValue.Low);
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
- pin.Write(GpioPinValue.High);
-
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional resources
-
-* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
-* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: hello-blinky
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
+---
+
+# “Hello, blinky!”
+
+We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
+
+> [!NOTE]
+>
+> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
+
+## Step 1: Load the project in Visual Studio 2019
+
+* * *
+
+1. Open the application in Visual Studio 2019
+2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
+
+## Step 2: Connect the LED to your Windows IoT device
+
+* * *
+
+You’ll need a few components:
+
+* a LED (any color you like)
+
+* a 220 Ω resistor for the UP Board
+
+* a breadboard and a couple of connector wires
+
+
+
+### For UP Board
+
+1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
+2. Connect the longer leg of the LED to the resistor.
+3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
+4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
+
+And here is the pinout of the UP Board:
+
+
+
+Here is an example of what your breadboard might look like with the circuit assembled:
+
+
+
+## Step 3: Deploy your app
+
+* * *
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
+ 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+ 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+ 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+4. Click the Start button to search for the app by name, and then launch it.
+
+5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
+
+
+
+Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
+
+## Let’s look at the code
+
+* * *
+
+The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
+
+### Timer code
+
+Here is how you set up the timer in C#:
+
+
+ public MainPage()
+ {
+ // ...
+
+ timer = new DispatcherTimer();
+ timer.Interval = TimeSpan.FromMilliseconds(500);
+ timer.Tick += Timer_Tick;
+ InitGPIO();
+ if (pin != null)
+ {
+ timer.Start();
+ }
+
+ // ...
+ }
+
+ private void Timer_Tick(object sender, object e)
+ {
+ if (pinValue == GpioPinValue.High)
+ {
+ pinValue = GpioPinValue.Low;
+ pin.Write(pinValue);
+ LED.Fill = redBrush;
+ }
+ else
+ {
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ LED.Fill = grayBrush;
+ }
+ }
+
+### Initialize the GPIO pin
+
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+
+ using Windows.Devices.Gpio;
+
+ private void InitGPIO()
+ {
+ var gpio = GpioController.GetDefault();
+
+ // Show an error if there is no GPIO controller
+ if (gpio == null)
+ {
+ pin = null;
+ GpioStatus.Text = "There is no GPIO controller on this device.";
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+
+ GpioStatus.Text = "GPIO pin initialized correctly.";
+
+ }
+
+Let’s break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+### Modify the state of the GPIO pin
+
+Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+ pin.Write(GpioPinValue.Low);
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+ pin.Write(GpioPinValue.High);
+
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional resources
+
+* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
+* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/Hello Blinky/Cpp/README.md b/samples/Hello Blinky/Cpp/README.md
index 51ead218a..a6d1cb19a 100644
--- a/samples/Hello Blinky/Cpp/README.md
+++ b/samples/Hello Blinky/Cpp/README.md
@@ -1,186 +1,186 @@
----
-page_type: sample
-urlFragment: hello-blinky
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
----
-
-# “Hello, blinky!”
-
-We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
-
-> [!NOTE]
->
-> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
-
-## Step 1: Load the project in Visual Studio 2019
-
-* * *
-
-1. Open the application in Visual Studio 2019
-2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
-
-## Step 2: Connect the LED to your Windows IoT device
-
-* * *
-
-You’ll need a few components:
-
-* a LED (any color you like)
-
-* a 220 Ω resistor for the UP Board
-
-* a breadboard and a couple of connector wires
-
-
-
-### For UP Board
-
-1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
-2. Connect the longer leg of the LED to the resistor.
-3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
-4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
-
-And here is the pinout of the UP Board:
-
-
-
-Here is an example of what your breadboard might look like with the circuit assembled:
-
-
-
-## Step 3: Deploy your app
-
-* * *
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
- 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
- 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
- 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-4. Click the Start button to search for the app by name, and then launch it.
-
-5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
-
-
-
-Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
-
-## Let’s look at the code
-
-* * *
-
-The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
-
-### Timer code
-
-Here is how you set up the timer in C#:
-
-
- public MainPage()
- {
- // ...
-
- timer = new DispatcherTimer();
- timer.Interval = TimeSpan.FromMilliseconds(500);
- timer.Tick += Timer_Tick;
- InitGPIO();
- if (pin != null)
- {
- timer.Start();
- }
-
- // ...
- }
-
- private void Timer_Tick(object sender, object e)
- {
- if (pinValue == GpioPinValue.High)
- {
- pinValue = GpioPinValue.Low;
- pin.Write(pinValue);
- LED.Fill = redBrush;
- }
- else
- {
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- LED.Fill = grayBrush;
- }
- }
-
-### Initialize the GPIO pin
-
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-
- using Windows.Devices.Gpio;
-
- private void InitGPIO()
- {
- var gpio = GpioController.GetDefault();
-
- // Show an error if there is no GPIO controller
- if (gpio == null)
- {
- pin = null;
- GpioStatus.Text = "There is no GPIO controller on this device.";
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-
- GpioStatus.Text = "GPIO pin initialized correctly.";
-
- }
-
-Let’s break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-### Modify the state of the GPIO pin
-
-Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
- pin.Write(GpioPinValue.Low);
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
- pin.Write(GpioPinValue.High);
-
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional resources
-
-* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
-* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: hello-blinky
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
+---
+
+# “Hello, blinky!”
+
+We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
+
+> [!NOTE]
+>
+> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
+
+## Step 1: Load the project in Visual Studio 2019
+
+* * *
+
+1. Open the application in Visual Studio 2019
+2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
+
+## Step 2: Connect the LED to your Windows IoT device
+
+* * *
+
+You’ll need a few components:
+
+* a LED (any color you like)
+
+* a 220 Ω resistor for the UP Board
+
+* a breadboard and a couple of connector wires
+
+
+
+### For UP Board
+
+1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
+2. Connect the longer leg of the LED to the resistor.
+3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
+4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
+
+And here is the pinout of the UP Board:
+
+
+
+Here is an example of what your breadboard might look like with the circuit assembled:
+
+
+
+## Step 3: Deploy your app
+
+* * *
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
+ 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+ 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+ 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+4. Click the Start button to search for the app by name, and then launch it.
+
+5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
+
+
+
+Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
+
+## Let’s look at the code
+
+* * *
+
+The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
+
+### Timer code
+
+Here is how you set up the timer in C#:
+
+
+ public MainPage()
+ {
+ // ...
+
+ timer = new DispatcherTimer();
+ timer.Interval = TimeSpan.FromMilliseconds(500);
+ timer.Tick += Timer_Tick;
+ InitGPIO();
+ if (pin != null)
+ {
+ timer.Start();
+ }
+
+ // ...
+ }
+
+ private void Timer_Tick(object sender, object e)
+ {
+ if (pinValue == GpioPinValue.High)
+ {
+ pinValue = GpioPinValue.Low;
+ pin.Write(pinValue);
+ LED.Fill = redBrush;
+ }
+ else
+ {
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ LED.Fill = grayBrush;
+ }
+ }
+
+### Initialize the GPIO pin
+
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+
+ using Windows.Devices.Gpio;
+
+ private void InitGPIO()
+ {
+ var gpio = GpioController.GetDefault();
+
+ // Show an error if there is no GPIO controller
+ if (gpio == null)
+ {
+ pin = null;
+ GpioStatus.Text = "There is no GPIO controller on this device.";
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+
+ GpioStatus.Text = "GPIO pin initialized correctly.";
+
+ }
+
+Let’s break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+### Modify the state of the GPIO pin
+
+Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+ pin.Write(GpioPinValue.Low);
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+ pin.Write(GpioPinValue.High);
+
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional resources
+
+* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
+* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/Hello Blinky/README.md b/samples/Hello Blinky/README.md
index 310cc65c4..4a4e6bbf0 100644
--- a/samples/Hello Blinky/README.md
+++ b/samples/Hello Blinky/README.md
@@ -1,186 +1,186 @@
----
-page_type: sample
-urlFragment: hello-blinky
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
----
-
-# “Hello, blinky!”
-
-We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
-
-> [!NOTE]
->
-> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
-
-## Step 1: Load the project in Visual Studio 2019
-
-* * *
-
-1. Open the application in Visual Studio 2019
-2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
-
-## Step 2: Connect the LED to your Windows IoT device
-
-* * *
-
-You’ll need a few components:
-
-* a LED (any color you like)
-
-* a 220 Ω resistor for the UP Board
-
-* a breadboard and a couple of connector wires
-
-
-
-### For UP Board
-
-1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
-2. Connect the longer leg of the LED to the resistor.
-3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
-4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
-
-And here is the pinout of the UP Board:
-
-
-
-Here is an example of what your breadboard might look like with the circuit assembled:
-
-
-
-## Step 3: Deploy your app
-
-* * *
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
- 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
- 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
-
- 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-4. Click the Start button to search for the app by name, and then launch it.
-
-5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
-
-
-
-Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
-
-## Let’s look at the code
-
-* * *
-
-The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
-
-### Timer code
-
-Here is how you set up the timer in C#:
-
-
- public MainPage()
- {
- // ...
-
- timer = new DispatcherTimer();
- timer.Interval = TimeSpan.FromMilliseconds(500);
- timer.Tick += Timer_Tick;
- InitGPIO();
- if (pin != null)
- {
- timer.Start();
- }
-
- // ...
- }
-
- private void Timer_Tick(object sender, object e)
- {
- if (pinValue == GpioPinValue.High)
- {
- pinValue = GpioPinValue.Low;
- pin.Write(pinValue);
- LED.Fill = redBrush;
- }
- else
- {
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- LED.Fill = grayBrush;
- }
- }
-
-### Initialize the GPIO pin
-
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-
- using Windows.Devices.Gpio;
-
- private void InitGPIO()
- {
- var gpio = GpioController.GetDefault();
-
- // Show an error if there is no GPIO controller
- if (gpio == null)
- {
- pin = null;
- GpioStatus.Text = "There is no GPIO controller on this device.";
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
- pinValue = GpioPinValue.High;
- pin.Write(pinValue);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-
- GpioStatus.Text = "GPIO pin initialized correctly.";
-
- }
-
-Let’s break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-### Modify the state of the GPIO pin
-
-Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
- pin.Write(GpioPinValue.Low);
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
- pin.Write(GpioPinValue.High);
-
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional resources
-
-* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
-* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+---
+page_type: sample
+urlFragment: hello-blinky
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off for Windows 10 IoT Enterprise.
+---
+
+# “Hello, blinky!”
+
+We will create a simple LED blinking app and connect a LED to your Windows 10 IoT Enterprise device.
+
+> [!NOTE]
+>
+> GPIO APIs are not available on Desktop - this sample will be based on the UP Board.
+
+## Step 1: Load the project in Visual Studio 2019
+
+* * *
+
+1. Open the application in Visual Studio 2019
+2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select `x64`.
+
+## Step 2: Connect the LED to your Windows IoT device
+
+* * *
+
+You’ll need a few components:
+
+* a LED (any color you like)
+
+* a 220 Ω resistor for the UP Board
+
+* a breadboard and a couple of connector wires
+
+
+
+### For UP Board
+
+1. Connect the shorter leg of the LED to GPIO 5 (pin 15 on the expansion header) on the UP Board.
+2. Connect the longer leg of the LED to the resistor.
+3. Connect the other end of the resistor to one of the 3.3V pins on the UP Board.
+4. Note that the polarity of the LED is important. (This configuration is commonly known as Active Low)
+
+And here is the pinout of the UP Board:
+
+
+
+Here is an example of what your breadboard might look like with the circuit assembled:
+
+
+
+## Step 3: Deploy your app
+
+* * *
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+2. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+3. If you are using an UP Board, you have to setup the BIOS GPIO configuration.
+ 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+ 1. Navigate to the **Advance** tab and select the **Hat Configuration** and select **GPIO Configuration in Pin Order**.
+
+ 1. Configure the Pins you are using in the sample as **INPUT** or **OUTPUT**.
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+4. Click the Start button to search for the app by name, and then launch it.
+
+5. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
+
+
+
+Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
+
+## Let’s look at the code
+
+* * *
+
+The code for this sample is pretty simple. We use a timer, and each time the ‘Tick’ event is called, we flip the state of the LED.
+
+### Timer code
+
+Here is how you set up the timer in C#:
+
+
+ public MainPage()
+ {
+ // ...
+
+ timer = new DispatcherTimer();
+ timer.Interval = TimeSpan.FromMilliseconds(500);
+ timer.Tick += Timer_Tick;
+ InitGPIO();
+ if (pin != null)
+ {
+ timer.Start();
+ }
+
+ // ...
+ }
+
+ private void Timer_Tick(object sender, object e)
+ {
+ if (pinValue == GpioPinValue.High)
+ {
+ pinValue = GpioPinValue.Low;
+ pin.Write(pinValue);
+ LED.Fill = redBrush;
+ }
+ else
+ {
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ LED.Fill = grayBrush;
+ }
+ }
+
+### Initialize the GPIO pin
+
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+
+ using Windows.Devices.Gpio;
+
+ private void InitGPIO()
+ {
+ var gpio = GpioController.GetDefault();
+
+ // Show an error if there is no GPIO controller
+ if (gpio == null)
+ {
+ pin = null;
+ GpioStatus.Text = "There is no GPIO controller on this device.";
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+ pinValue = GpioPinValue.High;
+ pin.Write(pinValue);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+
+ GpioStatus.Text = "GPIO pin initialized correctly.";
+
+ }
+
+Let’s break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (High) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+### Modify the state of the GPIO pin
+
+Once we have access to the `GpioOutputPin` instance, it’s trivial to change the state of the pin to turn the LED on or off.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+ pin.Write(GpioPinValue.Low);
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+ pin.Write(GpioPinValue.High);
+
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional resources
+
+* [Windows 10 IoT Enterprise Documentation](https://docs.microsoft.com/windows/iot/iot-enterprise/getting_started)
+* [Documentation for all samples](https://developer.microsoft.com/windows/iot/samples)
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
diff --git a/samples/HelloBlinkyBackground/CPP/README.md b/samples/HelloBlinkyBackground/CPP/README.md
index 89d26a698..9bb8353fb 100644
--- a/samples/HelloBlinkyBackground/CPP/README.md
+++ b/samples/HelloBlinkyBackground/CPP/README.md
@@ -1,126 +1,126 @@
----
-page_type: sample
-urlFragment: hello-blinky-background
-languages:
- - csharp
- - cpp
- - vb
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
----
-
-# "Hello, blinky!" background service
-
-We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
-
-Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
-
-## Load the project in Visual Studio
-___
-
-You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
-
-Note that the app will not run successfully if it cannot find any available GPIO ports.
-
-Once the project is open and builds, the next step is to deploy the application to your device.
-
-When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
-
-## Let's look at the code
-___
-The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
-
-
-## Timer code
-___
-Here is how you set up the timer in C#:
-```csharp
-using Windows.System.Threading;
-
-BackgroundTaskDeferral _deferral;
-public void Run(IBackgroundTaskInstance taskInstance)
-{
- _deferral = taskInstance.GetDeferral();
-
- this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
- . . .
-}
-
-private void Timer_Tick(ThreadPoolTimer timer)
-{
- . . .
-}
-```
-
-
-## Initialize the GPIO pin
-___
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-```csharp
-using Windows.Devices.Gpio;
-
-private void InitGPIO()
-{
- var gpio = GpioController.GetDefault();
-
- if (gpio == null)
- {
- pin = null;
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
-
- if (pin == null)
- {
- return;
- }
-
- pin.Write(GpioPinValue.High);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-}
-```
-
-Let's break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-
-## Modify the state of the GPIO pin
-___
-Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
-```csharp
-this.pin.Write(GpioPinValue.Low);
-```
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
-```csharp
-this.pin.Write(GpioPinValue.High);
-```
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: hello-blinky-background
+languages:
+ - csharp
+ - cpp
+ - vb
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
+---
+
+# "Hello, blinky!" background service
+
+We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
+
+Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
+
+## Load the project in Visual Studio
+___
+
+You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
+
+Note that the app will not run successfully if it cannot find any available GPIO ports.
+
+Once the project is open and builds, the next step is to deploy the application to your device.
+
+When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
+
+## Let's look at the code
+___
+The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
+
+
+## Timer code
+___
+Here is how you set up the timer in C#:
+```csharp
+using Windows.System.Threading;
+
+BackgroundTaskDeferral _deferral;
+public void Run(IBackgroundTaskInstance taskInstance)
+{
+ _deferral = taskInstance.GetDeferral();
+
+ this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
+ . . .
+}
+
+private void Timer_Tick(ThreadPoolTimer timer)
+{
+ . . .
+}
+```
+
+
+## Initialize the GPIO pin
+___
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+```csharp
+using Windows.Devices.Gpio;
+
+private void InitGPIO()
+{
+ var gpio = GpioController.GetDefault();
+
+ if (gpio == null)
+ {
+ pin = null;
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+
+ if (pin == null)
+ {
+ return;
+ }
+
+ pin.Write(GpioPinValue.High);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+}
+```
+
+Let's break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+
+## Modify the state of the GPIO pin
+___
+Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+```csharp
+this.pin.Write(GpioPinValue.Low);
+```
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+```csharp
+this.pin.Write(GpioPinValue.High);
+```
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/HelloBlinkyBackground/CS/Properties/Default.rd.xml b/samples/HelloBlinkyBackground/CS/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/HelloBlinkyBackground/CS/Properties/Default.rd.xml
+++ b/samples/HelloBlinkyBackground/CS/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/HelloBlinkyBackground/CS/README.md b/samples/HelloBlinkyBackground/CS/README.md
index 89d26a698..9bb8353fb 100644
--- a/samples/HelloBlinkyBackground/CS/README.md
+++ b/samples/HelloBlinkyBackground/CS/README.md
@@ -1,126 +1,126 @@
----
-page_type: sample
-urlFragment: hello-blinky-background
-languages:
- - csharp
- - cpp
- - vb
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
----
-
-# "Hello, blinky!" background service
-
-We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
-
-Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
-
-## Load the project in Visual Studio
-___
-
-You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
-
-Note that the app will not run successfully if it cannot find any available GPIO ports.
-
-Once the project is open and builds, the next step is to deploy the application to your device.
-
-When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
-
-## Let's look at the code
-___
-The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
-
-
-## Timer code
-___
-Here is how you set up the timer in C#:
-```csharp
-using Windows.System.Threading;
-
-BackgroundTaskDeferral _deferral;
-public void Run(IBackgroundTaskInstance taskInstance)
-{
- _deferral = taskInstance.GetDeferral();
-
- this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
- . . .
-}
-
-private void Timer_Tick(ThreadPoolTimer timer)
-{
- . . .
-}
-```
-
-
-## Initialize the GPIO pin
-___
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-```csharp
-using Windows.Devices.Gpio;
-
-private void InitGPIO()
-{
- var gpio = GpioController.GetDefault();
-
- if (gpio == null)
- {
- pin = null;
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
-
- if (pin == null)
- {
- return;
- }
-
- pin.Write(GpioPinValue.High);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-}
-```
-
-Let's break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-
-## Modify the state of the GPIO pin
-___
-Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
-```csharp
-this.pin.Write(GpioPinValue.Low);
-```
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
-```csharp
-this.pin.Write(GpioPinValue.High);
-```
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: hello-blinky-background
+languages:
+ - csharp
+ - cpp
+ - vb
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
+---
+
+# "Hello, blinky!" background service
+
+We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
+
+Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
+
+## Load the project in Visual Studio
+___
+
+You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
+
+Note that the app will not run successfully if it cannot find any available GPIO ports.
+
+Once the project is open and builds, the next step is to deploy the application to your device.
+
+When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
+
+## Let's look at the code
+___
+The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
+
+
+## Timer code
+___
+Here is how you set up the timer in C#:
+```csharp
+using Windows.System.Threading;
+
+BackgroundTaskDeferral _deferral;
+public void Run(IBackgroundTaskInstance taskInstance)
+{
+ _deferral = taskInstance.GetDeferral();
+
+ this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
+ . . .
+}
+
+private void Timer_Tick(ThreadPoolTimer timer)
+{
+ . . .
+}
+```
+
+
+## Initialize the GPIO pin
+___
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+```csharp
+using Windows.Devices.Gpio;
+
+private void InitGPIO()
+{
+ var gpio = GpioController.GetDefault();
+
+ if (gpio == null)
+ {
+ pin = null;
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+
+ if (pin == null)
+ {
+ return;
+ }
+
+ pin.Write(GpioPinValue.High);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+}
+```
+
+Let's break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+
+## Modify the state of the GPIO pin
+___
+Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+```csharp
+this.pin.Write(GpioPinValue.Low);
+```
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+```csharp
+this.pin.Write(GpioPinValue.High);
+```
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/HelloBlinkyBackground/README.md b/samples/HelloBlinkyBackground/README.md
index 89d26a698..9bb8353fb 100644
--- a/samples/HelloBlinkyBackground/README.md
+++ b/samples/HelloBlinkyBackground/README.md
@@ -1,126 +1,126 @@
----
-page_type: sample
-urlFragment: hello-blinky-background
-languages:
- - csharp
- - cpp
- - vb
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
----
-
-# "Hello, blinky!" background service
-
-We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
-
-Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
-
-## Load the project in Visual Studio
-___
-
-You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
-
-Note that the app will not run successfully if it cannot find any available GPIO ports.
-
-Once the project is open and builds, the next step is to deploy the application to your device.
-
-When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
-
-## Let's look at the code
-___
-The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
-
-
-## Timer code
-___
-Here is how you set up the timer in C#:
-```csharp
-using Windows.System.Threading;
-
-BackgroundTaskDeferral _deferral;
-public void Run(IBackgroundTaskInstance taskInstance)
-{
- _deferral = taskInstance.GetDeferral();
-
- this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
- . . .
-}
-
-private void Timer_Tick(ThreadPoolTimer timer)
-{
- . . .
-}
-```
-
-
-## Initialize the GPIO pin
-___
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-```csharp
-using Windows.Devices.Gpio;
-
-private void InitGPIO()
-{
- var gpio = GpioController.GetDefault();
-
- if (gpio == null)
- {
- pin = null;
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
-
- if (pin == null)
- {
- return;
- }
-
- pin.Write(GpioPinValue.High);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-}
-```
-
-Let's break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-
-## Modify the state of the GPIO pin
-___
-Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
-```csharp
-this.pin.Write(GpioPinValue.Low);
-```
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
-```csharp
-this.pin.Write(GpioPinValue.High);
-```
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: hello-blinky-background
+languages:
+ - csharp
+ - cpp
+ - vb
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
+---
+
+# "Hello, blinky!" background service
+
+We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
+
+Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
+
+## Load the project in Visual Studio
+___
+
+You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
+
+Note that the app will not run successfully if it cannot find any available GPIO ports.
+
+Once the project is open and builds, the next step is to deploy the application to your device.
+
+When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
+
+## Let's look at the code
+___
+The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
+
+
+## Timer code
+___
+Here is how you set up the timer in C#:
+```csharp
+using Windows.System.Threading;
+
+BackgroundTaskDeferral _deferral;
+public void Run(IBackgroundTaskInstance taskInstance)
+{
+ _deferral = taskInstance.GetDeferral();
+
+ this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
+ . . .
+}
+
+private void Timer_Tick(ThreadPoolTimer timer)
+{
+ . . .
+}
+```
+
+
+## Initialize the GPIO pin
+___
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+```csharp
+using Windows.Devices.Gpio;
+
+private void InitGPIO()
+{
+ var gpio = GpioController.GetDefault();
+
+ if (gpio == null)
+ {
+ pin = null;
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+
+ if (pin == null)
+ {
+ return;
+ }
+
+ pin.Write(GpioPinValue.High);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+}
+```
+
+Let's break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+
+## Modify the state of the GPIO pin
+___
+Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+```csharp
+this.pin.Write(GpioPinValue.Low);
+```
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+```csharp
+this.pin.Write(GpioPinValue.High);
+```
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/HelloBlinkyBackground/VB/BlinkyHeadlessVB.vbproj b/samples/HelloBlinkyBackground/VB/BlinkyHeadlessVB.vbproj
index d465c2bfd..781cb1cf0 100644
--- a/samples/HelloBlinkyBackground/VB/BlinkyHeadlessVB.vbproj
+++ b/samples/HelloBlinkyBackground/VB/BlinkyHeadlessVB.vbproj
@@ -1,181 +1,181 @@
-
-
-
-
- Debug
- x86
- {E0F96575-9BCD-4EE8-99C1-6EEAD278E610}
- winmdobj
- BlinkyHeadlessVB
- BlinkyHeadlessVB
- en-US
- UAP
- 10.0.19041.0
- 10.0.15063.0
- 14
- true
- 512
- {A5A43C5B-DE2A-4C0C-9213-0A381AF9435A};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}
- false
- BlinkyHeadlessVB_TemporaryKey.pfx
- true
- true
- win10-arm;win10-arm-aot;win10-x86;win10-x86-aot;win10-x64;win10-x64-aot
-
-
- true
- true
- true
- bin\ARM\Debug\
- NETFX_CORE,WINDOWS_UWP
- full
- ARM
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
-
-
- true
- bin\ARM\Release\
- NETFX_CORE,WINDOWS_UWP
- true
- pdbonly
- ARM
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
- true
-
-
- true
- true
- true
- bin\x64\Debug\
- NETFX_CORE,WINDOWS_UWP
- full
- x64
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
-
-
- true
- bin\x64\Release\
- NETFX_CORE,WINDOWS_UWP
- true
- pdbonly
- x64
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
- true
-
-
- true
- true
- true
- bin\x86\Debug\
- NETFX_CORE,WINDOWS_UWP
- full
- x86
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
-
-
- true
- bin\x86\Release\
- NETFX_CORE,WINDOWS_UWP
- true
- pdbonly
- x86
- false
- true
- BlinkyHeadlessVB.xml
- 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
- true
-
-
-
-
-
-
-
- Designer
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 5.0.0
-
-
-
- 14.0
-
-
- On
-
-
- Binary
-
-
- Off
-
-
- On
-
-
-
-
+
+
+
+
+ Debug
+ x86
+ {E0F96575-9BCD-4EE8-99C1-6EEAD278E610}
+ winmdobj
+ BlinkyHeadlessVB
+ BlinkyHeadlessVB
+ en-US
+ UAP
+ 10.0.19041.0
+ 10.0.15063.0
+ 14
+ true
+ 512
+ {A5A43C5B-DE2A-4C0C-9213-0A381AF9435A};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}
+ false
+ BlinkyHeadlessVB_TemporaryKey.pfx
+ true
+ true
+ win10-arm;win10-arm-aot;win10-x86;win10-x86-aot;win10-x64;win10-x64-aot
+
+
+ true
+ true
+ true
+ bin\ARM\Debug\
+ NETFX_CORE,WINDOWS_UWP
+ full
+ ARM
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+
+
+ true
+ bin\ARM\Release\
+ NETFX_CORE,WINDOWS_UWP
+ true
+ pdbonly
+ ARM
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+ true
+
+
+ true
+ true
+ true
+ bin\x64\Debug\
+ NETFX_CORE,WINDOWS_UWP
+ full
+ x64
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+
+
+ true
+ bin\x64\Release\
+ NETFX_CORE,WINDOWS_UWP
+ true
+ pdbonly
+ x64
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+ true
+
+
+ true
+ true
+ true
+ bin\x86\Debug\
+ NETFX_CORE,WINDOWS_UWP
+ full
+ x86
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+
+
+ true
+ bin\x86\Release\
+ NETFX_CORE,WINDOWS_UWP
+ true
+ pdbonly
+ x86
+ false
+ true
+ BlinkyHeadlessVB.xml
+ 41999,42016,42017,42018,42019,42020,42021,42022,42032,42036,42314
+ true
+
+
+
+
+
+
+
+ Designer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 5.0.0
+
+
+
+ 14.0
+
+
+ On
+
+
+ Binary
+
+
+ Off
+
+
+ On
+
+
+
+
diff --git a/samples/HelloBlinkyBackground/VB/My Project/AssemblyInfo.vb b/samples/HelloBlinkyBackground/VB/My Project/AssemblyInfo.vb
index 9f6c2278e..2015fa464 100644
--- a/samples/HelloBlinkyBackground/VB/My Project/AssemblyInfo.vb
+++ b/samples/HelloBlinkyBackground/VB/My Project/AssemblyInfo.vb
@@ -1,31 +1,31 @@
-Imports System
-Imports System.Reflection
-Imports System.Runtime.InteropServices
-
-' General Information about an assembly is controlled through the following
-' set of attributes. Change these attribute values to modify the information
-' associated with an assembly.
-
-' Review the values of the assembly attributes
-
-
-
-
-
-
-
-
-' Version information for an assembly consists of the following four values:
-'
-' Major Version
-' Minor Version
-' Build Number
-' Revision
-'
-' You can specify all the values or you can default the Build and Revision Numbers
-' by using the '*' as shown below:
-'
-
-
-
+Imports System
+Imports System.Reflection
+Imports System.Runtime.InteropServices
+
+' General Information about an assembly is controlled through the following
+' set of attributes. Change these attribute values to modify the information
+' associated with an assembly.
+
+' Review the values of the assembly attributes
+
+
+
+
+
+
+
+
+' Version information for an assembly consists of the following four values:
+'
+' Major Version
+' Minor Version
+' Build Number
+' Revision
+'
+' You can specify all the values or you can default the Build and Revision Numbers
+' by using the '*' as shown below:
+'
+
+
+
\ No newline at end of file
diff --git a/samples/HelloBlinkyBackground/VB/My Project/Default.rd.xml b/samples/HelloBlinkyBackground/VB/My Project/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/HelloBlinkyBackground/VB/My Project/Default.rd.xml
+++ b/samples/HelloBlinkyBackground/VB/My Project/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/HelloBlinkyBackground/VB/README.md b/samples/HelloBlinkyBackground/VB/README.md
index 89d26a698..9bb8353fb 100644
--- a/samples/HelloBlinkyBackground/VB/README.md
+++ b/samples/HelloBlinkyBackground/VB/README.md
@@ -1,126 +1,126 @@
----
-page_type: sample
-urlFragment: hello-blinky-background
-languages:
- - csharp
- - cpp
- - vb
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
----
-
-# "Hello, blinky!" background service
-
-We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
-
-Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
-
-## Load the project in Visual Studio
-___
-
-You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
-
-Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
-
-Note that the app will not run successfully if it cannot find any available GPIO ports.
-
-Once the project is open and builds, the next step is to deploy the application to your device.
-
-When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
-
-## Let's look at the code
-___
-The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
-
-
-## Timer code
-___
-Here is how you set up the timer in C#:
-```csharp
-using Windows.System.Threading;
-
-BackgroundTaskDeferral _deferral;
-public void Run(IBackgroundTaskInstance taskInstance)
-{
- _deferral = taskInstance.GetDeferral();
-
- this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
- . . .
-}
-
-private void Timer_Tick(ThreadPoolTimer timer)
-{
- . . .
-}
-```
-
-
-## Initialize the GPIO pin
-___
-To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
-
-```csharp
-using Windows.Devices.Gpio;
-
-private void InitGPIO()
-{
- var gpio = GpioController.GetDefault();
-
- if (gpio == null)
- {
- pin = null;
- return;
- }
-
- pin = gpio.OpenPin(LED_PIN);
-
- if (pin == null)
- {
- return;
- }
-
- pin.Write(GpioPinValue.High);
- pin.SetDriveMode(GpioPinDriveMode.Output);
-}
-```
-
-Let's break this down a little:
-
-* First, we use `GpioController.GetDefault()` to get the GPIO controller.
-
-* If the device does not have a GPIO controller, this function will return `null`.
-
-* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
-
-* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
-
-* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
-
-
-## Modify the state of the GPIO pin
-___
-Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
-
-To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
-
-```csharp
-this.pin.Write(GpioPinValue.Low);
-```
-
-and of course, write `GpioPinValue.High` to turn the LED off:
-
-```csharp
-this.pin.Write(GpioPinValue.High);
-```
-
-Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
-
-## Additional Notes
-
-Make sure that LowLevel Capabilities in set in PackageAppManifest.
-* To do that go to Package.appxmanifesto and view the code
-* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
-* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
+---
+page_type: sample
+urlFragment: hello-blinky-background
+languages:
+ - csharp
+ - cpp
+ - vb
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to make an LED attached to a GPIO pin blink on and off from a background service for Windows 10 IoT Enterprise.
+---
+
+# "Hello, blinky!" background service
+
+We'll create a simple Blinky app and connect a LED to your Windows IoT Enterprise device (UP Board).
+
+Be aware that the GPIO APIs are only available on the board, so this sample cannot run on your desktop.
+
+## Load the project in Visual Studio
+___
+
+You can find the source code for this sample by downloading a zip of all of our samples and navigating to the `samples\HelloBlinkyBackground`. The sample code is available in either C++ or C#, however the documentation here only details the C# variant. Make a copy of the folder on your disk and open the project from Visual Studio 2019.
+
+Make sure you connect the LED to your board. Go back to the basic 'Blinky' if you need guidance.
+
+Note that the app will not run successfully if it cannot find any available GPIO ports.
+
+Once the project is open and builds, the next step is to deploy the application to your device.
+
+When everything is set up, you should be able to press *F5* from Visual Studio. The Blinky app will deploy and start on the Windows IoT device.
+
+## Let's look at the code
+___
+The code for this sample is pretty simple. We use a timer, and each time the 'Tick' event is called, we flip the state of the LED.
+
+
+## Timer code
+___
+Here is how you set up the timer in C#:
+```csharp
+using Windows.System.Threading;
+
+BackgroundTaskDeferral _deferral;
+public void Run(IBackgroundTaskInstance taskInstance)
+{
+ _deferral = taskInstance.GetDeferral();
+
+ this.timer = ThreadPoolTimer.CreatePeriodicTimer(Timer_Tick, TimeSpan.FromMilliseconds(500));
+ . . .
+}
+
+private void Timer_Tick(ThreadPoolTimer timer)
+{
+ . . .
+}
+```
+
+
+## Initialize the GPIO pin
+___
+To drive the GPIO pin, first we need to initialize it. Here is the C# code (notice how we leverage the new WinRT classes in the Windows.Devices.Gpio namespace):
+
+```csharp
+using Windows.Devices.Gpio;
+
+private void InitGPIO()
+{
+ var gpio = GpioController.GetDefault();
+
+ if (gpio == null)
+ {
+ pin = null;
+ return;
+ }
+
+ pin = gpio.OpenPin(LED_PIN);
+
+ if (pin == null)
+ {
+ return;
+ }
+
+ pin.Write(GpioPinValue.High);
+ pin.SetDriveMode(GpioPinDriveMode.Output);
+}
+```
+
+Let's break this down a little:
+
+* First, we use `GpioController.GetDefault()` to get the GPIO controller.
+
+* If the device does not have a GPIO controller, this function will return `null`.
+
+* Then we attempt to open the pin by calling `GpioController.OpenPin()` with the `LED_PIN` value.
+
+* Once we have the `pin`, we set it to be off (HIGH) by default using the `GpioPin.Write()` function.
+
+* We also set the `pin` to run in output mode using the `GpioPin.SetDriveMode()` function.
+
+
+## Modify the state of the GPIO pin
+___
+Once we have access to the `GpioOutputPin` instance, it's trivial to change the state of the pin to turn the LED on or off. You can modify 'Timer_Tick' to do this.
+
+To turn the LED on, simply write the value `GpioPinValue.Low` to the pin:
+
+```csharp
+this.pin.Write(GpioPinValue.Low);
+```
+
+and of course, write `GpioPinValue.High` to turn the LED off:
+
+```csharp
+this.pin.Write(GpioPinValue.High);
+```
+
+Remember that we connected the other end of the LED to the 3.3 Volts power supply, so we need to drive the pin to low to have current flow into the LED.
+
+## Additional Notes
+
+Make sure that LowLevel Capabilities in set in PackageAppManifest.
+* To do that go to Package.appxmanifesto and view the code
+* Under Capabilities if you can find "DeviceCapability Name="lowLevel"/" then your lowLevel Capabilities is enabled.
+* If this line "DeviceCapability Name="lowLevel"/" is not present then add it to enable the LowLevel mode and save the PackageAppManifest.
diff --git a/samples/HelloBlinkyBackground/VB/StartupTask.vb b/samples/HelloBlinkyBackground/VB/StartupTask.vb
index 28cd92fbf..713f35b0f 100644
--- a/samples/HelloBlinkyBackground/VB/StartupTask.vb
+++ b/samples/HelloBlinkyBackground/VB/StartupTask.vb
@@ -1,60 +1,60 @@
-' Copyright (c) Microsoft. All rights reserved.
-
-Imports System
-Imports System.Collections.Generic
-Imports System.Linq
-Imports System.Text
-Imports System.Net.Http
-Imports Windows.ApplicationModel.Background
-Imports Windows.Devices.Gpio
-
-' The Background Application template is documented at http://go.microsoft.com/fwlink/?LinkID=533884&clcid=0x409
-
-Public NotInheritable Class StartupTask
- Implements IBackgroundTask
-
- Dim pin As GpioPin
- Dim deferral As BackgroundTaskDeferral
- Dim timer As Windows.System.Threading.ThreadPoolTimer
- 'Dim lightOn As Boolean
- Dim value As GpioPinValue = GpioPinValue.High
-
- Dim _cancelReason = BackgroundTaskCancellationReason.Abort
- Dim _cancelRequested As Boolean = False
-
- Public Sub Run(taskInstance As IBackgroundTaskInstance) Implements IBackgroundTask.Run
-
- Debug.WriteLine("Background " + taskInstance.Task.Name + " Starting...")
- AddHandler taskInstance.Canceled, AddressOf OnCanceled
-
- deferral = taskInstance.GetDeferral()
- pin = GpioController.GetDefault().OpenPin(5)
- pin.SetDriveMode(GpioPinDriveMode.Output)
- ' lightOn = False
- Windows.System.Threading.ThreadPoolTimer.CreatePeriodicTimer(AddressOf Tick, TimeSpan.FromMilliseconds(500))
-
- End Sub
-
- Public Sub Tick(timer As Windows.System.Threading.ThreadPoolTimer)
-
- If (_cancelRequested = False) Then
- value = If(value = GpioPinValue.High, GpioPinValue.Low, GpioPinValue.High)
- pin.Write(value)
- Else
- timer.Cancel()
- ' Indicate that the background task has completed.
- deferral.Complete()
- End If
-
- End Sub
-
- Private Sub OnCanceled(sender As IBackgroundTaskInstance, reason As BackgroundTaskCancellationReason)
-
- _cancelRequested = True
- _cancelReason = reason
-
- Debug.WriteLine("Background " + sender.Task.Name + " Cancel Requested...")
- End Sub
-
-
-End Class
+' Copyright (c) Microsoft. All rights reserved.
+
+Imports System
+Imports System.Collections.Generic
+Imports System.Linq
+Imports System.Text
+Imports System.Net.Http
+Imports Windows.ApplicationModel.Background
+Imports Windows.Devices.Gpio
+
+' The Background Application template is documented at http://go.microsoft.com/fwlink/?LinkID=533884&clcid=0x409
+
+Public NotInheritable Class StartupTask
+ Implements IBackgroundTask
+
+ Dim pin As GpioPin
+ Dim deferral As BackgroundTaskDeferral
+ Dim timer As Windows.System.Threading.ThreadPoolTimer
+ 'Dim lightOn As Boolean
+ Dim value As GpioPinValue = GpioPinValue.High
+
+ Dim _cancelReason = BackgroundTaskCancellationReason.Abort
+ Dim _cancelRequested As Boolean = False
+
+ Public Sub Run(taskInstance As IBackgroundTaskInstance) Implements IBackgroundTask.Run
+
+ Debug.WriteLine("Background " + taskInstance.Task.Name + " Starting...")
+ AddHandler taskInstance.Canceled, AddressOf OnCanceled
+
+ deferral = taskInstance.GetDeferral()
+ pin = GpioController.GetDefault().OpenPin(5)
+ pin.SetDriveMode(GpioPinDriveMode.Output)
+ ' lightOn = False
+ Windows.System.Threading.ThreadPoolTimer.CreatePeriodicTimer(AddressOf Tick, TimeSpan.FromMilliseconds(500))
+
+ End Sub
+
+ Public Sub Tick(timer As Windows.System.Threading.ThreadPoolTimer)
+
+ If (_cancelRequested = False) Then
+ value = If(value = GpioPinValue.High, GpioPinValue.Low, GpioPinValue.High)
+ pin.Write(value)
+ Else
+ timer.Cancel()
+ ' Indicate that the background task has completed.
+ deferral.Complete()
+ End If
+
+ End Sub
+
+ Private Sub OnCanceled(sender As IBackgroundTaskInstance, reason As BackgroundTaskCancellationReason)
+
+ _cancelRequested = True
+ _cancelReason = reason
+
+ Debug.WriteLine("Background " + sender.Task.Name + " Cancel Requested...")
+ End Sub
+
+
+End Class
diff --git a/samples/I2CCompass/CS/Properties/Default.rd.xml b/samples/I2CCompass/CS/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/I2CCompass/CS/Properties/Default.rd.xml
+++ b/samples/I2CCompass/CS/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/I2CCompass/README.md b/samples/I2CCompass/README.md
index 9df66d101..9dae9f532 100644
--- a/samples/I2CCompass/README.md
+++ b/samples/I2CCompass/README.md
@@ -1,59 +1,59 @@
----
-page_type: sample
-urlFragment: I2CCompass
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample uses I2C on Windows 10 IoT Enterprise to communicate with an HMC5883L Magnetometer device.
----
-
-# I2C Compass
-
-This sample uses I2C on Windows IoT Enterprise to communicate with an HMC5883L Magnetometer device.
-
-## Step 1: Set up your hardware
-Please reference the datasheet for the HMC5883L found [here](https://github.com/microsoft/Windows-iotcore-samples/blob/develop/Samples/I2CCompass/HMC5883L_3-Axis_Digital_Compass_IC.pdf).
-
-For more information on compass heading using magnetometers please see [here](https://github.com/microsoft/Windows-iotcore-samples/blob/develop/Samples/I2CCompass/AN203_Compass_Heading_Using_Magnetometers.pdf).
-
-## Step 2: Load the project in Visual Studio
-You can find the source code for this sample by downloading a zip of all of our samples. Extract the zip to your disk, then open the `Samples\I2CCompass\CS\I2CCompass.sln` project from Visual Studio.
-
-## Step 3: Deploy the sample
-
-* Choose `Release` and `x64` configuration.
-* Compile the Solution file
-
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-### BIOS Settings for UP Board
-If you are using an UP Board, you have to setup the BIOS SPI configuration.
-
-1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
-1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
-1. Navigate to the **Advance** tab and select the **Hat Configuration** and set **I2C0/GPIO SELECTION** as **I2C0**.
-
-1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-1. Click the Start button to search for the app by name, and then launch it.
-
-
-## Additional information
-The HMC3883L device is accessed through the [Windows.Devices.I2c API](https://docs.microsoft.com/en-us/uwp/api/windows.devices.i2c) using the default I2C controller and the address 0x1E.
-```CS
- // Setup the settings to address 0x1E with a 400KHz bus speed
- var i2cSettings = new I2cConnectionSettings(ADDRESS);
- i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
-
- // Create an I2cDevice with our selected bus controller ID and I2C settings
- var controller = await I2cController.GetDefaultAsync();
- _i2cController = controller.GetDevice(i2cSettings);
-```
+---
+page_type: sample
+urlFragment: I2CCompass
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample uses I2C on Windows 10 IoT Enterprise to communicate with an HMC5883L Magnetometer device.
+---
+
+# I2C Compass
+
+This sample uses I2C on Windows IoT Enterprise to communicate with an HMC5883L Magnetometer device.
+
+## Step 1: Set up your hardware
+Please reference the datasheet for the HMC5883L found [here](https://github.com/microsoft/Windows-iotcore-samples/blob/develop/Samples/I2CCompass/HMC5883L_3-Axis_Digital_Compass_IC.pdf).
+
+For more information on compass heading using magnetometers please see [here](https://github.com/microsoft/Windows-iotcore-samples/blob/develop/Samples/I2CCompass/AN203_Compass_Heading_Using_Magnetometers.pdf).
+
+## Step 2: Load the project in Visual Studio
+You can find the source code for this sample by downloading a zip of all of our samples. Extract the zip to your disk, then open the `Samples\I2CCompass\CS\I2CCompass.sln` project from Visual Studio.
+
+## Step 3: Deploy the sample
+
+* Choose `Release` and `x64` configuration.
+* Compile the Solution file
+
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+### BIOS Settings for UP Board
+If you are using an UP Board, you have to setup the BIOS SPI configuration.
+
+1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+1. Navigate to the **Advance** tab and select the **Hat Configuration** and set **I2C0/GPIO SELECTION** as **I2C0**.
+
+1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+1. Click the Start button to search for the app by name, and then launch it.
+
+
+## Additional information
+The HMC3883L device is accessed through the [Windows.Devices.I2c API](https://docs.microsoft.com/en-us/uwp/api/windows.devices.i2c) using the default I2C controller and the address 0x1E.
+```CS
+ // Setup the settings to address 0x1E with a 400KHz bus speed
+ var i2cSettings = new I2cConnectionSettings(ADDRESS);
+ i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
+
+ // Create an I2cDevice with our selected bus controller ID and I2C settings
+ var controller = await I2cController.GetDefaultAsync();
+ _i2cController = controller.GetDevice(i2cSettings);
+```
diff --git a/samples/I2CPortExpander/CS/README.md b/samples/I2CPortExpander/CS/README.md
index 9f4ee8bb3..0fa45686b 100644
--- a/samples/I2CPortExpander/CS/README.md
+++ b/samples/I2CPortExpander/CS/README.md
@@ -1,599 +1,599 @@
----
-page_type: sample
-urlFragment: I2CPortExpander
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to use a port expander to read the status of a tactile switch and control an LED for Windows 10 IoT Enterprise.
----
-
-# I2C port expander
-
-In this sample, we'll connect an I2C port expander to your Windows 10 IoT Enterprise device and create a simple app that uses the port expander to read the status of a tactile switch and control an LED.
-
-No background knowledge of I2C or port expanders is needed. If you want to know more about I2C, SparkFun provides a great [tutorial on I2C](https://learn.sparkfun.com/tutorials/i2c).
-
-## Step 1: Connect the I2C Port Expander to your device
-
-You will need the following components:
-
-* 1 Windows 10 IoT Enterprise Compatible Board (This example uses an [UP Board](https://up-board.org/up/specifications/))
-
-* 1 [MCP23008 8-bit I/O Port Expander](http://www.digikey.com/product-detail/en/MCP23008-E%2FP/MCP23008-E%2FP-ND/735951) in PDIP package
-
-* 1 [red LED](http://www.digikey.com/product-detail/en/C5SMF-RJS-CT0W0BB1/C5SMF-RJS-CT0W0BB1-ND/2341832)
-
-* 1 [tactile switch](http://www.digikey.com/product-detail/en/320.02E11.08BLK/EG1311-ND/101397)
-
-* 1 [330 Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-330R/330QBK-ND/1636)
-
-* 1 [10k Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-10K/10KQBK-ND/338)
-
-* An HDMI monitor
-
-* A breadboard and several male-to-female and male-to-male connector wires
-
-Let's start by wiring up the components on the breadboard as shown in the diagram below.
-
-**Note: Make sure to power off the UP Board when connecting your circuit. This is good practice to reduce the chance of an accidental short circuit during construction.**
-
-
-
-
-Here is the schematic:
-
-
-
-
-## Step 2: Connecting the MCP23008 Port Expander
-
-Place the MCP23008 Port Expander on your breadboard such that it straddles the center gap of the breadboard.
-
-
-
- Locate pin 1 of the port expander by finding the notch on the IC. If you orient the IC so that the end with the notch is facing left, pin 1 will be the first pin in the lower left below the notch.
-
-
-
-The pinout of the MCP23008 is shown below and can be found in the [datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf).
-
-
-
-
-Make the following connections on the MCP23008 Port Expander:
-
-* Pin 1 **SCL**: Connect to **I2C1 SCL** (Pin 28) on the UP Board (pin mapping is below)
-
-* Pin 2 **SDA**: Connect to **I2C1 SDA** (Pin 27) on the UP Board
-
-* Pin 3 **A2**: Connect to the ground rail on the side of the breadboard (blue stripe)
-
-* Pin 4 **A1**: Connect to the ground rail on the side of the breadboard
-
-* Pin 5 **A0**: Connect to the ground rail on the side of the breadboard
-
-* Pin 6 **Reset**: Connect to the voltage supply rail on the side of the breadboard (red stripe)
-
-* Pin 9 **VSS**: Connect to the ground rail on the side of the breadboard
-
-* Pin 10 **GP0**: Connect to the cathode (the shorter leg) of the LED
-
-* Pin 11 **GP1**: Connect to one lead of the 10k Ω resistor and one pin of the tactile switch
-
-* Pin 18 **VDD**: Connect to the voltage supply rail on the side of the breadboard
-
-Leave the remaining pins on the MCP23008 unconnected.
-
-
-## Step 3: Connecting the LED
-
-* If not already connected, connect the cathode (the shorter leg) of the LED to Pin 10 of the MCP23008 Port Expander
-
-* Connect the anode (the longer leg) of the LED to one lead of the 330 Ω resistor
-
-* Connect the other end of the 330 Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
-
-
-## Step 4: Connecting the Tactile Switch
-
-* If not already connected, connect one lead of the 10k Ω resistor to Pin 11 of the MCP23008 Port Expander
-
-* Connect the other end of the 10k Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
-
-* If not already connected, connect one pin of the tactile switch to Pin 11 of the MCP23008 Port Expander
-
-* Connect the other pin of the tactile switch to the ground rail on the side of the breadboard (blue stripe)
-
-
-## Step 5: Connecting the UP Board
-
-We need to hook up power, ground, and the I2C lines from on the UP Board to the MCP23008 Port Expander and the breadboard.
-
-
-
-* Pin 1 **3.3V PWR** Connect to the voltage supply rail on the side of the breadboard (red stripe)
-
-* Pin 27 **I2C0 SDA** If not already connected, connect to Pin 2 of the MCP23008 Port Expander
-
-* Pin 28 **I2C0 SCL** If not already connected, connect to pin 1 of the MCP23008 Port Expander
-
-* Pin 6 **GND** Connect to the ground rail on the side of the breadboard (blue stripe)
-
-The I2C bus requires pull-up resistors on the SDA and SCL lines. However, the UP Board SDA and SCL pins we are using in this sample already have pull-up resistors connected on the UP Board, so we don't need to add any additional external pull-ups.
-
-## Step 6: Create the sample app
-
-When everything is set up, power your device back on. You can find the source code for this sample by downloading a zip of all of our samples, navigate to the `samples-develop\I2CPortExpander`,
-but as an exercise, this tutorial will take you through the complete steps to create this app from scratch.
-Open up Visual Studio 2019.
-For this sample, we named **I2cPortExpanderLedSample**.
-
-## Step 7: Compile the sample
-
-* Choose `Release` and `x64` configuration.
-* Compile the Solution file
-
-## Step 8: Generate an app package
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-1. If you are using an UP Board, you have to setup the BIOS SPI configuration.
-
- 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
- 1. Navigate to the **Advance** tab and select the **Hat Configuration** and change "I2C0/GPIO SELECTION" to "I2C0".
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-The code in this sample does several things:
-
-1. Initializes the I2C bus and the port expander
-
-2. Communicates over I2C with the port expander to turn the LED on and off at regular intervals
-
-3. Communicates over I2C with the port expander to check the status of the tactile switch (is it pressed or not) at regular intervals
-
-4. Displays the LED on/off status and the tactile switch pressed/released status to the display attached to the UP Board
-
-5. Stops flashing the LED when the tactile switch is pressed and restarts flashing the LED when the tactile switch is released
-
-6. Checks if the user has changed the LED flash frequency and updates the LED flash frequency as needed
-
-#### Add content to MainPage.xaml
-
-Let's add some content to the MainPage which will be displayed on a screen connected to the UP Board. We want to add a circle, a couple text boxes and a slider. The circle will emulate the on/off status of the LED. The Slider allows the user to control the frequency that the LED flashes. The Textboxes will provide info about the slider and report the tactile button status.
-
-* From Solution Explorer, select the MainPage.xaml file.
-
-* Locate the `` tag in the XAML section of the designer, and add the following markup:
-
-```csharp
-
-
-
-
-
-
-
-
-```
-#### Add code to MainPage.xaml.cs
-Before we add any code to MainPage.xaml.cs, we need to add a reference to the Windows IoT Extension SDK.
- * In Solution Explorer, right-click on **References** and select **Add Reference...**
- * In the Reference Manager window, click the arrow next to **Windows Universal** then click on **Extensions**
- * Place a check mark in the box next to **Windows IoT Extension SDK** and click **OK**
- * Open MainPage.xaml.cs from Solution Explorer (you may need to click on the arrow next to MainPage.xaml first)
- * Add the following lines at the top of MainPage.xaml.cs
-```csharp
-using Windows.Devices.Enumeration;
-using Windows.Devices.I2c;
-```
-
-
-With the references added, let's start adding code. The complete code we implemented for MainPage.xaml.cs is located at end of this section. Below are some key parts of the code with explanations
-
-
-Variables and Constants
-
-```csharp
-// use these constants for controlling how the I2C bus is setup
-
-private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
-private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
-private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
-private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
-private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
-private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
-private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
-private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
-private byte iodirRegister; // local copy of I2C Port Expander IODIR register
-private byte gpioRegister; // local copy of I2C Port Expander GPIO register
-private byte olatRegister; // local copy of I2C Port Expander OLAT register
-private I2cDevice i2cPortExpander;
-private DispatcherTimer ledTimer;
-private DispatcherTimer buttonStatusCheckTimer;
-private bool isLedOn = false;
-private bool isButtonPressed = false;
-private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
-private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
-```
-
-Here are what some of these constants and variables represent
-
- * `I2C_CONTROLLER_NAME` holds the string constant `I2C0` which is the name of the I2C controller on the UP Board.
-
- * `PORT_EXPANDER_I2C_ADDRESS` is the I2C address of the port expander we are using. \*
-
- * `PORT_EXPANDER_IODIR_REGISTER_ADDRESS`, `PORT_EXPANDER_GPIO_REGISTER_ADDRESS`, `PORT_EXPANDER_OLAT_REGISTER_ADDRESS` are the register addresses in the port expander that correspond to the IODIR register, GPIO register and OLAT register.\*
-
- * `TIMER_INTERVAL` is the starting time interval in milliseconds between an LED on or off toggle.
-
- * `BUTTON_STATUS_CHECK_TIMER_INTERVAL` is the time interval in milliseconds between each check of the tactile switch status
-
- * `iodirRegister`, `gpioRegister` and `olatRegister` are our local copies of the values in the corresponding registers in the port expander.
-
-\* See the [MCP23008 datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf)for details.
-
-The method `InitializeSystem()`
-
-`InitializeSystem()` does the following:
-
- * Sets up the I2C communications on the UP Board
-
- * Configures the port expander to be able to turn the LED on and off and to get the tactile switch status
-
- * Initializes the local copies of the port expander registers IODIR, GPIO and OLAT
-
- * Sets up two timers - One for controlling the LED and another for checking the tactile switch status
-
-When complete, the variable `i2cPortExpander` will be our handle to the UP Board I2C bus.
-
-```csharp
-private async void InitializeSystem()
-{
- byte[] i2CWriteBuffer;
- byte[] i2CReadBuffer;
- byte bitMask;
- // initialize I2C communications
- try
- {
- var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
- string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
- var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
- i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // initialize I2C Port Expander registers
- try
- {
- // initialize local copies of the IODIR, GPIO, and OLAT registers
- i2CReadBuffer = new byte[1];
- // read in each register value on register at a time (could do this all at once but
- // for example clarity purposes we do it this way)
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
- iodirRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
- gpioRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
- olatRegister = i2CReadBuffer[0];
- // configure the LED pin output to be logic high, leave the other pins as they are.
- olatRegister |= LED_GPIO_PIN;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- // configure only the LED pin to be an output and leave the other pins as they are.
- // input is logic low, output is logic high
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
- iodirRegister &= bitMask;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // setup our timers, one for the LED blink interval, the other for checking button status
- try
- {
- ledTimer = new DispatcherTimer();
- ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
- ledTimer.Tick += LedTimer_Tick;
- ledTimer.Start();
- buttonStatusCheckTimer = new DispatcherTimer();
- buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
- buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
- buttonStatusCheckTimer.Start();
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
-}
-```
-
-The method `FlipLED()`
-
-`FlipLED()` is called by the ledTimer whenever the LED timer has reached the end of its interval length. Initially, this is 500 milliseconds but can be changed by a user via the slider displayed on a monitor connected to the UP Board.
-
- This method determines if the LED is currently on or off.
-
- * If the LED is currently off, it sends commands to the port expander to turn the LED on and sets the color of the circle on the display to red.
-
- * If the LED is currently on, it sends commands to the port expander to turn the LED off and sets the color of the circle on the display to gray.
-
-```csharp
-private void FlipLED()
-{
- byte bitMask;
- if (isLedOn == true)
- {
- // turn off the LED
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- else
- {
- // turn on the LED
- isLedOn = true;
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
- olatRegister &= bitMask;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = redBrush;
- }
-}
-```
-
-`CheckButtonStatus()` communicates with the port expander to get the tactile switch status. It reads the GPIO register on the port expander and checks the value of the second bit which corresponds to the status of the switch.
-
- * If the second bit of the GPIO register is '0' then the switch is currently pressed.
-
- * If the second bit of the GPIO register is '1' then the switch is currently released.
-
-This method updates the text in Textbox displayed to the screen to reflect the status of the switch.
-
-```csharp
-private void CheckButtonStatus()
-{
- byte[] readBuffer = new byte[1];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
- // a button press results in a logic low for the GPIO pin
- if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
- {
- ButtonStatusText.Text = "Button Status: Pressed";
- isButtonPressed = true;
- }
- else
- {
- ButtonStatusText.Text = "Button Status: Released";
- isButtonPressed = false;
- }
-}
-```
-
-## Step 9: Deploy and Run the App
-
-Let's build, deploy and run the app on our UP Board.
-
-* If not already open, open in Visual Studio the app you created with the code above.
-
-After several moments, you will see the screen attached to the UP Board change to show a circle, some text, and a slider. The LED on the breadboard will begin to turn on and off.
-
-Congratulations! You've successfully connected an I2C port expander to your device.
-
-### The complete MainPage.xaml.cs code
-
-```csharp
-using System;
-//using System.Diagnostics;
-using System.Collections.Generic;
-using System.IO;
-using System.Linq;
-using System.Runtime.InteropServices.WindowsRuntime;
-using Windows.Foundation;
-using Windows.Foundation.Collections;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
-using Windows.UI.Xaml.Controls.Primitives;
-using Windows.UI.Xaml.Data;
-using Windows.UI.Xaml.Input;
-using Windows.UI.Xaml.Media;
-using Windows.UI.Xaml.Navigation;
-using Windows.Devices.Enumeration;
-using Windows.Devices.I2c;
-// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=402352&clcid=0x409
-namespace I2cPortExpanderLedSample
-{
- ///
- /// An empty page that can be used on its own or navigated to within a Frame.
- ///
- public sealed partial class MainPage : Page
- {
- // use these constants for controlling how the I2C bus is setup
- private const string I2C_CONTROLLER_NAME = "I2C0"; //specific to UP Board
- private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
- private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
- private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
- private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
- private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
- private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
- private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
- private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
- private byte iodirRegister; // local copy of I2C Port Expander IODIR register
- private byte gpioRegister; // local copy of I2C Port Expander GPIO register
- private byte olatRegister; // local copy of I2C Port Expander OLAT register
- private I2cDevice i2cPortExpander;
- private DispatcherTimer ledTimer;
- private DispatcherTimer buttonStatusCheckTimer;
- private bool isLedOn = false;
- private bool isButtonPressed = false;
- private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
- private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
- public MainPage()
- {
- this.InitializeComponent();
- // Register for the unloaded event so we can clean up upon exit
- Unloaded += MainPage_Unloaded;
- InitializeSystem();
- }
- private async void InitializeSystem()
- {
- byte[] i2CWriteBuffer;
- byte[] i2CReadBuffer;
- byte bitMask;
- // initialize I2C communications
- try
- {
- var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
- i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
- string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
- var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
- i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // initialize I2C Port Expander registers
- try
- {
- // initialize local copies of the IODIR, GPIO, and OLAT registers
- i2CReadBuffer = new byte[1];
- // read in each register value on register at a time (could do this all at once but
- // for example clarity purposes we do it this way)
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
- iodirRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
- gpioRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
- olatRegister = i2CReadBuffer[0];
- // configure the LED pin output to be logic high, leave the other pins as they are.
- olatRegister |= LED_GPIO_PIN;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- // configure only the LED pin to be an output and leave the other pins as they are.
- // input is logic low, output is logic high
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
- iodirRegister &= bitMask;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // setup our timers, one for the LED blink interval, the other for checking button status
- try
- {
- ledTimer = new DispatcherTimer();
- ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
- ledTimer.Tick += LedTimer_Tick;
- ledTimer.Start();
- buttonStatusCheckTimer = new DispatcherTimer();
- buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
- buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
- buttonStatusCheckTimer.Start();
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- }
- private void MainPage_Unloaded(object sender, object args)
- {
- /* Cleanup */
- i2cPortExpander.Dispose();
- }
- private void FlipLED()
- {
- byte bitMask;
- if (isLedOn == true)
- {
- // turn off the LED
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- else
- {
- // turn on the LED
- isLedOn = true;
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
- olatRegister &= bitMask;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = redBrush;
- }
- }
- private void TurnOffLED()
- {
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- private void CheckButtonStatus()
- {
- byte[] readBuffer = new byte[1];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
- // a button press results in a logic low for the GPIO pin
- if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
- {
- ButtonStatusText.Text = "Button Status: Pressed";
- isButtonPressed = true;
- }
- else
- {
- ButtonStatusText.Text = "Button Status: Released";
- isButtonPressed = false;
- }
- }
- private void LedTimer_Tick(object sender, object e)
- {
- if (isButtonPressed == false)
- {
- FlipLED();
- }
- }
- private void ButtonStatusCheckTimer_Tick(object sender, object e)
- {
- CheckButtonStatus();
- }
- private void Delay_ValueChanged(object sender, RangeBaseValueChangedEventArgs e)
- {
- if (ledTimer == null)
- {
- return;
- }
- if (e.NewValue == Delay.Minimum)
- {
- DelayText.Text = "Stopped";
- ledTimer.Stop();
- TurnOffLED();
- }
- else
- {
- DelayText.Text = e.NewValue + "ms";
- ledTimer.Interval = TimeSpan.FromMilliseconds(e.NewValue);
- ledTimer.Start();
- }
- }
- }
-}
-```
+---
+page_type: sample
+urlFragment: I2CPortExpander
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to use a port expander to read the status of a tactile switch and control an LED for Windows 10 IoT Enterprise.
+---
+
+# I2C port expander
+
+In this sample, we'll connect an I2C port expander to your Windows 10 IoT Enterprise device and create a simple app that uses the port expander to read the status of a tactile switch and control an LED.
+
+No background knowledge of I2C or port expanders is needed. If you want to know more about I2C, SparkFun provides a great [tutorial on I2C](https://learn.sparkfun.com/tutorials/i2c).
+
+## Step 1: Connect the I2C Port Expander to your device
+
+You will need the following components:
+
+* 1 Windows 10 IoT Enterprise Compatible Board (This example uses an [UP Board](https://up-board.org/up/specifications/))
+
+* 1 [MCP23008 8-bit I/O Port Expander](http://www.digikey.com/product-detail/en/MCP23008-E%2FP/MCP23008-E%2FP-ND/735951) in PDIP package
+
+* 1 [red LED](http://www.digikey.com/product-detail/en/C5SMF-RJS-CT0W0BB1/C5SMF-RJS-CT0W0BB1-ND/2341832)
+
+* 1 [tactile switch](http://www.digikey.com/product-detail/en/320.02E11.08BLK/EG1311-ND/101397)
+
+* 1 [330 Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-330R/330QBK-ND/1636)
+
+* 1 [10k Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-10K/10KQBK-ND/338)
+
+* An HDMI monitor
+
+* A breadboard and several male-to-female and male-to-male connector wires
+
+Let's start by wiring up the components on the breadboard as shown in the diagram below.
+
+**Note: Make sure to power off the UP Board when connecting your circuit. This is good practice to reduce the chance of an accidental short circuit during construction.**
+
+
+
+
+Here is the schematic:
+
+
+
+
+## Step 2: Connecting the MCP23008 Port Expander
+
+Place the MCP23008 Port Expander on your breadboard such that it straddles the center gap of the breadboard.
+
+
+
+ Locate pin 1 of the port expander by finding the notch on the IC. If you orient the IC so that the end with the notch is facing left, pin 1 will be the first pin in the lower left below the notch.
+
+
+
+The pinout of the MCP23008 is shown below and can be found in the [datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf).
+
+
+
+
+Make the following connections on the MCP23008 Port Expander:
+
+* Pin 1 **SCL**: Connect to **I2C1 SCL** (Pin 28) on the UP Board (pin mapping is below)
+
+* Pin 2 **SDA**: Connect to **I2C1 SDA** (Pin 27) on the UP Board
+
+* Pin 3 **A2**: Connect to the ground rail on the side of the breadboard (blue stripe)
+
+* Pin 4 **A1**: Connect to the ground rail on the side of the breadboard
+
+* Pin 5 **A0**: Connect to the ground rail on the side of the breadboard
+
+* Pin 6 **Reset**: Connect to the voltage supply rail on the side of the breadboard (red stripe)
+
+* Pin 9 **VSS**: Connect to the ground rail on the side of the breadboard
+
+* Pin 10 **GP0**: Connect to the cathode (the shorter leg) of the LED
+
+* Pin 11 **GP1**: Connect to one lead of the 10k Ω resistor and one pin of the tactile switch
+
+* Pin 18 **VDD**: Connect to the voltage supply rail on the side of the breadboard
+
+Leave the remaining pins on the MCP23008 unconnected.
+
+
+## Step 3: Connecting the LED
+
+* If not already connected, connect the cathode (the shorter leg) of the LED to Pin 10 of the MCP23008 Port Expander
+
+* Connect the anode (the longer leg) of the LED to one lead of the 330 Ω resistor
+
+* Connect the other end of the 330 Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
+
+
+## Step 4: Connecting the Tactile Switch
+
+* If not already connected, connect one lead of the 10k Ω resistor to Pin 11 of the MCP23008 Port Expander
+
+* Connect the other end of the 10k Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
+
+* If not already connected, connect one pin of the tactile switch to Pin 11 of the MCP23008 Port Expander
+
+* Connect the other pin of the tactile switch to the ground rail on the side of the breadboard (blue stripe)
+
+
+## Step 5: Connecting the UP Board
+
+We need to hook up power, ground, and the I2C lines from on the UP Board to the MCP23008 Port Expander and the breadboard.
+
+
+
+* Pin 1 **3.3V PWR** Connect to the voltage supply rail on the side of the breadboard (red stripe)
+
+* Pin 27 **I2C0 SDA** If not already connected, connect to Pin 2 of the MCP23008 Port Expander
+
+* Pin 28 **I2C0 SCL** If not already connected, connect to pin 1 of the MCP23008 Port Expander
+
+* Pin 6 **GND** Connect to the ground rail on the side of the breadboard (blue stripe)
+
+The I2C bus requires pull-up resistors on the SDA and SCL lines. However, the UP Board SDA and SCL pins we are using in this sample already have pull-up resistors connected on the UP Board, so we don't need to add any additional external pull-ups.
+
+## Step 6: Create the sample app
+
+When everything is set up, power your device back on. You can find the source code for this sample by downloading a zip of all of our samples, navigate to the `samples-develop\I2CPortExpander`,
+but as an exercise, this tutorial will take you through the complete steps to create this app from scratch.
+Open up Visual Studio 2019.
+For this sample, we named **I2cPortExpanderLedSample**.
+
+## Step 7: Compile the sample
+
+* Choose `Release` and `x64` configuration.
+* Compile the Solution file
+
+## Step 8: Generate an app package
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+1. If you are using an UP Board, you have to setup the BIOS SPI configuration.
+
+ 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+ 1. Navigate to the **Advance** tab and select the **Hat Configuration** and change "I2C0/GPIO SELECTION" to "I2C0".
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+The code in this sample does several things:
+
+1. Initializes the I2C bus and the port expander
+
+2. Communicates over I2C with the port expander to turn the LED on and off at regular intervals
+
+3. Communicates over I2C with the port expander to check the status of the tactile switch (is it pressed or not) at regular intervals
+
+4. Displays the LED on/off status and the tactile switch pressed/released status to the display attached to the UP Board
+
+5. Stops flashing the LED when the tactile switch is pressed and restarts flashing the LED when the tactile switch is released
+
+6. Checks if the user has changed the LED flash frequency and updates the LED flash frequency as needed
+
+#### Add content to MainPage.xaml
+
+Let's add some content to the MainPage which will be displayed on a screen connected to the UP Board. We want to add a circle, a couple text boxes and a slider. The circle will emulate the on/off status of the LED. The Slider allows the user to control the frequency that the LED flashes. The Textboxes will provide info about the slider and report the tactile button status.
+
+* From Solution Explorer, select the MainPage.xaml file.
+
+* Locate the `` tag in the XAML section of the designer, and add the following markup:
+
+```csharp
+
+
+
+
+
+
+
+
+```
+#### Add code to MainPage.xaml.cs
+Before we add any code to MainPage.xaml.cs, we need to add a reference to the Windows IoT Extension SDK.
+ * In Solution Explorer, right-click on **References** and select **Add Reference...**
+ * In the Reference Manager window, click the arrow next to **Windows Universal** then click on **Extensions**
+ * Place a check mark in the box next to **Windows IoT Extension SDK** and click **OK**
+ * Open MainPage.xaml.cs from Solution Explorer (you may need to click on the arrow next to MainPage.xaml first)
+ * Add the following lines at the top of MainPage.xaml.cs
+```csharp
+using Windows.Devices.Enumeration;
+using Windows.Devices.I2c;
+```
+
+
+With the references added, let's start adding code. The complete code we implemented for MainPage.xaml.cs is located at end of this section. Below are some key parts of the code with explanations
+
+
+Variables and Constants
+
+```csharp
+// use these constants for controlling how the I2C bus is setup
+
+private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
+private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
+private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
+private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
+private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
+private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
+private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
+private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
+private byte iodirRegister; // local copy of I2C Port Expander IODIR register
+private byte gpioRegister; // local copy of I2C Port Expander GPIO register
+private byte olatRegister; // local copy of I2C Port Expander OLAT register
+private I2cDevice i2cPortExpander;
+private DispatcherTimer ledTimer;
+private DispatcherTimer buttonStatusCheckTimer;
+private bool isLedOn = false;
+private bool isButtonPressed = false;
+private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
+private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
+```
+
+Here are what some of these constants and variables represent
+
+ * `I2C_CONTROLLER_NAME` holds the string constant `I2C0` which is the name of the I2C controller on the UP Board.
+
+ * `PORT_EXPANDER_I2C_ADDRESS` is the I2C address of the port expander we are using. \*
+
+ * `PORT_EXPANDER_IODIR_REGISTER_ADDRESS`, `PORT_EXPANDER_GPIO_REGISTER_ADDRESS`, `PORT_EXPANDER_OLAT_REGISTER_ADDRESS` are the register addresses in the port expander that correspond to the IODIR register, GPIO register and OLAT register.\*
+
+ * `TIMER_INTERVAL` is the starting time interval in milliseconds between an LED on or off toggle.
+
+ * `BUTTON_STATUS_CHECK_TIMER_INTERVAL` is the time interval in milliseconds between each check of the tactile switch status
+
+ * `iodirRegister`, `gpioRegister` and `olatRegister` are our local copies of the values in the corresponding registers in the port expander.
+
+\* See the [MCP23008 datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf)for details.
+
+The method `InitializeSystem()`
+
+`InitializeSystem()` does the following:
+
+ * Sets up the I2C communications on the UP Board
+
+ * Configures the port expander to be able to turn the LED on and off and to get the tactile switch status
+
+ * Initializes the local copies of the port expander registers IODIR, GPIO and OLAT
+
+ * Sets up two timers - One for controlling the LED and another for checking the tactile switch status
+
+When complete, the variable `i2cPortExpander` will be our handle to the UP Board I2C bus.
+
+```csharp
+private async void InitializeSystem()
+{
+ byte[] i2CWriteBuffer;
+ byte[] i2CReadBuffer;
+ byte bitMask;
+ // initialize I2C communications
+ try
+ {
+ var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
+ string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
+ var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
+ i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // initialize I2C Port Expander registers
+ try
+ {
+ // initialize local copies of the IODIR, GPIO, and OLAT registers
+ i2CReadBuffer = new byte[1];
+ // read in each register value on register at a time (could do this all at once but
+ // for example clarity purposes we do it this way)
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
+ iodirRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
+ gpioRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
+ olatRegister = i2CReadBuffer[0];
+ // configure the LED pin output to be logic high, leave the other pins as they are.
+ olatRegister |= LED_GPIO_PIN;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ // configure only the LED pin to be an output and leave the other pins as they are.
+ // input is logic low, output is logic high
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
+ iodirRegister &= bitMask;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // setup our timers, one for the LED blink interval, the other for checking button status
+ try
+ {
+ ledTimer = new DispatcherTimer();
+ ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
+ ledTimer.Tick += LedTimer_Tick;
+ ledTimer.Start();
+ buttonStatusCheckTimer = new DispatcherTimer();
+ buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
+ buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
+ buttonStatusCheckTimer.Start();
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+}
+```
+
+The method `FlipLED()`
+
+`FlipLED()` is called by the ledTimer whenever the LED timer has reached the end of its interval length. Initially, this is 500 milliseconds but can be changed by a user via the slider displayed on a monitor connected to the UP Board.
+
+ This method determines if the LED is currently on or off.
+
+ * If the LED is currently off, it sends commands to the port expander to turn the LED on and sets the color of the circle on the display to red.
+
+ * If the LED is currently on, it sends commands to the port expander to turn the LED off and sets the color of the circle on the display to gray.
+
+```csharp
+private void FlipLED()
+{
+ byte bitMask;
+ if (isLedOn == true)
+ {
+ // turn off the LED
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ else
+ {
+ // turn on the LED
+ isLedOn = true;
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
+ olatRegister &= bitMask;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = redBrush;
+ }
+}
+```
+
+`CheckButtonStatus()` communicates with the port expander to get the tactile switch status. It reads the GPIO register on the port expander and checks the value of the second bit which corresponds to the status of the switch.
+
+ * If the second bit of the GPIO register is '0' then the switch is currently pressed.
+
+ * If the second bit of the GPIO register is '1' then the switch is currently released.
+
+This method updates the text in Textbox displayed to the screen to reflect the status of the switch.
+
+```csharp
+private void CheckButtonStatus()
+{
+ byte[] readBuffer = new byte[1];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
+ // a button press results in a logic low for the GPIO pin
+ if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
+ {
+ ButtonStatusText.Text = "Button Status: Pressed";
+ isButtonPressed = true;
+ }
+ else
+ {
+ ButtonStatusText.Text = "Button Status: Released";
+ isButtonPressed = false;
+ }
+}
+```
+
+## Step 9: Deploy and Run the App
+
+Let's build, deploy and run the app on our UP Board.
+
+* If not already open, open in Visual Studio the app you created with the code above.
+
+After several moments, you will see the screen attached to the UP Board change to show a circle, some text, and a slider. The LED on the breadboard will begin to turn on and off.
+
+Congratulations! You've successfully connected an I2C port expander to your device.
+
+### The complete MainPage.xaml.cs code
+
+```csharp
+using System;
+//using System.Diagnostics;
+using System.Collections.Generic;
+using System.IO;
+using System.Linq;
+using System.Runtime.InteropServices.WindowsRuntime;
+using Windows.Foundation;
+using Windows.Foundation.Collections;
+using Windows.UI.Xaml;
+using Windows.UI.Xaml.Controls;
+using Windows.UI.Xaml.Controls.Primitives;
+using Windows.UI.Xaml.Data;
+using Windows.UI.Xaml.Input;
+using Windows.UI.Xaml.Media;
+using Windows.UI.Xaml.Navigation;
+using Windows.Devices.Enumeration;
+using Windows.Devices.I2c;
+// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=402352&clcid=0x409
+namespace I2cPortExpanderLedSample
+{
+ ///
+ /// An empty page that can be used on its own or navigated to within a Frame.
+ ///
+ public sealed partial class MainPage : Page
+ {
+ // use these constants for controlling how the I2C bus is setup
+ private const string I2C_CONTROLLER_NAME = "I2C0"; //specific to UP Board
+ private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
+ private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
+ private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
+ private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
+ private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
+ private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
+ private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
+ private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
+ private byte iodirRegister; // local copy of I2C Port Expander IODIR register
+ private byte gpioRegister; // local copy of I2C Port Expander GPIO register
+ private byte olatRegister; // local copy of I2C Port Expander OLAT register
+ private I2cDevice i2cPortExpander;
+ private DispatcherTimer ledTimer;
+ private DispatcherTimer buttonStatusCheckTimer;
+ private bool isLedOn = false;
+ private bool isButtonPressed = false;
+ private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
+ private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
+ public MainPage()
+ {
+ this.InitializeComponent();
+ // Register for the unloaded event so we can clean up upon exit
+ Unloaded += MainPage_Unloaded;
+ InitializeSystem();
+ }
+ private async void InitializeSystem()
+ {
+ byte[] i2CWriteBuffer;
+ byte[] i2CReadBuffer;
+ byte bitMask;
+ // initialize I2C communications
+ try
+ {
+ var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
+ i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
+ string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
+ var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
+ i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // initialize I2C Port Expander registers
+ try
+ {
+ // initialize local copies of the IODIR, GPIO, and OLAT registers
+ i2CReadBuffer = new byte[1];
+ // read in each register value on register at a time (could do this all at once but
+ // for example clarity purposes we do it this way)
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
+ iodirRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
+ gpioRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
+ olatRegister = i2CReadBuffer[0];
+ // configure the LED pin output to be logic high, leave the other pins as they are.
+ olatRegister |= LED_GPIO_PIN;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ // configure only the LED pin to be an output and leave the other pins as they are.
+ // input is logic low, output is logic high
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
+ iodirRegister &= bitMask;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // setup our timers, one for the LED blink interval, the other for checking button status
+ try
+ {
+ ledTimer = new DispatcherTimer();
+ ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
+ ledTimer.Tick += LedTimer_Tick;
+ ledTimer.Start();
+ buttonStatusCheckTimer = new DispatcherTimer();
+ buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
+ buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
+ buttonStatusCheckTimer.Start();
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ }
+ private void MainPage_Unloaded(object sender, object args)
+ {
+ /* Cleanup */
+ i2cPortExpander.Dispose();
+ }
+ private void FlipLED()
+ {
+ byte bitMask;
+ if (isLedOn == true)
+ {
+ // turn off the LED
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ else
+ {
+ // turn on the LED
+ isLedOn = true;
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
+ olatRegister &= bitMask;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = redBrush;
+ }
+ }
+ private void TurnOffLED()
+ {
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ private void CheckButtonStatus()
+ {
+ byte[] readBuffer = new byte[1];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
+ // a button press results in a logic low for the GPIO pin
+ if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
+ {
+ ButtonStatusText.Text = "Button Status: Pressed";
+ isButtonPressed = true;
+ }
+ else
+ {
+ ButtonStatusText.Text = "Button Status: Released";
+ isButtonPressed = false;
+ }
+ }
+ private void LedTimer_Tick(object sender, object e)
+ {
+ if (isButtonPressed == false)
+ {
+ FlipLED();
+ }
+ }
+ private void ButtonStatusCheckTimer_Tick(object sender, object e)
+ {
+ CheckButtonStatus();
+ }
+ private void Delay_ValueChanged(object sender, RangeBaseValueChangedEventArgs e)
+ {
+ if (ledTimer == null)
+ {
+ return;
+ }
+ if (e.NewValue == Delay.Minimum)
+ {
+ DelayText.Text = "Stopped";
+ ledTimer.Stop();
+ TurnOffLED();
+ }
+ else
+ {
+ DelayText.Text = e.NewValue + "ms";
+ ledTimer.Interval = TimeSpan.FromMilliseconds(e.NewValue);
+ ledTimer.Start();
+ }
+ }
+ }
+}
+```
diff --git a/samples/I2CPortExpander/README.md b/samples/I2CPortExpander/README.md
index 277d9e436..8fd4aa6f7 100644
--- a/samples/I2CPortExpander/README.md
+++ b/samples/I2CPortExpander/README.md
@@ -1,599 +1,599 @@
----
-page_type: sample
-urlFragment: I2CPortExpander
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: A sample that shows how to use a port expander to read the status of a tactile switch and control an LED for Windows 10 IoT Enterprise.
----
-
-# I2C port expander
-
-In this sample, we'll connect an I2C port expander to your Windows 10 IoT Enterprise device and create a simple app that uses the port expander to read the status of a tactile switch and control an LED.
-
-No background knowledge of I2C or port expanders is needed. If you want to know more about I2C, SparkFun provides a great [tutorial on I2C](https://learn.sparkfun.com/tutorials/i2c).
-
-## Step 1: Connect the I2C Port Expander to your device
-
-You will need the following components:
-
-* 1 Windows 10 IoT Enterprise Compatible Board (This example uses an [UP Board](https://up-board.org/up/specifications/))
-
-* 1 [MCP23008 8-bit I/O Port Expander](http://www.digikey.com/product-detail/en/MCP23008-E%2FP/MCP23008-E%2FP-ND/735951) in PDIP package
-
-* 1 [red LED](http://www.digikey.com/product-detail/en/C5SMF-RJS-CT0W0BB1/C5SMF-RJS-CT0W0BB1-ND/2341832)
-
-* 1 [tactile switch](http://www.digikey.com/product-detail/en/320.02E11.08BLK/EG1311-ND/101397)
-
-* 1 [330 Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-330R/330QBK-ND/1636)
-
-* 1 [10k Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-10K/10KQBK-ND/338)
-
-* An HDMI monitor
-
-* A breadboard and several male-to-female and male-to-male connector wires
-
-Let's start by wiring up the components on the breadboard as shown in the diagram below.
-
-**Note: Make sure to power off the UP Board when connecting your circuit. This is good practice to reduce the chance of an accidental short circuit during construction.**
-
-
-
-
-Here is the schematic:
-
-
-
-
-## Step 2: Connecting the MCP23008 Port Expander
-
-Place the MCP23008 Port Expander on your breadboard such that it straddles the center gap of the breadboard.
-
-
-
- Locate pin 1 of the port expander by finding the notch on the IC. If you orient the IC so that the end with the notch is facing left, pin 1 will be the first pin in the lower left below the notch.
-
-
-
-The pinout of the MCP23008 is shown below and can be found in the [datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf).
-
-
-
-
-Make the following connections on the MCP23008 Port Expander:
-
-* Pin 1 **SCL**: Connect to **I2C1 SCL** (Pin 28) on the UP Board (pin mapping is below)
-
-* Pin 2 **SDA**: Connect to **I2C1 SDA** (Pin 27) on the UP Board
-
-* Pin 3 **A2**: Connect to the ground rail on the side of the breadboard (blue stripe)
-
-* Pin 4 **A1**: Connect to the ground rail on the side of the breadboard
-
-* Pin 5 **A0**: Connect to the ground rail on the side of the breadboard
-
-* Pin 6 **Reset**: Connect to the voltage supply rail on the side of the breadboard (red stripe)
-
-* Pin 9 **VSS**: Connect to the ground rail on the side of the breadboard
-
-* Pin 10 **GP0**: Connect to the cathode (the shorter leg) of the LED
-
-* Pin 11 **GP1**: Connect to one lead of the 10k Ω resistor and one pin of the tactile switch
-
-* Pin 18 **VDD**: Connect to the voltage supply rail on the side of the breadboard
-
-Leave the remaining pins on the MCP23008 unconnected.
-
-
-## Step 3: Connecting the LED
-
-* If not already connected, connect the cathode (the shorter leg) of the LED to Pin 10 of the MCP23008 Port Expander
-
-* Connect the anode (the longer leg) of the LED to one lead of the 330 Ω resistor
-
-* Connect the other end of the 330 Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
-
-
-## Step 4: Connecting the Tactile Switch
-
-* If not already connected, connect one lead of the 10k Ω resistor to Pin 11 of the MCP23008 Port Expander
-
-* Connect the other end of the 10k Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
-
-* If not already connected, connect one pin of the tactile switch to Pin 11 of the MCP23008 Port Expander
-
-* Connect the other pin of the tactile switch to the ground rail on the side of the breadboard (blue stripe)
-
-
-## Step 5: Connecting the UP Board
-
-We need to hook up power, ground, and the I2C lines from on the UP Board to the MCP23008 Port Expander and the breadboard.
-
-
-
-* Pin 1 **3.3V PWR** Connect to the voltage supply rail on the side of the breadboard (red stripe)
-
-* Pin 27 **I2C0 SDA** If not already connected, connect to Pin 2 of the MCP23008 Port Expander
-
-* Pin 28 **I2C0 SCL** If not already connected, connect to pin 1 of the MCP23008 Port Expander
-
-* Pin 6 **GND** Connect to the ground rail on the side of the breadboard (blue stripe)
-
-The I2C bus requires pull-up resistors on the SDA and SCL lines. However, the UP Board SDA and SCL pins we are using in this sample already have pull-up resistors connected on the UP Board, so we don't need to add any additional external pull-ups.
-
-## Step 6: Create the sample app
-
-When everything is set up, power your device back on. You can find the source code for this sample by downloading a zip of all of our samples, navigate to the `samples-develop\I2CPortExpander`,
-but as an exercise, this tutorial will take you through the complete steps to create this app from scratch.
-Open up Visual Studio 2019.
-For this sample, we named **I2cPortExpanderLedSample**.
-
-## Step 7: Compile the sample
-
-* Choose `Release` and `x64` configuration.
-* Compile the Solution file
-
-## Step 8: Generate an app package
-
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-1. If you are using an UP Board, you have to setup the BIOS SPI configuration.
-
- 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
-
- 1. Navigate to the **Advance** tab and select the **Hat Configuration** and change "I2C0/GPIO SELECTION" to "I2C0".
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-The code in this sample does several things:
-
-1. Initializes the I2C bus and the port expander
-
-2. Communicates over I2C with the port expander to turn the LED on and off at regular intervals
-
-3. Communicates over I2C with the port expander to check the status of the tactile switch (is it pressed or not) at regular intervals
-
-4. Displays the LED on/off status and the tactile switch pressed/released status to the display attached to the UP Board
-
-5. Stops flashing the LED when the tactile switch is pressed and restarts flashing the LED when the tactile switch is released
-
-6. Checks if the user has changed the LED flash frequency and updates the LED flash frequency as needed
-
-#### Add content to MainPage.xaml
-
-Let's add some content to the MainPage which will be displayed on a screen connected to the UP Board. We want to add a circle, a couple text boxes and a slider. The circle will emulate the on/off status of the LED. The Slider allows the user to control the frequency that the LED flashes. The Textboxes will provide info about the slider and report the tactile button status.
-
-* From Solution Explorer, select the MainPage.xaml file.
-
-* Locate the `` tag in the XAML section of the designer, and add the following markup:
-
-```csharp
-
-
-
-
-
-
-
-
-```
-#### Add code to MainPage.xaml.cs
-Before we add any code to MainPage.xaml.cs, we need to add a reference to the Windows IoT Extension SDK.
- * In Solution Explorer, right-click on **References** and select **Add Reference...**
- * In the Reference Manager window, click the arrow next to **Windows Universal** then click on **Extensions**
- * Place a check mark in the box next to **Windows IoT Extension SDK** and click **OK**
- * Open MainPage.xaml.cs from Solution Explorer (you may need to click on the arrow next to MainPage.xaml first)
- * Add the following lines at the top of MainPage.xaml.cs
-```csharp
-using Windows.Devices.Enumeration;
-using Windows.Devices.I2c;
-```
-
-
-With the references added, let's start adding code. The complete code we implemented for MainPage.xaml.cs is located at end of this section. Below are some key parts of the code with explanations
-
-
-Variables and Constants
-
-```csharp
-// use these constants for controlling how the I2C bus is setup
-
-private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
-private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
-private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
-private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
-private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
-private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
-private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
-private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
-private byte iodirRegister; // local copy of I2C Port Expander IODIR register
-private byte gpioRegister; // local copy of I2C Port Expander GPIO register
-private byte olatRegister; // local copy of I2C Port Expander OLAT register
-private I2cDevice i2cPortExpander;
-private DispatcherTimer ledTimer;
-private DispatcherTimer buttonStatusCheckTimer;
-private bool isLedOn = false;
-private bool isButtonPressed = false;
-private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
-private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
-```
-
-Here are what some of these constants and variables represent
-
- * `I2C_CONTROLLER_NAME` holds the string constant `I2C0` which is the name of the I2C controller on the UP Board.
-
- * `PORT_EXPANDER_I2C_ADDRESS` is the I2C address of the port expander we are using. \*
-
- * `PORT_EXPANDER_IODIR_REGISTER_ADDRESS`, `PORT_EXPANDER_GPIO_REGISTER_ADDRESS`, `PORT_EXPANDER_OLAT_REGISTER_ADDRESS` are the register addresses in the port expander that correspond to the IODIR register, GPIO register and OLAT register.\*
-
- * `TIMER_INTERVAL` is the starting time interval in milliseconds between an LED on or off toggle.
-
- * `BUTTON_STATUS_CHECK_TIMER_INTERVAL` is the time interval in milliseconds between each check of the tactile switch status
-
- * `iodirRegister`, `gpioRegister` and `olatRegister` are our local copies of the values in the corresponding registers in the port expander.
-
-\* See the [MCP23008 datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf)for details.
-
-The method `InitializeSystem()`
-
-`InitializeSystem()` does the following:
-
- * Sets up the I2C communications on the UP Board
-
- * Configures the port expander to be able to turn the LED on and off and to get the tactile switch status
-
- * Initializes the local copies of the port expander registers IODIR, GPIO and OLAT
-
- * Sets up two timers - One for controlling the LED and another for checking the tactile switch status
-
-When complete, the variable `i2cPortExpander` will be our handle to the UP Board I2C bus.
-
-```csharp
-private async void InitializeSystem()
-{
- byte[] i2CWriteBuffer;
- byte[] i2CReadBuffer;
- byte bitMask;
- // initialize I2C communications
- try
- {
- var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
- string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
- var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
- i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // initialize I2C Port Expander registers
- try
- {
- // initialize local copies of the IODIR, GPIO, and OLAT registers
- i2CReadBuffer = new byte[1];
- // read in each register value on register at a time (could do this all at once but
- // for example clarity purposes we do it this way)
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
- iodirRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
- gpioRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
- olatRegister = i2CReadBuffer[0];
- // configure the LED pin output to be logic high, leave the other pins as they are.
- olatRegister |= LED_GPIO_PIN;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- // configure only the LED pin to be an output and leave the other pins as they are.
- // input is logic low, output is logic high
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
- iodirRegister &= bitMask;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // setup our timers, one for the LED blink interval, the other for checking button status
- try
- {
- ledTimer = new DispatcherTimer();
- ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
- ledTimer.Tick += LedTimer_Tick;
- ledTimer.Start();
- buttonStatusCheckTimer = new DispatcherTimer();
- buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
- buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
- buttonStatusCheckTimer.Start();
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
-}
-```
-
-The method `FlipLED()`
-
-`FlipLED()` is called by the ledTimer whenever the LED timer has reached the end of its interval length. Initially, this is 500 milliseconds but can be changed by a user via the slider displayed on a monitor connected to the UP Board.
-
- This method determines if the LED is currently on or off.
-
- * If the LED is currently off, it sends commands to the port expander to turn the LED on and sets the color of the circle on the display to red.
-
- * If the LED is currently on, it sends commands to the port expander to turn the LED off and sets the color of the circle on the display to gray.
-
-```csharp
-private void FlipLED()
-{
- byte bitMask;
- if (isLedOn == true)
- {
- // turn off the LED
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- else
- {
- // turn on the LED
- isLedOn = true;
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
- olatRegister &= bitMask;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = redBrush;
- }
-}
-```
-
-`CheckButtonStatus()` communicates with the port expander to get the tactile switch status. It reads the GPIO register on the port expander and checks the value of the second bit which corresponds to the status of the switch.
-
- * If the second bit of the GPIO register is '0' then the switch is currently pressed.
-
- * If the second bit of the GPIO register is '1' then the switch is currently released.
-
-This method updates the text in Textbox displayed to the screen to reflect the status of the switch.
-
-```csharp
-private void CheckButtonStatus()
-{
- byte[] readBuffer = new byte[1];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
- // a button press results in a logic low for the GPIO pin
- if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
- {
- ButtonStatusText.Text = "Button Status: Pressed";
- isButtonPressed = true;
- }
- else
- {
- ButtonStatusText.Text = "Button Status: Released";
- isButtonPressed = false;
- }
-}
-```
-
-## Step 9: Deploy and Run the App
-
-Let's build, deploy and run the app on our UP Board.
-
-* If not already open, open in Visual Studio the app you created with the code above.
-
-After several moments, you will see the screen attached to the UP Board change to show a circle, some text, and a slider. The LED on the breadboard will begin to turn on and off.
-
-Congratulations! You've successfully connected an I2C port expander to your device.
-
-### The complete MainPage.xaml.cs code
-
-```csharp
-using System;
-//using System.Diagnostics;
-using System.Collections.Generic;
-using System.IO;
-using System.Linq;
-using System.Runtime.InteropServices.WindowsRuntime;
-using Windows.Foundation;
-using Windows.Foundation.Collections;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
-using Windows.UI.Xaml.Controls.Primitives;
-using Windows.UI.Xaml.Data;
-using Windows.UI.Xaml.Input;
-using Windows.UI.Xaml.Media;
-using Windows.UI.Xaml.Navigation;
-using Windows.Devices.Enumeration;
-using Windows.Devices.I2c;
-// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=402352&clcid=0x409
-namespace I2cPortExpanderLedSample
-{
- ///
- /// An empty page that can be used on its own or navigated to within a Frame.
- ///
- public sealed partial class MainPage : Page
- {
- // use these constants for controlling how the I2C bus is setup
- private const string I2C_CONTROLLER_NAME = "I2C0"; //specific to UP Board
- private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
- private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
- private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
- private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
- private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
- private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
- private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
- private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
- private byte iodirRegister; // local copy of I2C Port Expander IODIR register
- private byte gpioRegister; // local copy of I2C Port Expander GPIO register
- private byte olatRegister; // local copy of I2C Port Expander OLAT register
- private I2cDevice i2cPortExpander;
- private DispatcherTimer ledTimer;
- private DispatcherTimer buttonStatusCheckTimer;
- private bool isLedOn = false;
- private bool isButtonPressed = false;
- private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
- private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
- public MainPage()
- {
- this.InitializeComponent();
- // Register for the unloaded event so we can clean up upon exit
- Unloaded += MainPage_Unloaded;
- InitializeSystem();
- }
- private async void InitializeSystem()
- {
- byte[] i2CWriteBuffer;
- byte[] i2CReadBuffer;
- byte bitMask;
- // initialize I2C communications
- try
- {
- var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
- i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
- string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
- var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
- i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // initialize I2C Port Expander registers
- try
- {
- // initialize local copies of the IODIR, GPIO, and OLAT registers
- i2CReadBuffer = new byte[1];
- // read in each register value on register at a time (could do this all at once but
- // for example clarity purposes we do it this way)
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
- iodirRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
- gpioRegister = i2CReadBuffer[0];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
- olatRegister = i2CReadBuffer[0];
- // configure the LED pin output to be logic high, leave the other pins as they are.
- olatRegister |= LED_GPIO_PIN;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- // configure only the LED pin to be an output and leave the other pins as they are.
- // input is logic low, output is logic high
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
- iodirRegister &= bitMask;
- i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
- i2cPortExpander.Write(i2CWriteBuffer);
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- // setup our timers, one for the LED blink interval, the other for checking button status
- try
- {
- ledTimer = new DispatcherTimer();
- ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
- ledTimer.Tick += LedTimer_Tick;
- ledTimer.Start();
- buttonStatusCheckTimer = new DispatcherTimer();
- buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
- buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
- buttonStatusCheckTimer.Start();
- }
- catch (Exception e)
- {
- System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
- return;
- }
- }
- private void MainPage_Unloaded(object sender, object args)
- {
- /* Cleanup */
- i2cPortExpander.Dispose();
- }
- private void FlipLED()
- {
- byte bitMask;
- if (isLedOn == true)
- {
- // turn off the LED
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- else
- {
- // turn on the LED
- isLedOn = true;
- bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
- olatRegister &= bitMask;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = redBrush;
- }
- }
- private void TurnOffLED()
- {
- isLedOn = false;
- olatRegister |= LED_GPIO_PIN;
- i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
- Led.Fill = grayBrush;
- }
- private void CheckButtonStatus()
- {
- byte[] readBuffer = new byte[1];
- i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
- // a button press results in a logic low for the GPIO pin
- if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
- {
- ButtonStatusText.Text = "Button Status: Pressed";
- isButtonPressed = true;
- }
- else
- {
- ButtonStatusText.Text = "Button Status: Released";
- isButtonPressed = false;
- }
- }
- private void LedTimer_Tick(object sender, object e)
- {
- if (isButtonPressed == false)
- {
- FlipLED();
- }
- }
- private void ButtonStatusCheckTimer_Tick(object sender, object e)
- {
- CheckButtonStatus();
- }
- private void Delay_ValueChanged(object sender, RangeBaseValueChangedEventArgs e)
- {
- if (ledTimer == null)
- {
- return;
- }
- if (e.NewValue == Delay.Minimum)
- {
- DelayText.Text = "Stopped";
- ledTimer.Stop();
- TurnOffLED();
- }
- else
- {
- DelayText.Text = e.NewValue + "ms";
- ledTimer.Interval = TimeSpan.FromMilliseconds(e.NewValue);
- ledTimer.Start();
- }
- }
- }
-}
-```
+---
+page_type: sample
+urlFragment: I2CPortExpander
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: A sample that shows how to use a port expander to read the status of a tactile switch and control an LED for Windows 10 IoT Enterprise.
+---
+
+# I2C port expander
+
+In this sample, we'll connect an I2C port expander to your Windows 10 IoT Enterprise device and create a simple app that uses the port expander to read the status of a tactile switch and control an LED.
+
+No background knowledge of I2C or port expanders is needed. If you want to know more about I2C, SparkFun provides a great [tutorial on I2C](https://learn.sparkfun.com/tutorials/i2c).
+
+## Step 1: Connect the I2C Port Expander to your device
+
+You will need the following components:
+
+* 1 Windows 10 IoT Enterprise Compatible Board (This example uses an [UP Board](https://up-board.org/up/specifications/))
+
+* 1 [MCP23008 8-bit I/O Port Expander](http://www.digikey.com/product-detail/en/MCP23008-E%2FP/MCP23008-E%2FP-ND/735951) in PDIP package
+
+* 1 [red LED](http://www.digikey.com/product-detail/en/C5SMF-RJS-CT0W0BB1/C5SMF-RJS-CT0W0BB1-ND/2341832)
+
+* 1 [tactile switch](http://www.digikey.com/product-detail/en/320.02E11.08BLK/EG1311-ND/101397)
+
+* 1 [330 Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-330R/330QBK-ND/1636)
+
+* 1 [10k Ω resistor](http://www.digikey.com/product-detail/en/CFR-25JB-52-10K/10KQBK-ND/338)
+
+* An HDMI monitor
+
+* A breadboard and several male-to-female and male-to-male connector wires
+
+Let's start by wiring up the components on the breadboard as shown in the diagram below.
+
+**Note: Make sure to power off the UP Board when connecting your circuit. This is good practice to reduce the chance of an accidental short circuit during construction.**
+
+
+
+
+Here is the schematic:
+
+
+
+
+## Step 2: Connecting the MCP23008 Port Expander
+
+Place the MCP23008 Port Expander on your breadboard such that it straddles the center gap of the breadboard.
+
+
+
+ Locate pin 1 of the port expander by finding the notch on the IC. If you orient the IC so that the end with the notch is facing left, pin 1 will be the first pin in the lower left below the notch.
+
+
+
+The pinout of the MCP23008 is shown below and can be found in the [datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf).
+
+
+
+
+Make the following connections on the MCP23008 Port Expander:
+
+* Pin 1 **SCL**: Connect to **I2C1 SCL** (Pin 28) on the UP Board (pin mapping is below)
+
+* Pin 2 **SDA**: Connect to **I2C1 SDA** (Pin 27) on the UP Board
+
+* Pin 3 **A2**: Connect to the ground rail on the side of the breadboard (blue stripe)
+
+* Pin 4 **A1**: Connect to the ground rail on the side of the breadboard
+
+* Pin 5 **A0**: Connect to the ground rail on the side of the breadboard
+
+* Pin 6 **Reset**: Connect to the voltage supply rail on the side of the breadboard (red stripe)
+
+* Pin 9 **VSS**: Connect to the ground rail on the side of the breadboard
+
+* Pin 10 **GP0**: Connect to the cathode (the shorter leg) of the LED
+
+* Pin 11 **GP1**: Connect to one lead of the 10k Ω resistor and one pin of the tactile switch
+
+* Pin 18 **VDD**: Connect to the voltage supply rail on the side of the breadboard
+
+Leave the remaining pins on the MCP23008 unconnected.
+
+
+## Step 3: Connecting the LED
+
+* If not already connected, connect the cathode (the shorter leg) of the LED to Pin 10 of the MCP23008 Port Expander
+
+* Connect the anode (the longer leg) of the LED to one lead of the 330 Ω resistor
+
+* Connect the other end of the 330 Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
+
+
+## Step 4: Connecting the Tactile Switch
+
+* If not already connected, connect one lead of the 10k Ω resistor to Pin 11 of the MCP23008 Port Expander
+
+* Connect the other end of the 10k Ω resistor to the voltage supply rail on the side of the breadboard (red stripe)
+
+* If not already connected, connect one pin of the tactile switch to Pin 11 of the MCP23008 Port Expander
+
+* Connect the other pin of the tactile switch to the ground rail on the side of the breadboard (blue stripe)
+
+
+## Step 5: Connecting the UP Board
+
+We need to hook up power, ground, and the I2C lines from on the UP Board to the MCP23008 Port Expander and the breadboard.
+
+
+
+* Pin 1 **3.3V PWR** Connect to the voltage supply rail on the side of the breadboard (red stripe)
+
+* Pin 27 **I2C0 SDA** If not already connected, connect to Pin 2 of the MCP23008 Port Expander
+
+* Pin 28 **I2C0 SCL** If not already connected, connect to pin 1 of the MCP23008 Port Expander
+
+* Pin 6 **GND** Connect to the ground rail on the side of the breadboard (blue stripe)
+
+The I2C bus requires pull-up resistors on the SDA and SCL lines. However, the UP Board SDA and SCL pins we are using in this sample already have pull-up resistors connected on the UP Board, so we don't need to add any additional external pull-ups.
+
+## Step 6: Create the sample app
+
+When everything is set up, power your device back on. You can find the source code for this sample by downloading a zip of all of our samples, navigate to the `samples-develop\I2CPortExpander`,
+but as an exercise, this tutorial will take you through the complete steps to create this app from scratch.
+Open up Visual Studio 2019.
+For this sample, we named **I2cPortExpanderLedSample**.
+
+## Step 7: Compile the sample
+
+* Choose `Release` and `x64` configuration.
+* Compile the Solution file
+
+## Step 8: Generate an app package
+
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+1. If you are using an UP Board, you have to setup the BIOS SPI configuration.
+
+ 1. Once you power on the UP board, select the **Del** or **F7** key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to **Boot** > **OS Image ID** tab, and select **Windows 10 IoT Core**.
+
+ 1. Navigate to the **Advance** tab and select the **Hat Configuration** and change "I2C0/GPIO SELECTION" to "I2C0".
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+The code in this sample does several things:
+
+1. Initializes the I2C bus and the port expander
+
+2. Communicates over I2C with the port expander to turn the LED on and off at regular intervals
+
+3. Communicates over I2C with the port expander to check the status of the tactile switch (is it pressed or not) at regular intervals
+
+4. Displays the LED on/off status and the tactile switch pressed/released status to the display attached to the UP Board
+
+5. Stops flashing the LED when the tactile switch is pressed and restarts flashing the LED when the tactile switch is released
+
+6. Checks if the user has changed the LED flash frequency and updates the LED flash frequency as needed
+
+#### Add content to MainPage.xaml
+
+Let's add some content to the MainPage which will be displayed on a screen connected to the UP Board. We want to add a circle, a couple text boxes and a slider. The circle will emulate the on/off status of the LED. The Slider allows the user to control the frequency that the LED flashes. The Textboxes will provide info about the slider and report the tactile button status.
+
+* From Solution Explorer, select the MainPage.xaml file.
+
+* Locate the `` tag in the XAML section of the designer, and add the following markup:
+
+```csharp
+
+
+
+
+
+
+
+
+```
+#### Add code to MainPage.xaml.cs
+Before we add any code to MainPage.xaml.cs, we need to add a reference to the Windows IoT Extension SDK.
+ * In Solution Explorer, right-click on **References** and select **Add Reference...**
+ * In the Reference Manager window, click the arrow next to **Windows Universal** then click on **Extensions**
+ * Place a check mark in the box next to **Windows IoT Extension SDK** and click **OK**
+ * Open MainPage.xaml.cs from Solution Explorer (you may need to click on the arrow next to MainPage.xaml first)
+ * Add the following lines at the top of MainPage.xaml.cs
+```csharp
+using Windows.Devices.Enumeration;
+using Windows.Devices.I2c;
+```
+
+
+With the references added, let's start adding code. The complete code we implemented for MainPage.xaml.cs is located at end of this section. Below are some key parts of the code with explanations
+
+
+Variables and Constants
+
+```csharp
+// use these constants for controlling how the I2C bus is setup
+
+private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
+private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
+private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
+private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
+private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
+private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
+private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
+private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
+private byte iodirRegister; // local copy of I2C Port Expander IODIR register
+private byte gpioRegister; // local copy of I2C Port Expander GPIO register
+private byte olatRegister; // local copy of I2C Port Expander OLAT register
+private I2cDevice i2cPortExpander;
+private DispatcherTimer ledTimer;
+private DispatcherTimer buttonStatusCheckTimer;
+private bool isLedOn = false;
+private bool isButtonPressed = false;
+private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
+private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
+```
+
+Here are what some of these constants and variables represent
+
+ * `I2C_CONTROLLER_NAME` holds the string constant `I2C0` which is the name of the I2C controller on the UP Board.
+
+ * `PORT_EXPANDER_I2C_ADDRESS` is the I2C address of the port expander we are using. \*
+
+ * `PORT_EXPANDER_IODIR_REGISTER_ADDRESS`, `PORT_EXPANDER_GPIO_REGISTER_ADDRESS`, `PORT_EXPANDER_OLAT_REGISTER_ADDRESS` are the register addresses in the port expander that correspond to the IODIR register, GPIO register and OLAT register.\*
+
+ * `TIMER_INTERVAL` is the starting time interval in milliseconds between an LED on or off toggle.
+
+ * `BUTTON_STATUS_CHECK_TIMER_INTERVAL` is the time interval in milliseconds between each check of the tactile switch status
+
+ * `iodirRegister`, `gpioRegister` and `olatRegister` are our local copies of the values in the corresponding registers in the port expander.
+
+\* See the [MCP23008 datasheet](http://ww1.microchip.com/downloads/en/DeviceDoc/21919e.pdf)for details.
+
+The method `InitializeSystem()`
+
+`InitializeSystem()` does the following:
+
+ * Sets up the I2C communications on the UP Board
+
+ * Configures the port expander to be able to turn the LED on and off and to get the tactile switch status
+
+ * Initializes the local copies of the port expander registers IODIR, GPIO and OLAT
+
+ * Sets up two timers - One for controlling the LED and another for checking the tactile switch status
+
+When complete, the variable `i2cPortExpander` will be our handle to the UP Board I2C bus.
+
+```csharp
+private async void InitializeSystem()
+{
+ byte[] i2CWriteBuffer;
+ byte[] i2CReadBuffer;
+ byte bitMask;
+ // initialize I2C communications
+ try
+ {
+ var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
+ string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
+ var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
+ i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // initialize I2C Port Expander registers
+ try
+ {
+ // initialize local copies of the IODIR, GPIO, and OLAT registers
+ i2CReadBuffer = new byte[1];
+ // read in each register value on register at a time (could do this all at once but
+ // for example clarity purposes we do it this way)
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
+ iodirRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
+ gpioRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
+ olatRegister = i2CReadBuffer[0];
+ // configure the LED pin output to be logic high, leave the other pins as they are.
+ olatRegister |= LED_GPIO_PIN;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ // configure only the LED pin to be an output and leave the other pins as they are.
+ // input is logic low, output is logic high
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
+ iodirRegister &= bitMask;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // setup our timers, one for the LED blink interval, the other for checking button status
+ try
+ {
+ ledTimer = new DispatcherTimer();
+ ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
+ ledTimer.Tick += LedTimer_Tick;
+ ledTimer.Start();
+ buttonStatusCheckTimer = new DispatcherTimer();
+ buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
+ buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
+ buttonStatusCheckTimer.Start();
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+}
+```
+
+The method `FlipLED()`
+
+`FlipLED()` is called by the ledTimer whenever the LED timer has reached the end of its interval length. Initially, this is 500 milliseconds but can be changed by a user via the slider displayed on a monitor connected to the UP Board.
+
+ This method determines if the LED is currently on or off.
+
+ * If the LED is currently off, it sends commands to the port expander to turn the LED on and sets the color of the circle on the display to red.
+
+ * If the LED is currently on, it sends commands to the port expander to turn the LED off and sets the color of the circle on the display to gray.
+
+```csharp
+private void FlipLED()
+{
+ byte bitMask;
+ if (isLedOn == true)
+ {
+ // turn off the LED
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ else
+ {
+ // turn on the LED
+ isLedOn = true;
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
+ olatRegister &= bitMask;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = redBrush;
+ }
+}
+```
+
+`CheckButtonStatus()` communicates with the port expander to get the tactile switch status. It reads the GPIO register on the port expander and checks the value of the second bit which corresponds to the status of the switch.
+
+ * If the second bit of the GPIO register is '0' then the switch is currently pressed.
+
+ * If the second bit of the GPIO register is '1' then the switch is currently released.
+
+This method updates the text in Textbox displayed to the screen to reflect the status of the switch.
+
+```csharp
+private void CheckButtonStatus()
+{
+ byte[] readBuffer = new byte[1];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
+ // a button press results in a logic low for the GPIO pin
+ if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
+ {
+ ButtonStatusText.Text = "Button Status: Pressed";
+ isButtonPressed = true;
+ }
+ else
+ {
+ ButtonStatusText.Text = "Button Status: Released";
+ isButtonPressed = false;
+ }
+}
+```
+
+## Step 9: Deploy and Run the App
+
+Let's build, deploy and run the app on our UP Board.
+
+* If not already open, open in Visual Studio the app you created with the code above.
+
+After several moments, you will see the screen attached to the UP Board change to show a circle, some text, and a slider. The LED on the breadboard will begin to turn on and off.
+
+Congratulations! You've successfully connected an I2C port expander to your device.
+
+### The complete MainPage.xaml.cs code
+
+```csharp
+using System;
+//using System.Diagnostics;
+using System.Collections.Generic;
+using System.IO;
+using System.Linq;
+using System.Runtime.InteropServices.WindowsRuntime;
+using Windows.Foundation;
+using Windows.Foundation.Collections;
+using Windows.UI.Xaml;
+using Windows.UI.Xaml.Controls;
+using Windows.UI.Xaml.Controls.Primitives;
+using Windows.UI.Xaml.Data;
+using Windows.UI.Xaml.Input;
+using Windows.UI.Xaml.Media;
+using Windows.UI.Xaml.Navigation;
+using Windows.Devices.Enumeration;
+using Windows.Devices.I2c;
+// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=402352&clcid=0x409
+namespace I2cPortExpanderLedSample
+{
+ ///
+ /// An empty page that can be used on its own or navigated to within a Frame.
+ ///
+ public sealed partial class MainPage : Page
+ {
+ // use these constants for controlling how the I2C bus is setup
+ private const string I2C_CONTROLLER_NAME = "I2C0"; //specific to UP Board
+ private const byte PORT_EXPANDER_I2C_ADDRESS = 0x20; // 7-bit I2C address of the port expander
+ private const byte PORT_EXPANDER_IODIR_REGISTER_ADDRESS = 0x00; // IODIR register controls the direction of the GPIO on the port expander
+ private const byte PORT_EXPANDER_GPIO_REGISTER_ADDRESS = 0x09; // GPIO register is used to read the pins input
+ private const byte PORT_EXPANDER_OLAT_REGISTER_ADDRESS = 0x0A; // Output Latch register is used to set the pins output high/low
+ private const double TIMER_INTERVAL = 500; // value is milliseconds and denotes the timer interval
+ private const double BUTTON_STATUS_CHECK_TIMER_INTERVAL = 50;
+ private byte LED_GPIO_PIN = 0x01; // using GPIO pin 0 on the port expander for the LED
+ private byte PUSHBUTTON_GPIO_PIN = 0x02; // using GPIO pin 1 on the port expander for reading the toggle button status
+ private byte iodirRegister; // local copy of I2C Port Expander IODIR register
+ private byte gpioRegister; // local copy of I2C Port Expander GPIO register
+ private byte olatRegister; // local copy of I2C Port Expander OLAT register
+ private I2cDevice i2cPortExpander;
+ private DispatcherTimer ledTimer;
+ private DispatcherTimer buttonStatusCheckTimer;
+ private bool isLedOn = false;
+ private bool isButtonPressed = false;
+ private SolidColorBrush redBrush = new SolidColorBrush(Windows.UI.Colors.Red);
+ private SolidColorBrush grayBrush = new SolidColorBrush(Windows.UI.Colors.LightGray);
+ public MainPage()
+ {
+ this.InitializeComponent();
+ // Register for the unloaded event so we can clean up upon exit
+ Unloaded += MainPage_Unloaded;
+ InitializeSystem();
+ }
+ private async void InitializeSystem()
+ {
+ byte[] i2CWriteBuffer;
+ byte[] i2CReadBuffer;
+ byte bitMask;
+ // initialize I2C communications
+ try
+ {
+ var i2cSettings = new I2cConnectionSettings(PORT_EXPANDER_I2C_ADDRESS);
+ i2cSettings.BusSpeed = I2cBusSpeed.FastMode;
+ string deviceSelector = I2cDevice.GetDeviceSelector(I2C_CONTROLLER_NAME);
+ var i2cDeviceControllers = await DeviceInformation.FindAllAsync(deviceSelector);
+ i2cPortExpander = await I2cDevice.FromIdAsync(i2cDeviceControllers[0].Id, i2cSettings);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // initialize I2C Port Expander registers
+ try
+ {
+ // initialize local copies of the IODIR, GPIO, and OLAT registers
+ i2CReadBuffer = new byte[1];
+ // read in each register value on register at a time (could do this all at once but
+ // for example clarity purposes we do it this way)
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS }, i2CReadBuffer);
+ iodirRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, i2CReadBuffer);
+ gpioRegister = i2CReadBuffer[0];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS }, i2CReadBuffer);
+ olatRegister = i2CReadBuffer[0];
+ // configure the LED pin output to be logic high, leave the other pins as they are.
+ olatRegister |= LED_GPIO_PIN;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ // configure only the LED pin to be an output and leave the other pins as they are.
+ // input is logic low, output is logic high
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN); // set the LED GPIO pin mask bit to '0', all other bits to '1'
+ iodirRegister &= bitMask;
+ i2CWriteBuffer = new byte[] { PORT_EXPANDER_IODIR_REGISTER_ADDRESS, iodirRegister };
+ i2cPortExpander.Write(i2CWriteBuffer);
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ // setup our timers, one for the LED blink interval, the other for checking button status
+ try
+ {
+ ledTimer = new DispatcherTimer();
+ ledTimer.Interval = TimeSpan.FromMilliseconds(TIMER_INTERVAL);
+ ledTimer.Tick += LedTimer_Tick;
+ ledTimer.Start();
+ buttonStatusCheckTimer = new DispatcherTimer();
+ buttonStatusCheckTimer.Interval = TimeSpan.FromMilliseconds(BUTTON_STATUS_CHECK_TIMER_INTERVAL);
+ buttonStatusCheckTimer.Tick += ButtonStatusCheckTimer_Tick;
+ buttonStatusCheckTimer.Start();
+ }
+ catch (Exception e)
+ {
+ System.Diagnostics.Debug.WriteLine("Exception: {0}", e.Message);
+ return;
+ }
+ }
+ private void MainPage_Unloaded(object sender, object args)
+ {
+ /* Cleanup */
+ i2cPortExpander.Dispose();
+ }
+ private void FlipLED()
+ {
+ byte bitMask;
+ if (isLedOn == true)
+ {
+ // turn off the LED
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ else
+ {
+ // turn on the LED
+ isLedOn = true;
+ bitMask = (byte)(0xFF ^ LED_GPIO_PIN);
+ olatRegister &= bitMask;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = redBrush;
+ }
+ }
+ private void TurnOffLED()
+ {
+ isLedOn = false;
+ olatRegister |= LED_GPIO_PIN;
+ i2cPortExpander.Write(new byte[] { PORT_EXPANDER_OLAT_REGISTER_ADDRESS, olatRegister });
+ Led.Fill = grayBrush;
+ }
+ private void CheckButtonStatus()
+ {
+ byte[] readBuffer = new byte[1];
+ i2cPortExpander.WriteRead(new byte[] { PORT_EXPANDER_GPIO_REGISTER_ADDRESS }, readBuffer);
+ // a button press results in a logic low for the GPIO pin
+ if ((byte)(readBuffer[0] & PUSHBUTTON_GPIO_PIN) == 0x00 )
+ {
+ ButtonStatusText.Text = "Button Status: Pressed";
+ isButtonPressed = true;
+ }
+ else
+ {
+ ButtonStatusText.Text = "Button Status: Released";
+ isButtonPressed = false;
+ }
+ }
+ private void LedTimer_Tick(object sender, object e)
+ {
+ if (isButtonPressed == false)
+ {
+ FlipLED();
+ }
+ }
+ private void ButtonStatusCheckTimer_Tick(object sender, object e)
+ {
+ CheckButtonStatus();
+ }
+ private void Delay_ValueChanged(object sender, RangeBaseValueChangedEventArgs e)
+ {
+ if (ledTimer == null)
+ {
+ return;
+ }
+ if (e.NewValue == Delay.Minimum)
+ {
+ DelayText.Text = "Stopped";
+ ledTimer.Stop();
+ TurnOffLED();
+ }
+ else
+ {
+ DelayText.Text = e.NewValue + "ms";
+ ledTimer.Interval = TimeSpan.FromMilliseconds(e.NewValue);
+ ledTimer.Start();
+ }
+ }
+ }
+}
+```
diff --git a/samples/IoTEnterpriseDefault/CS/README.md b/samples/IoTEnterpriseDefault/CS/README.md
index ae131cd84..54b8c7909 100644
--- a/samples/IoTEnterpriseDefault/CS/README.md
+++ b/samples/IoTEnterpriseDefault/CS/README.md
@@ -1,167 +1,167 @@
----
-page_type: sample
-urlFragment: iotcore-defaultapp
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: The current IoT Core Default App, a fully featured sample app for Windows 10 IoT Enterprise.
----
-
-# Windows 10 IoT Enterprise Default App Overview
-
-This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
-
-Windows 10 IoT Enterprise Default App looks like this:
-
-
-
-This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
-
-## Leveraging the Windows IoT Enterprise Default App
-
-The Windows IoT Enterprise Default App can be customized and extended, or you can use the source code as an example for your own app.
-
-To try this out for yourself, download the zip of our samples or check out the code for the Windows IoT Enterprise Default App. Open the project from Visual Studio 2019.
-
-For UP Board, set the target architecture to 'x64'.
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-Click the Start button to search for the app by name, and then launch it.
-
-As shown below, in some cases you may configure default settings and features on your customer system on behalf of the end user. However, if you turn these settings and features on by default or if diagnostics are above the basic setting, you must:
-
-* Notify the end user that these features have been enable and provide the end user with the link to Microsoft's Privacy Statement web page [here](http://go.microsoft.com/fwlink/?LinkId=521839).
-* Secure consent from the relevant end user to enable such features by default (as required by applicable law).
-* Provide end users the ability to change the Diagnostics setting back to the basic setting.
-* If you enable Microsoft Accounts and you have access to end user data, if the end user deletes the Microsoft Account, you must enable simultaneous deletion of all the end user's Microsoft Account data on the device.
-
-## Out-of-Box Experience (OOBE)
-
-The out-of-box experience for the IoT Enterprise Default App is as lean as it gets. The first pages will ask for a default language and wi-fi settings. From there, in order for your app to be GDPR-compliant, you must have a diagnostic data screen and, if you're planning to track location, you will need to have a location permissions screen too. Examples of both are shown below.
-
-
-
-
-## Command Bar
-The Command Bar is the persistant horizonatal bar located at the bottom of the screen. This provides easy access to the following funtionality:
-- Forward and backward page navigation
-- Basic device info without leaving the current page
-- Turning fullscreen mode on or off
-- Advance shortcuts
-- Page specific buttons
-
-There are a lot buttons in the Command Bar, and sometimes those buttons can be confusing or hidden. To expand the Command Bar and access those buttons, please press the menu button in the bottom right:
-
-
-
-## Start Menu - Play
-
-The Start Menu is where most plug and play features live.
-
-### Weather
-Using data from the National Weather Service, the weather page renders weather information in your current location.
-
-### Web Browser
-The web browser allows you to pull up most sites from the web.
-
-### Music
-This page will play MP3 and WAV files from the **Music Library**, that can be accessed from the web
-
-### Slideshow
-This page will display any PNG or JPEG image files from the **Pictures Library**, that can be accessed from the web
-
-### Draw
-This page allows you to test out Windows 10 IoT Enterprise's inking capabilities.
-
-## Start Menu - Explore
-
-### Apps
-This page allows you to launch other foreground applications installed on the device. Launching an application will suspend IoT Enterprise Default App, which can be relaunched by using App Packages.
-
-Nothing special is needed to have your foreground application listed in the page, simply install or deploy the application. After successful installation or deployment, re-navigate to the Apps page to refresh the list of applications.
-
-Note that there are a couple of auto-generated OS related applications that we filter out, you can find the list of app names in the samples.
-
-### Notifications
-This page will list the past 20 notifications since IoT Enterprise Default App was launched. When IoT Enterprise Default App is running in debug mode, buttons are added that will create test notifications.
-
-### Logs
-This page will list any auto-generated crash or error logs, which then can be taken off the device and analyzed.
-
-### GitHub
-This page will take you to the open-sourced GitHub location of the IoT Enterprise Default App code.
-
-## Start Menu - Windows Device Portal
-
-The pages in this section leverage the Windows Device Portal REST APIs, which requires you to sign in using your Windows Device Portal credentials.
-
-## Device Information
-
-This page allows you to see the different features for your device including Ethernet, OS version, connected devices, and more.
-
-## Command Line
-
-This page allows you to run commands directly on your device.
-
-To enable this feature you have to set a registry key so that the app can run the commands.
-
-Some commands require administrator access. For security purposes the app uses a non-admin account by default to run commands. If you need to run a command as an admin you can type "RunAsAdmin " in the command line prompt.
-
-## Settings
-You'll be able to configure a number of settings here including Wi-Fi, Bluetooth, power options, and more.
-
-### App Settings
-The **App Settings** section allows you to configure various settings for pages in the app.
-
-Some of the settings you can customize are:
-
-##### Weather Settings
-* Change the location
- > This feature is only enabled if you have provided a valid [Bing Map Service Token](https://msdn.microsoft.com/en-us/library/ff428642.aspx). To pass the token to the app, create a **MapToken.config** file in the LocalState folder of the app (e.g. C:\Data\USERS\\[User Account]\AppData\Packages\\[Package Full Name]\LocalState\MapToken.config) and restart the app.
-* Expand the map
-* Enable/disable map flipping so that the map and the weather switch places periodically to prevent screen burn-in
-
-##### Web Browser Settings
-* Set the home page for the Web Browser
-
-##### Slideshow Settings
-* Set the slideshow interval
-
-##### Appearance
-* Use MDL2 Assets instead of Emojis for the tile icons
-* Set the tile width and height
-* Set UI scaling - Automatic scaling is set by default
-* Set the tile color
-
-#### System
-Change the language, keyboard layout, and time zone.
-
-#### Network & Wi-Fi
-View network adapter properties or connect to an available Wi-Fi network.
-
-#### Bluetooth
-Pair with a Bluetooth device.
-
-#### App Updates
-Check for app updates or change automatic update settings.
-
-#### Power Options
-Restart or shutdown the device.
-
-#### Diagnostics
-Select the amount of diagnostic data you wish to provide Microsoft. We encourage users to opt into **Full** diagnostic data so we can diagnose issues quickly and make improvements to the product.
-
-##### Basic
-Send only info about your device, its settings and capabilities, and whether it is performing properly.
-
-##### Full
-Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
-
-#### Location
-Allow or deny the app access to your location.
+---
+page_type: sample
+urlFragment: iotcore-defaultapp
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: The current IoT Core Default App, a fully featured sample app for Windows 10 IoT Enterprise.
+---
+
+# Windows 10 IoT Enterprise Default App Overview
+
+This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
+
+Windows 10 IoT Enterprise Default App looks like this:
+
+
+
+This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
+
+## Leveraging the Windows IoT Enterprise Default App
+
+The Windows IoT Enterprise Default App can be customized and extended, or you can use the source code as an example for your own app.
+
+To try this out for yourself, download the zip of our samples or check out the code for the Windows IoT Enterprise Default App. Open the project from Visual Studio 2019.
+
+For UP Board, set the target architecture to 'x64'.
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+Click the Start button to search for the app by name, and then launch it.
+
+As shown below, in some cases you may configure default settings and features on your customer system on behalf of the end user. However, if you turn these settings and features on by default or if diagnostics are above the basic setting, you must:
+
+* Notify the end user that these features have been enable and provide the end user with the link to Microsoft's Privacy Statement web page [here](http://go.microsoft.com/fwlink/?LinkId=521839).
+* Secure consent from the relevant end user to enable such features by default (as required by applicable law).
+* Provide end users the ability to change the Diagnostics setting back to the basic setting.
+* If you enable Microsoft Accounts and you have access to end user data, if the end user deletes the Microsoft Account, you must enable simultaneous deletion of all the end user's Microsoft Account data on the device.
+
+## Out-of-Box Experience (OOBE)
+
+The out-of-box experience for the IoT Enterprise Default App is as lean as it gets. The first pages will ask for a default language and wi-fi settings. From there, in order for your app to be GDPR-compliant, you must have a diagnostic data screen and, if you're planning to track location, you will need to have a location permissions screen too. Examples of both are shown below.
+
+
+
+
+## Command Bar
+The Command Bar is the persistant horizonatal bar located at the bottom of the screen. This provides easy access to the following funtionality:
+- Forward and backward page navigation
+- Basic device info without leaving the current page
+- Turning fullscreen mode on or off
+- Advance shortcuts
+- Page specific buttons
+
+There are a lot buttons in the Command Bar, and sometimes those buttons can be confusing or hidden. To expand the Command Bar and access those buttons, please press the menu button in the bottom right:
+
+
+
+## Start Menu - Play
+
+The Start Menu is where most plug and play features live.
+
+### Weather
+Using data from the National Weather Service, the weather page renders weather information in your current location.
+
+### Web Browser
+The web browser allows you to pull up most sites from the web.
+
+### Music
+This page will play MP3 and WAV files from the **Music Library**, that can be accessed from the web
+
+### Slideshow
+This page will display any PNG or JPEG image files from the **Pictures Library**, that can be accessed from the web
+
+### Draw
+This page allows you to test out Windows 10 IoT Enterprise's inking capabilities.
+
+## Start Menu - Explore
+
+### Apps
+This page allows you to launch other foreground applications installed on the device. Launching an application will suspend IoT Enterprise Default App, which can be relaunched by using App Packages.
+
+Nothing special is needed to have your foreground application listed in the page, simply install or deploy the application. After successful installation or deployment, re-navigate to the Apps page to refresh the list of applications.
+
+Note that there are a couple of auto-generated OS related applications that we filter out, you can find the list of app names in the samples.
+
+### Notifications
+This page will list the past 20 notifications since IoT Enterprise Default App was launched. When IoT Enterprise Default App is running in debug mode, buttons are added that will create test notifications.
+
+### Logs
+This page will list any auto-generated crash or error logs, which then can be taken off the device and analyzed.
+
+### GitHub
+This page will take you to the open-sourced GitHub location of the IoT Enterprise Default App code.
+
+## Start Menu - Windows Device Portal
+
+The pages in this section leverage the Windows Device Portal REST APIs, which requires you to sign in using your Windows Device Portal credentials.
+
+## Device Information
+
+This page allows you to see the different features for your device including Ethernet, OS version, connected devices, and more.
+
+## Command Line
+
+This page allows you to run commands directly on your device.
+
+To enable this feature you have to set a registry key so that the app can run the commands.
+
+Some commands require administrator access. For security purposes the app uses a non-admin account by default to run commands. If you need to run a command as an admin you can type "RunAsAdmin " in the command line prompt.
+
+## Settings
+You'll be able to configure a number of settings here including Wi-Fi, Bluetooth, power options, and more.
+
+### App Settings
+The **App Settings** section allows you to configure various settings for pages in the app.
+
+Some of the settings you can customize are:
+
+##### Weather Settings
+* Change the location
+ > This feature is only enabled if you have provided a valid [Bing Map Service Token](https://msdn.microsoft.com/en-us/library/ff428642.aspx). To pass the token to the app, create a **MapToken.config** file in the LocalState folder of the app (e.g. C:\Data\USERS\\[User Account]\AppData\Packages\\[Package Full Name]\LocalState\MapToken.config) and restart the app.
+* Expand the map
+* Enable/disable map flipping so that the map and the weather switch places periodically to prevent screen burn-in
+
+##### Web Browser Settings
+* Set the home page for the Web Browser
+
+##### Slideshow Settings
+* Set the slideshow interval
+
+##### Appearance
+* Use MDL2 Assets instead of Emojis for the tile icons
+* Set the tile width and height
+* Set UI scaling - Automatic scaling is set by default
+* Set the tile color
+
+#### System
+Change the language, keyboard layout, and time zone.
+
+#### Network & Wi-Fi
+View network adapter properties or connect to an available Wi-Fi network.
+
+#### Bluetooth
+Pair with a Bluetooth device.
+
+#### App Updates
+Check for app updates or change automatic update settings.
+
+#### Power Options
+Restart or shutdown the device.
+
+#### Diagnostics
+Select the amount of diagnostic data you wish to provide Microsoft. We encourage users to opt into **Full** diagnostic data so we can diagnose issues quickly and make improvements to the product.
+
+##### Basic
+Send only info about your device, its settings and capabilities, and whether it is performing properly.
+
+##### Full
+Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
+
+#### Location
+Allow or deny the app access to your location.
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Contracts/Properties/SmartDisplay.Contracts.rd.xml b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Contracts/Properties/SmartDisplay.Contracts.rd.xml
index 19f3dc074..d66edc3f8 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Contracts/Properties/SmartDisplay.Contracts.rd.xml
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Contracts/Properties/SmartDisplay.Contracts.rd.xml
@@ -1,33 +1,33 @@
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Properties/SmartDisplay.Features.rd.xml b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Properties/SmartDisplay.Features.rd.xml
index dda7aa3d8..4891bd422 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Properties/SmartDisplay.Features.rd.xml
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Properties/SmartDisplay.Features.rd.xml
@@ -1,33 +1,33 @@
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Strings/en-US/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Strings/en-US/Resources.resw
index 20f2cdb46..d5be57304 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Strings/en-US/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Features/Strings/en-US/Resources.resw
@@ -1,138 +1,138 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Clear
-
-
- Guess
-
-
- Write a number between 0 and 9
-
-
- This page uses a pre-trained ONNX model, along with Windows Machine Learning to guess the number you write.
-
-
- WinML is only available in OS builds 17728 or higher
-
-
- WinML not available
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Clear
+
+
+ Guess
+
+
+ Write a number between 0 and 9
+
+
+ This page uses a pre-trained ONNX model, along with Windows Machine Learning to guess the number you write.
+
+
+ WinML is only available in OS builds 17728 or higher
+
+
+ WinML not available
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Utils/Properties/SmartDisplay.Utils.rd.xml b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Utils/Properties/SmartDisplay.Utils.rd.xml
index 1c49f7ce7..d3c7087b4 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay.Utils/Properties/SmartDisplay.Utils.rd.xml
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay.Utils/Properties/SmartDisplay.Utils.rd.xml
@@ -1,33 +1,33 @@
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Assets/Messages/LogDescription.txt b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Assets/Messages/LogDescription.txt
index a2dcc4fb6..17a49554a 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Assets/Messages/LogDescription.txt
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Assets/Messages/LogDescription.txt
@@ -1 +1 @@
-Logs are auto-generated when the app crashes due to an unhandled exception. However, you can also manually generate a log by tapping on the command bar below and selecting "Quick-Save Log".
+Logs are auto-generated when the app crashes due to an unhandled exception. However, you can also manually generate a log by tapping on the command bar below and selecting "Quick-Save Log".
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Properties/Default.rd.xml b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Properties/Default.rd.xml
index 461bc4c13..80a960ce3 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Properties/Default.rd.xml
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/de-DE/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/de-DE/Resources.resw
index 6f915ae95..7876e742d 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/de-DE/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/de-DE/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- AAD v2 verwenden
-
-
- Zugriff widerrufen
-
-
- Beschreibung:
-
-
- DHCP-Server:
-
-
- DNS:
-
-
- Gateway-Adresse:
-
-
- IPv4-Adresse:
-
-
- Name:
-
-
- Physische Adresse:
-
-
- Subnetzmaske:
-
-
- Typ:
-
-
- App-Version
-
-
- Apps
-
-
- Sie sind im Begriff, eine externe App zu starten. Sie müssen das Windows-Geräteportal verwenden, um zu dieser App zurückzukehren. Fortfahren?
- Dialog prompt for launching external apps
-
-
- Apps
-
-
- App-Einstellungen
-
-
- Legen Sie Nutzungszeiten fest, damit wir wissen, wann Sie dieses Gerät in der Regel nutzen. Während der Nutzungszeiten werden keine automatischen Neustarts durchgeführt.
-
-
- Die neuen Start- und Endzeiten können nicht gespeichert werden, da sie identisch sind. Wählen Sie neue Zeiten, oder deaktivieren Sie die Funktion.
-
-
- Erweiterte Optionen
- Advanced section title
-
-
- Kontrollieren Sie die einzelnen Update-Schritte zum Abrufen, Herunterladen und Installieren.
-
-
- Optionen für automatische Updates
- Auto-Update section title
-
-
- Zulassen, dass die App außerhalb der Nutzungszeit Updates installiert
-
-
- App-Updates
- App update display dialog header
-
-
- Letzte Überprüfung: {0}, {1}
- {0} is date, {1} is time
-
-
- Zeitpunkt der letzten Suche nach Updates kann nicht ermittelt werden.
-
-
- App-Updates
- Label for setting item to check for app updates
-
-
- Bei MSA und AAD anmelden
-
-
- Melden Sie sich mit Ihrem Organisationskonto bei AAD an.
-
-
- Azure AD (AAD)-Anmeldung
-
-
- AAD
-
-
- Authentifiziert Microsoft Graph und andere Ressourcen
-
-
- Authentifiziert nur Microsoft Graph
-
-
- Abbrechen
-
-
- Ihr Organisationskonto
-
-
- Wenn Sie an einem Punkt nicht weiterkommen und den Anmeldeassistenten nicht beenden können, warten Sie {0} Sekunden, und sie sollten zur App zurückgeleitet werden.
-
-
- Anmeldung…
-
-
- Abmeldung...
-
-
- Melden Sie sich hier bei Ihrem Microsoft-Konto an.
-
-
- Microsoft-Konto (MSA)-Anmeldung
-
-
- MSA
-
-
- Authentifizierung
-
-
- Microsoft-Anmeldung
-
-
- Fehler beim Anmelden ({0})
-
-
- Anmeldung erfolgreich ({0})
-
-
- Anmelden
-
-
- Abgemeldet: {0}
-
-
- Abmelden
-
-
- Automatische Wiedergabe
- Music player page auto-play toggle text
-
-
- Automatische Skalierung
-
-
- Update aufgrund von niedrigem Akkustand fehlgeschlagen.
- App update error, low battery
-
-
- Es wird versucht, mit {0} ({1}) zu koppeln.
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Kopplung mit {0} ({1}) wird ausgeführt.
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- Stimmt die auf dem Gerät angezeigte PIN mit {0} überein?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Unbekannt
- Text displayed when the Bluetooth device name is unknown
-
-
- Derzeit gekoppelt
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Koppelungsbereit
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Unbekannter Status
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Geben Sie die folgende PIN auf dem Gerät ein, das Sie koppeln möchten: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Geben Sie die PIN ein:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Eingehende Kopplungsanforderung von {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Dieses Gerät ist bereits für eingehende Kopplung registriert. (Unterstützte Zeremonien: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Fehler beim Registrieren für eingehende Kopplung.
- Text displayed when Inbound pairing handler registration fails
-
-
- Registrierung für eingehende Kopplung war erfolgreich. (Unterstützte Zeremonien: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- Die eingegebene PIN ist falsch.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- Auf diesem Gerät wurde kein verwendbarer Bluetooth-Adapter gefunden: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Koppeln
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Fehler beim Koppeln mit {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Erfolgreich mit {0} ({1}) gekoppelt.
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Standard
- Text label for the corresponding device pairing protection level
-
-
- Verschlüsselung und Authentifizierung
- Text label for the corresponding device pairing protection level
-
-
- Verschlüsselung
- Text label for the corresponding device pairing protection level
-
-
- Keine
- Text label for the corresponding device pairing protection level
-
-
- Ihr Gerät ist nun sichtbar und zur Kopplung mit anderen Bluetooth-Geräten bereit.
- Text displayed when StartWatcher is invoked
-
-
- Ihr Gerät sucht nicht mehr nach anderen Bluetooth-Geräten.
- Text displayed when StopWatcher is invoked
-
-
- Entkoppeln
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Fehler beim Entkoppeln von {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Erfolgreich von {0} ({1}) entkoppelt.
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Startseite
-
-
- Webbrowser
-
-
- Abbrechen
-
-
- Der Verzeichniswechsel wird derzeit nicht unterstützt. Verwenden Sie in Ihren Befehlen vollständige Pfade.
-
-
- Zeitzone
- Time zone text
-
-
- Suche nach Updates...
- App update status
-
-
- Nach Updates suchen
-
-
- Konten löschen
-
-
- Beim Löschen Ihrer Konten ist ein Problem aufgetreten.
-
-
- Dadurch werden die folgenden Windows-Konten gelöscht:
-{0}
-
-Fortfahren?
-
-
- Konten wurden gelöscht.
-
-
- Konten werden gelöscht...
-
-
- Löschen
-
-
- Schließen
-
-
- Ihr Gerät ist nicht zur Ausführung des Befehlszeilenprozessors berechtigt.
-Führen Sie den folgenden Befehl als „Administrator“ auf Ihrem Gerät aus, um ihn zu aktivieren:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Sie können den Befehl auf der Seite „Prozesse“ des IoT Windows-Geräteportals ausführen oder mithilfe von PowerShell eine Verbindung mit Ihrem Windows IoT-Gerät herstellen.
-Weitere Informationen finden Sie unter http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Fehler beim Ausführen des Befehls als Administrator: {0}
-
-
- Fehler beim Aktivieren des Befehlszeilenprozessors (cmd.exe) auf Ihrem Gerät: {0}
-
-
- Der Befehlszeilenprozessor (cmd.exe) wurde erfolgreich auf Ihrem Gerät aktiviert.
-
-
- Kachelfarbe
-
-
- Zurück
- Back UI navigation
-
-
- Geräteinformationen anzeigen
-
-
- Weiter
- Forward UI navigation
-
-
- Vollbild ein/aus
-
-
- Anzeige klonen
- Clone current view to another display
-
-
- Protokoll schnell speichern
-
-
- Sitzungsprotokoll
-
-
- Standardseite festlegen
-
-
- Befehl abgebrochen.
-
-
- Befehlszeile eingeben
- Placeholder for command line input text box
-
-
- Fehler beim Ausführen der Befehlszeile: {0}
-
-
- Befehlszeile
-
-
- Befehlszeile
- Title for command line page
-
-
- Zeitüberschreitung beim Befehl nach {0} Sekunden ohne Ausgabe.
-
-
- Computername
-
-
- Bestätigung
-
-
- Automatisch verbinden
-
-
- Automatisch verbinden
-
-
- Verbinden
-
-
- Verbinden
-
-
- Verbundene Geräte
-
-
- Update fehlgeschlagen. Stellen Sie eine WLAN-Verbindung her, und versuchen Sie es noch mal.
- App update error, poor connection
-
-
- Weiter
-
-
- Befehlsausgabe konnte nicht analysiert werden.
-
-
- Aktueller Ring
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- App-Standardseite
-
-
- Die Standardsprache wird automatisch ausgewählt…
-
-
- {0} Protokolle löschen
- {0} is plural number of logs
-
-
- {0} Protokoll löschen
- {0} is singular number of logs
-
-
- {0} Protokoll löschen?
- {0} is singular number of logs
-
-
- {0} Protokolle löschen?
- {0} is plural number of logs
-
-
- Auswahl löschen
-
-
- Azure-Geräte-ID
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- Zur Geräteseite wechseln
-
-
- IP-Adresse: {0}
-Betriebssystemversion: {1}
-App-Version: {2}
-
-
- App-Version
- Field label
-
-
- Gerätename
- Field label
-
-
- IP-Adresse
- Field label
-
-
- Netzwerk
- Field label
-
-
- Betriebssystemversion
- Label for OS Version field in main page
-
-
- um mit der Entwicklung zu beginnen.
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Geräteinfo
-
-
- Besuchen Sie
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Die Seite, auf die Sie zugreifen möchten, erfordert die Verwendung von Windows-Geräteportal (WDP)-APIs. Melden Sie sich mit Ihren WDP-Anmeldedaten an, um fortzufahren.
-
-
- Beim Anmelden ist ein Problem aufgetreten.
-
-
- Anmeldung beim Geräteportal erfolgreich!
-
-
- Anmeldedaten für das Geräteportal werden überprüft...
-
-
- Beim Abrufen des Wetters ist ein Problem aufgetreten, noch mal versuchen?
-
-
- Direkte Verbindungen
-
-
- Trennen
- This disconnects the connected network
-
-
- Anzeigesprache aktualisiert: {0}
-
-
- Domäne
-
-
- Download abgeschlossen!
- App update status
-
-
- Fehler beim Download. Versuchen Sie es später noch mal!
-
-
- Update wird heruntergeladen
- App update status
-
-
- Updates herunterladen
-
-
- Zeichnen
-
-
- „{0} Protokolle wurden an „{1}“ gesendet.“
- {0} is plural number of logs, {1} is email address
-
-
- „{0} Protokoll wurde an „{1}“ gesendet.“
- {0} is singular number of logs, {1} is email address
-
-
- Protokoll per E-Mail senden
-
-
- Möchten Sie „{0}“ per E-Mail an sich selbst senden?
- {0} is filename
-
-
- Beim Senden des Protokolls per E-Mail ist ein Problem aufgetreten: {0}
- {0} is exception message
-
-
- Ihre Protokolle befinden sich auf der Seite „Protokolle“.
-
-
- „{0} Protokoll per E-Mail an sich selbst senden?“
- {0} is singular number of logs
-
-
- Beim Senden der Protokolle per E-Mail ist ein Problem aufgetreten: {0}
- {0} is an exception message
-
-
- {0} Protokolle per E-Mail an sich selbst senden?
- {0} is plural number of logs
-
-
- Protokolle per E-Mail senden
-
-
- Auswahl per E-Mail senden
-
-
- Befehlszeilenprozessor aktivieren
-
-
- Bildschirmschoner
- Toggle switch for enabling the screensaver
-
-
- Endzeit
-
-
- Fehler
-
-
- Beim Abrufen der Wetterinfos ist ein Problem aufgetreten.
-
-
- Ethernet
- Field label
-
-
- ETW-Anbieter-GUID: {0}
- Format string for app settings page
-
-
- Befehle werden unter DefaultAccount ausgeführt.
-
-
- Erkunden
-
-
- Datei gespeichert: {0}
- {0} is a filename
-
-
- Test-Flighting
- Device servicing flighting
-
-
- Test-Flighting-Infos
- Device servicing flighting
-
-
- Der Test-Flight-Ring wurde in „{0}“ geändert!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- Beim Ändern des Test-Flight-Rings ist ein Problem aufgetreten.
-
-
- Prognose
- Weather forecast
-
-
- Sie sind im Begriff, den Vollbildmodus zu aktivieren. Zum Beenden müssen Sie auf der Tastatur [Esc] drücken. Fortfahren?
-
-
- Vollbildmodus
-
-
- Drücken Sie [Esc], um den Vollbildmodus zu beenden.
-
-
- Allgemein
-
-
- IoTEnterprise Board
- A generic board name
-
-
- GitHub
-
-
- Hilfe
-
-
- Hilfe
-
-
- Hilfe
-
-
- Eingabesprache der Tastatur aktualisiert: {0}
-
-
- Installation abgeschlossen!
- App update status
-
-
- Fehler bei der Installation. Versuchen Sie es später noch mal!
-
-
- Update wird installiert
- App update status
-
-
- Updates installieren
-
-
- Ungültige Anmeldeinformationen
-
-
- „{0}“ ist ein ungültiger Standort.
- Format string for app settings page
-
-
- „{0}“ ist ein ungültiger Wert. Der Wert muss mindestens 1 sein.
- Format string for app settings page
-
-
- „{0}“ ist ein ungültiger Wert.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Tastaturlayout
- Field label
-
-
- Diese App neu starten, um die neuen Einstellungen zu übernehmen
-
-
- Sprache
-
-
- Sprache
- Field label
-
-
- Wird geladen...
-
-
- Wetterinfo wird geladen...
-
-
- Das Protokoll wurde an „{0}“ gesendet.
- {0} is email address
-
-
- Protokoll gespeichert: {0}
- {0} is filename
-
-
- Protokolle
-
-
- Protokolle
-
-
- Gerätename
- Field label
-
-
- IP-Adresse
- Field label
-
-
- Betriebssystemversion
- Label for OS Version field in main page
-
-
- Dies ist ein Windows 10 IoT Enterprise-Testimage, das nur für Prototypen entworfen wurde. Wenn Sie Ihr Gerät gewerblich anbieten möchten, müssen Sie ein benutzerdefiniertes FFU für optimale Sicherheit verwenden.
- Maker Imager Security Notice
-
-
- Token für Bing-Kartendienst
-
-
- Token für Bing-Kartendienst erforderlich
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Microsoft-Konto (MSA)
-
-
- Aktuelle Wiedergabe
- Music player page status text (currently playing)
-
-
- Wählen Sie einen Song aus, und klicken Sie auf „Wiedergeben“.
- Music player page status text (default)
-
-
- Fügen Sie dem Musikordner mindestens eine Audiodatei hinzu.
-Sie können Musik im Windows-Geräteportal über „Apps“ > „Datei-Explorer“ hinzufügen.
- Music player page instructions text
-
-
- Musik wird geladen
- Music player page loading panel text
-
-
- Wird geladen
- Music player page status text (loading)
-
-
- Keine Musik gefunden
- Music player page no music found prompt text
-
-
- Wiederholen
- Music player page reload button text (no files prompt)
-
-
- Musik
-
-
- Musik
-
-
- Angehalten
- Music player page status text (paused)
-
-
- Wiedergabe
- Music player page status text (playing)
-
-
- Anmelden
-
-
- Unbekannt
-
-
- Menü
-
-
- Netzwerkadapter
-
-
- Verbunden
-
-
- Verbunden
-
-
- Netzwerkanforderungen werden überprüft.
-
-
- Netzwerkanforderungen werden überprüft.
-
-
- Eingeschränkter Internetzugriff
-
-
- Lokaler und Internetzugriff
-
-
- Nur lokaler Netzwerkzugriff
-
-
- Keine Konnektivität
-
-
- NETZWERKINFORMATIONEN
-
-
- Netzwerk nicht verfügbar
-
-
- Netzwerksicherheitsschlüssel eingeben
-
-
- Netzwerksicherheitsschlüssel eingeben
-
-
- Netzwerk & WLAN
-
-
- Netzwerk & WLAN
-
-
- Netzwerkeigenschaften anzeigen
-
-
- Netzwerkeigenschaften
-
-
- Sie werden demnächst auf das Erfassungsportal dieses WLAN-Netzwerks umgeleitet. Fortfahren?
-
-
- Netzwerkumleitung
-
-
- Weiter
-
-
- Weiter
-
-
- Keine Konten gefunden
-
-
- Nein
-
-
- kein Gerätename
-
-
- keine Internetverbindung
-
-
- Keine Protokolle ausgewählt
-
-
- Keine Musik gefunden
- Music player page panel text
-
-
- Keine gefunden
-
-
- Es sind keine ausstehenden Updates zum Download verfügbar.
- App update status
-
-
- Es sind keine ausstehenden Updates zur Installation verfügbar.
- App update status
-
-
- k. A.
-
-
- Benachrichtigungen
-
-
- Benachrichtigungen
-
-
- Keine neuen Updates gefunden.
- Format string displayed when no app updates are found
-
-
- OK
- Button content text for the Bluetooth settings page
-
-
- Sprache auswählen
-
-
- Verbindung herstellen
-
-
- Willkommen bei Windows 10 IoT Enterprise
-
-
- Lassen Sie uns zunächst einige grundlegende Dinge klären.
-
-
- Willkommen bei Windows 10 IoT Enterprise
-
-
- ID der Betriebsversionsedition
-
-
- Betriebssystemedition
-
-
- Betriebssysteminfos
-
-
- Betriebssysteminfos
-
-
- Nicht verfügbar
- Text shown when we cannot retrieve the OS Version
-
-
- Betriebssystemversion
-
-
- Pakete
- Software packages
-
-
- Installierte Pakete
- Software packages
-
-
- Seiteneinstellungen
-
-
- Seiten
-
-
- Passwort
-
-
- Bilder werden geladen
- Default text when no images are available
-
-
- Fügen Sie dem Bilderordner Bilder hinzu.
-Sie können Bilder im Windows-Geräteportal über „Apps“ > „Datei-Explorer“ hinzufügen.
-
-
- Keine Bilder gefunden
- Default text when no images are available
-
-
- Plattform
-
-
- Wiedergeben
-
-
- Energieoptionen
- Label for Setting item to control Power (shutdown/restart)
-
-
- Einfach: Sendet nur Informationen zum Gerät, zu den Einstellungen und Funktionen und dazu, ob es ordnungsgemäß funktioniert.
-
-
- Vollständig: Sendet neben allen Diagnosedaten der Stufe „Einfach“ zusätzliche Informationen zu den besuchten Websites, zur Verwendung von Apps und Features, zur Geräteintegrität und -aktivität sowie erweiterte Fehlerberichte.
-
-
- Wir konnten die Datenschutzeinstellung nicht ändern. Überprüfen Sie Ihren Benutzernamen und das Kennwort, und wiederholen Sie den Vorgang.
-
-
- Legen Sie fest, welche Diagnosedaten an Microsoft gesendet werden sollen. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
-
-
- Diagnosedaten
- Label for Setting item to control Privacy
-
-
- Geben Sie Ihre Anmeldeinformationen ein, um die Datenschutzebene für dieses Gerät festzulegen.
-
-
- Datenschutzebene festlegen
-
-
- Aktualisieren
- Refresh button
-
-
- Song wiederholen
- Music player page repeat toggle text
-
-
- Neu starten
-
-
- Neu starten
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Nutzung: RunAsAdmin-Befehl
-
-Beispiele:
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Speichern
-
-
- Skalierungsfaktor
-
-
- Alles auswählen
-
-
- Telemetriedaten senden
-
-
- Nicht verfügbar
-
-
- Sitzungsprotokoll
-
-
- Beim Festlegen der Standardseite auf {0} ist ein Problem aufgetreten.
- Format string for app settings page
-
-
- Einstellungen
-
-
- Zufällige Wiedergabe
- Music player page shuffle toggle text
-
-
- Herunterfahren
-
-
- Herunterfahren
- Shutdown entry in the shutdown menu
-
-
- Melden Sie sich bei Ihrem Azure AD-Konto an, um diese Funktion zu nutzen.
-
-
- Überspringen
-
-
- Diesen Schritt überspringen
-
-
- Diashowintervall (Sekunden)
-
-
- Diashow
-
-
- Diashow
-
-
- Starten
-
-
- Starten
-
-
- Startzeit
-
-
- Status
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Übermitteln
-
-
- Erfolgreich
-
-
- System
-
-
- Beim Versuch, Ihre Systemeinstellungen zu aktualisieren, ist ein Problem aufgetreten.
- Used within system settings
-
-
- Telemetrie-Ebene
-
-
- Telemetrie
-
-
- Große Testbenachrichtigung
-
-
- Testbenachrichtigung
-
-
- Windows 10 IoT gehört zur Windows 10-Familie und stellt erstklassige Leistung, Sicherheit und Verwaltbarkeit im Internet der Dinge (Internet of Things, IoT) bereit. Die Version nutzt die eingebettete Umgebung, das Ökosystem und die Cloudkonnektivität von Windows und ermöglicht Organisationen die Erstellung einer eigenen IoT-Bereitstellung mit sicheren Geräten, die schnell bereitgestellt, einfach verwaltet und nahtlos in die allgemeine Cloudstrategie eingebunden werden können.
-
-
- Kachelhöhe
-
-
- Personalisierung
-
-
- Kachelbreite
-
-
- Zeitüberschreitung bei Verbindung
-
-
- Zeitzone aktualisiert: {0}
-
-
- Fehler: Kommunikation mit dem Wetterdienst nicht möglich
-
-
- Update aufgrund eines unbekannten Fehlers fehlgeschlagen.
- App update error, unknown
-
-
- Gesamte Auswahl aufheben
-
-
- Unbekannter Fehler
-
-
- Erweiterte Optionen
-
-
- Jetzt überprüfen
-
-
- Jetzt installieren
-
-
- {0} ausstehendes Update
- {0} is singular amount of updates
-
-
- {0} neue Updates gefunden.
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} ausstehende Updates
- {0} is plural amount of updates
-
-
- MDL2-Kachelsymbole verwenden
-
-
- Passwort verwenden
-
-
- Benutzername
-
-
- Windows-Geräteportal
-
-
- Geräteportaleinstellungen
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows-Geräteportal
-
-
- Aktuelle Position ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Ihr Standort
-
-
- Ihr Standort
- Label for map pin
-
-
- Unbekannte Position
- Label for map pin
-
-
- Sensor:
- Label for temperature sensor output
-
-
- Wetter
-
-
- Fehler beim Laden der Wetterseite.
-
-Klicken Sie unten rechts auf dem Bildschirm auf die Schaltfläche „Aktualisieren“, um diese Seite neu zu laden.
-
-Navigieren Sie zu „weatherunlocked.com“, falls Sie nicht über Wetter-API-Schlüssel verfügen. Speichern Sie die Schlüssel in „WeatherTokens.config“ im Ordner „Local State“ dieser App. Aktualisieren Sie anschließend die Seite.
-
-
- Wetter bereitgestellt von:
-
-
- Wetter
-
-
- Webadresse eingeben
-
-
- Webbrowser
-
-
- Willkommen bei Windows IoT Enterprise
-
-
- WLAN
- Label for Wi-Fi list in options page
-
-
- Aktualisieren
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Letzte Überprüfung:
- For a timestamp
-
-
- Letzte Aktualisierung:
- For a timestamp
-
-
- Aktualisierter Zustand:
-
-
- Statusmeldung:
-
-
- Windows Update
-
-
- Windows Update
-
-
- Ungültiges Arbeitsverzeichnis: {0}
-
-
- WPS
-
-
- Dieser App den Zugriff auf Ihren Standort erlauben
-
-
- Wählen Sie Ihre Einstellungen aus, und wählen Sie dann die Option „Annehmen“, um sie zu speichern. Sie können diese Einstellungen jederzeit ändern.
-
-
- Microsoft die Verwendung Ihres Standorts erlauben
-
-
- Vorgang wird automatisch fortgesetzt...
-
-
- Annehmen
-
-
- Zugriff auf Ihre genaue Position für {0} zulassen?
- {0} is the name of a page
-
-
- Standort
-
-
- Sie können dies auch später unter „Einstellungen“ > „Berechtigungen“ ändern.
-
-
- Nein
-
-
- Ja
-
-
- Sie können keine positionsbasierten Features wie Karten und den Wetterbericht oder andere Dienste nutzen, die für die richtige Funktionsweise Ihre Position benötigen.
-
-
- Nutzen Sie positionsbasierte Features wie Karten und den Wetterbericht. Lassen Sie zu, dass diese App Ihren Standort abfragt. Microsoft verwendet Ihre Positionsdaten zur Verbesserung von Positionsdiensten.
-
-
- Sendet nur Informationen zum Gerät, zu den Einstellungen und Funktionen und dazu, ob es ordnungsgemäß funktioniert. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
-
-
- Einfach
-
-
- Sendet neben allen Diagnosedaten der Stufe „Einfach“ zusätzliche Informationen zu den besuchten Websites, zur Verwendung von Apps und Features, zur Geräteintegrität und -aktivität sowie erweiterte Fehlerberichte. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
-
-
- Vollständig
-
-
- Wählen Sie eine Datenschutzeinstellung für Ihr Gerät aus, und klicken Sie zum Speichern auf „Akzeptieren“.
-
-
- Diagnosedaten an Microsoft senden
-
-
- Diagnose
-
-
- Wenn Sie den Zugriff zulassen, können die Funktionen Ihres Geräts von dieser Apps genutzt werden, um Ihren Standort zu ermitteln. Microsoft verwendet Ihre Positionsdaten, um die Positionsdienste zu verbessern. Wenn Sie den Zugriff verweigern, wird von Windows der Zugriff auf Ihren Standort für die App blockiert.
-
-
- Informieren Sie sich über die Optionen zur Privatsphäre.
-
-
- Hier erfahren Sie, wie sich diese Einstellung auf Ihre Privatsphäre auswirkt.
-
-
- Weitere Informationen zu diesen Einstellungen
-
-
- Datenschutzerklärung
-
-
- Ja
-
-
- Ja
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ AAD v2 verwenden
+
+
+ Zugriff widerrufen
+
+
+ Beschreibung:
+
+
+ DHCP-Server:
+
+
+ DNS:
+
+
+ Gateway-Adresse:
+
+
+ IPv4-Adresse:
+
+
+ Name:
+
+
+ Physische Adresse:
+
+
+ Subnetzmaske:
+
+
+ Typ:
+
+
+ App-Version
+
+
+ Apps
+
+
+ Sie sind im Begriff, eine externe App zu starten. Sie müssen das Windows-Geräteportal verwenden, um zu dieser App zurückzukehren. Fortfahren?
+ Dialog prompt for launching external apps
+
+
+ Apps
+
+
+ App-Einstellungen
+
+
+ Legen Sie Nutzungszeiten fest, damit wir wissen, wann Sie dieses Gerät in der Regel nutzen. Während der Nutzungszeiten werden keine automatischen Neustarts durchgeführt.
+
+
+ Die neuen Start- und Endzeiten können nicht gespeichert werden, da sie identisch sind. Wählen Sie neue Zeiten, oder deaktivieren Sie die Funktion.
+
+
+ Erweiterte Optionen
+ Advanced section title
+
+
+ Kontrollieren Sie die einzelnen Update-Schritte zum Abrufen, Herunterladen und Installieren.
+
+
+ Optionen für automatische Updates
+ Auto-Update section title
+
+
+ Zulassen, dass die App außerhalb der Nutzungszeit Updates installiert
+
+
+ App-Updates
+ App update display dialog header
+
+
+ Letzte Überprüfung: {0}, {1}
+ {0} is date, {1} is time
+
+
+ Zeitpunkt der letzten Suche nach Updates kann nicht ermittelt werden.
+
+
+ App-Updates
+ Label for setting item to check for app updates
+
+
+ Bei MSA und AAD anmelden
+
+
+ Melden Sie sich mit Ihrem Organisationskonto bei AAD an.
+
+
+ Azure AD (AAD)-Anmeldung
+
+
+ AAD
+
+
+ Authentifiziert Microsoft Graph und andere Ressourcen
+
+
+ Authentifiziert nur Microsoft Graph
+
+
+ Abbrechen
+
+
+ Ihr Organisationskonto
+
+
+ Wenn Sie an einem Punkt nicht weiterkommen und den Anmeldeassistenten nicht beenden können, warten Sie {0} Sekunden, und sie sollten zur App zurückgeleitet werden.
+
+
+ Anmeldung…
+
+
+ Abmeldung...
+
+
+ Melden Sie sich hier bei Ihrem Microsoft-Konto an.
+
+
+ Microsoft-Konto (MSA)-Anmeldung
+
+
+ MSA
+
+
+ Authentifizierung
+
+
+ Microsoft-Anmeldung
+
+
+ Fehler beim Anmelden ({0})
+
+
+ Anmeldung erfolgreich ({0})
+
+
+ Anmelden
+
+
+ Abgemeldet: {0}
+
+
+ Abmelden
+
+
+ Automatische Wiedergabe
+ Music player page auto-play toggle text
+
+
+ Automatische Skalierung
+
+
+ Update aufgrund von niedrigem Akkustand fehlgeschlagen.
+ App update error, low battery
+
+
+ Es wird versucht, mit {0} ({1}) zu koppeln.
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Kopplung mit {0} ({1}) wird ausgeführt.
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ Stimmt die auf dem Gerät angezeigte PIN mit {0} überein?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Unbekannt
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Derzeit gekoppelt
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Koppelungsbereit
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Unbekannter Status
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Geben Sie die folgende PIN auf dem Gerät ein, das Sie koppeln möchten: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Geben Sie die PIN ein:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Eingehende Kopplungsanforderung von {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Dieses Gerät ist bereits für eingehende Kopplung registriert. (Unterstützte Zeremonien: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Fehler beim Registrieren für eingehende Kopplung.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Registrierung für eingehende Kopplung war erfolgreich. (Unterstützte Zeremonien: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ Die eingegebene PIN ist falsch.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ Auf diesem Gerät wurde kein verwendbarer Bluetooth-Adapter gefunden: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Koppeln
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Fehler beim Koppeln mit {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Erfolgreich mit {0} ({1}) gekoppelt.
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Standard
+ Text label for the corresponding device pairing protection level
+
+
+ Verschlüsselung und Authentifizierung
+ Text label for the corresponding device pairing protection level
+
+
+ Verschlüsselung
+ Text label for the corresponding device pairing protection level
+
+
+ Keine
+ Text label for the corresponding device pairing protection level
+
+
+ Ihr Gerät ist nun sichtbar und zur Kopplung mit anderen Bluetooth-Geräten bereit.
+ Text displayed when StartWatcher is invoked
+
+
+ Ihr Gerät sucht nicht mehr nach anderen Bluetooth-Geräten.
+ Text displayed when StopWatcher is invoked
+
+
+ Entkoppeln
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Fehler beim Entkoppeln von {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Erfolgreich von {0} ({1}) entkoppelt.
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Startseite
+
+
+ Webbrowser
+
+
+ Abbrechen
+
+
+ Der Verzeichniswechsel wird derzeit nicht unterstützt. Verwenden Sie in Ihren Befehlen vollständige Pfade.
+
+
+ Zeitzone
+ Time zone text
+
+
+ Suche nach Updates...
+ App update status
+
+
+ Nach Updates suchen
+
+
+ Konten löschen
+
+
+ Beim Löschen Ihrer Konten ist ein Problem aufgetreten.
+
+
+ Dadurch werden die folgenden Windows-Konten gelöscht:
+{0}
+
+Fortfahren?
+
+
+ Konten wurden gelöscht.
+
+
+ Konten werden gelöscht...
+
+
+ Löschen
+
+
+ Schließen
+
+
+ Ihr Gerät ist nicht zur Ausführung des Befehlszeilenprozessors berechtigt.
+Führen Sie den folgenden Befehl als „Administrator“ auf Ihrem Gerät aus, um ihn zu aktivieren:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Sie können den Befehl auf der Seite „Prozesse“ des IoT Windows-Geräteportals ausführen oder mithilfe von PowerShell eine Verbindung mit Ihrem Windows IoT-Gerät herstellen.
+Weitere Informationen finden Sie unter http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Fehler beim Ausführen des Befehls als Administrator: {0}
+
+
+ Fehler beim Aktivieren des Befehlszeilenprozessors (cmd.exe) auf Ihrem Gerät: {0}
+
+
+ Der Befehlszeilenprozessor (cmd.exe) wurde erfolgreich auf Ihrem Gerät aktiviert.
+
+
+ Kachelfarbe
+
+
+ Zurück
+ Back UI navigation
+
+
+ Geräteinformationen anzeigen
+
+
+ Weiter
+ Forward UI navigation
+
+
+ Vollbild ein/aus
+
+
+ Anzeige klonen
+ Clone current view to another display
+
+
+ Protokoll schnell speichern
+
+
+ Sitzungsprotokoll
+
+
+ Standardseite festlegen
+
+
+ Befehl abgebrochen.
+
+
+ Befehlszeile eingeben
+ Placeholder for command line input text box
+
+
+ Fehler beim Ausführen der Befehlszeile: {0}
+
+
+ Befehlszeile
+
+
+ Befehlszeile
+ Title for command line page
+
+
+ Zeitüberschreitung beim Befehl nach {0} Sekunden ohne Ausgabe.
+
+
+ Computername
+
+
+ Bestätigung
+
+
+ Automatisch verbinden
+
+
+ Automatisch verbinden
+
+
+ Verbinden
+
+
+ Verbinden
+
+
+ Verbundene Geräte
+
+
+ Update fehlgeschlagen. Stellen Sie eine WLAN-Verbindung her, und versuchen Sie es noch mal.
+ App update error, poor connection
+
+
+ Weiter
+
+
+ Befehlsausgabe konnte nicht analysiert werden.
+
+
+ Aktueller Ring
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ App-Standardseite
+
+
+ Die Standardsprache wird automatisch ausgewählt…
+
+
+ {0} Protokolle löschen
+ {0} is plural number of logs
+
+
+ {0} Protokoll löschen
+ {0} is singular number of logs
+
+
+ {0} Protokoll löschen?
+ {0} is singular number of logs
+
+
+ {0} Protokolle löschen?
+ {0} is plural number of logs
+
+
+ Auswahl löschen
+
+
+ Azure-Geräte-ID
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ Zur Geräteseite wechseln
+
+
+ IP-Adresse: {0}
+Betriebssystemversion: {1}
+App-Version: {2}
+
+
+ App-Version
+ Field label
+
+
+ Gerätename
+ Field label
+
+
+ IP-Adresse
+ Field label
+
+
+ Netzwerk
+ Field label
+
+
+ Betriebssystemversion
+ Label for OS Version field in main page
+
+
+ um mit der Entwicklung zu beginnen.
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Geräteinfo
+
+
+ Besuchen Sie
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Die Seite, auf die Sie zugreifen möchten, erfordert die Verwendung von Windows-Geräteportal (WDP)-APIs. Melden Sie sich mit Ihren WDP-Anmeldedaten an, um fortzufahren.
+
+
+ Beim Anmelden ist ein Problem aufgetreten.
+
+
+ Anmeldung beim Geräteportal erfolgreich!
+
+
+ Anmeldedaten für das Geräteportal werden überprüft...
+
+
+ Beim Abrufen des Wetters ist ein Problem aufgetreten, noch mal versuchen?
+
+
+ Direkte Verbindungen
+
+
+ Trennen
+ This disconnects the connected network
+
+
+ Anzeigesprache aktualisiert: {0}
+
+
+ Domäne
+
+
+ Download abgeschlossen!
+ App update status
+
+
+ Fehler beim Download. Versuchen Sie es später noch mal!
+
+
+ Update wird heruntergeladen
+ App update status
+
+
+ Updates herunterladen
+
+
+ Zeichnen
+
+
+ „{0} Protokolle wurden an „{1}“ gesendet.“
+ {0} is plural number of logs, {1} is email address
+
+
+ „{0} Protokoll wurde an „{1}“ gesendet.“
+ {0} is singular number of logs, {1} is email address
+
+
+ Protokoll per E-Mail senden
+
+
+ Möchten Sie „{0}“ per E-Mail an sich selbst senden?
+ {0} is filename
+
+
+ Beim Senden des Protokolls per E-Mail ist ein Problem aufgetreten: {0}
+ {0} is exception message
+
+
+ Ihre Protokolle befinden sich auf der Seite „Protokolle“.
+
+
+ „{0} Protokoll per E-Mail an sich selbst senden?“
+ {0} is singular number of logs
+
+
+ Beim Senden der Protokolle per E-Mail ist ein Problem aufgetreten: {0}
+ {0} is an exception message
+
+
+ {0} Protokolle per E-Mail an sich selbst senden?
+ {0} is plural number of logs
+
+
+ Protokolle per E-Mail senden
+
+
+ Auswahl per E-Mail senden
+
+
+ Befehlszeilenprozessor aktivieren
+
+
+ Bildschirmschoner
+ Toggle switch for enabling the screensaver
+
+
+ Endzeit
+
+
+ Fehler
+
+
+ Beim Abrufen der Wetterinfos ist ein Problem aufgetreten.
+
+
+ Ethernet
+ Field label
+
+
+ ETW-Anbieter-GUID: {0}
+ Format string for app settings page
+
+
+ Befehle werden unter DefaultAccount ausgeführt.
+
+
+ Erkunden
+
+
+ Datei gespeichert: {0}
+ {0} is a filename
+
+
+ Test-Flighting
+ Device servicing flighting
+
+
+ Test-Flighting-Infos
+ Device servicing flighting
+
+
+ Der Test-Flight-Ring wurde in „{0}“ geändert!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ Beim Ändern des Test-Flight-Rings ist ein Problem aufgetreten.
+
+
+ Prognose
+ Weather forecast
+
+
+ Sie sind im Begriff, den Vollbildmodus zu aktivieren. Zum Beenden müssen Sie auf der Tastatur [Esc] drücken. Fortfahren?
+
+
+ Vollbildmodus
+
+
+ Drücken Sie [Esc], um den Vollbildmodus zu beenden.
+
+
+ Allgemein
+
+
+ IoTEnterprise Board
+ A generic board name
+
+
+ GitHub
+
+
+ Hilfe
+
+
+ Hilfe
+
+
+ Hilfe
+
+
+ Eingabesprache der Tastatur aktualisiert: {0}
+
+
+ Installation abgeschlossen!
+ App update status
+
+
+ Fehler bei der Installation. Versuchen Sie es später noch mal!
+
+
+ Update wird installiert
+ App update status
+
+
+ Updates installieren
+
+
+ Ungültige Anmeldeinformationen
+
+
+ „{0}“ ist ein ungültiger Standort.
+ Format string for app settings page
+
+
+ „{0}“ ist ein ungültiger Wert. Der Wert muss mindestens 1 sein.
+ Format string for app settings page
+
+
+ „{0}“ ist ein ungültiger Wert.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Tastaturlayout
+ Field label
+
+
+ Diese App neu starten, um die neuen Einstellungen zu übernehmen
+
+
+ Sprache
+
+
+ Sprache
+ Field label
+
+
+ Wird geladen...
+
+
+ Wetterinfo wird geladen...
+
+
+ Das Protokoll wurde an „{0}“ gesendet.
+ {0} is email address
+
+
+ Protokoll gespeichert: {0}
+ {0} is filename
+
+
+ Protokolle
+
+
+ Protokolle
+
+
+ Gerätename
+ Field label
+
+
+ IP-Adresse
+ Field label
+
+
+ Betriebssystemversion
+ Label for OS Version field in main page
+
+
+ Dies ist ein Windows 10 IoT Enterprise-Testimage, das nur für Prototypen entworfen wurde. Wenn Sie Ihr Gerät gewerblich anbieten möchten, müssen Sie ein benutzerdefiniertes FFU für optimale Sicherheit verwenden.
+ Maker Imager Security Notice
+
+
+ Token für Bing-Kartendienst
+
+
+ Token für Bing-Kartendienst erforderlich
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Microsoft-Konto (MSA)
+
+
+ Aktuelle Wiedergabe
+ Music player page status text (currently playing)
+
+
+ Wählen Sie einen Song aus, und klicken Sie auf „Wiedergeben“.
+ Music player page status text (default)
+
+
+ Fügen Sie dem Musikordner mindestens eine Audiodatei hinzu.
+Sie können Musik im Windows-Geräteportal über „Apps“ > „Datei-Explorer“ hinzufügen.
+ Music player page instructions text
+
+
+ Musik wird geladen
+ Music player page loading panel text
+
+
+ Wird geladen
+ Music player page status text (loading)
+
+
+ Keine Musik gefunden
+ Music player page no music found prompt text
+
+
+ Wiederholen
+ Music player page reload button text (no files prompt)
+
+
+ Musik
+
+
+ Musik
+
+
+ Angehalten
+ Music player page status text (paused)
+
+
+ Wiedergabe
+ Music player page status text (playing)
+
+
+ Anmelden
+
+
+ Unbekannt
+
+
+ Menü
+
+
+ Netzwerkadapter
+
+
+ Verbunden
+
+
+ Verbunden
+
+
+ Netzwerkanforderungen werden überprüft.
+
+
+ Netzwerkanforderungen werden überprüft.
+
+
+ Eingeschränkter Internetzugriff
+
+
+ Lokaler und Internetzugriff
+
+
+ Nur lokaler Netzwerkzugriff
+
+
+ Keine Konnektivität
+
+
+ NETZWERKINFORMATIONEN
+
+
+ Netzwerk nicht verfügbar
+
+
+ Netzwerksicherheitsschlüssel eingeben
+
+
+ Netzwerksicherheitsschlüssel eingeben
+
+
+ Netzwerk & WLAN
+
+
+ Netzwerk & WLAN
+
+
+ Netzwerkeigenschaften anzeigen
+
+
+ Netzwerkeigenschaften
+
+
+ Sie werden demnächst auf das Erfassungsportal dieses WLAN-Netzwerks umgeleitet. Fortfahren?
+
+
+ Netzwerkumleitung
+
+
+ Weiter
+
+
+ Weiter
+
+
+ Keine Konten gefunden
+
+
+ Nein
+
+
+ kein Gerätename
+
+
+ keine Internetverbindung
+
+
+ Keine Protokolle ausgewählt
+
+
+ Keine Musik gefunden
+ Music player page panel text
+
+
+ Keine gefunden
+
+
+ Es sind keine ausstehenden Updates zum Download verfügbar.
+ App update status
+
+
+ Es sind keine ausstehenden Updates zur Installation verfügbar.
+ App update status
+
+
+ k. A.
+
+
+ Benachrichtigungen
+
+
+ Benachrichtigungen
+
+
+ Keine neuen Updates gefunden.
+ Format string displayed when no app updates are found
+
+
+ OK
+ Button content text for the Bluetooth settings page
+
+
+ Sprache auswählen
+
+
+ Verbindung herstellen
+
+
+ Willkommen bei Windows 10 IoT Enterprise
+
+
+ Lassen Sie uns zunächst einige grundlegende Dinge klären.
+
+
+ Willkommen bei Windows 10 IoT Enterprise
+
+
+ ID der Betriebsversionsedition
+
+
+ Betriebssystemedition
+
+
+ Betriebssysteminfos
+
+
+ Betriebssysteminfos
+
+
+ Nicht verfügbar
+ Text shown when we cannot retrieve the OS Version
+
+
+ Betriebssystemversion
+
+
+ Pakete
+ Software packages
+
+
+ Installierte Pakete
+ Software packages
+
+
+ Seiteneinstellungen
+
+
+ Seiten
+
+
+ Passwort
+
+
+ Bilder werden geladen
+ Default text when no images are available
+
+
+ Fügen Sie dem Bilderordner Bilder hinzu.
+Sie können Bilder im Windows-Geräteportal über „Apps“ > „Datei-Explorer“ hinzufügen.
+
+
+ Keine Bilder gefunden
+ Default text when no images are available
+
+
+ Plattform
+
+
+ Wiedergeben
+
+
+ Energieoptionen
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Einfach: Sendet nur Informationen zum Gerät, zu den Einstellungen und Funktionen und dazu, ob es ordnungsgemäß funktioniert.
+
+
+ Vollständig: Sendet neben allen Diagnosedaten der Stufe „Einfach“ zusätzliche Informationen zu den besuchten Websites, zur Verwendung von Apps und Features, zur Geräteintegrität und -aktivität sowie erweiterte Fehlerberichte.
+
+
+ Wir konnten die Datenschutzeinstellung nicht ändern. Überprüfen Sie Ihren Benutzernamen und das Kennwort, und wiederholen Sie den Vorgang.
+
+
+ Legen Sie fest, welche Diagnosedaten an Microsoft gesendet werden sollen. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
+
+
+ Diagnosedaten
+ Label for Setting item to control Privacy
+
+
+ Geben Sie Ihre Anmeldeinformationen ein, um die Datenschutzebene für dieses Gerät festzulegen.
+
+
+ Datenschutzebene festlegen
+
+
+ Aktualisieren
+ Refresh button
+
+
+ Song wiederholen
+ Music player page repeat toggle text
+
+
+ Neu starten
+
+
+ Neu starten
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Nutzung: RunAsAdmin-Befehl
+
+Beispiele:
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Speichern
+
+
+ Skalierungsfaktor
+
+
+ Alles auswählen
+
+
+ Telemetriedaten senden
+
+
+ Nicht verfügbar
+
+
+ Sitzungsprotokoll
+
+
+ Beim Festlegen der Standardseite auf {0} ist ein Problem aufgetreten.
+ Format string for app settings page
+
+
+ Einstellungen
+
+
+ Zufällige Wiedergabe
+ Music player page shuffle toggle text
+
+
+ Herunterfahren
+
+
+ Herunterfahren
+ Shutdown entry in the shutdown menu
+
+
+ Melden Sie sich bei Ihrem Azure AD-Konto an, um diese Funktion zu nutzen.
+
+
+ Überspringen
+
+
+ Diesen Schritt überspringen
+
+
+ Diashowintervall (Sekunden)
+
+
+ Diashow
+
+
+ Diashow
+
+
+ Starten
+
+
+ Starten
+
+
+ Startzeit
+
+
+ Status
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Übermitteln
+
+
+ Erfolgreich
+
+
+ System
+
+
+ Beim Versuch, Ihre Systemeinstellungen zu aktualisieren, ist ein Problem aufgetreten.
+ Used within system settings
+
+
+ Telemetrie-Ebene
+
+
+ Telemetrie
+
+
+ Große Testbenachrichtigung
+
+
+ Testbenachrichtigung
+
+
+ Windows 10 IoT gehört zur Windows 10-Familie und stellt erstklassige Leistung, Sicherheit und Verwaltbarkeit im Internet der Dinge (Internet of Things, IoT) bereit. Die Version nutzt die eingebettete Umgebung, das Ökosystem und die Cloudkonnektivität von Windows und ermöglicht Organisationen die Erstellung einer eigenen IoT-Bereitstellung mit sicheren Geräten, die schnell bereitgestellt, einfach verwaltet und nahtlos in die allgemeine Cloudstrategie eingebunden werden können.
+
+
+ Kachelhöhe
+
+
+ Personalisierung
+
+
+ Kachelbreite
+
+
+ Zeitüberschreitung bei Verbindung
+
+
+ Zeitzone aktualisiert: {0}
+
+
+ Fehler: Kommunikation mit dem Wetterdienst nicht möglich
+
+
+ Update aufgrund eines unbekannten Fehlers fehlgeschlagen.
+ App update error, unknown
+
+
+ Gesamte Auswahl aufheben
+
+
+ Unbekannter Fehler
+
+
+ Erweiterte Optionen
+
+
+ Jetzt überprüfen
+
+
+ Jetzt installieren
+
+
+ {0} ausstehendes Update
+ {0} is singular amount of updates
+
+
+ {0} neue Updates gefunden.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} ausstehende Updates
+ {0} is plural amount of updates
+
+
+ MDL2-Kachelsymbole verwenden
+
+
+ Passwort verwenden
+
+
+ Benutzername
+
+
+ Windows-Geräteportal
+
+
+ Geräteportaleinstellungen
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows-Geräteportal
+
+
+ Aktuelle Position ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Ihr Standort
+
+
+ Ihr Standort
+ Label for map pin
+
+
+ Unbekannte Position
+ Label for map pin
+
+
+ Sensor:
+ Label for temperature sensor output
+
+
+ Wetter
+
+
+ Fehler beim Laden der Wetterseite.
+
+Klicken Sie unten rechts auf dem Bildschirm auf die Schaltfläche „Aktualisieren“, um diese Seite neu zu laden.
+
+Navigieren Sie zu „weatherunlocked.com“, falls Sie nicht über Wetter-API-Schlüssel verfügen. Speichern Sie die Schlüssel in „WeatherTokens.config“ im Ordner „Local State“ dieser App. Aktualisieren Sie anschließend die Seite.
+
+
+ Wetter bereitgestellt von:
+
+
+ Wetter
+
+
+ Webadresse eingeben
+
+
+ Webbrowser
+
+
+ Willkommen bei Windows IoT Enterprise
+
+
+ WLAN
+ Label for Wi-Fi list in options page
+
+
+ Aktualisieren
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Letzte Überprüfung:
+ For a timestamp
+
+
+ Letzte Aktualisierung:
+ For a timestamp
+
+
+ Aktualisierter Zustand:
+
+
+ Statusmeldung:
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Ungültiges Arbeitsverzeichnis: {0}
+
+
+ WPS
+
+
+ Dieser App den Zugriff auf Ihren Standort erlauben
+
+
+ Wählen Sie Ihre Einstellungen aus, und wählen Sie dann die Option „Annehmen“, um sie zu speichern. Sie können diese Einstellungen jederzeit ändern.
+
+
+ Microsoft die Verwendung Ihres Standorts erlauben
+
+
+ Vorgang wird automatisch fortgesetzt...
+
+
+ Annehmen
+
+
+ Zugriff auf Ihre genaue Position für {0} zulassen?
+ {0} is the name of a page
+
+
+ Standort
+
+
+ Sie können dies auch später unter „Einstellungen“ > „Berechtigungen“ ändern.
+
+
+ Nein
+
+
+ Ja
+
+
+ Sie können keine positionsbasierten Features wie Karten und den Wetterbericht oder andere Dienste nutzen, die für die richtige Funktionsweise Ihre Position benötigen.
+
+
+ Nutzen Sie positionsbasierte Features wie Karten und den Wetterbericht. Lassen Sie zu, dass diese App Ihren Standort abfragt. Microsoft verwendet Ihre Positionsdaten zur Verbesserung von Positionsdiensten.
+
+
+ Sendet nur Informationen zum Gerät, zu den Einstellungen und Funktionen und dazu, ob es ordnungsgemäß funktioniert. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
+
+
+ Einfach
+
+
+ Sendet neben allen Diagnosedaten der Stufe „Einfach“ zusätzliche Informationen zu den besuchten Websites, zur Verwendung von Apps und Features, zur Geräteintegrität und -aktivität sowie erweiterte Fehlerberichte. Die Diagnosedaten werden genutzt, um Windows sicher und auf dem neuesten Stand zu halten, Probleme zu beheben und Produktverbesserungen vorzunehmen. Ihr Gerät ist unabhängig davon, ob Sie „Einfach“ oder „Vollständig“ auswählen, gleichermaßen geschützt und funktioniert normal.
+
+
+ Vollständig
+
+
+ Wählen Sie eine Datenschutzeinstellung für Ihr Gerät aus, und klicken Sie zum Speichern auf „Akzeptieren“.
+
+
+ Diagnosedaten an Microsoft senden
+
+
+ Diagnose
+
+
+ Wenn Sie den Zugriff zulassen, können die Funktionen Ihres Geräts von dieser Apps genutzt werden, um Ihren Standort zu ermitteln. Microsoft verwendet Ihre Positionsdaten, um die Positionsdienste zu verbessern. Wenn Sie den Zugriff verweigern, wird von Windows der Zugriff auf Ihren Standort für die App blockiert.
+
+
+ Informieren Sie sich über die Optionen zur Privatsphäre.
+
+
+ Hier erfahren Sie, wie sich diese Einstellung auf Ihre Privatsphäre auswirkt.
+
+
+ Weitere Informationen zu diesen Einstellungen
+
+
+ Datenschutzerklärung
+
+
+ Ja
+
+
+ Ja
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/en-US/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/en-US/Resources.resw
index 50c8b7a9d..d6092a949 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/en-US/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/en-US/Resources.resw
@@ -1,1632 +1,1632 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Use AAD v2
-
-
- Accept
-
-
- Access Revoked
-
-
- Description:
-
-
- DHCP Server:
-
-
- DNS:
-
-
- Gateway Address:
-
-
- IPv4 Address:
-
-
- Name:
-
-
- Physical Address:
-
-
- Subnet Mask:
-
-
- Type:
-
-
- App Version
-
-
- You are about to launch an external app. You will need to use Windows Device Portal to return to this app. Continue?
- Dialog prompt for launching external apps
-
-
- Apps
-
-
- Apps
-
-
- App Settings
-
-
- Set active hours to let us know when you typically use this device. We won't automatically restart during active hours.
-
-
- Unable to save new Start and End times, as they are the same. Please pick new times or turn off feature.
-
-
- Advanced Options
- Advanced section title
-
-
- Control each of the Fetch, Download, and Install update steps.
-
-
- Auto-Update Options
- Auto-Update section title
-
-
- Let app install app updates outside of active hours
-
-
- App Updates
- App update display dialog header
-
-
- {0}: {1}
- {0} is status text, {1} is version number
-
-
- Last checked: {0}, {1}
- {0} is date, {1} is time
-
-
- Unable to determine when last checked for updates
-
-
- App Updates
- Label for setting item to check for app updates
-
-
- Sign in to MSA and AAD
-
-
- Please sign in to AAD using your organization account.
-
-
- Azure AD (AAD) Sign In
-
-
- AAD
-
-
- Azure AD (AAD) Account
-
-
- Azure AD (AAD {0}) Account
- {0} is a version string, ex: "v1", "v2", "v3"...
-
-
- Authenticates Microsoft Graph and other resources
-
-
- Authenticates Microsoft Graph only
-
-
- Cancel
-
-
- Your organization account
-
-
- If you get stuck at any point and cannot exit the sign in wizard, please wait {0} seconds, and you should return back to the app.
-
-
- Signing in...
-
-
- Signing out...
-
-
- Sign in to your Microsoft Account here
-
-
- Microsoft Account (MSA) Sign In
-
-
- MSA
-
-
- Authentication
-
-
- Microsoft Sign In
-
-
- Sign in failed ({0})
-
-
- Sign in successful ({0})
-
-
- Sign In
-
-
- Signed out: {0}
-
-
- Sign Out
-
-
- Auto-Play
- Music player page auto-play toggle text
-
-
- Auto Scaling
-
-
- Send only info about your device, its settings and capabilities, and whether it is performing properly. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of whether you select Basic or Full, your device will be equally secure and will operate normally.
-
-
- Basic
-
-
- Update failed due to low battery.
- App update error, low battery
-
-
- Attempting to pair with {0} ({1}).
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Pairing with {0} ({1}).
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- Does the PIN shown on the device match: {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Unknown
- Text displayed when the Bluetooth device name is unknown
-
-
- Currently paired
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Ready to pair
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Unknown state
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Please enter the following PIN on the device you wish to pair: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Enter the PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Inbound pairing request from {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- This device is already registered for inbound pairing. (Supported ceremonies: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Failed to register for inbound pairing.
- Text displayed when Inbound pairing handler registration fails
-
-
- Successfully registered for inbound pairing. (Supported ceremonies: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- The PIN you entered is incorrect.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- No usable Bluetooth adapter can be found on this device: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Pair
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Failed to pair with {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Successfully paired with {0} ({1}).
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Default
- Text label for the corresponding device pairing protection level
-
-
- Encryption and authentication
- Text label for the corresponding device pairing protection level
-
-
- Encryption
- Text label for the corresponding device pairing protection level
-
-
- None
- Text label for the corresponding device pairing protection level
-
-
- Your device is now discoverable and ready to pair with other Bluetooth devices.
- Text displayed when StartWatcher is invoked
-
-
- Your device is no longer searching for other Bluetooth devices.
- Text displayed when StopWatcher is invoked
-
-
- Unpair
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Failed to unpair from {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Successfully unpaired from {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Home Page
-
-
- Web Browser
-
-
- Cancel
-
-
- Change Directory not currently supported. Please use full paths in your commands.
-
-
- Time zone
- Time zone text
-
-
- Check connection and try again
-
-
- Checking for updates...
- App update status
-
-
- Check for updates
-
-
- Clear Accounts
-
-
- There was a problem clearing your accounts
-
-
- This will clear the following Windows accounts:
-{0}
-
-Continue?
-
-
- Accounts have been cleared
-
-
- Cleared WDP Credentials
- WDP is acronym for Windows Device Portal
-
-
- Clearing accounts...
-
-
- Clear
-
-
- Clear WDP Credentials
- WDP is acronym for Windows Device Portal
-
-
- Close
-
-
- Close
-
-
- Your device is not allowed to run the command line processor.
-To enable it, run the following command as "Administrator" on your device:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-You can run the command in IoT Windows Device Portal's Processes page, or use PowerShell to connect to your Windows IoT device.
-For more information, please visit http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Failed to run command as Administrator: {0}
-
-
- Failed to enable Command Line Processor (cmd.exe) on your device: {0}
-
-
- Successfully enabled Command Line Processor (cmd.exe) on your device.
-
-
- Tile Color
-
-
- Back
- Back UI navigation
-
-
- Show Device Info
-
-
- Forward
- Forward UI navigation
-
-
- Toggle Fullscreen
-
-
- Clone View
- Clone current view to another display
-
-
- Quick-Save Log
-
-
- Session Log
-
-
- Set Default Page
-
-
- Command canceled.
-
-
- Enter command line
- Placeholder for command line input text box
-
-
- Error running command line: {0}
-
-
- Command Line
-
-
- Command line
- Title for command line page
-
-
- Command timed out after {0} seconds of no output.
-
-
- Computer Name
-
-
- Confirmation
-
-
- Connect automatically
-
-
- Connect automatically
-
-
- Connect
-
-
- Connect
-
-
- Connected Devices
-
-
- Update failed. Please connect to Wi-Fi and try again.
- App update error, poor connection
-
-
- Continue
-
-
- Could not parse command output
-
-
- Current Ring
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Default App Page
-
-
- We're choosing the default language automatically...
-
-
- Deleted {0} logs
- {0} is plural number of logs
-
-
- Deleted {0} log
- {0} is singular number of logs
-
-
- Delete {0} log?
- {0} is singular number of logs
-
-
- Delete {0} logs?
- {0} is plural number of logs
-
-
- Delete Selected
-
-
- Azure Device ID
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- Device Info
-
-
- Go To Device Page
-
-
- IP Address: {0}
-OS Version: {1}
-App Version: {2}
-
-
- Device Info
-
-
- App Version
- Field label
-
-
- Device Name
- Field label
-
-
- IP Address
- Field label
-
-
- Network
- Field label
-
-
- OS Version
- Label for OS Version field in main page
-
-
- to start developing
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Device Info
-
-
- Visit
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- The page you are trying to access requires use of Windows Device Portal (WDP) APIs. Please sign in using your WDP credentials to proceed.
-
-
- There was a problem signing in.
-
-
- Successfully signed into Device Portal!
-
-
- Verifying Device Portal Credentials...
-
-
- Device Twin properties have been applied to Settings ({0})
- {0} is the name of the settings
-
-
- Diagnostic Data
- Label for Setting item to control Privacy
-
-
- Diagnostics
-
-
- There was a problem getting the weather, try again?
-
-
- Direct connections
-
-
- Disconnect
- This disconnects the connected network
-
-
- Display language updated: {0}
-
-
- Domain
-
-
- Download Complete!
- App update status
-
-
- Download failed. Please try again later!
-
-
- Downloading Update
- App update status
-
-
- Download updates
-
-
- Draw
-
-
- "{0} logs sent to {1}"
- {0} is plural number of logs, {1} is email address
-
-
- "{0} log sent to {1}"
- {0} is singular number of logs, {1} is email address
-
-
- Email Log
-
-
- Would you like to email {0} to yourself?
- {0} is filename
-
-
- There was a problem emailing your log: {0}
- {0} is exception message
-
-
- You can find your logs on the Logs page
-
-
- "Email {0} log to yourself?"
- {0} is singular number of logs
-
-
- There was a problem emailing your logs: {0}
- {0} is an exception message
-
-
- Email {0} logs to yourself?
- {0} is plural number of logs
-
-
- Email Logs
-
-
- Email Selected
-
-
- Enable Command Line Processor
-
-
- Screensaver
- Toggle switch for enabling the screensaver
-
-
- End time
-
-
- Error
-
-
- There was a problem retrieving weather info
-
-
- Ethernet
- Field label
-
-
- ETW Provider GUID: {0}
- Format string for app settings page
-
-
- Executing commands as DefaultAccount
-
-
- Explore
-
-
- File saved: {0}
- {0} is a filename
-
-
- Flighting
- Device servicing flighting
-
-
- Flighting Info
- Device servicing flighting
-
-
- Flight Ring has been changed to {0}!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- There was a problem changing your flight ring
-
-
- Forecast
- Weather forecast
-
-
- You are about to enter full screen mode. To exit, you must press [Esc] on the keyboard. Continue?
-
-
- Full Screen Mode
-
-
- Press [Esc] to exit full screen mode.
-
-
- Send all Basic diagnostic data, along with info about the websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of whether you select Basic or Full, your device will be equally secure and will operate normally.
-
-
- Full
-
-
- General
-
-
- IoTEnterprise Board
- A generic board name
-
-
- GitHub
-
-
- Help
-
-
- "Sorry, there doesn't seem to be any help here."
-
-
- Help
-
-
- Help
-
-
- Humidity: {0}%
- {0} is the humidity reading
-
-
- Input keyboard language updated: {0}
-
-
- Install complete!
- App update status
-
-
- Install failed. Please try again later!
-
-
- Installing Update
- App update status
-
-
- Install updates
-
-
- Invalid Credential
-
-
- '{0}' is an invalid location.
- Format string for app settings page
-
-
- '{0}' is an invalid value. Value must be greater than or equal to 1.
- Format string for app settings page
-
-
- '{0}' is an invalid value.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Keyboard layout
- Field label
-
-
- Know your privacy options
-
-
- Learn how this setting impacts your privacy.
-
-
- Restart this app to apply new settings
-
-
- Language
-
-
- Language
- Field label
-
-
- Last Checked:
- For a timestamp
-
-
- Last Updated:
- For a timestamp
-
-
- Loading...
-
-
- Loading weather info...
-
-
- You won’t be able to get location-based experiences like maps and weather or enjoy other services that require your location to work.
-
-
- Get location-based experiences like maps and weather. Let this app request your location. Microsoft will use location data to improve location services.
-
-
- Allow this app to access your location
-
-
- To change this later, go to Settings > Permissions.
-
-
- Let {0} access your precise location?
- {0} is the name of a page
-
-
- Location
-
-
- If you allow access, you will enable this app to use your device’s capabilities to determine your location and Microsoft will use your location data to improve location services. Denying access blocks Windows from providing location to this app.
-
-
- Log has been sent to {0}
- {0} is email address
-
-
- Log saved to: {0}
- {0} is filename
-
-
- Logs
-
-
- Logs
-
-
- This is a Windows 10 IoT Enterprise test image designed for prototyping only. If you are looking to commercialize, you must use a custom FFU for optimal security.
- Maker Imager Security Notice
-
-
- Bing Map Service Token
-
-
- Bing Map Service Token Required
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Microsoft Account (MSA)
-
-
- Multi-View Window
-
-
- Currently playing
- Music player page status text (currently playing)
-
-
- Select a song and click play.
- Music player page status text (default)
-
-
- Please add one or more audio files to the Music folder.
-You can add music in Windows Device Portal using Apps > File explorer.
- Music player page instructions text
-
-
- Loading Music
- Music player page loading panel text
-
-
- Loading
- Music player page status text (loading)
-
-
- No music found
- Music player page no music found prompt text
-
-
- Try Again
- Music player page reload button text (no files prompt)
-
-
- Music
-
-
- Music
-
-
- Paused
- Music player page status text (paused)
-
-
- Now Playing
- Music player page status text (playing)
-
-
- Sign In
-
-
- Unknown
-
-
- Menu
-
-
- Network Adapters
-
-
- Connected
-
-
- Connected
-
-
- Checking network requirements
-
-
- Checking network requirements
-
-
- Limited Internet access
-
-
- Local and Internet access
-
-
- Local network access only
-
-
- No connectivity
-
-
- NETWORK INFORMATION
-
-
- Network Not Available
-
-
- Enter the network security key
-
-
- Enter the network security key
-
-
- Network & Wi-Fi
-
-
- Network & Wi-Fi
-
-
- View network properties
-
-
- Network Properties
-
-
- You are about to be redirected to this Wi-Fi network's captive portal. Continue?
-
-
- Network Redirect
-
-
- Next
-
-
- Next
-
-
- No accounts found
-
-
- No
-
-
- No Device Name
-
-
- No Internet Connection
-
-
- No logs selected
-
-
- No music found
- Music player page panel text
-
-
- None found
-
-
- There are no pending updates to download.
- App update status
-
-
- There are no pending updates to install.
- App update status
-
-
- N/A
-
-
- No
-
-
- Notifications
-
-
- Notifications
-
-
- No new updates found.
- Format string displayed when no app updates are found
-
-
- Ok
- Button content text for the Bluetooth settings page
-
-
- Choose your language
-
-
- Let's get connected
-
-
- Welcome to Windows 10 IoT Enterprise
-
-
- Choose your settings, then select 'Accept' to save them. You can change these settings at any time.
-
-
- Let Microsoft use your location
-
-
- Choose a privacy setting for your device, then select 'Accept' to save it.
-
-
- Send diagnostic data to Microsoft
-
-
- Continuing automatically...
-
-
- Device Name
- Field label
-
-
- IP Address
- Field label
-
-
- OS Version
- Label for OS Version field in main page
-
-
- Let's get some basic stuff out of the way.
-
-
- Welcome to Windows 10 IoT Enterprise
-
-
- OS Edition ID
-
-
- OS Edition
-
-
- OS Info
-
-
- OS Info
-
-
- Not Available
- Text shown when we cannot retrieve the OS Version
-
-
- OS Version
-
-
- Packages
- Software packages
-
-
- Installed Packages
- Software packages
-
-
- Page Settings
-
-
- Pages
-
-
- Password
-
-
- Loading Pictures
- Default text when no images are available
-
-
- Please add images to the Pictures folder.
-You can add images in Windows Device Portal using Apps > File explorer.
-
-
- No images found
- Default text when no images are available
-
-
- Platform
-
-
- Play
-
-
- Power Options
- Label for Setting item to control Power (shutdown/restart)
-
-
- Basic: Send only info about your device, its settings and capabilities, and whether it is performing properly.
-
-
- Full: Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
-
-
- Get more info about these settings
-
-
- We were unable to change the privacy setting. Verify your username and password and try again.
-
-
- Choose how much diagnostic data you want to send to Microsoft. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of which option you select, your device will be equally secure and will operate normally.
-
-
- Enter your credentials to set the privacy level on this device.
-
-
- Set your privacy level
-
-
- Privacy statement
-
-
- Refresh
- Refresh button
-
-
- Repeat Song
- Music player page repeat toggle text
-
-
- Restart
-
-
- Restart
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Usage: RunAsAdmin command
-
-Examples:
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Save
-
-
- Scaling Factor
-
-
- Select All
-
-
- Send Telemetry
-
-
- Unavailable
-
-
- Session Log
-
-
- There was a problem setting the default page to {0}.
- Format string for app settings page
-
-
- Default page has been set to {0}
- {0} is name of page
-
-
- Settings
-
-
- Shuffle
- Music player page shuffle toggle text
-
-
- Shut down
-
-
- Shut down
- Shutdown entry in the shutdown menu
-
-
- Sign in to your Azure AD account to use this feature.
-
-
- Skip
-
-
- Skip this step
-
-
- Slideshow Interval (seconds)
-
-
- Slideshow
-
-
- Slideshow
-
-
- Start
-
-
- Start
-
-
- Start time
-
-
- Status Message:
-
-
- Status
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Submit
-
-
- Success
-
-
- System
-
-
- There was an issue trying to update your system settings.
- Used within system settings
-
-
- Security
- Name of telemetry level 0
-
-
- Basic
- Name of telemetry level 1
-
-
- Enhanced
- Name of telemetry level 2
-
-
- Full
- Name of telemetry level 3
-
-
- Telemetry Level
-
-
- Unknown: {0}
- {0} is value of telemetry value
-
-
- Telemetry
-
-
- Test Jumbo Notification
-
-
- Test Notification
-
-
- Windows 10 IoT is a member of the Windows 10 family that brings enterprise-class power, security and manageability to the Internet of Things. It leverages Windows' embedded experience, ecosystem and cloud connectivity, allowing organizations to create their Internet of Things with secure devices that can be quickly provisioned, easily managed, and seamlessly connected to an overall cloud strategy.
-
-
- Tile Height
-
-
- Personalization
-
-
- Tile Width
-
-
- Connection Timed Out
-
-
- Time zone updated: {0}
-
-
- Error: Unable to communicate with the weather service
-
-
- Update failed due to unknown error.
- App update error, unknown
-
-
- Unselect All
-
-
- Unspecified Failure
-
-
- Advanced Options
-
-
- Check Now
-
-
- Install Now
-
-
- Updated State:
-
-
- {0} pending update
- {0} is singular amount of updates
-
-
- {0} new updates found.
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} pending updates
- {0} is plural amount of updates
-
-
- Use MDL2 Tile Icons
-
-
- Use password
-
-
- Username
-
-
- Windows Device Portal
-
-
- Device Portal Settings
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows Device Portal
-
-
- Current Location ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Your Location
-
-
- Your Location
- Label for map pin
-
-
- Unknown Location
- Label for map pin
-
-
- Error loading the Weather page.
-
-Click on the Refresh button at the bottom right of the screen to reload this page.
-
-If you don't have Weather API keys, navigate to weatherunlocked.com. Save the keys in "WeatherTokens.config" in this App's Local State folder. Then Refresh the page.
-
-
- Sensor:
- Label for temperature sensor output
-
-
- Weather
-
-
- Weather provided by:
-
-
- Weather
-
-
- Wind Speed: {0} at {1}
- {0} is the wind direction and {1} is the wind speed.
-
-
- Enter web address
-
-
- Web Browser
-
-
- Error: {0} - {1}
- {0} is the error number and {1} is the error name.
-
-
- Welcome to Windows IoT Enterprise
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Refresh
- Refresh button
-
-
- WiFi Settings
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Windows Update
-
-
- Windows Update
-
-
- Update in progress
- Windows Update status based on id
-
-
- Staging
- Windows Update status based on id
-
-
- Pending reboot
- Windows Update status based on id
-
-
- No update
- Windows Update status based on id
-
-
- Invalid working directory: {0}
-
-
- WPS
-
-
- Yes
-
-
- Yes
- Button content text for the Bluetooth settings page
-
-
- Yes
-
-
- Temperature Unit
-
-
- Where are you?
-
-
- Your location couldn't be found.
-Make sure you've enabled Location permissions on the Settings page.
-
-
- We hit a snag.
-
-
- There was a problem getting the weather,
-please try again later.
-
-
- You don't have any music.
-Add music to your device using the Windows Device Portal.
-
-
- Let's play some music
-
-
- Reload
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Use AAD v2
+
+
+ Accept
+
+
+ Access Revoked
+
+
+ Description:
+
+
+ DHCP Server:
+
+
+ DNS:
+
+
+ Gateway Address:
+
+
+ IPv4 Address:
+
+
+ Name:
+
+
+ Physical Address:
+
+
+ Subnet Mask:
+
+
+ Type:
+
+
+ App Version
+
+
+ You are about to launch an external app. You will need to use Windows Device Portal to return to this app. Continue?
+ Dialog prompt for launching external apps
+
+
+ Apps
+
+
+ Apps
+
+
+ App Settings
+
+
+ Set active hours to let us know when you typically use this device. We won't automatically restart during active hours.
+
+
+ Unable to save new Start and End times, as they are the same. Please pick new times or turn off feature.
+
+
+ Advanced Options
+ Advanced section title
+
+
+ Control each of the Fetch, Download, and Install update steps.
+
+
+ Auto-Update Options
+ Auto-Update section title
+
+
+ Let app install app updates outside of active hours
+
+
+ App Updates
+ App update display dialog header
+
+
+ {0}: {1}
+ {0} is status text, {1} is version number
+
+
+ Last checked: {0}, {1}
+ {0} is date, {1} is time
+
+
+ Unable to determine when last checked for updates
+
+
+ App Updates
+ Label for setting item to check for app updates
+
+
+ Sign in to MSA and AAD
+
+
+ Please sign in to AAD using your organization account.
+
+
+ Azure AD (AAD) Sign In
+
+
+ AAD
+
+
+ Azure AD (AAD) Account
+
+
+ Azure AD (AAD {0}) Account
+ {0} is a version string, ex: "v1", "v2", "v3"...
+
+
+ Authenticates Microsoft Graph and other resources
+
+
+ Authenticates Microsoft Graph only
+
+
+ Cancel
+
+
+ Your organization account
+
+
+ If you get stuck at any point and cannot exit the sign in wizard, please wait {0} seconds, and you should return back to the app.
+
+
+ Signing in...
+
+
+ Signing out...
+
+
+ Sign in to your Microsoft Account here
+
+
+ Microsoft Account (MSA) Sign In
+
+
+ MSA
+
+
+ Authentication
+
+
+ Microsoft Sign In
+
+
+ Sign in failed ({0})
+
+
+ Sign in successful ({0})
+
+
+ Sign In
+
+
+ Signed out: {0}
+
+
+ Sign Out
+
+
+ Auto-Play
+ Music player page auto-play toggle text
+
+
+ Auto Scaling
+
+
+ Send only info about your device, its settings and capabilities, and whether it is performing properly. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of whether you select Basic or Full, your device will be equally secure and will operate normally.
+
+
+ Basic
+
+
+ Update failed due to low battery.
+ App update error, low battery
+
+
+ Attempting to pair with {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Pairing with {0} ({1}).
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ Does the PIN shown on the device match: {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Unknown
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Currently paired
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Ready to pair
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Unknown state
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Please enter the following PIN on the device you wish to pair: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Enter the PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Inbound pairing request from {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ This device is already registered for inbound pairing. (Supported ceremonies: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Failed to register for inbound pairing.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Successfully registered for inbound pairing. (Supported ceremonies: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ The PIN you entered is incorrect.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ No usable Bluetooth adapter can be found on this device: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Pair
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Failed to pair with {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Successfully paired with {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Default
+ Text label for the corresponding device pairing protection level
+
+
+ Encryption and authentication
+ Text label for the corresponding device pairing protection level
+
+
+ Encryption
+ Text label for the corresponding device pairing protection level
+
+
+ None
+ Text label for the corresponding device pairing protection level
+
+
+ Your device is now discoverable and ready to pair with other Bluetooth devices.
+ Text displayed when StartWatcher is invoked
+
+
+ Your device is no longer searching for other Bluetooth devices.
+ Text displayed when StopWatcher is invoked
+
+
+ Unpair
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Failed to unpair from {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Successfully unpaired from {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Home Page
+
+
+ Web Browser
+
+
+ Cancel
+
+
+ Change Directory not currently supported. Please use full paths in your commands.
+
+
+ Time zone
+ Time zone text
+
+
+ Check connection and try again
+
+
+ Checking for updates...
+ App update status
+
+
+ Check for updates
+
+
+ Clear Accounts
+
+
+ There was a problem clearing your accounts
+
+
+ This will clear the following Windows accounts:
+{0}
+
+Continue?
+
+
+ Accounts have been cleared
+
+
+ Cleared WDP Credentials
+ WDP is acronym for Windows Device Portal
+
+
+ Clearing accounts...
+
+
+ Clear
+
+
+ Clear WDP Credentials
+ WDP is acronym for Windows Device Portal
+
+
+ Close
+
+
+ Close
+
+
+ Your device is not allowed to run the command line processor.
+To enable it, run the following command as "Administrator" on your device:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+You can run the command in IoT Windows Device Portal's Processes page, or use PowerShell to connect to your Windows IoT device.
+For more information, please visit http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Failed to run command as Administrator: {0}
+
+
+ Failed to enable Command Line Processor (cmd.exe) on your device: {0}
+
+
+ Successfully enabled Command Line Processor (cmd.exe) on your device.
+
+
+ Tile Color
+
+
+ Back
+ Back UI navigation
+
+
+ Show Device Info
+
+
+ Forward
+ Forward UI navigation
+
+
+ Toggle Fullscreen
+
+
+ Clone View
+ Clone current view to another display
+
+
+ Quick-Save Log
+
+
+ Session Log
+
+
+ Set Default Page
+
+
+ Command canceled.
+
+
+ Enter command line
+ Placeholder for command line input text box
+
+
+ Error running command line: {0}
+
+
+ Command Line
+
+
+ Command line
+ Title for command line page
+
+
+ Command timed out after {0} seconds of no output.
+
+
+ Computer Name
+
+
+ Confirmation
+
+
+ Connect automatically
+
+
+ Connect automatically
+
+
+ Connect
+
+
+ Connect
+
+
+ Connected Devices
+
+
+ Update failed. Please connect to Wi-Fi and try again.
+ App update error, poor connection
+
+
+ Continue
+
+
+ Could not parse command output
+
+
+ Current Ring
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Default App Page
+
+
+ We're choosing the default language automatically...
+
+
+ Deleted {0} logs
+ {0} is plural number of logs
+
+
+ Deleted {0} log
+ {0} is singular number of logs
+
+
+ Delete {0} log?
+ {0} is singular number of logs
+
+
+ Delete {0} logs?
+ {0} is plural number of logs
+
+
+ Delete Selected
+
+
+ Azure Device ID
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ Device Info
+
+
+ Go To Device Page
+
+
+ IP Address: {0}
+OS Version: {1}
+App Version: {2}
+
+
+ Device Info
+
+
+ App Version
+ Field label
+
+
+ Device Name
+ Field label
+
+
+ IP Address
+ Field label
+
+
+ Network
+ Field label
+
+
+ OS Version
+ Label for OS Version field in main page
+
+
+ to start developing
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Device Info
+
+
+ Visit
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ The page you are trying to access requires use of Windows Device Portal (WDP) APIs. Please sign in using your WDP credentials to proceed.
+
+
+ There was a problem signing in.
+
+
+ Successfully signed into Device Portal!
+
+
+ Verifying Device Portal Credentials...
+
+
+ Device Twin properties have been applied to Settings ({0})
+ {0} is the name of the settings
+
+
+ Diagnostic Data
+ Label for Setting item to control Privacy
+
+
+ Diagnostics
+
+
+ There was a problem getting the weather, try again?
+
+
+ Direct connections
+
+
+ Disconnect
+ This disconnects the connected network
+
+
+ Display language updated: {0}
+
+
+ Domain
+
+
+ Download Complete!
+ App update status
+
+
+ Download failed. Please try again later!
+
+
+ Downloading Update
+ App update status
+
+
+ Download updates
+
+
+ Draw
+
+
+ "{0} logs sent to {1}"
+ {0} is plural number of logs, {1} is email address
+
+
+ "{0} log sent to {1}"
+ {0} is singular number of logs, {1} is email address
+
+
+ Email Log
+
+
+ Would you like to email {0} to yourself?
+ {0} is filename
+
+
+ There was a problem emailing your log: {0}
+ {0} is exception message
+
+
+ You can find your logs on the Logs page
+
+
+ "Email {0} log to yourself?"
+ {0} is singular number of logs
+
+
+ There was a problem emailing your logs: {0}
+ {0} is an exception message
+
+
+ Email {0} logs to yourself?
+ {0} is plural number of logs
+
+
+ Email Logs
+
+
+ Email Selected
+
+
+ Enable Command Line Processor
+
+
+ Screensaver
+ Toggle switch for enabling the screensaver
+
+
+ End time
+
+
+ Error
+
+
+ There was a problem retrieving weather info
+
+
+ Ethernet
+ Field label
+
+
+ ETW Provider GUID: {0}
+ Format string for app settings page
+
+
+ Executing commands as DefaultAccount
+
+
+ Explore
+
+
+ File saved: {0}
+ {0} is a filename
+
+
+ Flighting
+ Device servicing flighting
+
+
+ Flighting Info
+ Device servicing flighting
+
+
+ Flight Ring has been changed to {0}!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ There was a problem changing your flight ring
+
+
+ Forecast
+ Weather forecast
+
+
+ You are about to enter full screen mode. To exit, you must press [Esc] on the keyboard. Continue?
+
+
+ Full Screen Mode
+
+
+ Press [Esc] to exit full screen mode.
+
+
+ Send all Basic diagnostic data, along with info about the websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of whether you select Basic or Full, your device will be equally secure and will operate normally.
+
+
+ Full
+
+
+ General
+
+
+ IoTEnterprise Board
+ A generic board name
+
+
+ GitHub
+
+
+ Help
+
+
+ "Sorry, there doesn't seem to be any help here."
+
+
+ Help
+
+
+ Help
+
+
+ Humidity: {0}%
+ {0} is the humidity reading
+
+
+ Input keyboard language updated: {0}
+
+
+ Install complete!
+ App update status
+
+
+ Install failed. Please try again later!
+
+
+ Installing Update
+ App update status
+
+
+ Install updates
+
+
+ Invalid Credential
+
+
+ '{0}' is an invalid location.
+ Format string for app settings page
+
+
+ '{0}' is an invalid value. Value must be greater than or equal to 1.
+ Format string for app settings page
+
+
+ '{0}' is an invalid value.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Keyboard layout
+ Field label
+
+
+ Know your privacy options
+
+
+ Learn how this setting impacts your privacy.
+
+
+ Restart this app to apply new settings
+
+
+ Language
+
+
+ Language
+ Field label
+
+
+ Last Checked:
+ For a timestamp
+
+
+ Last Updated:
+ For a timestamp
+
+
+ Loading...
+
+
+ Loading weather info...
+
+
+ You won’t be able to get location-based experiences like maps and weather or enjoy other services that require your location to work.
+
+
+ Get location-based experiences like maps and weather. Let this app request your location. Microsoft will use location data to improve location services.
+
+
+ Allow this app to access your location
+
+
+ To change this later, go to Settings > Permissions.
+
+
+ Let {0} access your precise location?
+ {0} is the name of a page
+
+
+ Location
+
+
+ If you allow access, you will enable this app to use your device’s capabilities to determine your location and Microsoft will use your location data to improve location services. Denying access blocks Windows from providing location to this app.
+
+
+ Log has been sent to {0}
+ {0} is email address
+
+
+ Log saved to: {0}
+ {0} is filename
+
+
+ Logs
+
+
+ Logs
+
+
+ This is a Windows 10 IoT Enterprise test image designed for prototyping only. If you are looking to commercialize, you must use a custom FFU for optimal security.
+ Maker Imager Security Notice
+
+
+ Bing Map Service Token
+
+
+ Bing Map Service Token Required
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Microsoft Account (MSA)
+
+
+ Multi-View Window
+
+
+ Currently playing
+ Music player page status text (currently playing)
+
+
+ Select a song and click play.
+ Music player page status text (default)
+
+
+ Please add one or more audio files to the Music folder.
+You can add music in Windows Device Portal using Apps > File explorer.
+ Music player page instructions text
+
+
+ Loading Music
+ Music player page loading panel text
+
+
+ Loading
+ Music player page status text (loading)
+
+
+ No music found
+ Music player page no music found prompt text
+
+
+ Try Again
+ Music player page reload button text (no files prompt)
+
+
+ Music
+
+
+ Music
+
+
+ Paused
+ Music player page status text (paused)
+
+
+ Now Playing
+ Music player page status text (playing)
+
+
+ Sign In
+
+
+ Unknown
+
+
+ Menu
+
+
+ Network Adapters
+
+
+ Connected
+
+
+ Connected
+
+
+ Checking network requirements
+
+
+ Checking network requirements
+
+
+ Limited Internet access
+
+
+ Local and Internet access
+
+
+ Local network access only
+
+
+ No connectivity
+
+
+ NETWORK INFORMATION
+
+
+ Network Not Available
+
+
+ Enter the network security key
+
+
+ Enter the network security key
+
+
+ Network & Wi-Fi
+
+
+ Network & Wi-Fi
+
+
+ View network properties
+
+
+ Network Properties
+
+
+ You are about to be redirected to this Wi-Fi network's captive portal. Continue?
+
+
+ Network Redirect
+
+
+ Next
+
+
+ Next
+
+
+ No accounts found
+
+
+ No
+
+
+ No Device Name
+
+
+ No Internet Connection
+
+
+ No logs selected
+
+
+ No music found
+ Music player page panel text
+
+
+ None found
+
+
+ There are no pending updates to download.
+ App update status
+
+
+ There are no pending updates to install.
+ App update status
+
+
+ N/A
+
+
+ No
+
+
+ Notifications
+
+
+ Notifications
+
+
+ No new updates found.
+ Format string displayed when no app updates are found
+
+
+ Ok
+ Button content text for the Bluetooth settings page
+
+
+ Choose your language
+
+
+ Let's get connected
+
+
+ Welcome to Windows 10 IoT Enterprise
+
+
+ Choose your settings, then select 'Accept' to save them. You can change these settings at any time.
+
+
+ Let Microsoft use your location
+
+
+ Choose a privacy setting for your device, then select 'Accept' to save it.
+
+
+ Send diagnostic data to Microsoft
+
+
+ Continuing automatically...
+
+
+ Device Name
+ Field label
+
+
+ IP Address
+ Field label
+
+
+ OS Version
+ Label for OS Version field in main page
+
+
+ Let's get some basic stuff out of the way.
+
+
+ Welcome to Windows 10 IoT Enterprise
+
+
+ OS Edition ID
+
+
+ OS Edition
+
+
+ OS Info
+
+
+ OS Info
+
+
+ Not Available
+ Text shown when we cannot retrieve the OS Version
+
+
+ OS Version
+
+
+ Packages
+ Software packages
+
+
+ Installed Packages
+ Software packages
+
+
+ Page Settings
+
+
+ Pages
+
+
+ Password
+
+
+ Loading Pictures
+ Default text when no images are available
+
+
+ Please add images to the Pictures folder.
+You can add images in Windows Device Portal using Apps > File explorer.
+
+
+ No images found
+ Default text when no images are available
+
+
+ Platform
+
+
+ Play
+
+
+ Power Options
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Basic: Send only info about your device, its settings and capabilities, and whether it is performing properly.
+
+
+ Full: Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
+
+
+ Get more info about these settings
+
+
+ We were unable to change the privacy setting. Verify your username and password and try again.
+
+
+ Choose how much diagnostic data you want to send to Microsoft. Diagnostic data is used to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Regardless of which option you select, your device will be equally secure and will operate normally.
+
+
+ Enter your credentials to set the privacy level on this device.
+
+
+ Set your privacy level
+
+
+ Privacy statement
+
+
+ Refresh
+ Refresh button
+
+
+ Repeat Song
+ Music player page repeat toggle text
+
+
+ Restart
+
+
+ Restart
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Usage: RunAsAdmin command
+
+Examples:
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Save
+
+
+ Scaling Factor
+
+
+ Select All
+
+
+ Send Telemetry
+
+
+ Unavailable
+
+
+ Session Log
+
+
+ There was a problem setting the default page to {0}.
+ Format string for app settings page
+
+
+ Default page has been set to {0}
+ {0} is name of page
+
+
+ Settings
+
+
+ Shuffle
+ Music player page shuffle toggle text
+
+
+ Shut down
+
+
+ Shut down
+ Shutdown entry in the shutdown menu
+
+
+ Sign in to your Azure AD account to use this feature.
+
+
+ Skip
+
+
+ Skip this step
+
+
+ Slideshow Interval (seconds)
+
+
+ Slideshow
+
+
+ Slideshow
+
+
+ Start
+
+
+ Start
+
+
+ Start time
+
+
+ Status Message:
+
+
+ Status
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Submit
+
+
+ Success
+
+
+ System
+
+
+ There was an issue trying to update your system settings.
+ Used within system settings
+
+
+ Security
+ Name of telemetry level 0
+
+
+ Basic
+ Name of telemetry level 1
+
+
+ Enhanced
+ Name of telemetry level 2
+
+
+ Full
+ Name of telemetry level 3
+
+
+ Telemetry Level
+
+
+ Unknown: {0}
+ {0} is value of telemetry value
+
+
+ Telemetry
+
+
+ Test Jumbo Notification
+
+
+ Test Notification
+
+
+ Windows 10 IoT is a member of the Windows 10 family that brings enterprise-class power, security and manageability to the Internet of Things. It leverages Windows' embedded experience, ecosystem and cloud connectivity, allowing organizations to create their Internet of Things with secure devices that can be quickly provisioned, easily managed, and seamlessly connected to an overall cloud strategy.
+
+
+ Tile Height
+
+
+ Personalization
+
+
+ Tile Width
+
+
+ Connection Timed Out
+
+
+ Time zone updated: {0}
+
+
+ Error: Unable to communicate with the weather service
+
+
+ Update failed due to unknown error.
+ App update error, unknown
+
+
+ Unselect All
+
+
+ Unspecified Failure
+
+
+ Advanced Options
+
+
+ Check Now
+
+
+ Install Now
+
+
+ Updated State:
+
+
+ {0} pending update
+ {0} is singular amount of updates
+
+
+ {0} new updates found.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} pending updates
+ {0} is plural amount of updates
+
+
+ Use MDL2 Tile Icons
+
+
+ Use password
+
+
+ Username
+
+
+ Windows Device Portal
+
+
+ Device Portal Settings
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows Device Portal
+
+
+ Current Location ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Your Location
+
+
+ Your Location
+ Label for map pin
+
+
+ Unknown Location
+ Label for map pin
+
+
+ Error loading the Weather page.
+
+Click on the Refresh button at the bottom right of the screen to reload this page.
+
+If you don't have Weather API keys, navigate to weatherunlocked.com. Save the keys in "WeatherTokens.config" in this App's Local State folder. Then Refresh the page.
+
+
+ Sensor:
+ Label for temperature sensor output
+
+
+ Weather
+
+
+ Weather provided by:
+
+
+ Weather
+
+
+ Wind Speed: {0} at {1}
+ {0} is the wind direction and {1} is the wind speed.
+
+
+ Enter web address
+
+
+ Web Browser
+
+
+ Error: {0} - {1}
+ {0} is the error number and {1} is the error name.
+
+
+ Welcome to Windows IoT Enterprise
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Refresh
+ Refresh button
+
+
+ WiFi Settings
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Update in progress
+ Windows Update status based on id
+
+
+ Staging
+ Windows Update status based on id
+
+
+ Pending reboot
+ Windows Update status based on id
+
+
+ No update
+ Windows Update status based on id
+
+
+ Invalid working directory: {0}
+
+
+ WPS
+
+
+ Yes
+
+
+ Yes
+ Button content text for the Bluetooth settings page
+
+
+ Yes
+
+
+ Temperature Unit
+
+
+ Where are you?
+
+
+ Your location couldn't be found.
+Make sure you've enabled Location permissions on the Settings page.
+
+
+ We hit a snag.
+
+
+ There was a problem getting the weather,
+please try again later.
+
+
+ You don't have any music.
+Add music to your device using the Windows Device Portal.
+
+
+ Let's play some music
+
+
+ Reload
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/es-ES/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/es-ES/Resources.resw
index 44bafb87c..c7d00bb9c 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/es-ES/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/es-ES/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Usar AAD v2
-
-
- Acceso revocado
-
-
- Descripción:
-
-
- Servidor DHCP:
-
-
- DNS:
-
-
- Dirección de puerta de enlace:
-
-
- Dirección IPv4:
-
-
- Nombre:
-
-
- Dirección física:
-
-
- Máscara de subred:
-
-
- Tipo
-
-
- Versión de la aplicación
-
-
- Aplicaciones
-
-
- Estás a punto de iniciar una aplicación externa. Tendrás que usar el Portal de dispositivos Windows para volver a esta aplicación. ¿Quieres continuar?
- Dialog prompt for launching external apps
-
-
- Aplicaciones
-
-
- Configuración de la aplicación
-
-
- Establece las horas activas para que sepamos cuándo sueles usar este dispositivo. No reiniciaremos automáticamente durante las horas activas.
-
-
- No se pueden guardar las nuevas horas de inicio y finalización porque son iguales. Selecciona nuevas horas o desactiva la característica.
-
-
- Opciones avanzadas
- Advanced section title
-
-
- Controla cada uno de los pasos de actualización de captura, descarga e instalación.
-
-
- Opciones de actualización automática
- Auto-Update section title
-
-
- Permitir que la aplicación instale actualizaciones de la aplicación fuera de horas activas
-
-
- Actualizaciones de aplicaciones
- App update display dialog header
-
-
- Última comprobación: {0}, {1}
- {0} is date, {1} is time
-
-
- No se puede determinar cuándo se buscaron actualizaciones por última vez
-
-
- Actualizaciones de aplicaciones
- Label for setting item to check for app updates
-
-
- Iniciar sesión en MSA y AAD
-
-
- Inicia sesión en AAD usando la cuenta de tu organización.
-
-
- Inicio de sesión en Azure AD (AAD)
-
-
- AAD
-
-
- Autentica Microsoft Graph y otros recursos
-
-
- Autentica solo Microsoft Graph
-
-
- Cancelar
-
-
- La cuenta de tu organización
-
-
- Si te bloqueas en cualquier momento y no puedes salir del asistente de inicio de sesión, espera {0} segundos y deberías volver a la aplicación.
-
-
- Iniciando sesión...
-
-
- Cerrando sesión...
-
-
- Inicia sesión en tu cuenta de Microsoft aquí
-
-
- Inicio de sesión en la cuenta de Microsoft (MSA)
-
-
- MSA
-
-
- Autenticación
-
-
- Inicio de sesión en Microsoft
-
-
- Error al iniciar sesión ({0})
-
-
- Inicio de sesión correcto ({0})
-
-
- Iniciar sesión
-
-
- Cierre de sesión: {0}
-
-
- Cerrar sesión
-
-
- Reproducción automática
- Music player page auto-play toggle text
-
-
- Ajuste de escala automático
-
-
- Error al actualizar debido a que la batería está baja.
- App update error, low battery
-
-
- Intentando emparejarse con {0} ({1}).
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Emparejándose con {0} ({1}).
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- ¿El PIN que se muestra en el dispositivo coincide con {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Desconocido
- Text displayed when the Bluetooth device name is unknown
-
-
- Actualmente emparejado
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Listo para emparejar
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Estado desconocido
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Escribe este PIN en el dispositivo con el que se va a emparejar: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Escribe el PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Solicitud de emparejamiento entrante de {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Este dispositivo ya está registrado para emparejamientos entrantes. (operaciones admitidas: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Error de registro para emparejamientos entrantes.
- Text displayed when Inbound pairing handler registration fails
-
-
- Registrado correctamente para emparejamientos entrantes. (Operaciones admitidas: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- El PIN introducido es incorrecto.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- No se encontró ningún adaptador Bluetooth que se pueda usar en este dispositivo: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Emparejar
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Error al emparejarse con {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Emparejado correctamente con {0} ({1}).
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Predeterminado
- Text label for the corresponding device pairing protection level
-
-
- Encriptación y autenticación
- Text label for the corresponding device pairing protection level
-
-
- Encriptación
- Text label for the corresponding device pairing protection level
-
-
- Ninguno
- Text label for the corresponding device pairing protection level
-
-
- El dispositivo ahora es reconocible y está listo para emparejarse con otros dispositivos Bluetooth.
- Text displayed when StartWatcher is invoked
-
-
- Tu dispositivo ya no busca otros dispositivos Bluetooth.
- Text displayed when StopWatcher is invoked
-
-
- Desemparejar
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Error al desemparejarse de {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Desemparejado correctamente de {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Página Inicio
-
-
- Explorador web
-
-
- Cancelar
-
-
- No se puede cambiar de directorio. Usa rutas de acceso completas en los comandos.
-
-
- Zona horaria
- Time zone text
-
-
- Buscando actualizaciones...
- App update status
-
-
- Buscar actualizaciones
-
-
- Borrar cuentas
-
-
- Se ha producido un problema al borrar las cuentas.
-
-
- Se borrarán las cuentas de Windows siguientes:
-{0}
-
-¿Quieres continuar?
-
-
- Se han borrado las cuentas
-
-
- Borrando las cuentas...
-
-
- Borrar
-
-
- Cerrar
-
-
- El dispositivo no puede ejecutar el procesador de línea de comandos.
-Para habilitarlo, ejecuta el siguiente comando como "administrador" en el dispositivo:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Puedes ejecutar el comando en la página Procesos del Portal de dispositivos Windows IoT. De lo contrario, también puedes usar PowerShell para conectarte al dispositivo de Windows IoT.
-Para obtener más información, visita http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Error al ejecutar el comando como administrador: {0}
-
-
- Error al habilitar el procesador de línea de comandos (cmd.exe) en el dispositivo: {0}
-
-
- El procesador de línea de comandos (cmd.exe) se habilitó correctamente en el dispositivo.
-
-
- Color del mosaico
-
-
- Atrás
- Back UI navigation
-
-
- Mostrar información del dispositivo
-
-
- Adelante
- Forward UI navigation
-
-
- Activar/Desactivar pantalla completa
-
-
- Clonar vista
- Clone current view to another display
-
-
- Guardar rápidamente el registro
-
-
- Registro de sesión
-
-
- Establecer página predeterminada
-
-
- Comando confirmado.
-
-
- Escribir línea de comandos
- Placeholder for command line input text box
-
-
- Error al ejecutar la línea de comandos: {0}
-
-
- Línea de comandos
-
-
- Línea de comandos
- Title for command line page
-
-
- Se agotó el tiempo de espera del comando tras {0} segundos sin resultados.
-
-
- Nombre del equipo
-
-
- Confirmación
-
-
- Conectar automáticamente
-
-
- Conectar automáticamente
-
-
- Conectar
-
-
- Conectar
-
-
- Dispositivos conectados
-
-
- Error al actualizar. Conéctate a una Wi-Fi y vuelve a intentarlo.
- App update error, poor connection
-
-
- Continuar
-
-
- No se pudieron analizar los resultados del comando
-
-
- Anillo actual
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Página de la aplicación predeterminada
-
-
- El idioma predeterminado se está seleccionando automáticamente...
-
-
- Se han eliminado {0} registros
- {0} is plural number of logs
-
-
- Se ha eliminado {0} registro
- {0} is singular number of logs
-
-
- ¿Quieres eliminar {0} registro?
- {0} is singular number of logs
-
-
- ¿Quieres eliminar {0} registros?
- {0} is plural number of logs
-
-
- Eliminar selección
-
-
- Identificador de dispositivo de Azure
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- Ir a la página del dispositivo
-
-
- Dirección IP: {0}
-Versión del sistema operativo: {1}
-Versión de la aplicación: {2}
-
-
- Versión de la aplicación
- Field label
-
-
- Nombre del dispositivo
- Field label
-
-
- Dirección IP
- Field label
-
-
- Red
- Field label
-
-
- Versión del SO
- Label for OS Version field in main page
-
-
- para comenzar a desarrollar
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Información del dispositivo
-
-
- Visita
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- La página a la que estás intentando acceder requiere el uso de API del Portal de dispositivos Windows (WDP). Inicia sesión con tus credenciales de WDP para continuar.
-
-
- Hubo un problema al iniciar sesión.
-
-
- Has iniciado sesión correctamente en el Portal de dispositivos
-
-
- Comprobando las credenciales del Portal de dispositivos...
-
-
- No se puede obtener el tiempo. ¿Quieres intentarlo de nuevo?
-
-
- Conexiones directas
-
-
- Desconectar
- This disconnects the connected network
-
-
- Se ha actualizado el idioma para mostrar: {0}
-
-
- Dominio
-
-
- La descarga ha finalizado.
- App update status
-
-
- Error al descargar. Vuelve a intentarlo más tarde.
-
-
- Descargando actualización
- App update status
-
-
- Descargar actualizaciones
-
-
- Dibujar
-
-
- "{0} registros enviados a {1}"
- {0} is plural number of logs, {1} is email address
-
-
- "Registro {0} enviado a {1}"
- {0} is singular number of logs, {1} is email address
-
-
- Registro de correo electrónico
-
-
- ¿Quieres enviarte {0} por correo electrónico?
- {0} is filename
-
-
- Se ha producido un problema al enviar el registro por correo electrónico: {0}
- {0} is exception message
-
-
- Puedes encontrar los registros en la página de registros
-
-
- "¿Quieres enviarte el registro {0} por correo electrónico?"
- {0} is singular number of logs
-
-
- Se ha producido un problema al enviar los registros por correo electrónico: {0}
- {0} is an exception message
-
-
- ¿Quieres enviarte los registros {0} por correo electrónico?
- {0} is plural number of logs
-
-
- Registros de correo electrónico
-
-
- Correo electrónico seleccionado
-
-
- Habilitar procesador de línea de comandos
-
-
- Protector de pantalla
- Toggle switch for enabling the screensaver
-
-
- Hora de finalización
-
-
- Error
-
-
- Hubo un problema al recuperar la información del tiempo
-
-
- Ethernet
- Field label
-
-
- GUID de proveedor de ETW: {0}
- Format string for app settings page
-
-
- Ejecutar comandos como DefaultAccount
-
-
- Explorar
-
-
- Archivo guardado: {0}
- {0} is a filename
-
-
- Distribución de paquetes piloto
- Device servicing flighting
-
-
- Información sobre la distribución de paquetes piloto
- Device servicing flighting
-
-
- El anillo del piloto se ha cambiado a {0}.
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- Hubo un problema al cambiar el anillo del piloto
-
-
- Previsión
- Weather forecast
-
-
- Estás a punto de entrar en modo de pantalla completa. Para salir, debes presionar [Esc] en el teclado. ¿Quieres continuar?
-
-
- Modo de pantalla completa
-
-
- Presiona [Esc] para salir del modo de pantalla completa.
-
-
- General
-
-
- Panel IoTEnterprise
- A generic board name
-
-
- GitHub
-
-
- Ayuda
-
-
- Ayuda
-
-
- Ayuda
-
-
- Idioma de entrada del teclado actualizado: {0}
-
-
- La instalación ha finalizado.
- App update status
-
-
- Error de instalación. Vuelve a intentarlo más tarde.
-
-
- Instalando actualización
- App update status
-
-
- Instalar actualizaciones
-
-
- Credencial no válida
-
-
- '{0}' no es una ubicación válida.
- Format string for app settings page
-
-
- '{0}' no es un valor válido. El valor debe ser mayor o igual que 1.
- Format string for app settings page
-
-
- '{0}' no es un valor válido.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Diseño del teclado
- Field label
-
-
- Reiniciar esta aplicación para aplicar una configuración nueva
-
-
- Idioma
-
-
- Idioma
- Field label
-
-
- Cargando...
-
-
- Cargando información del tiempo...
-
-
- El registro se ha enviado a {0}
- {0} is email address
-
-
- El registro se ha guardado en: {0}
- {0} is filename
-
-
- Registros
-
-
- Registros
-
-
- Nombre del dispositivo
- Field label
-
-
- Dirección IP
- Field label
-
-
- Versión del sistema operativo
- Label for OS Version field in main page
-
-
- Esta es una imagen de prueba de Windows 10 IoT Enterprise diseñada únicamente para prototipos. Si quieres comercializar tu dispositivo, debes usar un FFU personalizado para optimizar la seguridad del dispositivo.
- Maker Imager Security Notice
-
-
- Token de Servicio de Mapas de Bing
-
-
- Es necesario el token de Servicio de Mapas de Bing
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Cuenta de Microsoft (MSA)
-
-
- Actualmente reproduciendo
- Music player page status text (currently playing)
-
-
- Selecciona una canción y haz clic en reproducir.
- Music player page status text (default)
-
-
- Agrega uno o más archivos de audio a la carpeta Música.
-Puedes agregar música en el Portal de dispositivos Windows usando Aplicaciones > Explorador de archivos.
- Music player page instructions text
-
-
- Cargando música
- Music player page loading panel text
-
-
- Cargando
- Music player page status text (loading)
-
-
- No se ha encontrado música
- Music player page no music found prompt text
-
-
- Volver a intentarlo
- Music player page reload button text (no files prompt)
-
-
- Música
-
-
- Música
-
-
- En pausa
- Music player page status text (paused)
-
-
- Reproduciendo
- Music player page status text (playing)
-
-
- Iniciar sesión
-
-
- Desconocido
-
-
- Menú
-
-
- Adaptadores de red
-
-
- Conectado
-
-
- Conectado
-
-
- Comprobando los requisitos de red
-
-
- Comprobando los requisitos de red
-
-
- Acceso a Internet limitado
-
-
- Acceso local y a Internet
-
-
- Solo acceso de red local
-
-
- Sin conectividad
-
-
- INFORMACIÓN DE RED
-
-
- Red no disponible
-
-
- Escribe la clave de seguridad de red
-
-
- Escribe la clave de seguridad de red
-
-
- Red y Wi-Fi
-
-
- Red y Wi-Fi
-
-
- Ver las propiedades de red
-
-
- Propiedades de red
-
-
- Estás a punto de ser redirigido al portal interno de esta red Wi-Fi. ¿Quieres continuar?
-
-
- Network Redirect
-
-
- Siguiente
-
-
- Siguiente
-
-
- No se encontró ninguna cuenta
-
-
- No
-
-
- no hay nombre de dispositivo
-
-
- sin conexión a Internet
-
-
- No hay registros seleccionados
-
-
- No se ha encontrado música
- Music player page panel text
-
-
- No se encontró ninguno
-
-
- No hay ninguna actualización pendiente de descarga.
- App update status
-
-
- No hay ninguna actualización pendiente de instalación.
- App update status
-
-
- n/a
-
-
- Notificaciones
-
-
- Notificaciones
-
-
- No se encontraron nuevas soluciones.
- Format string displayed when no app updates are found
-
-
- Aceptar
- Button content text for the Bluetooth settings page
-
-
- Elige tu idioma
-
-
- Vamos a conectarnos
-
-
- Te damos la bienvenida a Windows 10 IoT Enterprise
-
-
- Vamos a quitar algunas cosas de en medio.
-
-
- Te damos la bienvenida a Windows 10 IoT Enterprise
-
-
- Id. de edición del sistema operativo
-
-
- Edición del sistema operativo
-
-
- Información del sistema operativo
-
-
- Información del sistema operativo
-
-
- No disponible
- Text shown when we cannot retrieve the OS Version
-
-
- Versión del sistema operativo
-
-
- Paquetes
- Software packages
-
-
- Paquetes instalados
- Software packages
-
-
- Configuración de la página
-
-
- Páginas
-
-
- Contraseña
-
-
- Cargando imágenes...
- Default text when no images are available
-
-
- Agrega imágenes a la carpeta Imágenes.
-Puedes agregar imágenes en el Portal de dispositivos Windows usando Aplicaciones > Explorador de archivos.
-
-
- No se encontró ninguna imagen
- Default text when no images are available
-
-
- Plataforma
-
-
- Reproducir
-
-
- Opciones de Inicio/apagado
- Label for Setting item to control Power (shutdown/restart)
-
-
- Básico: solo se envía información sobre el dispositivo, su configuración y funcionalidades, y sobre si funciona correctamente.
-
-
- Completo: se envían todos los datos de diagnóstico básicos, junto con información de uso de las aplicaciones y las características y sobre los sitios web que exploras, así como información adicional sobre el estado y la actividad del dispositivo y el informe de errores mejorado.
-
-
- No hemos podido cambiar la configuración de privacidad. Comprueba el nombre de usuario y la contraseña e inténtalo de nuevo.
-
-
- Elige la cantidad de datos de diagnóstico que deseas enviar a Microsoft. Los datos de diagnóstico se utilizan para ayudar a mantener Windows seguro y actualizado, solucionar problemas y hacer mejoras en los productos. Independientemente de la opción que selecciones, el dispositivo será igual de seguro y funcionará normalmente.
-
-
- Datos de diagnóstico
- Label for Setting item to control Privacy
-
-
- Escribe tus credenciales para establecer el nivel de privacidad en este dispositivo.
-
-
- Establecer el nivel de privacidad
-
-
- Actualizar
- Refresh button
-
-
- Repetir canción
- Music player page repeat toggle text
-
-
- Reiniciar
-
-
- Reiniciar
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Uso: Comando RunAsAdmin
-
-Ejemplos:
-> RunAsdmin TZUTIL /s "Hora estándar del Pacífico"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Guardar
-
-
- Factor de escala
-
-
- Seleccionar todo
-
-
- Enviar telemetría
-
-
- No disponible
-
-
- Registro de sesión
-
-
- Hubo un problema al configurar la página predeterminada a {0}.
- Format string for app settings page
-
-
- Configuración
-
-
- Orden aleatorio
- Music player page shuffle toggle text
-
-
- Apagar
-
-
- Apagar
- Shutdown entry in the shutdown menu
-
-
- Inicia sesión en tu cuenta de Azure AD para usar esta característica.
-
-
- Omitir
-
-
- Omitir este paso
-
-
- Intervalo de presentación (segundos)
-
-
- Presentación
-
-
- Presentación
-
-
- Iniciar
-
-
- Iniciar
-
-
- Hora de inicio
-
-
- Estado
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Enviar
-
-
- Correcto
-
-
- Sistema
-
-
- Hubo un problema al intentar actualizar la configuración del sistema.
- Used within system settings
-
-
- Nivel de telemetría
-
-
- Telemetría
-
-
- Probar notificación gigante
-
-
- Probar notificación
-
-
- Windows 10 IoT es miembro de la familia de Windows 10 que lleva energía de la clase empresarial, seguridad y manejabilidad a Internet de las cosas. Aprovecha la experiencia incorporada, el ecosistema y la conectividad en la nube de Windows, que permite a las organizaciones crear su Internet de las cosas con dispositivos seguros que se pueden aprovisionar rápidamente, administrar fácilmente y conectar sin problemas a una estrategia de nube global.
-
-
- Altura del mosaico
-
-
- Personalización
-
-
- Ancho del icono
-
-
- Tiempo de espera de la conexión agotado
-
-
- Se ha actualizado la zona horaria: {0}
-
-
- Error: Error de comunicación con el servicio de El tiempo
-
-
- Error al actualizar debido a un error desconocido.
- App update error, unknown
-
-
- Anular toda la selección
-
-
- Error no especificado
-
-
- Opciones avanzadas
-
-
- Buscar ahora
-
-
- Instalar ahora
-
-
- {0} actualización pendiente
- {0} is singular amount of updates
-
-
- Se encontraron {0} actualizaciones nuevas.
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} actualizaciones pendientes
- {0} is plural amount of updates
-
-
- Usar los iconos de ventana de MDL2
-
-
- Usar contraseña
-
-
- Nombre de usuario
-
-
- Portal de dispositivos Windows
-
-
- Configuración del Portal de dispositivos
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Portal de dispositivos Windows
-
-
- Ubicación actual ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Tu ubicación
-
-
- Tu ubicación
- Label for map pin
-
-
- Ubicación desconocida
- Label for map pin
-
-
- Sensor:
- Label for temperature sensor output
-
-
- Tiempo
-
-
- Error al cargar la página del Tiempo.
-
-Haz clic en el botón Actualizar en la parte inferior derecha de la pantalla para volver a cargar esta página.
-
-Si no tiene claves de la API del Tiempo, ve a weatherunlocked.com. Guarda las claves en "WeatherTokens.config" en la carpeta de estado Local de la aplicación. A continuación, actualiza la página.
-
-
- El tiempo proporcionados por:
-
-
- Tiempo
-
-
- Escribir dirección web
-
-
- Explorador web
-
-
- Esto es Windows IoT Enterprise
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Actualizar
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Última comprobación:
- For a timestamp
-
-
- Última actualización:
- For a timestamp
-
-
- Estado de actualización:
-
-
- Mensaje de estado:
-
-
- Windows Update
-
-
- Windows Update
-
-
- Directorio de trabajo no válido: {0}
-
-
- WPS
-
-
- Permite que esta aplicación acceda a tu ubicación
-
-
- Elige tu configuración y selecciona "Aceptar" para guardarla. Puedes cambiar esta configuración en cualquier momento.
-
-
- Permite que Microsoft use tu ubicación
-
-
- Continuar automáticamente...
-
-
- Aceptar
-
-
- Quieres permitir que {0} acceda a tu ubicación precisa?
- {0} is the name of a page
-
-
- Ubicación
-
-
- Para cambiar esto más adelante, ve a Configuración > Permisos.
-
-
- No
-
-
- Sí
-
-
- No podrás obtener experiencias basadas en la ubicación como, por ejemplo, mapas y el tiempo, ni podrás disfrutar de otros servicios que requieran tu ubicación para funcionar.
-
-
- Obtén experiencias basadas en la ubicación como, por ejemplo, mapas y el tiempo. Permite que esta aplicación solicite tu ubicación. Microsoft usará los datos de ubicación para que podamos mejorar los servicios de ubicación.
-
-
- Solo se envía información sobre el dispositivo, su configuración y funcionalidades, y sobre si funciona correctamente. Los datos de diagnóstico se usan para ayudar a mantener Windows actualizado y protegido, solucionar problemas y realizar mejoras en los productos. Independientemente de si seleccionas el nivel Básico o Completo, el dispositivo estará protegido y funcionará con normalidad.
-
-
- Básico
-
-
- Se envían todos los datos de diagnóstico básicos, junto con información de uso de las aplicaciones y las características y sobre los sitios web que exploras, así como información adicional sobre el estado y la actividad del dispositivo y el informe de errores mejorado. Los datos de diagnóstico se usan para ayudar a mantener Windows actualizado y protegido, solucionar problemas y realizar mejoras en los productos. Independientemente de si seleccionas el nivel Básico o Completo, el dispositivo estará protegido y funcionará con normalidad.
-
-
- Completo
-
-
- Elige una configuración de privacidad para tu dispositivo y selecciona "Aceptar" para guardarla.
-
-
- Envía datos de diagnóstico a Microsoft
-
-
- Diagnósticos
-
-
- Si permites el acceso, esta aplicación podrán usar las capacidades del dispositivo para determinar tu ubicación y Microsoft usará los datos de ubicación para mejorar los servicios de ubicación. La denegación de acceso bloquea a Windows para que no pueda proporcionarle tu ubicación a la aplicación.
-
-
- Información sobre las opciones de privacidad
-
-
- Descubre cómo esta configuración influye en tu privacidad.
-
-
- Obtén más información sobre estas configuraciones
-
-
- Declaración de privacidad
-
-
- Sí
-
-
- Sí
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Usar AAD v2
+
+
+ Acceso revocado
+
+
+ Descripción:
+
+
+ Servidor DHCP:
+
+
+ DNS:
+
+
+ Dirección de puerta de enlace:
+
+
+ Dirección IPv4:
+
+
+ Nombre:
+
+
+ Dirección física:
+
+
+ Máscara de subred:
+
+
+ Tipo
+
+
+ Versión de la aplicación
+
+
+ Aplicaciones
+
+
+ Estás a punto de iniciar una aplicación externa. Tendrás que usar el Portal de dispositivos Windows para volver a esta aplicación. ¿Quieres continuar?
+ Dialog prompt for launching external apps
+
+
+ Aplicaciones
+
+
+ Configuración de la aplicación
+
+
+ Establece las horas activas para que sepamos cuándo sueles usar este dispositivo. No reiniciaremos automáticamente durante las horas activas.
+
+
+ No se pueden guardar las nuevas horas de inicio y finalización porque son iguales. Selecciona nuevas horas o desactiva la característica.
+
+
+ Opciones avanzadas
+ Advanced section title
+
+
+ Controla cada uno de los pasos de actualización de captura, descarga e instalación.
+
+
+ Opciones de actualización automática
+ Auto-Update section title
+
+
+ Permitir que la aplicación instale actualizaciones de la aplicación fuera de horas activas
+
+
+ Actualizaciones de aplicaciones
+ App update display dialog header
+
+
+ Última comprobación: {0}, {1}
+ {0} is date, {1} is time
+
+
+ No se puede determinar cuándo se buscaron actualizaciones por última vez
+
+
+ Actualizaciones de aplicaciones
+ Label for setting item to check for app updates
+
+
+ Iniciar sesión en MSA y AAD
+
+
+ Inicia sesión en AAD usando la cuenta de tu organización.
+
+
+ Inicio de sesión en Azure AD (AAD)
+
+
+ AAD
+
+
+ Autentica Microsoft Graph y otros recursos
+
+
+ Autentica solo Microsoft Graph
+
+
+ Cancelar
+
+
+ La cuenta de tu organización
+
+
+ Si te bloqueas en cualquier momento y no puedes salir del asistente de inicio de sesión, espera {0} segundos y deberías volver a la aplicación.
+
+
+ Iniciando sesión...
+
+
+ Cerrando sesión...
+
+
+ Inicia sesión en tu cuenta de Microsoft aquí
+
+
+ Inicio de sesión en la cuenta de Microsoft (MSA)
+
+
+ MSA
+
+
+ Autenticación
+
+
+ Inicio de sesión en Microsoft
+
+
+ Error al iniciar sesión ({0})
+
+
+ Inicio de sesión correcto ({0})
+
+
+ Iniciar sesión
+
+
+ Cierre de sesión: {0}
+
+
+ Cerrar sesión
+
+
+ Reproducción automática
+ Music player page auto-play toggle text
+
+
+ Ajuste de escala automático
+
+
+ Error al actualizar debido a que la batería está baja.
+ App update error, low battery
+
+
+ Intentando emparejarse con {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Emparejándose con {0} ({1}).
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ ¿El PIN que se muestra en el dispositivo coincide con {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Desconocido
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Actualmente emparejado
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Listo para emparejar
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Estado desconocido
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Escribe este PIN en el dispositivo con el que se va a emparejar: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Escribe el PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Solicitud de emparejamiento entrante de {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Este dispositivo ya está registrado para emparejamientos entrantes. (operaciones admitidas: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Error de registro para emparejamientos entrantes.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Registrado correctamente para emparejamientos entrantes. (Operaciones admitidas: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ El PIN introducido es incorrecto.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ No se encontró ningún adaptador Bluetooth que se pueda usar en este dispositivo: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Emparejar
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Error al emparejarse con {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Emparejado correctamente con {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Predeterminado
+ Text label for the corresponding device pairing protection level
+
+
+ Encriptación y autenticación
+ Text label for the corresponding device pairing protection level
+
+
+ Encriptación
+ Text label for the corresponding device pairing protection level
+
+
+ Ninguno
+ Text label for the corresponding device pairing protection level
+
+
+ El dispositivo ahora es reconocible y está listo para emparejarse con otros dispositivos Bluetooth.
+ Text displayed when StartWatcher is invoked
+
+
+ Tu dispositivo ya no busca otros dispositivos Bluetooth.
+ Text displayed when StopWatcher is invoked
+
+
+ Desemparejar
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Error al desemparejarse de {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Desemparejado correctamente de {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Página Inicio
+
+
+ Explorador web
+
+
+ Cancelar
+
+
+ No se puede cambiar de directorio. Usa rutas de acceso completas en los comandos.
+
+
+ Zona horaria
+ Time zone text
+
+
+ Buscando actualizaciones...
+ App update status
+
+
+ Buscar actualizaciones
+
+
+ Borrar cuentas
+
+
+ Se ha producido un problema al borrar las cuentas.
+
+
+ Se borrarán las cuentas de Windows siguientes:
+{0}
+
+¿Quieres continuar?
+
+
+ Se han borrado las cuentas
+
+
+ Borrando las cuentas...
+
+
+ Borrar
+
+
+ Cerrar
+
+
+ El dispositivo no puede ejecutar el procesador de línea de comandos.
+Para habilitarlo, ejecuta el siguiente comando como "administrador" en el dispositivo:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Puedes ejecutar el comando en la página Procesos del Portal de dispositivos Windows IoT. De lo contrario, también puedes usar PowerShell para conectarte al dispositivo de Windows IoT.
+Para obtener más información, visita http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Error al ejecutar el comando como administrador: {0}
+
+
+ Error al habilitar el procesador de línea de comandos (cmd.exe) en el dispositivo: {0}
+
+
+ El procesador de línea de comandos (cmd.exe) se habilitó correctamente en el dispositivo.
+
+
+ Color del mosaico
+
+
+ Atrás
+ Back UI navigation
+
+
+ Mostrar información del dispositivo
+
+
+ Adelante
+ Forward UI navigation
+
+
+ Activar/Desactivar pantalla completa
+
+
+ Clonar vista
+ Clone current view to another display
+
+
+ Guardar rápidamente el registro
+
+
+ Registro de sesión
+
+
+ Establecer página predeterminada
+
+
+ Comando confirmado.
+
+
+ Escribir línea de comandos
+ Placeholder for command line input text box
+
+
+ Error al ejecutar la línea de comandos: {0}
+
+
+ Línea de comandos
+
+
+ Línea de comandos
+ Title for command line page
+
+
+ Se agotó el tiempo de espera del comando tras {0} segundos sin resultados.
+
+
+ Nombre del equipo
+
+
+ Confirmación
+
+
+ Conectar automáticamente
+
+
+ Conectar automáticamente
+
+
+ Conectar
+
+
+ Conectar
+
+
+ Dispositivos conectados
+
+
+ Error al actualizar. Conéctate a una Wi-Fi y vuelve a intentarlo.
+ App update error, poor connection
+
+
+ Continuar
+
+
+ No se pudieron analizar los resultados del comando
+
+
+ Anillo actual
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Página de la aplicación predeterminada
+
+
+ El idioma predeterminado se está seleccionando automáticamente...
+
+
+ Se han eliminado {0} registros
+ {0} is plural number of logs
+
+
+ Se ha eliminado {0} registro
+ {0} is singular number of logs
+
+
+ ¿Quieres eliminar {0} registro?
+ {0} is singular number of logs
+
+
+ ¿Quieres eliminar {0} registros?
+ {0} is plural number of logs
+
+
+ Eliminar selección
+
+
+ Identificador de dispositivo de Azure
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ Ir a la página del dispositivo
+
+
+ Dirección IP: {0}
+Versión del sistema operativo: {1}
+Versión de la aplicación: {2}
+
+
+ Versión de la aplicación
+ Field label
+
+
+ Nombre del dispositivo
+ Field label
+
+
+ Dirección IP
+ Field label
+
+
+ Red
+ Field label
+
+
+ Versión del SO
+ Label for OS Version field in main page
+
+
+ para comenzar a desarrollar
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Información del dispositivo
+
+
+ Visita
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ La página a la que estás intentando acceder requiere el uso de API del Portal de dispositivos Windows (WDP). Inicia sesión con tus credenciales de WDP para continuar.
+
+
+ Hubo un problema al iniciar sesión.
+
+
+ Has iniciado sesión correctamente en el Portal de dispositivos
+
+
+ Comprobando las credenciales del Portal de dispositivos...
+
+
+ No se puede obtener el tiempo. ¿Quieres intentarlo de nuevo?
+
+
+ Conexiones directas
+
+
+ Desconectar
+ This disconnects the connected network
+
+
+ Se ha actualizado el idioma para mostrar: {0}
+
+
+ Dominio
+
+
+ La descarga ha finalizado.
+ App update status
+
+
+ Error al descargar. Vuelve a intentarlo más tarde.
+
+
+ Descargando actualización
+ App update status
+
+
+ Descargar actualizaciones
+
+
+ Dibujar
+
+
+ "{0} registros enviados a {1}"
+ {0} is plural number of logs, {1} is email address
+
+
+ "Registro {0} enviado a {1}"
+ {0} is singular number of logs, {1} is email address
+
+
+ Registro de correo electrónico
+
+
+ ¿Quieres enviarte {0} por correo electrónico?
+ {0} is filename
+
+
+ Se ha producido un problema al enviar el registro por correo electrónico: {0}
+ {0} is exception message
+
+
+ Puedes encontrar los registros en la página de registros
+
+
+ "¿Quieres enviarte el registro {0} por correo electrónico?"
+ {0} is singular number of logs
+
+
+ Se ha producido un problema al enviar los registros por correo electrónico: {0}
+ {0} is an exception message
+
+
+ ¿Quieres enviarte los registros {0} por correo electrónico?
+ {0} is plural number of logs
+
+
+ Registros de correo electrónico
+
+
+ Correo electrónico seleccionado
+
+
+ Habilitar procesador de línea de comandos
+
+
+ Protector de pantalla
+ Toggle switch for enabling the screensaver
+
+
+ Hora de finalización
+
+
+ Error
+
+
+ Hubo un problema al recuperar la información del tiempo
+
+
+ Ethernet
+ Field label
+
+
+ GUID de proveedor de ETW: {0}
+ Format string for app settings page
+
+
+ Ejecutar comandos como DefaultAccount
+
+
+ Explorar
+
+
+ Archivo guardado: {0}
+ {0} is a filename
+
+
+ Distribución de paquetes piloto
+ Device servicing flighting
+
+
+ Información sobre la distribución de paquetes piloto
+ Device servicing flighting
+
+
+ El anillo del piloto se ha cambiado a {0}.
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ Hubo un problema al cambiar el anillo del piloto
+
+
+ Previsión
+ Weather forecast
+
+
+ Estás a punto de entrar en modo de pantalla completa. Para salir, debes presionar [Esc] en el teclado. ¿Quieres continuar?
+
+
+ Modo de pantalla completa
+
+
+ Presiona [Esc] para salir del modo de pantalla completa.
+
+
+ General
+
+
+ Panel IoTEnterprise
+ A generic board name
+
+
+ GitHub
+
+
+ Ayuda
+
+
+ Ayuda
+
+
+ Ayuda
+
+
+ Idioma de entrada del teclado actualizado: {0}
+
+
+ La instalación ha finalizado.
+ App update status
+
+
+ Error de instalación. Vuelve a intentarlo más tarde.
+
+
+ Instalando actualización
+ App update status
+
+
+ Instalar actualizaciones
+
+
+ Credencial no válida
+
+
+ '{0}' no es una ubicación válida.
+ Format string for app settings page
+
+
+ '{0}' no es un valor válido. El valor debe ser mayor o igual que 1.
+ Format string for app settings page
+
+
+ '{0}' no es un valor válido.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Diseño del teclado
+ Field label
+
+
+ Reiniciar esta aplicación para aplicar una configuración nueva
+
+
+ Idioma
+
+
+ Idioma
+ Field label
+
+
+ Cargando...
+
+
+ Cargando información del tiempo...
+
+
+ El registro se ha enviado a {0}
+ {0} is email address
+
+
+ El registro se ha guardado en: {0}
+ {0} is filename
+
+
+ Registros
+
+
+ Registros
+
+
+ Nombre del dispositivo
+ Field label
+
+
+ Dirección IP
+ Field label
+
+
+ Versión del sistema operativo
+ Label for OS Version field in main page
+
+
+ Esta es una imagen de prueba de Windows 10 IoT Enterprise diseñada únicamente para prototipos. Si quieres comercializar tu dispositivo, debes usar un FFU personalizado para optimizar la seguridad del dispositivo.
+ Maker Imager Security Notice
+
+
+ Token de Servicio de Mapas de Bing
+
+
+ Es necesario el token de Servicio de Mapas de Bing
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Cuenta de Microsoft (MSA)
+
+
+ Actualmente reproduciendo
+ Music player page status text (currently playing)
+
+
+ Selecciona una canción y haz clic en reproducir.
+ Music player page status text (default)
+
+
+ Agrega uno o más archivos de audio a la carpeta Música.
+Puedes agregar música en el Portal de dispositivos Windows usando Aplicaciones > Explorador de archivos.
+ Music player page instructions text
+
+
+ Cargando música
+ Music player page loading panel text
+
+
+ Cargando
+ Music player page status text (loading)
+
+
+ No se ha encontrado música
+ Music player page no music found prompt text
+
+
+ Volver a intentarlo
+ Music player page reload button text (no files prompt)
+
+
+ Música
+
+
+ Música
+
+
+ En pausa
+ Music player page status text (paused)
+
+
+ Reproduciendo
+ Music player page status text (playing)
+
+
+ Iniciar sesión
+
+
+ Desconocido
+
+
+ Menú
+
+
+ Adaptadores de red
+
+
+ Conectado
+
+
+ Conectado
+
+
+ Comprobando los requisitos de red
+
+
+ Comprobando los requisitos de red
+
+
+ Acceso a Internet limitado
+
+
+ Acceso local y a Internet
+
+
+ Solo acceso de red local
+
+
+ Sin conectividad
+
+
+ INFORMACIÓN DE RED
+
+
+ Red no disponible
+
+
+ Escribe la clave de seguridad de red
+
+
+ Escribe la clave de seguridad de red
+
+
+ Red y Wi-Fi
+
+
+ Red y Wi-Fi
+
+
+ Ver las propiedades de red
+
+
+ Propiedades de red
+
+
+ Estás a punto de ser redirigido al portal interno de esta red Wi-Fi. ¿Quieres continuar?
+
+
+ Network Redirect
+
+
+ Siguiente
+
+
+ Siguiente
+
+
+ No se encontró ninguna cuenta
+
+
+ No
+
+
+ no hay nombre de dispositivo
+
+
+ sin conexión a Internet
+
+
+ No hay registros seleccionados
+
+
+ No se ha encontrado música
+ Music player page panel text
+
+
+ No se encontró ninguno
+
+
+ No hay ninguna actualización pendiente de descarga.
+ App update status
+
+
+ No hay ninguna actualización pendiente de instalación.
+ App update status
+
+
+ n/a
+
+
+ Notificaciones
+
+
+ Notificaciones
+
+
+ No se encontraron nuevas soluciones.
+ Format string displayed when no app updates are found
+
+
+ Aceptar
+ Button content text for the Bluetooth settings page
+
+
+ Elige tu idioma
+
+
+ Vamos a conectarnos
+
+
+ Te damos la bienvenida a Windows 10 IoT Enterprise
+
+
+ Vamos a quitar algunas cosas de en medio.
+
+
+ Te damos la bienvenida a Windows 10 IoT Enterprise
+
+
+ Id. de edición del sistema operativo
+
+
+ Edición del sistema operativo
+
+
+ Información del sistema operativo
+
+
+ Información del sistema operativo
+
+
+ No disponible
+ Text shown when we cannot retrieve the OS Version
+
+
+ Versión del sistema operativo
+
+
+ Paquetes
+ Software packages
+
+
+ Paquetes instalados
+ Software packages
+
+
+ Configuración de la página
+
+
+ Páginas
+
+
+ Contraseña
+
+
+ Cargando imágenes...
+ Default text when no images are available
+
+
+ Agrega imágenes a la carpeta Imágenes.
+Puedes agregar imágenes en el Portal de dispositivos Windows usando Aplicaciones > Explorador de archivos.
+
+
+ No se encontró ninguna imagen
+ Default text when no images are available
+
+
+ Plataforma
+
+
+ Reproducir
+
+
+ Opciones de Inicio/apagado
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Básico: solo se envía información sobre el dispositivo, su configuración y funcionalidades, y sobre si funciona correctamente.
+
+
+ Completo: se envían todos los datos de diagnóstico básicos, junto con información de uso de las aplicaciones y las características y sobre los sitios web que exploras, así como información adicional sobre el estado y la actividad del dispositivo y el informe de errores mejorado.
+
+
+ No hemos podido cambiar la configuración de privacidad. Comprueba el nombre de usuario y la contraseña e inténtalo de nuevo.
+
+
+ Elige la cantidad de datos de diagnóstico que deseas enviar a Microsoft. Los datos de diagnóstico se utilizan para ayudar a mantener Windows seguro y actualizado, solucionar problemas y hacer mejoras en los productos. Independientemente de la opción que selecciones, el dispositivo será igual de seguro y funcionará normalmente.
+
+
+ Datos de diagnóstico
+ Label for Setting item to control Privacy
+
+
+ Escribe tus credenciales para establecer el nivel de privacidad en este dispositivo.
+
+
+ Establecer el nivel de privacidad
+
+
+ Actualizar
+ Refresh button
+
+
+ Repetir canción
+ Music player page repeat toggle text
+
+
+ Reiniciar
+
+
+ Reiniciar
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Uso: Comando RunAsAdmin
+
+Ejemplos:
+> RunAsdmin TZUTIL /s "Hora estándar del Pacífico"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Guardar
+
+
+ Factor de escala
+
+
+ Seleccionar todo
+
+
+ Enviar telemetría
+
+
+ No disponible
+
+
+ Registro de sesión
+
+
+ Hubo un problema al configurar la página predeterminada a {0}.
+ Format string for app settings page
+
+
+ Configuración
+
+
+ Orden aleatorio
+ Music player page shuffle toggle text
+
+
+ Apagar
+
+
+ Apagar
+ Shutdown entry in the shutdown menu
+
+
+ Inicia sesión en tu cuenta de Azure AD para usar esta característica.
+
+
+ Omitir
+
+
+ Omitir este paso
+
+
+ Intervalo de presentación (segundos)
+
+
+ Presentación
+
+
+ Presentación
+
+
+ Iniciar
+
+
+ Iniciar
+
+
+ Hora de inicio
+
+
+ Estado
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Enviar
+
+
+ Correcto
+
+
+ Sistema
+
+
+ Hubo un problema al intentar actualizar la configuración del sistema.
+ Used within system settings
+
+
+ Nivel de telemetría
+
+
+ Telemetría
+
+
+ Probar notificación gigante
+
+
+ Probar notificación
+
+
+ Windows 10 IoT es miembro de la familia de Windows 10 que lleva energía de la clase empresarial, seguridad y manejabilidad a Internet de las cosas. Aprovecha la experiencia incorporada, el ecosistema y la conectividad en la nube de Windows, que permite a las organizaciones crear su Internet de las cosas con dispositivos seguros que se pueden aprovisionar rápidamente, administrar fácilmente y conectar sin problemas a una estrategia de nube global.
+
+
+ Altura del mosaico
+
+
+ Personalización
+
+
+ Ancho del icono
+
+
+ Tiempo de espera de la conexión agotado
+
+
+ Se ha actualizado la zona horaria: {0}
+
+
+ Error: Error de comunicación con el servicio de El tiempo
+
+
+ Error al actualizar debido a un error desconocido.
+ App update error, unknown
+
+
+ Anular toda la selección
+
+
+ Error no especificado
+
+
+ Opciones avanzadas
+
+
+ Buscar ahora
+
+
+ Instalar ahora
+
+
+ {0} actualización pendiente
+ {0} is singular amount of updates
+
+
+ Se encontraron {0} actualizaciones nuevas.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} actualizaciones pendientes
+ {0} is plural amount of updates
+
+
+ Usar los iconos de ventana de MDL2
+
+
+ Usar contraseña
+
+
+ Nombre de usuario
+
+
+ Portal de dispositivos Windows
+
+
+ Configuración del Portal de dispositivos
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Portal de dispositivos Windows
+
+
+ Ubicación actual ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Tu ubicación
+
+
+ Tu ubicación
+ Label for map pin
+
+
+ Ubicación desconocida
+ Label for map pin
+
+
+ Sensor:
+ Label for temperature sensor output
+
+
+ Tiempo
+
+
+ Error al cargar la página del Tiempo.
+
+Haz clic en el botón Actualizar en la parte inferior derecha de la pantalla para volver a cargar esta página.
+
+Si no tiene claves de la API del Tiempo, ve a weatherunlocked.com. Guarda las claves en "WeatherTokens.config" en la carpeta de estado Local de la aplicación. A continuación, actualiza la página.
+
+
+ El tiempo proporcionados por:
+
+
+ Tiempo
+
+
+ Escribir dirección web
+
+
+ Explorador web
+
+
+ Esto es Windows IoT Enterprise
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Actualizar
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Última comprobación:
+ For a timestamp
+
+
+ Última actualización:
+ For a timestamp
+
+
+ Estado de actualización:
+
+
+ Mensaje de estado:
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Directorio de trabajo no válido: {0}
+
+
+ WPS
+
+
+ Permite que esta aplicación acceda a tu ubicación
+
+
+ Elige tu configuración y selecciona "Aceptar" para guardarla. Puedes cambiar esta configuración en cualquier momento.
+
+
+ Permite que Microsoft use tu ubicación
+
+
+ Continuar automáticamente...
+
+
+ Aceptar
+
+
+ Quieres permitir que {0} acceda a tu ubicación precisa?
+ {0} is the name of a page
+
+
+ Ubicación
+
+
+ Para cambiar esto más adelante, ve a Configuración > Permisos.
+
+
+ No
+
+
+ Sí
+
+
+ No podrás obtener experiencias basadas en la ubicación como, por ejemplo, mapas y el tiempo, ni podrás disfrutar de otros servicios que requieran tu ubicación para funcionar.
+
+
+ Obtén experiencias basadas en la ubicación como, por ejemplo, mapas y el tiempo. Permite que esta aplicación solicite tu ubicación. Microsoft usará los datos de ubicación para que podamos mejorar los servicios de ubicación.
+
+
+ Solo se envía información sobre el dispositivo, su configuración y funcionalidades, y sobre si funciona correctamente. Los datos de diagnóstico se usan para ayudar a mantener Windows actualizado y protegido, solucionar problemas y realizar mejoras en los productos. Independientemente de si seleccionas el nivel Básico o Completo, el dispositivo estará protegido y funcionará con normalidad.
+
+
+ Básico
+
+
+ Se envían todos los datos de diagnóstico básicos, junto con información de uso de las aplicaciones y las características y sobre los sitios web que exploras, así como información adicional sobre el estado y la actividad del dispositivo y el informe de errores mejorado. Los datos de diagnóstico se usan para ayudar a mantener Windows actualizado y protegido, solucionar problemas y realizar mejoras en los productos. Independientemente de si seleccionas el nivel Básico o Completo, el dispositivo estará protegido y funcionará con normalidad.
+
+
+ Completo
+
+
+ Elige una configuración de privacidad para tu dispositivo y selecciona "Aceptar" para guardarla.
+
+
+ Envía datos de diagnóstico a Microsoft
+
+
+ Diagnósticos
+
+
+ Si permites el acceso, esta aplicación podrán usar las capacidades del dispositivo para determinar tu ubicación y Microsoft usará los datos de ubicación para mejorar los servicios de ubicación. La denegación de acceso bloquea a Windows para que no pueda proporcionarle tu ubicación a la aplicación.
+
+
+ Información sobre las opciones de privacidad
+
+
+ Descubre cómo esta configuración influye en tu privacidad.
+
+
+ Obtén más información sobre estas configuraciones
+
+
+ Declaración de privacidad
+
+
+ Sí
+
+
+ Sí
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/fr-FR/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/fr-FR/Resources.resw
index 5e22b8fb3..5bfe3f6e5 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/fr-FR/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/fr-FR/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Utiliser AAD v2
-
-
- Accès révoqué
-
-
- Description :
-
-
- Serveur DHCP :
-
-
- DNS :
-
-
- Adresse de la passerelle :
-
-
- Adresse IPv4 :
-
-
- Nom :
-
-
- Adresse physique :
-
-
- Masque de sous-réseau :
-
-
- Type :
-
-
- Version de l’application
-
-
- Applications
-
-
- Vous êtes sur le point de lancer une application externe. Vous devez utiliser le Portail d'appareil Windows pour revenir à cette application. Voulez-vous continuer ?
- Dialog prompt for launching external apps
-
-
- Applications
-
-
- Paramètres des applications
-
-
- Définissez des heures d’activité pour nous permettre de savoir quand vous utilisez généralement cet appareil. Nous ne procéderons pas automatiquement au redémarrage pendant les heures d’activité.
-
-
- Impossible d’enregistrer les nouvelles heures de début et de fin, car elles sont identiques. Sélectionnez de nouvelles heures ou désactivez la fonctionnalité.
-
-
- Options avancées
- Advanced section title
-
-
- Contrôlez chacune des étapes de récupération, de téléchargement et d'installation de la mise à jour.
-
-
- Options de mise à jour automatique
- Auto-Update section title
-
-
- Autoriser l'application installer des mises à jour d'application en dehors des heures d’activité
-
-
- Mises à jour d'applications
- App update display dialog header
-
-
- Dernière vérification : le {0} à {1}
- {0} is date, {1} is time
-
-
- Impossible de déterminer l'heure de la dernière recherche de mises à jour
-
-
- Mises à jour d'applications
- Label for setting item to check for app updates
-
-
- Se connecter à MSA et AAD
-
-
- Connectez-vous à AAD à l’aide de votre compte d’organisation.
-
-
- Connexion à Azure AD (AAD)
-
-
- AAD
-
-
- Authentifie Microsoft Graph et d'autres ressources
-
-
- Authentifie Microsoft Graph uniquement
-
-
- Annuler
-
-
- Votre compte d'organisation
-
-
- Si vous êtes bloqué à un certain point et ne pouvez pas quitter l’Assistant Connexion, veuillez patienter {0} secondes avant de revenir dans l’application.
-
-
- Connexion en cours...
-
-
- Déconnexion en cours...
-
-
- Connectez-vous à votre compte Microsoft ici
-
-
- Connexion au compte Microsoft (MSA)
-
-
- MSA
-
-
- Authentification
-
-
- Connexion à Microsoft
-
-
- Échec de la connexion ({0})
-
-
- Connexion réussie ({0})
-
-
- Se connecter
-
-
- Déconnecté : {0}
-
-
- Se déconnecter
-
-
- Lecture automatique
- Music player page auto-play toggle text
-
-
- Montée en charge automatique
-
-
- Échec de la mise à jour en raison d’une batterie faible.
- App update error, low battery
-
-
- Tentative de couplage avec {0} ({1}).
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Couplage avec {0} ({1}).
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- Le PIN indiqué sur l’appareil correspond-il à {0} ?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Inconnu
- Text displayed when the Bluetooth device name is unknown
-
-
- Actuellement couplé
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Prêt au couplage
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- État inconnu
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Entrez le code PIN suivant sur l’appareil que vous souhaitez coupler : {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Entrer le code PIN :
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Demande de couplage entrante provenant de {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Cet appareil est déjà enregistré pour le couplage entrant. (Cérémonies prises en charge : {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Échec de l'enregistrement pour le couplage entrant.
- Text displayed when Inbound pairing handler registration fails
-
-
- Enregistrement pour le couplage entrant réussi. (Cérémonies prises en charge : {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- Le code PIN que vous avez entré n'est pas correct.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- Aucun adaptateur Bluetooth utilisable n’a été trouvé sur cet appareil : \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Coupler
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Échec du couplage avec {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Couplage avec {0} réussi ({1}).
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Par défaut
- Text label for the corresponding device pairing protection level
-
-
- Chiffrement et authentification
- Text label for the corresponding device pairing protection level
-
-
- Chiffrement
- Text label for the corresponding device pairing protection level
-
-
- Aucun(e)
- Text label for the corresponding device pairing protection level
-
-
- Votre appareil peut maintenant être détecté et est prêt à être couplé avec d'autres appareils Bluetooth.
- Text displayed when StartWatcher is invoked
-
-
- Votre appareil ne recherche plus d’autres appareils Bluetooth.
- Text displayed when StopWatcher is invoked
-
-
- Découpler
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Échec du découplage de {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Découplage avec {0} réussi ({1}).
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Page d'accueil
-
-
- Navigateur web
-
-
- Annuler
-
-
- La modification du répertoire n’est pas prise en charge pour le moment. Utilisez des chemins complets dans vos commandes.
-
-
- Fuseau horaire
- Time zone text
-
-
- Recherche des mises à jour...
- App update status
-
-
- Rechercher les mises à jour
-
-
- Désactiver des comptes
-
-
- Un problème s'est produit lors de la désactivation de vos comptes
-
-
- Cette opération va désactiver les comptes Windows suivants :
-{0}
-
-Continuer ?
-
-
- Comptes désactivés
-
-
- Désactivation de comptes en cours...
-
-
- Effacer
-
-
- Fermer
-
-
- Votre appareil n’est pas autorisé à exécuter le processeur de ligne de commande.
-Pour qu'il puisse le faire, exécutez la commande en tant qu'administrateur sur votre appareil :
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Vous pouvez exécuter la commande sur la page Processus du Portail d'appareil Windows IoT ou utiliser PowerShell pour vous connecter à votre appareil Windows IoT.
-Pour plus d'informations, visitez http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Échec de l’exécution de la commande en tant qu’administrateur : {0}
-
-
- Échec de l’activation du processeur de ligne de commande (cmd.exe) sur votre appareil : {0}
-
-
- Le processeur de ligne de commande (cmd.exe) a été activé sur votre appareil.
-
-
- Couleur de la vignette
-
-
- Retour
- Back UI navigation
-
-
- Afficher les informations sur l’appareil
-
-
- Suivant
- Forward UI navigation
-
-
- Basculer en mode plein écran
-
-
- Cloner l'affichage
- Clone current view to another display
-
-
- Journal d’enregistrement rapide
-
-
- Journal de la session
-
-
- Définir la page par défaut
-
-
- Commande annulée.
-
-
- Entrer la ligne de commande
- Placeholder for command line input text box
-
-
- Erreur lors de l'exécution de la ligne de commande : {0}
-
-
- Ligne de commande
-
-
- Ligne de commande
- Title for command line page
-
-
- La commande a expiré après {0} secondes sans résultat.
-
-
- Nom de l'ordinateur
-
-
- Confirmation
-
-
- Se connecter automatiquement
-
-
- Se connecter automatiquement
-
-
- Se connecter
-
-
- Se connecter
-
-
- Appareils connectés
-
-
- Échec de la mise à jour. Connectez-vous au Wi-Fi et réessayez.
- App update error, poor connection
-
-
- Continue
-
-
- Impossible d’analyser le résultat de la commande
-
-
- Anneau actuel
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Page Application par défaut
-
-
- Nous lançons la sélection automatique de la langue par défaut...
-
-
- {0} journaux supprimés
- {0} is plural number of logs
-
-
- {0} journal supprimé
- {0} is singular number of logs
-
-
- Supprimer {0} journal ?
- {0} is singular number of logs
-
-
- Supprimer {0} journaux ?
- {0} is plural number of logs
-
-
- Supprimer la sélection
-
-
- ID d’appareil Azure
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- Accéder à la page Appareil
-
-
- Adresse IP : {0}
-Version du système d'exploitation : {1}
-Version de l'application : {2}
-
-
- Version de l’application
- Field label
-
-
- Nom de l’appareil
- Field label
-
-
- Adresse IP
- Field label
-
-
- Réseau
- Field label
-
-
- Version du système d’exploitation
- Label for OS Version field in main page
-
-
- pour commencer à développer
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Informations sur l’appareil
-
-
- Visitez
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- La page à laquelle vous tentez d’accéder nécessite l’utilisation d'API du Portail d'appareil Windows (WDP). Connectez-vous à l’aide de vos identifiants WDP pour continuer.
-
-
- Un problème s'est produit lors de la connexion.
-
-
- Connexion établie avec le Portail d'appareil !
-
-
- Vérification des identifiants du Portail d'appareil...
-
-
- Un problème s'est produit lors de l'obtention de la météo. Réessayer ?
-
-
- Connexions directes
-
-
- Déconnecter
- This disconnects the connected network
-
-
- Langue d'affichage mise à jour : {0}
-
-
- Domaine
-
-
- Téléchargement terminé !
- App update status
-
-
- Échec du téléchargement. Réessayez plus tard !
-
-
- Téléchargement de la mise à jour
- App update status
-
-
- Télécharger des mises à jour
-
-
- Dessiner
-
-
- « {0} journaux envoyés à {1} »
- {0} is plural number of logs, {1} is email address
-
-
- « {0} journal envoyé à {1} »
- {0} is singular number of logs, {1} is email address
-
-
- Envoyer le journal par e-mail
-
-
- Voulez-vous vous envoyer {0} par e-mail ?
- {0} is filename
-
-
- Un problème s'est produit lors de l'envoi de votre journal par e-mail : {0}
- {0} is exception message
-
-
- Vous trouverez vos journaux sur la page Journaux
-
-
- « Envoyer le journal {0} par e-mail à vous-même ? »
- {0} is singular number of logs
-
-
- Un problème s'est produit lors de l'envoi de vos journaux par e-mail : {0}
- {0} is an exception message
-
-
- Envoyer {0} journaux par e-mail à vous-même ?
- {0} is plural number of logs
-
-
- Envoyer les journaux par e-mail
-
-
- E-mail sélectionné
-
-
- Activer le processeur de ligne de commande
-
-
- Écran de veille
- Toggle switch for enabling the screensaver
-
-
- Heure de fin
-
-
- Erreur
-
-
- Un problème s’est produit lors de la récupération des infos sur la météo
-
-
- Ethernet
- Field label
-
-
- GUID du fournisseur ETW : {0}
- Format string for app settings page
-
-
- Exécution des commandes en tant que DefaultAccount
-
-
- Explorer
-
-
- Fichier enregistré : {0}
- {0} is a filename
-
-
- Distribution de version d’évaluation
- Device servicing flighting
-
-
- Informations sur la distribution de version d’évaluation
- Device servicing flighting
-
-
- L'anneau de la version d’évaluation a été modifié en {0} !
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- Un problème s'est produit lors de la modification de l'anneau de la version d’évaluation
-
-
- Prévision
- Weather forecast
-
-
- Vous êtes sur le point de passer en mode Plein écran. Pour quitter, vous devez appuyer sur [Échap] sur le clavier. Voulez-vous continuer ?
-
-
- Mode Plein écran
-
-
- Appuyez sur [Échap] pour quitter le mode Plein écran.
-
-
- Général
-
-
- Carte IoTEnterprise
- A generic board name
-
-
- GitHub
-
-
- Aide
-
-
- Aide
-
-
- Aide
-
-
- Langue du clavier de saisie mise à jour : {0}
-
-
- Installation terminée !
- App update status
-
-
- Échec de l'installation. Réessayez plus tard !
-
-
- Installation de la mise à jour
- App update status
-
-
- Installer les mises à jour
-
-
- Informations d'identification non valides
-
-
- « {0} » n'est pas un emplacement valide.
- Format string for app settings page
-
-
- « {0} » est une valeur non valide. La valeur doit être supérieure ou égale à 1.
- Format string for app settings page
-
-
- « {0} » est une valeur non valide.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Disposition du clavier
- Field label
-
-
- Redémarrer cette application pour appliquer les nouveaux paramètres
-
-
- Langue
-
-
- Langue
- Field label
-
-
- Chargement...
-
-
- Chargement des infos sur la météo...
-
-
- Le journal a été envoyé à {0}
- {0} is email address
-
-
- Journal enregistré dans : {0}
- {0} is filename
-
-
- Journaux
-
-
- Journaux
-
-
- Nom de l’appareil
- Field label
-
-
- Adresse IP
- Field label
-
-
- Version du système d’exploitation
- Label for OS Version field in main page
-
-
- Il s’agit d’une image de test de Windows 10 IoT Standard conçue pour le prototypage uniquement. Si vous envisager la commercialisation, vous devez utiliser un FFU personnalisé pour une sécurité optimale.
- Maker Imager Security Notice
-
-
- Jeton de service de Carte Bing
-
-
- Jeton de service de Carte Bing nécessaire
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Compte Microsoft (MSA)
-
-
- En cours de lecture
- Music player page status text (currently playing)
-
-
- Sélectionnez un morceau et cliquez sur lire.
- Music player page status text (default)
-
-
- Ajoutez au moins un fichier audio dans le dossier Musique.
-Vous pouvez ajouter de la musique dans le Portail d'appareil Windows en utilisant Applications > Explorateur de fichiers.
- Music player page instructions text
-
-
- Chargement de la musique
- Music player page loading panel text
-
-
- Chargement en cours
- Music player page status text (loading)
-
-
- Aucune musique trouvée
- Music player page no music found prompt text
-
-
- Réessayer
- Music player page reload button text (no files prompt)
-
-
- Musique
-
-
- Musique
-
-
- En pause
- Music player page status text (paused)
-
-
- Lecture en cours
- Music player page status text (playing)
-
-
- Se connecter
-
-
- Inconnu
-
-
- Menu
-
-
- Cartes réseau
-
-
- Connecté
-
-
- Connecté
-
-
- Vérification de la configuration réseau requise
-
-
- Vérification de la configuration réseau requise
-
-
- Accès Internet limité
-
-
- Accès Internet et local
-
-
- Accès réseau local uniquement
-
-
- Aucune connectivité
-
-
- INFORMATIONS RÉSEAU
-
-
- Réseau non disponible
-
-
- Entrer la clé de sécurité réseau
-
-
- Entrez la clé de sécurité réseau
-
-
- Réseau et Wi-Fi
-
-
- Réseau et Wi-Fi
-
-
- Afficher les propriétés du réseau
-
-
- Propriétés du réseau
-
-
- Vous allez être redirigé vers le portail captif de ce réseau Wi-Fi. Voulez-vous continuer ?
-
-
- Redirection du réseau
-
-
- Suivant
-
-
- Suivant
-
-
- Comptes introuvables
-
-
- Non
-
-
- no device name
-
-
- pas de connexion Internet
-
-
- Aucun journal sélectionné
-
-
- Aucune musique trouvée
- Music player page panel text
-
-
- Aucun élément trouvé
-
-
- Aucune mise à jour en attente à télécharger.
- App update status
-
-
- Aucune mise à jour en attente à installer.
- App update status
-
-
- N/A
-
-
- Notifications
-
-
- Notifications
-
-
- Aucune nouvelle mise à jour trouvée.
- Format string displayed when no app updates are found
-
-
- OK
- Button content text for the Bluetooth settings page
-
-
- Choisissez votre langue
-
-
- Connectez-vous
-
-
- Bienvenue dans Windows 10 IoT Standard
-
-
- Commençons par le commencement.
-
-
- Bienvenue dans Windows 10 IoT Standard
-
-
- ID d'édition du système d'exploitation
-
-
- Édition du système d'exploitation
-
-
- Informations sur le système d’exploitation
-
-
- Informations sur le système d’exploitation
-
-
- Non disponible
- Text shown when we cannot retrieve the OS Version
-
-
- Version du système d’exploitation
-
-
- Packages
- Software packages
-
-
- Packages installés
- Software packages
-
-
- Paramètres de page
-
-
- Pages
-
-
- Mot de passe
-
-
- Chargement des images
- Default text when no images are available
-
-
- Ajoutez des images dans le dossier Images.
-Vous pouvez ajouter des images dans le Portail d'appareil Windows en utilisant Applications > Explorateur de fichiers.
-
-
- Images introuvables
- Default text when no images are available
-
-
- Plateforme
-
-
- Lire
-
-
- Options d’alimentation
- Label for Setting item to control Power (shutdown/restart)
-
-
- De base : n'envoyez que des informations sur votre appareil, ses paramètres et ses fonctionnalités, ainsi que pour indiquer s'il fonctionne correctement.
-
-
- Complet : envoyez toutes les données de diagnostic de base en plus d'informations sur les sites web que vous parcourez et sur la manière dont vous utilisez des applications et des fonctionnalités, ainsi que des informations supplémentaires sur l'intégrité de votre appareil, son activité et des rapports d'erreurs améliorés.
-
-
- Nous ne pouvons pas modifier les paramètres de confidentialité. Vérifiez votre nom d'utilisateur et votre mot de passe, puis réessayez.
-
-
- Choisissez la quantité de données de diagnostic que vous souhaitez envoyer à Microsoft. Les données de diagnostic sont utilisées pour aider à maintenir Windows sécurisé et à jour, résoudre les problèmes et améliorer les produits. Quelle que soit l'option sélectionnée, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
-
-
- Données de diagnostic
- Label for Setting item to control Privacy
-
-
- Entrez vos identifiants pour définir le niveau de confidentialité sur cet appareil.
-
-
- Définir votre niveau de confidentialité
-
-
- Actualiser
- Refresh button
-
-
- Répéter le morceau
- Music player page repeat toggle text
-
-
- Redémarrer
-
-
- Redémarrer
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Utilisation : commande RunAsAdmin
-
-Exemples :
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Enregistrer
-
-
- Facteur de montée en charge
-
-
- Sélectionner tout
-
-
- Envoyer la télémétrie
-
-
- Non disponible
-
-
- Journal de la session
-
-
- Un problème s’est produit lors de la définition de la page par défaut sur {0}.
- Format string for app settings page
-
-
- Paramètres
-
-
- Lecture aléatoire
- Music player page shuffle toggle text
-
-
- Arrêter
-
-
- Arrêter
- Shutdown entry in the shutdown menu
-
-
- Connectez-vous à votre compte Azure AD pour utiliser cette fonctionnalité.
-
-
- Ignorer
-
-
- Ignorer cette étape
-
-
- Intervalle du diaporama (secondes)
-
-
- Diaporama
-
-
- Diaporama
-
-
- Démarrer
-
-
- Démarrer
-
-
- Heure de début
-
-
- Statut
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Soumettre
-
-
- Opération réussie
-
-
- Système
-
-
- Un problème s'est produit lors de la tentative de mise à jour de vos paramètres système.
- Used within system settings
-
-
- Niveau de télémétrie
-
-
- Télémétrie
-
-
- Tester la notification Jumbo
-
-
- Tester la notification
-
-
- Windows 10 IoT est un membre de la famille Windows 10 qui offre à l'Internet des objets de la puissance à l'échelle de l'entreprise, la sécurité et la facilité de gestion. Il tire profit de la connectivité au cloud, de l’écosystème et de l'expérience intégrés de Windows, ce qui permet aux organisations de créer leur Internet des objets avec des appareils sécurisés qui peuvent être rapidement approvisionnés, facilement gérés et connectés en toute transparence à une stratégie globale du cloud.
-
-
- Hauteur de la vignette
-
-
- Personnalisation
-
-
- Largeur de la vignette
-
-
- Délai de connexion dépassé
-
-
- Fuseau horaire mis à jour : {0}
-
-
- Erreur : Impossible de communiquer avec le service météo
-
-
- Échec de la mise à jour pour une raison inconnue.
- App update error, unknown
-
-
- Désélectionner tout
-
-
- Défaillance non spécifiée
-
-
- Options avancées
-
-
- Vérifier maintenant
-
-
- Installer maintenant
-
-
- Mise à jour en attente de {0}
- {0} is singular amount of updates
-
-
- {0} nouvelles mises à jour détectées.
- Format string displayed when new app updates are found. {0} is a number
-
-
- Mises à jour en attente de {0}
- {0} is plural amount of updates
-
-
- Utiliser des icônes de vignette MDL2
-
-
- Utiliser un mot de passe
-
-
- Nom d'utilisateur
-
-
- Portail d'appareil Windows
-
-
- Paramètres du Portail d'appareil
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Portail d'appareil Windows
-
-
- Emplacement actuel ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Votre emplacement
-
-
- Votre emplacement
- Label for map pin
-
-
- Emplacement inconnu
- Label for map pin
-
-
- Capteur :
- Label for temperature sensor output
-
-
- Météo
-
-
- Erreur lors du chargement de la page Météo.
-
-Cliquez sur le bouton Actualiser en bas à droite de l’écran pour recharger cette page.
-
-Si vous n’avez pas de clés API Météo, accédez à weatherunlocked.com. Enregistrez les clés de « WeatherTokens.config » dans le dossier de l’état local de cette application. Actualisez ensuite la page.
-
-
- Données météo fournies par :
-
-
- Météo
-
-
- Entrer une adresse web
-
-
- Navigateur web
-
-
- Bienvenue dans Windows IoT Standard
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Actualiser
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Dernière vérification :
- For a timestamp
-
-
- Dernière mise à jour :
- For a timestamp
-
-
- État mis à jour :
-
-
- Message de statut :
-
-
- Windows Update
-
-
- Windows Update
-
-
- Répertoire de travail non valide : {0}
-
-
- WPS
-
-
- Autoriser cette application à accéder à votre emplacement
-
-
- Choisissez vos paramètres, puis sélectionnez Accepter pour les enregistrer. Vous pouvez modifier ces paramètres à tout moment.
-
-
- Autoriser Microsoft à utiliser votre emplacement
-
-
- Continue automatiquement...
-
-
- Accepter
-
-
- Laissez {0} accéder à votre emplacement précis ?
- {0} is the name of a page
-
-
- Emplacement
-
-
- Pour modifier ce paramètre ultérieurement, accédez à Paramètres > Autorisations.
-
-
- Non
-
-
- Oui
-
-
- Vous ne serez pas en mesure de profiter d'expériences basées sur l'emplacement, comme les cartes et la météo, ou de profiter d'autres services qui requièrent votre emplacement pour pouvoir fonctionner.
-
-
- Profitez d'expériences basées sur l'emplacement, comme les cartes et la météo. Laissez cette application demander votre emplacement. Microsoft utilisera les données d'emplacement pour améliorer les services de localisation.
-
-
- Envoyez uniquement des informations sur votre appareil, ses paramètres et fonctionnalités, et sur son fonctionnement correct ou non. Les données de diagnostic sont utilisées pour permettre à Windows de rester sécurisé et à jour, de résoudre des problèmes et de permettre des améliorations des produits. Que vous sélectionniez De base ou Complet, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
-
-
- De base
-
-
- Envoyez toutes les données de diagnostic de base, ainsi que des informations sur les sites web que vous visitez et des informations sur votre utilisation des applications et des fonctionnalités, ainsi que des données supplémentaires sur l'intégrité des appareils, sur l'activité des appareils, ainsi que des rapports d'erreurs améliorés. Les données de diagnostic sont utilisées pour veiller à ce que Windows reste sécurisé et à jour, à résoudre les problèmes et à améliorer les produits. Que vous sélectionniez De base ou Complet, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
-
-
- Complet
-
-
- Choisissez un paramètre de confidentialité pour votre appareil, puis sélectionnez « Accepter » pour l’enregistrer.
-
-
- Envoyer des données de diagnostic à Microsoft
-
-
- Diagnostics
-
-
- Si vous autorisez l'accès, vous permettrez à cette application d'utiliser les fonctionnalités de votre appareil pour déterminer votre emplacement et Microsoft utilisera vos données d'emplacement pour améliorer les services de localisation. Refuser l'accès empêche uniquement Windows de fourni l'emplacement à cette application.
-
-
- Prenez connaissance de vos options de confidentialité
-
-
- Découvrez en quoi ce paramètre peut influencer votre confidentialité.
-
-
- Obtenir plus d'informations sur ces paramètres
-
-
- Déclaration de confidentialité
-
-
- Oui
-
-
- Oui
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Utiliser AAD v2
+
+
+ Accès révoqué
+
+
+ Description :
+
+
+ Serveur DHCP :
+
+
+ DNS :
+
+
+ Adresse de la passerelle :
+
+
+ Adresse IPv4 :
+
+
+ Nom :
+
+
+ Adresse physique :
+
+
+ Masque de sous-réseau :
+
+
+ Type :
+
+
+ Version de l’application
+
+
+ Applications
+
+
+ Vous êtes sur le point de lancer une application externe. Vous devez utiliser le Portail d'appareil Windows pour revenir à cette application. Voulez-vous continuer ?
+ Dialog prompt for launching external apps
+
+
+ Applications
+
+
+ Paramètres des applications
+
+
+ Définissez des heures d’activité pour nous permettre de savoir quand vous utilisez généralement cet appareil. Nous ne procéderons pas automatiquement au redémarrage pendant les heures d’activité.
+
+
+ Impossible d’enregistrer les nouvelles heures de début et de fin, car elles sont identiques. Sélectionnez de nouvelles heures ou désactivez la fonctionnalité.
+
+
+ Options avancées
+ Advanced section title
+
+
+ Contrôlez chacune des étapes de récupération, de téléchargement et d'installation de la mise à jour.
+
+
+ Options de mise à jour automatique
+ Auto-Update section title
+
+
+ Autoriser l'application installer des mises à jour d'application en dehors des heures d’activité
+
+
+ Mises à jour d'applications
+ App update display dialog header
+
+
+ Dernière vérification : le {0} à {1}
+ {0} is date, {1} is time
+
+
+ Impossible de déterminer l'heure de la dernière recherche de mises à jour
+
+
+ Mises à jour d'applications
+ Label for setting item to check for app updates
+
+
+ Se connecter à MSA et AAD
+
+
+ Connectez-vous à AAD à l’aide de votre compte d’organisation.
+
+
+ Connexion à Azure AD (AAD)
+
+
+ AAD
+
+
+ Authentifie Microsoft Graph et d'autres ressources
+
+
+ Authentifie Microsoft Graph uniquement
+
+
+ Annuler
+
+
+ Votre compte d'organisation
+
+
+ Si vous êtes bloqué à un certain point et ne pouvez pas quitter l’Assistant Connexion, veuillez patienter {0} secondes avant de revenir dans l’application.
+
+
+ Connexion en cours...
+
+
+ Déconnexion en cours...
+
+
+ Connectez-vous à votre compte Microsoft ici
+
+
+ Connexion au compte Microsoft (MSA)
+
+
+ MSA
+
+
+ Authentification
+
+
+ Connexion à Microsoft
+
+
+ Échec de la connexion ({0})
+
+
+ Connexion réussie ({0})
+
+
+ Se connecter
+
+
+ Déconnecté : {0}
+
+
+ Se déconnecter
+
+
+ Lecture automatique
+ Music player page auto-play toggle text
+
+
+ Montée en charge automatique
+
+
+ Échec de la mise à jour en raison d’une batterie faible.
+ App update error, low battery
+
+
+ Tentative de couplage avec {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Couplage avec {0} ({1}).
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ Le PIN indiqué sur l’appareil correspond-il à {0} ?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Inconnu
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Actuellement couplé
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Prêt au couplage
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ État inconnu
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Entrez le code PIN suivant sur l’appareil que vous souhaitez coupler : {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Entrer le code PIN :
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Demande de couplage entrante provenant de {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Cet appareil est déjà enregistré pour le couplage entrant. (Cérémonies prises en charge : {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Échec de l'enregistrement pour le couplage entrant.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Enregistrement pour le couplage entrant réussi. (Cérémonies prises en charge : {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ Le code PIN que vous avez entré n'est pas correct.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ Aucun adaptateur Bluetooth utilisable n’a été trouvé sur cet appareil : \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Coupler
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Échec du couplage avec {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Couplage avec {0} réussi ({1}).
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Par défaut
+ Text label for the corresponding device pairing protection level
+
+
+ Chiffrement et authentification
+ Text label for the corresponding device pairing protection level
+
+
+ Chiffrement
+ Text label for the corresponding device pairing protection level
+
+
+ Aucun(e)
+ Text label for the corresponding device pairing protection level
+
+
+ Votre appareil peut maintenant être détecté et est prêt à être couplé avec d'autres appareils Bluetooth.
+ Text displayed when StartWatcher is invoked
+
+
+ Votre appareil ne recherche plus d’autres appareils Bluetooth.
+ Text displayed when StopWatcher is invoked
+
+
+ Découpler
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Échec du découplage de {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Découplage avec {0} réussi ({1}).
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Page d'accueil
+
+
+ Navigateur web
+
+
+ Annuler
+
+
+ La modification du répertoire n’est pas prise en charge pour le moment. Utilisez des chemins complets dans vos commandes.
+
+
+ Fuseau horaire
+ Time zone text
+
+
+ Recherche des mises à jour...
+ App update status
+
+
+ Rechercher les mises à jour
+
+
+ Désactiver des comptes
+
+
+ Un problème s'est produit lors de la désactivation de vos comptes
+
+
+ Cette opération va désactiver les comptes Windows suivants :
+{0}
+
+Continuer ?
+
+
+ Comptes désactivés
+
+
+ Désactivation de comptes en cours...
+
+
+ Effacer
+
+
+ Fermer
+
+
+ Votre appareil n’est pas autorisé à exécuter le processeur de ligne de commande.
+Pour qu'il puisse le faire, exécutez la commande en tant qu'administrateur sur votre appareil :
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Vous pouvez exécuter la commande sur la page Processus du Portail d'appareil Windows IoT ou utiliser PowerShell pour vous connecter à votre appareil Windows IoT.
+Pour plus d'informations, visitez http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Échec de l’exécution de la commande en tant qu’administrateur : {0}
+
+
+ Échec de l’activation du processeur de ligne de commande (cmd.exe) sur votre appareil : {0}
+
+
+ Le processeur de ligne de commande (cmd.exe) a été activé sur votre appareil.
+
+
+ Couleur de la vignette
+
+
+ Retour
+ Back UI navigation
+
+
+ Afficher les informations sur l’appareil
+
+
+ Suivant
+ Forward UI navigation
+
+
+ Basculer en mode plein écran
+
+
+ Cloner l'affichage
+ Clone current view to another display
+
+
+ Journal d’enregistrement rapide
+
+
+ Journal de la session
+
+
+ Définir la page par défaut
+
+
+ Commande annulée.
+
+
+ Entrer la ligne de commande
+ Placeholder for command line input text box
+
+
+ Erreur lors de l'exécution de la ligne de commande : {0}
+
+
+ Ligne de commande
+
+
+ Ligne de commande
+ Title for command line page
+
+
+ La commande a expiré après {0} secondes sans résultat.
+
+
+ Nom de l'ordinateur
+
+
+ Confirmation
+
+
+ Se connecter automatiquement
+
+
+ Se connecter automatiquement
+
+
+ Se connecter
+
+
+ Se connecter
+
+
+ Appareils connectés
+
+
+ Échec de la mise à jour. Connectez-vous au Wi-Fi et réessayez.
+ App update error, poor connection
+
+
+ Continue
+
+
+ Impossible d’analyser le résultat de la commande
+
+
+ Anneau actuel
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Page Application par défaut
+
+
+ Nous lançons la sélection automatique de la langue par défaut...
+
+
+ {0} journaux supprimés
+ {0} is plural number of logs
+
+
+ {0} journal supprimé
+ {0} is singular number of logs
+
+
+ Supprimer {0} journal ?
+ {0} is singular number of logs
+
+
+ Supprimer {0} journaux ?
+ {0} is plural number of logs
+
+
+ Supprimer la sélection
+
+
+ ID d’appareil Azure
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ Accéder à la page Appareil
+
+
+ Adresse IP : {0}
+Version du système d'exploitation : {1}
+Version de l'application : {2}
+
+
+ Version de l’application
+ Field label
+
+
+ Nom de l’appareil
+ Field label
+
+
+ Adresse IP
+ Field label
+
+
+ Réseau
+ Field label
+
+
+ Version du système d’exploitation
+ Label for OS Version field in main page
+
+
+ pour commencer à développer
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Informations sur l’appareil
+
+
+ Visitez
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ La page à laquelle vous tentez d’accéder nécessite l’utilisation d'API du Portail d'appareil Windows (WDP). Connectez-vous à l’aide de vos identifiants WDP pour continuer.
+
+
+ Un problème s'est produit lors de la connexion.
+
+
+ Connexion établie avec le Portail d'appareil !
+
+
+ Vérification des identifiants du Portail d'appareil...
+
+
+ Un problème s'est produit lors de l'obtention de la météo. Réessayer ?
+
+
+ Connexions directes
+
+
+ Déconnecter
+ This disconnects the connected network
+
+
+ Langue d'affichage mise à jour : {0}
+
+
+ Domaine
+
+
+ Téléchargement terminé !
+ App update status
+
+
+ Échec du téléchargement. Réessayez plus tard !
+
+
+ Téléchargement de la mise à jour
+ App update status
+
+
+ Télécharger des mises à jour
+
+
+ Dessiner
+
+
+ « {0} journaux envoyés à {1} »
+ {0} is plural number of logs, {1} is email address
+
+
+ « {0} journal envoyé à {1} »
+ {0} is singular number of logs, {1} is email address
+
+
+ Envoyer le journal par e-mail
+
+
+ Voulez-vous vous envoyer {0} par e-mail ?
+ {0} is filename
+
+
+ Un problème s'est produit lors de l'envoi de votre journal par e-mail : {0}
+ {0} is exception message
+
+
+ Vous trouverez vos journaux sur la page Journaux
+
+
+ « Envoyer le journal {0} par e-mail à vous-même ? »
+ {0} is singular number of logs
+
+
+ Un problème s'est produit lors de l'envoi de vos journaux par e-mail : {0}
+ {0} is an exception message
+
+
+ Envoyer {0} journaux par e-mail à vous-même ?
+ {0} is plural number of logs
+
+
+ Envoyer les journaux par e-mail
+
+
+ E-mail sélectionné
+
+
+ Activer le processeur de ligne de commande
+
+
+ Écran de veille
+ Toggle switch for enabling the screensaver
+
+
+ Heure de fin
+
+
+ Erreur
+
+
+ Un problème s’est produit lors de la récupération des infos sur la météo
+
+
+ Ethernet
+ Field label
+
+
+ GUID du fournisseur ETW : {0}
+ Format string for app settings page
+
+
+ Exécution des commandes en tant que DefaultAccount
+
+
+ Explorer
+
+
+ Fichier enregistré : {0}
+ {0} is a filename
+
+
+ Distribution de version d’évaluation
+ Device servicing flighting
+
+
+ Informations sur la distribution de version d’évaluation
+ Device servicing flighting
+
+
+ L'anneau de la version d’évaluation a été modifié en {0} !
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ Un problème s'est produit lors de la modification de l'anneau de la version d’évaluation
+
+
+ Prévision
+ Weather forecast
+
+
+ Vous êtes sur le point de passer en mode Plein écran. Pour quitter, vous devez appuyer sur [Échap] sur le clavier. Voulez-vous continuer ?
+
+
+ Mode Plein écran
+
+
+ Appuyez sur [Échap] pour quitter le mode Plein écran.
+
+
+ Général
+
+
+ Carte IoTEnterprise
+ A generic board name
+
+
+ GitHub
+
+
+ Aide
+
+
+ Aide
+
+
+ Aide
+
+
+ Langue du clavier de saisie mise à jour : {0}
+
+
+ Installation terminée !
+ App update status
+
+
+ Échec de l'installation. Réessayez plus tard !
+
+
+ Installation de la mise à jour
+ App update status
+
+
+ Installer les mises à jour
+
+
+ Informations d'identification non valides
+
+
+ « {0} » n'est pas un emplacement valide.
+ Format string for app settings page
+
+
+ « {0} » est une valeur non valide. La valeur doit être supérieure ou égale à 1.
+ Format string for app settings page
+
+
+ « {0} » est une valeur non valide.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Disposition du clavier
+ Field label
+
+
+ Redémarrer cette application pour appliquer les nouveaux paramètres
+
+
+ Langue
+
+
+ Langue
+ Field label
+
+
+ Chargement...
+
+
+ Chargement des infos sur la météo...
+
+
+ Le journal a été envoyé à {0}
+ {0} is email address
+
+
+ Journal enregistré dans : {0}
+ {0} is filename
+
+
+ Journaux
+
+
+ Journaux
+
+
+ Nom de l’appareil
+ Field label
+
+
+ Adresse IP
+ Field label
+
+
+ Version du système d’exploitation
+ Label for OS Version field in main page
+
+
+ Il s’agit d’une image de test de Windows 10 IoT Standard conçue pour le prototypage uniquement. Si vous envisager la commercialisation, vous devez utiliser un FFU personnalisé pour une sécurité optimale.
+ Maker Imager Security Notice
+
+
+ Jeton de service de Carte Bing
+
+
+ Jeton de service de Carte Bing nécessaire
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Compte Microsoft (MSA)
+
+
+ En cours de lecture
+ Music player page status text (currently playing)
+
+
+ Sélectionnez un morceau et cliquez sur lire.
+ Music player page status text (default)
+
+
+ Ajoutez au moins un fichier audio dans le dossier Musique.
+Vous pouvez ajouter de la musique dans le Portail d'appareil Windows en utilisant Applications > Explorateur de fichiers.
+ Music player page instructions text
+
+
+ Chargement de la musique
+ Music player page loading panel text
+
+
+ Chargement en cours
+ Music player page status text (loading)
+
+
+ Aucune musique trouvée
+ Music player page no music found prompt text
+
+
+ Réessayer
+ Music player page reload button text (no files prompt)
+
+
+ Musique
+
+
+ Musique
+
+
+ En pause
+ Music player page status text (paused)
+
+
+ Lecture en cours
+ Music player page status text (playing)
+
+
+ Se connecter
+
+
+ Inconnu
+
+
+ Menu
+
+
+ Cartes réseau
+
+
+ Connecté
+
+
+ Connecté
+
+
+ Vérification de la configuration réseau requise
+
+
+ Vérification de la configuration réseau requise
+
+
+ Accès Internet limité
+
+
+ Accès Internet et local
+
+
+ Accès réseau local uniquement
+
+
+ Aucune connectivité
+
+
+ INFORMATIONS RÉSEAU
+
+
+ Réseau non disponible
+
+
+ Entrer la clé de sécurité réseau
+
+
+ Entrez la clé de sécurité réseau
+
+
+ Réseau et Wi-Fi
+
+
+ Réseau et Wi-Fi
+
+
+ Afficher les propriétés du réseau
+
+
+ Propriétés du réseau
+
+
+ Vous allez être redirigé vers le portail captif de ce réseau Wi-Fi. Voulez-vous continuer ?
+
+
+ Redirection du réseau
+
+
+ Suivant
+
+
+ Suivant
+
+
+ Comptes introuvables
+
+
+ Non
+
+
+ no device name
+
+
+ pas de connexion Internet
+
+
+ Aucun journal sélectionné
+
+
+ Aucune musique trouvée
+ Music player page panel text
+
+
+ Aucun élément trouvé
+
+
+ Aucune mise à jour en attente à télécharger.
+ App update status
+
+
+ Aucune mise à jour en attente à installer.
+ App update status
+
+
+ N/A
+
+
+ Notifications
+
+
+ Notifications
+
+
+ Aucune nouvelle mise à jour trouvée.
+ Format string displayed when no app updates are found
+
+
+ OK
+ Button content text for the Bluetooth settings page
+
+
+ Choisissez votre langue
+
+
+ Connectez-vous
+
+
+ Bienvenue dans Windows 10 IoT Standard
+
+
+ Commençons par le commencement.
+
+
+ Bienvenue dans Windows 10 IoT Standard
+
+
+ ID d'édition du système d'exploitation
+
+
+ Édition du système d'exploitation
+
+
+ Informations sur le système d’exploitation
+
+
+ Informations sur le système d’exploitation
+
+
+ Non disponible
+ Text shown when we cannot retrieve the OS Version
+
+
+ Version du système d’exploitation
+
+
+ Packages
+ Software packages
+
+
+ Packages installés
+ Software packages
+
+
+ Paramètres de page
+
+
+ Pages
+
+
+ Mot de passe
+
+
+ Chargement des images
+ Default text when no images are available
+
+
+ Ajoutez des images dans le dossier Images.
+Vous pouvez ajouter des images dans le Portail d'appareil Windows en utilisant Applications > Explorateur de fichiers.
+
+
+ Images introuvables
+ Default text when no images are available
+
+
+ Plateforme
+
+
+ Lire
+
+
+ Options d’alimentation
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ De base : n'envoyez que des informations sur votre appareil, ses paramètres et ses fonctionnalités, ainsi que pour indiquer s'il fonctionne correctement.
+
+
+ Complet : envoyez toutes les données de diagnostic de base en plus d'informations sur les sites web que vous parcourez et sur la manière dont vous utilisez des applications et des fonctionnalités, ainsi que des informations supplémentaires sur l'intégrité de votre appareil, son activité et des rapports d'erreurs améliorés.
+
+
+ Nous ne pouvons pas modifier les paramètres de confidentialité. Vérifiez votre nom d'utilisateur et votre mot de passe, puis réessayez.
+
+
+ Choisissez la quantité de données de diagnostic que vous souhaitez envoyer à Microsoft. Les données de diagnostic sont utilisées pour aider à maintenir Windows sécurisé et à jour, résoudre les problèmes et améliorer les produits. Quelle que soit l'option sélectionnée, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
+
+
+ Données de diagnostic
+ Label for Setting item to control Privacy
+
+
+ Entrez vos identifiants pour définir le niveau de confidentialité sur cet appareil.
+
+
+ Définir votre niveau de confidentialité
+
+
+ Actualiser
+ Refresh button
+
+
+ Répéter le morceau
+ Music player page repeat toggle text
+
+
+ Redémarrer
+
+
+ Redémarrer
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Utilisation : commande RunAsAdmin
+
+Exemples :
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Enregistrer
+
+
+ Facteur de montée en charge
+
+
+ Sélectionner tout
+
+
+ Envoyer la télémétrie
+
+
+ Non disponible
+
+
+ Journal de la session
+
+
+ Un problème s’est produit lors de la définition de la page par défaut sur {0}.
+ Format string for app settings page
+
+
+ Paramètres
+
+
+ Lecture aléatoire
+ Music player page shuffle toggle text
+
+
+ Arrêter
+
+
+ Arrêter
+ Shutdown entry in the shutdown menu
+
+
+ Connectez-vous à votre compte Azure AD pour utiliser cette fonctionnalité.
+
+
+ Ignorer
+
+
+ Ignorer cette étape
+
+
+ Intervalle du diaporama (secondes)
+
+
+ Diaporama
+
+
+ Diaporama
+
+
+ Démarrer
+
+
+ Démarrer
+
+
+ Heure de début
+
+
+ Statut
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Soumettre
+
+
+ Opération réussie
+
+
+ Système
+
+
+ Un problème s'est produit lors de la tentative de mise à jour de vos paramètres système.
+ Used within system settings
+
+
+ Niveau de télémétrie
+
+
+ Télémétrie
+
+
+ Tester la notification Jumbo
+
+
+ Tester la notification
+
+
+ Windows 10 IoT est un membre de la famille Windows 10 qui offre à l'Internet des objets de la puissance à l'échelle de l'entreprise, la sécurité et la facilité de gestion. Il tire profit de la connectivité au cloud, de l’écosystème et de l'expérience intégrés de Windows, ce qui permet aux organisations de créer leur Internet des objets avec des appareils sécurisés qui peuvent être rapidement approvisionnés, facilement gérés et connectés en toute transparence à une stratégie globale du cloud.
+
+
+ Hauteur de la vignette
+
+
+ Personnalisation
+
+
+ Largeur de la vignette
+
+
+ Délai de connexion dépassé
+
+
+ Fuseau horaire mis à jour : {0}
+
+
+ Erreur : Impossible de communiquer avec le service météo
+
+
+ Échec de la mise à jour pour une raison inconnue.
+ App update error, unknown
+
+
+ Désélectionner tout
+
+
+ Défaillance non spécifiée
+
+
+ Options avancées
+
+
+ Vérifier maintenant
+
+
+ Installer maintenant
+
+
+ Mise à jour en attente de {0}
+ {0} is singular amount of updates
+
+
+ {0} nouvelles mises à jour détectées.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ Mises à jour en attente de {0}
+ {0} is plural amount of updates
+
+
+ Utiliser des icônes de vignette MDL2
+
+
+ Utiliser un mot de passe
+
+
+ Nom d'utilisateur
+
+
+ Portail d'appareil Windows
+
+
+ Paramètres du Portail d'appareil
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Portail d'appareil Windows
+
+
+ Emplacement actuel ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Votre emplacement
+
+
+ Votre emplacement
+ Label for map pin
+
+
+ Emplacement inconnu
+ Label for map pin
+
+
+ Capteur :
+ Label for temperature sensor output
+
+
+ Météo
+
+
+ Erreur lors du chargement de la page Météo.
+
+Cliquez sur le bouton Actualiser en bas à droite de l’écran pour recharger cette page.
+
+Si vous n’avez pas de clés API Météo, accédez à weatherunlocked.com. Enregistrez les clés de « WeatherTokens.config » dans le dossier de l’état local de cette application. Actualisez ensuite la page.
+
+
+ Données météo fournies par :
+
+
+ Météo
+
+
+ Entrer une adresse web
+
+
+ Navigateur web
+
+
+ Bienvenue dans Windows IoT Standard
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Actualiser
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Dernière vérification :
+ For a timestamp
+
+
+ Dernière mise à jour :
+ For a timestamp
+
+
+ État mis à jour :
+
+
+ Message de statut :
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Répertoire de travail non valide : {0}
+
+
+ WPS
+
+
+ Autoriser cette application à accéder à votre emplacement
+
+
+ Choisissez vos paramètres, puis sélectionnez Accepter pour les enregistrer. Vous pouvez modifier ces paramètres à tout moment.
+
+
+ Autoriser Microsoft à utiliser votre emplacement
+
+
+ Continue automatiquement...
+
+
+ Accepter
+
+
+ Laissez {0} accéder à votre emplacement précis ?
+ {0} is the name of a page
+
+
+ Emplacement
+
+
+ Pour modifier ce paramètre ultérieurement, accédez à Paramètres > Autorisations.
+
+
+ Non
+
+
+ Oui
+
+
+ Vous ne serez pas en mesure de profiter d'expériences basées sur l'emplacement, comme les cartes et la météo, ou de profiter d'autres services qui requièrent votre emplacement pour pouvoir fonctionner.
+
+
+ Profitez d'expériences basées sur l'emplacement, comme les cartes et la météo. Laissez cette application demander votre emplacement. Microsoft utilisera les données d'emplacement pour améliorer les services de localisation.
+
+
+ Envoyez uniquement des informations sur votre appareil, ses paramètres et fonctionnalités, et sur son fonctionnement correct ou non. Les données de diagnostic sont utilisées pour permettre à Windows de rester sécurisé et à jour, de résoudre des problèmes et de permettre des améliorations des produits. Que vous sélectionniez De base ou Complet, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
+
+
+ De base
+
+
+ Envoyez toutes les données de diagnostic de base, ainsi que des informations sur les sites web que vous visitez et des informations sur votre utilisation des applications et des fonctionnalités, ainsi que des données supplémentaires sur l'intégrité des appareils, sur l'activité des appareils, ainsi que des rapports d'erreurs améliorés. Les données de diagnostic sont utilisées pour veiller à ce que Windows reste sécurisé et à jour, à résoudre les problèmes et à améliorer les produits. Que vous sélectionniez De base ou Complet, votre appareil sera parfaitement sécurisé et fonctionnera normalement.
+
+
+ Complet
+
+
+ Choisissez un paramètre de confidentialité pour votre appareil, puis sélectionnez « Accepter » pour l’enregistrer.
+
+
+ Envoyer des données de diagnostic à Microsoft
+
+
+ Diagnostics
+
+
+ Si vous autorisez l'accès, vous permettrez à cette application d'utiliser les fonctionnalités de votre appareil pour déterminer votre emplacement et Microsoft utilisera vos données d'emplacement pour améliorer les services de localisation. Refuser l'accès empêche uniquement Windows de fourni l'emplacement à cette application.
+
+
+ Prenez connaissance de vos options de confidentialité
+
+
+ Découvrez en quoi ce paramètre peut influencer votre confidentialité.
+
+
+ Obtenir plus d'informations sur ces paramètres
+
+
+ Déclaration de confidentialité
+
+
+ Oui
+
+
+ Oui
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/it-IT/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/it-IT/Resources.resw
index 16e2ff0c6..6712f0b2b 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/it-IT/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/it-IT/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Utilizza AAD v2
-
-
- Accesso revocato
-
-
- Descrizione:
-
-
- Server DHCP:
-
-
- DNS:
-
-
- Indirizzo del gateway:
-
-
- Indirizzo IPv4:
-
-
- Nome:
-
-
- Indirizzo fisico:
-
-
- Subnet mask:
-
-
- Tipo:
-
-
- Versione app
-
-
- App
-
-
- Stai per avviare un'app esterna. Dovrai utilizzare Portale di dispositivi di Windows per tornare a questa app. Continuare?
- Dialog prompt for launching external apps
-
-
- App
-
-
- Impostazioni app
-
-
- Imposta l'orario di attività per farci sapere quando usi questo dispositivo generalmente.
-
-
- Impossibile salvare il nuovo orario di inizio e fine in quanto sono uguali. Seleziona nuovi orari o disattiva la funzionalità.
-
-
- Opzioni avanzate
- Advanced section title
-
-
- Controlla tutti i passaggi di aggiornamento fetch, download e installazione.
-
-
- Opzioni di aggiornamento automatico
- Auto-Update section title
-
-
- Consenti alle app di installare gli aggiornamenti delle app al di fuori dell'orario di attività
-
-
- Aggiornamenti app
- App update display dialog header
-
-
- Ultimo controllo: {0}, {1}
- {0} is date, {1} is time
-
-
- Impossibile determinare quando è stato eseguito l'ultimo controllo per la disponibilità degli aggiornamenti
-
-
- Aggiornamenti app
- Label for setting item to check for app updates
-
-
- Accedi a MSA e AAD
-
-
- Accedi ad AAD utilizzando l'account dell'organizzazione.
-
-
- Accesso ad Azure AD (AAD)
-
-
- AAD
-
-
- Autentica Microsoft Graph e altre risorse
-
-
- Autentica solo Microsoft Graph
-
-
- Annulla
-
-
- Account dell'organizzazione
-
-
- Se rimani bloccato in un punto e non riesci a uscire dall'accesso guidato, attendi {0} secondi per tornare all'app.
-
-
- Accesso in corso...
-
-
- Disconnessione...
-
-
- Accedi qui al tuo account Microsoft
-
-
- Accesso all'account Microsoft (MSA)
-
-
- MSA
-
-
- Autenticazione
-
-
- Accesso Microsoft
-
-
- Accesso non riuscito ({0})
-
-
- Accesso riuscito ({0})
-
-
- Accedi
-
-
- Disconnesso: {0}
-
-
- Disconnetti
-
-
- Riproduzione automatica
- Music player page auto-play toggle text
-
-
- Ridimensionamento automatico
-
-
- Aggiornamento non riuscito a causa della batteria in esaurimento.
- App update error, low battery
-
-
- Tentativo di associazione con {0} ({1})
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Associazione con {0} ({1})
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- Il PIN visualizzato sul dispositivo corrisponde a {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Sconosciuto
- Text displayed when the Bluetooth device name is unknown
-
-
- Attualmente associato
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Pronto per l'associazione
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Stato sconosciuto
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Immetti il PIN seguente nel dispositivo che desideri associare: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Immetti il PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Richiesta di associazione in entrata da {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Il dispositivo è già registrato per l'associazione in entrata. (Procedure supportate: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Registrazione per l'associazione in entrata non riuscita.
- Text displayed when Inbound pairing handler registration fails
-
-
- Registrazione per l'associazione in entrata completata. (Procedure supportate: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- Il PIN immesso non è corretto.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- Non è possibile trovare alcuna scheda Bluetooth utilizzabile nel dispositivo: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Associa
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Impossibile associare con {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Associazione con {0} ({1}) completata.
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Predefinito
- Text label for the corresponding device pairing protection level
-
-
- Codifica e autenticazione
- Text label for the corresponding device pairing protection level
-
-
- Codifica
- Text label for the corresponding device pairing protection level
-
-
- Nessuno
- Text label for the corresponding device pairing protection level
-
-
- Il dispositivo è ora individuabile e pronto per l\'associazione con altri dispositivi Bluetooth.
- Text displayed when StartWatcher is invoked
-
-
- Il dispositivo non cerca più altri dispositivi Bluetooth.
- Text displayed when StopWatcher is invoked
-
-
- Annulla associazione
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Impossibile annullare l\'associazione da {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Annullamento dell\'associazione da {0} ({1}) completato.
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Home page
-
-
- Web browser
-
-
- Annulla
-
-
- La modifica della directory attualmente non è supportata. Usa i percorsi completi nei comandi.
-
-
- Fuso orario
- Time zone text
-
-
- Controllo degli aggiornamenti in corso...
- App update status
-
-
- Controlla aggiornamenti
-
-
- Elimina account
-
-
- Si è verificato un problema durante l'eliminazione degli account
-
-
- Con questa operazione verranno eliminati gli account di Windows seguenti:
-{0}
-
-Continuare?
-
-
- Account eliminati
-
-
- Eliminazione degli account in corso...
-
-
- Cancella
-
-
- Chiudi
-
-
- Il tuo dispositivo non può eseguire il processore della riga di comando.
-Per abilitarlo, esegui il seguente comando come "Amministratore" sul dispositivo:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Puoi eseguire il comando nella pagina dei processi del Portale di dispositivi di Windows IoT o usare PowerShell per collegare il tuo dispositivo Windows IoT.
-Per altre informazioni, visita la pagina http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Impossibile eseguire il comando come amministratore: {0}
-
-
- Impossibile abilitare Command Line Processor (cmd.exe) sul tuo dispositivo: {0}
-
-
- Abilitazione Command Line Processor (cmd.exe) riuscita sul tuo dispositivo.
-
-
- Colore riquadro
-
-
- Indietro
- Back UI navigation
-
-
- Mostra info dispositivo
-
-
- Avanti
- Forward UI navigation
-
-
- Attiva/Disattiva schermo intero
-
-
- Clona visualizzazione
- Clone current view to another display
-
-
- Salvataggio rapido registro
-
-
- Registro sessione
-
-
- Imposta pagina predefinita
-
-
- Comando annullato.
-
-
- Immetti la riga di comando
- Placeholder for command line input text box
-
-
- Errore nell'esecuzione della riga di comando: {0}
-
-
- Riga di comando
-
-
- Riga di comando
- Title for command line page
-
-
- Timeout del comando dopo {0} secondi senza output.
-
-
- Nome computer
-
-
- Conferma
-
-
- Connetti automaticamente
-
-
- Connetti automaticamente
-
-
- Connetti
-
-
- Connetti
-
-
- Dispositivi connessi
-
-
- Aggiornamento non riuscito. Connetti il Wi-Fi e riprova.
- App update error, poor connection
-
-
- Continua
-
-
- Impossibile analizzare l'output del comando
-
-
- Anello corrente
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Pagina app predefinita
-
-
- La lingua predefinita verrà scelta automaticamente...
-
-
- {0} registri eliminati
- {0} is plural number of logs
-
-
- {0} registro eliminato
- {0} is singular number of logs
-
-
- Eliminare {0} registro?
- {0} is singular number of logs
-
-
- Eliminare {0} registri?
- {0} is plural number of logs
-
-
- Elimina selezionato
-
-
- ID dispositivo Azure
- Field label
-
-
- Hub Azure IoT
- Field label
-
-
- Vai a pagina dispositivo
-
-
- Indirizzo IP: {0}
-Versione sistema operativo: {1}
-Versione app: {2}
-
-
- Versione app
- Field label
-
-
- Nome periferica
- Field label
-
-
- Indirizzo IP
- Field label
-
-
- Rete
- Field label
-
-
- Versione SO
- Label for OS Version field in main page
-
-
- per iniziare a sviluppare
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Info dispositivo
-
-
- Visita
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- La pagina a cui stai tentando di accedere richiede l'utilizzo delle API del Portale di dispositivi di Windows (WDP). Accedi utilizzando le credenziali WDP per continuare.
-
-
- Si è verificato un problema durante l'accesso.
-
-
- Accesso al Portale di dispositivi completato.
-
-
- Verifica delle credenziali del Portale di dispositivi in corso...
-
-
- Si è verificato un problema durante il recupero del meteo. Riprovare?
-
-
- Connessioni dirette
-
-
- Disconnetti
- This disconnects the connected network
-
-
- Lingua di visualizzazione aggiornata: {0}
-
-
- Dominio
-
-
- Download completato.
- App update status
-
-
- Download non riuscito. Riprova più tardi.
-
-
- Download dell'aggiornamento
- App update status
-
-
- Scarica aggiornamenti
-
-
- Disegno
-
-
- "{0} registri inviati a {1}"
- {0} is plural number of logs, {1} is email address
-
-
- "{0} registro inviato a {1}"
- {0} is singular number of logs, {1} is email address
-
-
- Registro e-mail
-
-
- Vuoi inviare tramite e-mail {0} a te stesso?
- {0} is filename
-
-
- Si è verificato un problema durante l'invio tramite e-mail del tuo registro: {0}
- {0} is exception message
-
-
- Puoi trovare i tuoi registri nella pagina Registri
-
-
- "Inviare tramite e-mail {0} registro a te stesso?"
- {0} is singular number of logs
-
-
- Si è verificato un problema durante l'invio tramite e-mail dei tuoi registri: {0}
- {0} is an exception message
-
-
- Inviare tramite e-mail {0} registri a te stesso?
- {0} is plural number of logs
-
-
- Invia tramite e-mail registri
-
-
- Invia tramite e-mail selezionato
-
-
- Abilita Command Line Processor
-
-
- Screen saver
- Toggle switch for enabling the screensaver
-
-
- Ora di fine
-
-
- Errore
-
-
- Si è verificato un problema durante il recupero delle informazioni sul meteo
-
-
- Ethernet
- Field label
-
-
- GUID del provider ETW: {0}
- Format string for app settings page
-
-
- Esecuzione dei comandi come DefaultAccount
-
-
- Esplora
-
-
- File salvato: {0}
- {0} is a filename
-
-
- Distribuzione di versioni di anteprima
- Device servicing flighting
-
-
- Info distribuzione di versioni di anteprima
- Device servicing flighting
-
-
- L'anello di versione di anteprima è stato modificato in {0}.
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- Si è verificato un problema durante la modifica dell'anello di versione di anteprima
-
-
- Previsione
- Weather forecast
-
-
- Stai per attivare la modalità schermo intero. Per uscire, premi il tasto [Esc] della tastiera. Continuare?
-
-
- Modalità schermo intero
-
-
- Premi [Esc] per uscire dalla modalità a schermo intero.
-
-
- Generale
-
-
- Scheda IoT Enterprise
- A generic board name
-
-
- GitHub
-
-
- ?
-
-
- ?
-
-
- ?
-
-
- Lingua di input della tastiera aggiornata: {0}
-
-
- Installazione completata.
- App update status
-
-
- Installazione non riuscita. Riprova più tardi.
-
-
- Installazione dell'aggiornamento
- App update status
-
-
- Installa aggiornamenti
-
-
- Credenziale non valida
-
-
- '{0}' è una posizione non valida.
- Format string for app settings page
-
-
- '{0}' è un valore non valido. Il valore deve essere maggiore o uguale a 1.
- Format string for app settings page
-
-
- '{0}' è un valore non valido.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Layout di tastiera
- Field label
-
-
- Riavvia l'app per applicare le nuove impostazioni
-
-
- Lingua
-
-
- Lingua
- Field label
-
-
- Caricamento in corso...
-
-
- Caricamento delle informazioni sul meteo in corso...
-
-
- Il registro è stato inviato a {0}
- {0} is email address
-
-
- Registro salvato in: {0}
- {0} is filename
-
-
- Registri
-
-
- Registri
-
-
- Nome periferica
- Field label
-
-
- Indirizzo IP
- Field label
-
-
- Versione sistema operativo
- Label for OS Version field in main page
-
-
- Questa è un'immagine di prova di Windows 10 IoT Enterprise progettata solo come prototipo. Se il tuo obiettivo è la commercializzazione, devi utilizzare un FFU personalizzato per ottimizzare la sicurezza.
- Maker Imager Security Notice
-
-
- Token del servizio Bing Mappe
-
-
- Token del servizio Bing Mappe richiesto
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Account Microsoft (MSA)
-
-
- In fase di riproduzione
- Music player page status text (currently playing)
-
-
- Seleziona un brano e fai clic su Riproduci.
- Music player page status text (default)
-
-
- Aggiungi uno o più file audio alla cartella Musica.
-Puoi aggiungere la musica nel Portale di dispositivi di Windows scegliendo App > Esplora File.
- Music player page instructions text
-
-
- Caricamento della musica
- Music player page loading panel text
-
-
- Caricamento
- Music player page status text (loading)
-
-
- Nessun contenuto musicale trovato
- Music player page no music found prompt text
-
-
- Riprova
- Music player page reload button text (no files prompt)
-
-
- Musica
-
-
- Musica
-
-
- In pausa
- Music player page status text (paused)
-
-
- Esecuzione
- Music player page status text (playing)
-
-
- Accedi
-
-
- Sconosciuto
-
-
- Menu
-
-
- Schede di rete
-
-
- Connesso
-
-
- Connesso
-
-
- Verifica dei requisiti di rete
-
-
- Verifica dei requisiti di rete in corso
-
-
- Accesso a Internet limitato
-
-
- Accesso locale e a Internet
-
-
- Solo accesso alla rete locale
-
-
- Nessuna connessione
-
-
- INFORMAZIONI RETE
-
-
- Rete non disponibile
-
-
- Immetti la chiave di sicurezza di rete
-
-
- Immetti la chiave di sicurezza di rete
-
-
- Rete e Wi-Fi
-
-
- Rete e Wi-Fi
-
-
- Visualizza proprietà di rete
-
-
- Proprietà di rete
-
-
- Stai per essere reindirizzato al captive portal di questa rete Wi-Fi. Continuare?
-
-
- Reindirizzamento di rete
-
-
- Avanti
-
-
- Avanti
-
-
- Nessun account trovato
-
-
- No
-
-
- nessun nome di dispositivo
-
-
- nessuna connessione a Internet
-
-
- Nessun registro selezionato
-
-
- Nessun contenuto musicale trovato
- Music player page panel text
-
-
- Non trovata
-
-
- Non sono presenti aggiornamenti in sospeso da scaricare.
- App update status
-
-
- Non sono presenti aggiornamenti in sospeso da installare.
- App update status
-
-
- N/D
-
-
- Notifiche
-
-
- Notifiche
-
-
- Nessun nuovo aggiornamento trovato.
- Format string displayed when no app updates are found
-
-
- OK
- Button content text for the Bluetooth settings page
-
-
- Scegli una lingua
-
-
- Attivazione della connessione
-
-
- Benvenuto in Windows 10 IoT Enterprise
-
-
- Per iniziare verranno configurate alcune impostazioni di base.
-
-
- Benvenuto in Windows 10 IoT Enterprise
-
-
- ID edizione sistema operativo
-
-
- Edizione sistema operativo
-
-
- Info sistema operativo
-
-
- Info sistema operativo
-
-
- Non disponibile
- Text shown when we cannot retrieve the OS Version
-
-
- Versione sistema operativo
-
-
- Pacchetti
- Software packages
-
-
- Pacchetti installati
- Software packages
-
-
- Impostazioni della pagina
-
-
- Pagine
-
-
- Password
-
-
- Caricamento delle immagini
- Default text when no images are available
-
-
- Aggiungi immagini alla cartella Immagini.
-Puoi aggiungere le immagini nel Portale di dispositivi di Windows scegliendo App > Esplora File.
-
-
- Nessuna immagine trovata
- Default text when no images are available
-
-
- Piattaforma
-
-
- Riproduci
-
-
- Opzioni risparmio energia
- Label for Setting item to control Power (shutdown/restart)
-
-
- Di base: invia solo le informazioni sul dispositivo, sulle relative impostazioni e funzionalità e sul suo corretto funzionamento.
-
-
- Invia tutti i dati di diagnostica di base oltre a informazioni sui siti Web visitati e sulla modalità di utilizzo di app e funzionalità, nonché informazioni aggiuntive sull'integrità e l'attività del dispositivo e sulla segnalazione errori avanzata.
-
-
- Impossibile modificare l'impostazione della privacy. Controlla il nome utente e la password e riprova.
-
-
- Scegli la quantità di dati di diagnostica da inviare a Microsoft. I dati di diagnostica vengono utilizzati per mantenere Windows sicuro e aggiornato, risolvere i problemi e apportare miglioramenti al prodotto. Indipendentemente dall'opzione selezionata, il dispositivo sarà ugualmente protetto e funzionerà normalmente.
-
-
- Dati di diagnostica
- Label for Setting item to control Privacy
-
-
- Immetti le tue credenziali per impostare il livello di privacy in questo dispositivo.
-
-
- Imposta il livello di privacy
-
-
- Aggiorna
- Refresh button
-
-
- Ripeti brano
- Music player page repeat toggle text
-
-
- Riavvia
-
-
- Riavvia
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Sintassi: comando RunAsAdmin
-
-Esempi:
-> RunAsdmin TZUTIL /s "Ora solare Pacifico"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Salva
-
-
- Fattore di proporzione
-
-
- Seleziona tutto
-
-
- Invia telemetria
-
-
- Non disponibile
-
-
- Registro sessione
-
-
- Si è verificato un problema durante l\'impostazione della pagina predefinita su {0}.
- Format string for app settings page
-
-
- Impostazioni
-
-
- Riproduci in modo casuale
- Music player page shuffle toggle text
-
-
- Arresta
-
-
- Arresta
- Shutdown entry in the shutdown menu
-
-
- Accedi al tuo account Azure AD per usare questa funzionalità.
-
-
- Ignora
-
-
- Ignora questo passaggio
-
-
- Intervallo presentazione (secondi)
-
-
- Presentazione
-
-
- Presentazione
-
-
- Avvia
-
-
- Avvia
-
-
- Ora di inizio
-
-
- Stato
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Invia
-
-
- Operazione riuscita
-
-
- Sistema
-
-
- Si è verificato un problema durante il tentativo di aggiornare le impostazioni del sistema.
- Used within system settings
-
-
- Livello telemetria
-
-
- Telemetria
-
-
- Testa notifica gigante
-
-
- Testa notifica
-
-
- Windows 10 IoT è un membro della famiglia Windows 10 che introduce sicurezza, gestibilità e potenza di livello aziendale nell'Internet delle cose. Sfrutta la connessione cloud, l'ecosistema e l'esperienza integrata di Windows, consentendo alle organizzazioni di creare un Internet delle cose personalizzato con dispositivi protetti di cui è possibile eseguire rapidamente il provisioning e che possono essere facilmente gestiti e integrati in una strategia cloud globale.
-
-
- Altezza riquadro
-
-
- Personalizzazione
-
-
- Larghezza riquadro
-
-
- Timeout della connessione
-
-
- Fuso orario aggiornato: {0}
-
-
- Errore: impossibile comunicare con il servizio meteo
-
-
- Aggiornamento non riuscito a causa di un errore sconosciuto.
- App update error, unknown
-
-
- Deseleziona tutti
-
-
- Errore non specificato
-
-
- Opzioni avanzate
-
-
- Controlla ora
-
-
- Installa ora
-
-
- {0} aggiornamento in sospeso
- {0} is singular amount of updates
-
-
- {0} nuovi aggiornamenti trovati.
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} aggiornamenti in sospeso
- {0} is plural amount of updates
-
-
- Utilizza icone riquadro MDL2
-
-
- Usa password
-
-
- Nome utente
-
-
- Portale di dispositivi di Windows
-
-
- Impostazioni Portale di dispositivi
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Portale di dispositivi di Windows
-
-
- Posizione corrente ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- La tua posizione
-
-
- La tua posizione
- Label for map pin
-
-
- Posizione sconosciuta
- Label for map pin
-
-
- Sensore:
- Label for temperature sensor output
-
-
- Meteo
-
-
- Errore durante il caricamento della pagina Meteo.
-
-Fai clic sul pulsante Aggiorna in basso a destra dello schermo per ricaricare la pagina.
-
-Se non disponi delle chiavi API Meteo, accedi a weatherunlocked.com. Salva le chiavi in "WeatherTokens.config" nella cartella di stato locale di questa app. Quindi aggiorna la pagina.
-
-
- Meteo fornito da:
-
-
- Meteo
-
-
- Immetti indirizzo Web
-
-
- Web browser
-
-
- Benvenuto in Windows IoT Enterprise
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Aggiorna
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Ultimo controllo:
- For a timestamp
-
-
- Ultimo aggiornamento:
- For a timestamp
-
-
- Stato aggiornato:
-
-
- Messaggio di stato:
-
-
- Windows Update
-
-
- Windows Update
-
-
- Directory di lavoro non valida: {0}
-
-
- WPS
-
-
- Consenti a questa app di accedere alla tua posizione
-
-
- Sceglie le impostazioni, quindi seleziona 'Accetta' per salvarle. Puoi modificare queste impostazioni in qualsiasi momento.
-
-
- Consenti a Microsoft di usare la tua posizione
-
-
- Continua automaticamente...
-
-
- Accetta
-
-
- Consentire a {0} di accedere a una posizione esatta?
- {0} is the name of a page
-
-
- Posizione
-
-
- Per modificare questa impostazione in seguito, vai a Impostazioni > Autorizzazioni.
-
-
- No
-
-
- Sì
-
-
- Non sarai in grado di ottenere le esperienze basate sulla posizione come le mappe e il meteo né di utilizzare altri servizi che richiedono la tua posizione per funzionare.
-
-
- Scarica le esperienze basate sulla posizione, come le mappe e il meteo. Lascia che questa app chieda la tua posizione. Microsoft utilizzerà i dati della posizione per migliorare i servizi di posizione.
-
-
- Invia solo le informazioni sul dispositivo, le relative impostazioni e funzionalità e i dati che ne indicano il corretto funzionamento. I dati di diagnostica vengono usati per mantenere Windows sicuro e aggiornato, risolvere i problemi e apportare miglioramenti al prodotto. Indipendentemente dalla selezione di Base o Completo, il dispositivo verrà ugualmente protetto e funzionerà normalmente.
-
-
- Di base
-
-
- Invia tutti i dati di diagnostica di base oltre a informazioni sui siti Web visitati e sulla modalità di utilizzo di app e funzionalità, nonché informazioni aggiuntive sull'integrità e l'attività del dispositivo e sulla segnalazione errori avanzata. I dati di diagnostica vengono usati per mantenere Windows sicuro e aggiornato, per risolvere i problemi e per apportare miglioramenti al prodotto. Indipendentemente dalla selezione di Base o Completo, il dispositivo verrà ugualmente protetto e funzionerà normalmente.
-
-
- Completo
-
-
- Scegli un'impostazione di privacy per il dispositivo, quindi seleziona 'Accetta' per salvarla.
-
-
- Invia dati di diagnostica a Microsoft
-
-
- Diagnostica
-
-
- Se consenti l'accesso, abiliterai questa app ad utilizzare le funzionalità del dispositivo per determinare la tua posizione e Microsoft utilizzerà i dati sulla tua posizione per migliorare i servizi di posizione. Se neghi l'accesso impedisci a Windows di fornire la posizione a questa app.
-
-
- Scopri le opzioni per la privacy
-
-
- Scopri qual è l'impatto di questa impostazione sulla privacy.
-
-
- Ottieni altre informazioni su queste impostazioni
-
-
- Informativa sulla privacy
-
-
- Sì
-
-
- Sì
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Utilizza AAD v2
+
+
+ Accesso revocato
+
+
+ Descrizione:
+
+
+ Server DHCP:
+
+
+ DNS:
+
+
+ Indirizzo del gateway:
+
+
+ Indirizzo IPv4:
+
+
+ Nome:
+
+
+ Indirizzo fisico:
+
+
+ Subnet mask:
+
+
+ Tipo:
+
+
+ Versione app
+
+
+ App
+
+
+ Stai per avviare un'app esterna. Dovrai utilizzare Portale di dispositivi di Windows per tornare a questa app. Continuare?
+ Dialog prompt for launching external apps
+
+
+ App
+
+
+ Impostazioni app
+
+
+ Imposta l'orario di attività per farci sapere quando usi questo dispositivo generalmente.
+
+
+ Impossibile salvare il nuovo orario di inizio e fine in quanto sono uguali. Seleziona nuovi orari o disattiva la funzionalità.
+
+
+ Opzioni avanzate
+ Advanced section title
+
+
+ Controlla tutti i passaggi di aggiornamento fetch, download e installazione.
+
+
+ Opzioni di aggiornamento automatico
+ Auto-Update section title
+
+
+ Consenti alle app di installare gli aggiornamenti delle app al di fuori dell'orario di attività
+
+
+ Aggiornamenti app
+ App update display dialog header
+
+
+ Ultimo controllo: {0}, {1}
+ {0} is date, {1} is time
+
+
+ Impossibile determinare quando è stato eseguito l'ultimo controllo per la disponibilità degli aggiornamenti
+
+
+ Aggiornamenti app
+ Label for setting item to check for app updates
+
+
+ Accedi a MSA e AAD
+
+
+ Accedi ad AAD utilizzando l'account dell'organizzazione.
+
+
+ Accesso ad Azure AD (AAD)
+
+
+ AAD
+
+
+ Autentica Microsoft Graph e altre risorse
+
+
+ Autentica solo Microsoft Graph
+
+
+ Annulla
+
+
+ Account dell'organizzazione
+
+
+ Se rimani bloccato in un punto e non riesci a uscire dall'accesso guidato, attendi {0} secondi per tornare all'app.
+
+
+ Accesso in corso...
+
+
+ Disconnessione...
+
+
+ Accedi qui al tuo account Microsoft
+
+
+ Accesso all'account Microsoft (MSA)
+
+
+ MSA
+
+
+ Autenticazione
+
+
+ Accesso Microsoft
+
+
+ Accesso non riuscito ({0})
+
+
+ Accesso riuscito ({0})
+
+
+ Accedi
+
+
+ Disconnesso: {0}
+
+
+ Disconnetti
+
+
+ Riproduzione automatica
+ Music player page auto-play toggle text
+
+
+ Ridimensionamento automatico
+
+
+ Aggiornamento non riuscito a causa della batteria in esaurimento.
+ App update error, low battery
+
+
+ Tentativo di associazione con {0} ({1})
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Associazione con {0} ({1})
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ Il PIN visualizzato sul dispositivo corrisponde a {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Sconosciuto
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Attualmente associato
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Pronto per l'associazione
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Stato sconosciuto
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Immetti il PIN seguente nel dispositivo che desideri associare: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Immetti il PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Richiesta di associazione in entrata da {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Il dispositivo è già registrato per l'associazione in entrata. (Procedure supportate: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Registrazione per l'associazione in entrata non riuscita.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Registrazione per l'associazione in entrata completata. (Procedure supportate: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ Il PIN immesso non è corretto.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ Non è possibile trovare alcuna scheda Bluetooth utilizzabile nel dispositivo: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Associa
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Impossibile associare con {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Associazione con {0} ({1}) completata.
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Predefinito
+ Text label for the corresponding device pairing protection level
+
+
+ Codifica e autenticazione
+ Text label for the corresponding device pairing protection level
+
+
+ Codifica
+ Text label for the corresponding device pairing protection level
+
+
+ Nessuno
+ Text label for the corresponding device pairing protection level
+
+
+ Il dispositivo è ora individuabile e pronto per l\'associazione con altri dispositivi Bluetooth.
+ Text displayed when StartWatcher is invoked
+
+
+ Il dispositivo non cerca più altri dispositivi Bluetooth.
+ Text displayed when StopWatcher is invoked
+
+
+ Annulla associazione
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Impossibile annullare l\'associazione da {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Annullamento dell\'associazione da {0} ({1}) completato.
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Home page
+
+
+ Web browser
+
+
+ Annulla
+
+
+ La modifica della directory attualmente non è supportata. Usa i percorsi completi nei comandi.
+
+
+ Fuso orario
+ Time zone text
+
+
+ Controllo degli aggiornamenti in corso...
+ App update status
+
+
+ Controlla aggiornamenti
+
+
+ Elimina account
+
+
+ Si è verificato un problema durante l'eliminazione degli account
+
+
+ Con questa operazione verranno eliminati gli account di Windows seguenti:
+{0}
+
+Continuare?
+
+
+ Account eliminati
+
+
+ Eliminazione degli account in corso...
+
+
+ Cancella
+
+
+ Chiudi
+
+
+ Il tuo dispositivo non può eseguire il processore della riga di comando.
+Per abilitarlo, esegui il seguente comando come "Amministratore" sul dispositivo:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Puoi eseguire il comando nella pagina dei processi del Portale di dispositivi di Windows IoT o usare PowerShell per collegare il tuo dispositivo Windows IoT.
+Per altre informazioni, visita la pagina http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Impossibile eseguire il comando come amministratore: {0}
+
+
+ Impossibile abilitare Command Line Processor (cmd.exe) sul tuo dispositivo: {0}
+
+
+ Abilitazione Command Line Processor (cmd.exe) riuscita sul tuo dispositivo.
+
+
+ Colore riquadro
+
+
+ Indietro
+ Back UI navigation
+
+
+ Mostra info dispositivo
+
+
+ Avanti
+ Forward UI navigation
+
+
+ Attiva/Disattiva schermo intero
+
+
+ Clona visualizzazione
+ Clone current view to another display
+
+
+ Salvataggio rapido registro
+
+
+ Registro sessione
+
+
+ Imposta pagina predefinita
+
+
+ Comando annullato.
+
+
+ Immetti la riga di comando
+ Placeholder for command line input text box
+
+
+ Errore nell'esecuzione della riga di comando: {0}
+
+
+ Riga di comando
+
+
+ Riga di comando
+ Title for command line page
+
+
+ Timeout del comando dopo {0} secondi senza output.
+
+
+ Nome computer
+
+
+ Conferma
+
+
+ Connetti automaticamente
+
+
+ Connetti automaticamente
+
+
+ Connetti
+
+
+ Connetti
+
+
+ Dispositivi connessi
+
+
+ Aggiornamento non riuscito. Connetti il Wi-Fi e riprova.
+ App update error, poor connection
+
+
+ Continua
+
+
+ Impossibile analizzare l'output del comando
+
+
+ Anello corrente
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Pagina app predefinita
+
+
+ La lingua predefinita verrà scelta automaticamente...
+
+
+ {0} registri eliminati
+ {0} is plural number of logs
+
+
+ {0} registro eliminato
+ {0} is singular number of logs
+
+
+ Eliminare {0} registro?
+ {0} is singular number of logs
+
+
+ Eliminare {0} registri?
+ {0} is plural number of logs
+
+
+ Elimina selezionato
+
+
+ ID dispositivo Azure
+ Field label
+
+
+ Hub Azure IoT
+ Field label
+
+
+ Vai a pagina dispositivo
+
+
+ Indirizzo IP: {0}
+Versione sistema operativo: {1}
+Versione app: {2}
+
+
+ Versione app
+ Field label
+
+
+ Nome periferica
+ Field label
+
+
+ Indirizzo IP
+ Field label
+
+
+ Rete
+ Field label
+
+
+ Versione SO
+ Label for OS Version field in main page
+
+
+ per iniziare a sviluppare
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Info dispositivo
+
+
+ Visita
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ La pagina a cui stai tentando di accedere richiede l'utilizzo delle API del Portale di dispositivi di Windows (WDP). Accedi utilizzando le credenziali WDP per continuare.
+
+
+ Si è verificato un problema durante l'accesso.
+
+
+ Accesso al Portale di dispositivi completato.
+
+
+ Verifica delle credenziali del Portale di dispositivi in corso...
+
+
+ Si è verificato un problema durante il recupero del meteo. Riprovare?
+
+
+ Connessioni dirette
+
+
+ Disconnetti
+ This disconnects the connected network
+
+
+ Lingua di visualizzazione aggiornata: {0}
+
+
+ Dominio
+
+
+ Download completato.
+ App update status
+
+
+ Download non riuscito. Riprova più tardi.
+
+
+ Download dell'aggiornamento
+ App update status
+
+
+ Scarica aggiornamenti
+
+
+ Disegno
+
+
+ "{0} registri inviati a {1}"
+ {0} is plural number of logs, {1} is email address
+
+
+ "{0} registro inviato a {1}"
+ {0} is singular number of logs, {1} is email address
+
+
+ Registro e-mail
+
+
+ Vuoi inviare tramite e-mail {0} a te stesso?
+ {0} is filename
+
+
+ Si è verificato un problema durante l'invio tramite e-mail del tuo registro: {0}
+ {0} is exception message
+
+
+ Puoi trovare i tuoi registri nella pagina Registri
+
+
+ "Inviare tramite e-mail {0} registro a te stesso?"
+ {0} is singular number of logs
+
+
+ Si è verificato un problema durante l'invio tramite e-mail dei tuoi registri: {0}
+ {0} is an exception message
+
+
+ Inviare tramite e-mail {0} registri a te stesso?
+ {0} is plural number of logs
+
+
+ Invia tramite e-mail registri
+
+
+ Invia tramite e-mail selezionato
+
+
+ Abilita Command Line Processor
+
+
+ Screen saver
+ Toggle switch for enabling the screensaver
+
+
+ Ora di fine
+
+
+ Errore
+
+
+ Si è verificato un problema durante il recupero delle informazioni sul meteo
+
+
+ Ethernet
+ Field label
+
+
+ GUID del provider ETW: {0}
+ Format string for app settings page
+
+
+ Esecuzione dei comandi come DefaultAccount
+
+
+ Esplora
+
+
+ File salvato: {0}
+ {0} is a filename
+
+
+ Distribuzione di versioni di anteprima
+ Device servicing flighting
+
+
+ Info distribuzione di versioni di anteprima
+ Device servicing flighting
+
+
+ L'anello di versione di anteprima è stato modificato in {0}.
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ Si è verificato un problema durante la modifica dell'anello di versione di anteprima
+
+
+ Previsione
+ Weather forecast
+
+
+ Stai per attivare la modalità schermo intero. Per uscire, premi il tasto [Esc] della tastiera. Continuare?
+
+
+ Modalità schermo intero
+
+
+ Premi [Esc] per uscire dalla modalità a schermo intero.
+
+
+ Generale
+
+
+ Scheda IoT Enterprise
+ A generic board name
+
+
+ GitHub
+
+
+ ?
+
+
+ ?
+
+
+ ?
+
+
+ Lingua di input della tastiera aggiornata: {0}
+
+
+ Installazione completata.
+ App update status
+
+
+ Installazione non riuscita. Riprova più tardi.
+
+
+ Installazione dell'aggiornamento
+ App update status
+
+
+ Installa aggiornamenti
+
+
+ Credenziale non valida
+
+
+ '{0}' è una posizione non valida.
+ Format string for app settings page
+
+
+ '{0}' è un valore non valido. Il valore deve essere maggiore o uguale a 1.
+ Format string for app settings page
+
+
+ '{0}' è un valore non valido.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Layout di tastiera
+ Field label
+
+
+ Riavvia l'app per applicare le nuove impostazioni
+
+
+ Lingua
+
+
+ Lingua
+ Field label
+
+
+ Caricamento in corso...
+
+
+ Caricamento delle informazioni sul meteo in corso...
+
+
+ Il registro è stato inviato a {0}
+ {0} is email address
+
+
+ Registro salvato in: {0}
+ {0} is filename
+
+
+ Registri
+
+
+ Registri
+
+
+ Nome periferica
+ Field label
+
+
+ Indirizzo IP
+ Field label
+
+
+ Versione sistema operativo
+ Label for OS Version field in main page
+
+
+ Questa è un'immagine di prova di Windows 10 IoT Enterprise progettata solo come prototipo. Se il tuo obiettivo è la commercializzazione, devi utilizzare un FFU personalizzato per ottimizzare la sicurezza.
+ Maker Imager Security Notice
+
+
+ Token del servizio Bing Mappe
+
+
+ Token del servizio Bing Mappe richiesto
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Account Microsoft (MSA)
+
+
+ In fase di riproduzione
+ Music player page status text (currently playing)
+
+
+ Seleziona un brano e fai clic su Riproduci.
+ Music player page status text (default)
+
+
+ Aggiungi uno o più file audio alla cartella Musica.
+Puoi aggiungere la musica nel Portale di dispositivi di Windows scegliendo App > Esplora File.
+ Music player page instructions text
+
+
+ Caricamento della musica
+ Music player page loading panel text
+
+
+ Caricamento
+ Music player page status text (loading)
+
+
+ Nessun contenuto musicale trovato
+ Music player page no music found prompt text
+
+
+ Riprova
+ Music player page reload button text (no files prompt)
+
+
+ Musica
+
+
+ Musica
+
+
+ In pausa
+ Music player page status text (paused)
+
+
+ Esecuzione
+ Music player page status text (playing)
+
+
+ Accedi
+
+
+ Sconosciuto
+
+
+ Menu
+
+
+ Schede di rete
+
+
+ Connesso
+
+
+ Connesso
+
+
+ Verifica dei requisiti di rete
+
+
+ Verifica dei requisiti di rete in corso
+
+
+ Accesso a Internet limitato
+
+
+ Accesso locale e a Internet
+
+
+ Solo accesso alla rete locale
+
+
+ Nessuna connessione
+
+
+ INFORMAZIONI RETE
+
+
+ Rete non disponibile
+
+
+ Immetti la chiave di sicurezza di rete
+
+
+ Immetti la chiave di sicurezza di rete
+
+
+ Rete e Wi-Fi
+
+
+ Rete e Wi-Fi
+
+
+ Visualizza proprietà di rete
+
+
+ Proprietà di rete
+
+
+ Stai per essere reindirizzato al captive portal di questa rete Wi-Fi. Continuare?
+
+
+ Reindirizzamento di rete
+
+
+ Avanti
+
+
+ Avanti
+
+
+ Nessun account trovato
+
+
+ No
+
+
+ nessun nome di dispositivo
+
+
+ nessuna connessione a Internet
+
+
+ Nessun registro selezionato
+
+
+ Nessun contenuto musicale trovato
+ Music player page panel text
+
+
+ Non trovata
+
+
+ Non sono presenti aggiornamenti in sospeso da scaricare.
+ App update status
+
+
+ Non sono presenti aggiornamenti in sospeso da installare.
+ App update status
+
+
+ N/D
+
+
+ Notifiche
+
+
+ Notifiche
+
+
+ Nessun nuovo aggiornamento trovato.
+ Format string displayed when no app updates are found
+
+
+ OK
+ Button content text for the Bluetooth settings page
+
+
+ Scegli una lingua
+
+
+ Attivazione della connessione
+
+
+ Benvenuto in Windows 10 IoT Enterprise
+
+
+ Per iniziare verranno configurate alcune impostazioni di base.
+
+
+ Benvenuto in Windows 10 IoT Enterprise
+
+
+ ID edizione sistema operativo
+
+
+ Edizione sistema operativo
+
+
+ Info sistema operativo
+
+
+ Info sistema operativo
+
+
+ Non disponibile
+ Text shown when we cannot retrieve the OS Version
+
+
+ Versione sistema operativo
+
+
+ Pacchetti
+ Software packages
+
+
+ Pacchetti installati
+ Software packages
+
+
+ Impostazioni della pagina
+
+
+ Pagine
+
+
+ Password
+
+
+ Caricamento delle immagini
+ Default text when no images are available
+
+
+ Aggiungi immagini alla cartella Immagini.
+Puoi aggiungere le immagini nel Portale di dispositivi di Windows scegliendo App > Esplora File.
+
+
+ Nessuna immagine trovata
+ Default text when no images are available
+
+
+ Piattaforma
+
+
+ Riproduci
+
+
+ Opzioni risparmio energia
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Di base: invia solo le informazioni sul dispositivo, sulle relative impostazioni e funzionalità e sul suo corretto funzionamento.
+
+
+ Invia tutti i dati di diagnostica di base oltre a informazioni sui siti Web visitati e sulla modalità di utilizzo di app e funzionalità, nonché informazioni aggiuntive sull'integrità e l'attività del dispositivo e sulla segnalazione errori avanzata.
+
+
+ Impossibile modificare l'impostazione della privacy. Controlla il nome utente e la password e riprova.
+
+
+ Scegli la quantità di dati di diagnostica da inviare a Microsoft. I dati di diagnostica vengono utilizzati per mantenere Windows sicuro e aggiornato, risolvere i problemi e apportare miglioramenti al prodotto. Indipendentemente dall'opzione selezionata, il dispositivo sarà ugualmente protetto e funzionerà normalmente.
+
+
+ Dati di diagnostica
+ Label for Setting item to control Privacy
+
+
+ Immetti le tue credenziali per impostare il livello di privacy in questo dispositivo.
+
+
+ Imposta il livello di privacy
+
+
+ Aggiorna
+ Refresh button
+
+
+ Ripeti brano
+ Music player page repeat toggle text
+
+
+ Riavvia
+
+
+ Riavvia
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Sintassi: comando RunAsAdmin
+
+Esempi:
+> RunAsdmin TZUTIL /s "Ora solare Pacifico"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Salva
+
+
+ Fattore di proporzione
+
+
+ Seleziona tutto
+
+
+ Invia telemetria
+
+
+ Non disponibile
+
+
+ Registro sessione
+
+
+ Si è verificato un problema durante l\'impostazione della pagina predefinita su {0}.
+ Format string for app settings page
+
+
+ Impostazioni
+
+
+ Riproduci in modo casuale
+ Music player page shuffle toggle text
+
+
+ Arresta
+
+
+ Arresta
+ Shutdown entry in the shutdown menu
+
+
+ Accedi al tuo account Azure AD per usare questa funzionalità.
+
+
+ Ignora
+
+
+ Ignora questo passaggio
+
+
+ Intervallo presentazione (secondi)
+
+
+ Presentazione
+
+
+ Presentazione
+
+
+ Avvia
+
+
+ Avvia
+
+
+ Ora di inizio
+
+
+ Stato
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Invia
+
+
+ Operazione riuscita
+
+
+ Sistema
+
+
+ Si è verificato un problema durante il tentativo di aggiornare le impostazioni del sistema.
+ Used within system settings
+
+
+ Livello telemetria
+
+
+ Telemetria
+
+
+ Testa notifica gigante
+
+
+ Testa notifica
+
+
+ Windows 10 IoT è un membro della famiglia Windows 10 che introduce sicurezza, gestibilità e potenza di livello aziendale nell'Internet delle cose. Sfrutta la connessione cloud, l'ecosistema e l'esperienza integrata di Windows, consentendo alle organizzazioni di creare un Internet delle cose personalizzato con dispositivi protetti di cui è possibile eseguire rapidamente il provisioning e che possono essere facilmente gestiti e integrati in una strategia cloud globale.
+
+
+ Altezza riquadro
+
+
+ Personalizzazione
+
+
+ Larghezza riquadro
+
+
+ Timeout della connessione
+
+
+ Fuso orario aggiornato: {0}
+
+
+ Errore: impossibile comunicare con il servizio meteo
+
+
+ Aggiornamento non riuscito a causa di un errore sconosciuto.
+ App update error, unknown
+
+
+ Deseleziona tutti
+
+
+ Errore non specificato
+
+
+ Opzioni avanzate
+
+
+ Controlla ora
+
+
+ Installa ora
+
+
+ {0} aggiornamento in sospeso
+ {0} is singular amount of updates
+
+
+ {0} nuovi aggiornamenti trovati.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} aggiornamenti in sospeso
+ {0} is plural amount of updates
+
+
+ Utilizza icone riquadro MDL2
+
+
+ Usa password
+
+
+ Nome utente
+
+
+ Portale di dispositivi di Windows
+
+
+ Impostazioni Portale di dispositivi
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Portale di dispositivi di Windows
+
+
+ Posizione corrente ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ La tua posizione
+
+
+ La tua posizione
+ Label for map pin
+
+
+ Posizione sconosciuta
+ Label for map pin
+
+
+ Sensore:
+ Label for temperature sensor output
+
+
+ Meteo
+
+
+ Errore durante il caricamento della pagina Meteo.
+
+Fai clic sul pulsante Aggiorna in basso a destra dello schermo per ricaricare la pagina.
+
+Se non disponi delle chiavi API Meteo, accedi a weatherunlocked.com. Salva le chiavi in "WeatherTokens.config" nella cartella di stato locale di questa app. Quindi aggiorna la pagina.
+
+
+ Meteo fornito da:
+
+
+ Meteo
+
+
+ Immetti indirizzo Web
+
+
+ Web browser
+
+
+ Benvenuto in Windows IoT Enterprise
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Aggiorna
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Ultimo controllo:
+ For a timestamp
+
+
+ Ultimo aggiornamento:
+ For a timestamp
+
+
+ Stato aggiornato:
+
+
+ Messaggio di stato:
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Directory di lavoro non valida: {0}
+
+
+ WPS
+
+
+ Consenti a questa app di accedere alla tua posizione
+
+
+ Sceglie le impostazioni, quindi seleziona 'Accetta' per salvarle. Puoi modificare queste impostazioni in qualsiasi momento.
+
+
+ Consenti a Microsoft di usare la tua posizione
+
+
+ Continua automaticamente...
+
+
+ Accetta
+
+
+ Consentire a {0} di accedere a una posizione esatta?
+ {0} is the name of a page
+
+
+ Posizione
+
+
+ Per modificare questa impostazione in seguito, vai a Impostazioni > Autorizzazioni.
+
+
+ No
+
+
+ Sì
+
+
+ Non sarai in grado di ottenere le esperienze basate sulla posizione come le mappe e il meteo né di utilizzare altri servizi che richiedono la tua posizione per funzionare.
+
+
+ Scarica le esperienze basate sulla posizione, come le mappe e il meteo. Lascia che questa app chieda la tua posizione. Microsoft utilizzerà i dati della posizione per migliorare i servizi di posizione.
+
+
+ Invia solo le informazioni sul dispositivo, le relative impostazioni e funzionalità e i dati che ne indicano il corretto funzionamento. I dati di diagnostica vengono usati per mantenere Windows sicuro e aggiornato, risolvere i problemi e apportare miglioramenti al prodotto. Indipendentemente dalla selezione di Base o Completo, il dispositivo verrà ugualmente protetto e funzionerà normalmente.
+
+
+ Di base
+
+
+ Invia tutti i dati di diagnostica di base oltre a informazioni sui siti Web visitati e sulla modalità di utilizzo di app e funzionalità, nonché informazioni aggiuntive sull'integrità e l'attività del dispositivo e sulla segnalazione errori avanzata. I dati di diagnostica vengono usati per mantenere Windows sicuro e aggiornato, per risolvere i problemi e per apportare miglioramenti al prodotto. Indipendentemente dalla selezione di Base o Completo, il dispositivo verrà ugualmente protetto e funzionerà normalmente.
+
+
+ Completo
+
+
+ Scegli un'impostazione di privacy per il dispositivo, quindi seleziona 'Accetta' per salvarla.
+
+
+ Invia dati di diagnostica a Microsoft
+
+
+ Diagnostica
+
+
+ Se consenti l'accesso, abiliterai questa app ad utilizzare le funzionalità del dispositivo per determinare la tua posizione e Microsoft utilizzerà i dati sulla tua posizione per migliorare i servizi di posizione. Se neghi l'accesso impedisci a Windows di fornire la posizione a questa app.
+
+
+ Scopri le opzioni per la privacy
+
+
+ Scopri qual è l'impatto di questa impostazione sulla privacy.
+
+
+ Ottieni altre informazioni su queste impostazioni
+
+
+ Informativa sulla privacy
+
+
+ Sì
+
+
+ Sì
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ja-JP/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ja-JP/Resources.resw
index 8c352d7ad..d5d96e811 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ja-JP/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ja-JP/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- AAD v2 を使用
-
-
- アクセスが取り消されました
-
-
- 説明:
-
-
- DHCP サーバー
-
-
- DNS:
-
-
- ゲートウェイ アドレス:
-
-
- IPv4 アドレス:
-
-
- 名前:
-
-
- 物理アドレス:
-
-
- サブネット マスク
-
-
- 種類:
-
-
- アプリのバージョン
-
-
- アプリ
-
-
- 外部アプリを起動しようとしています。このアプリに戻るには、Windows デバイス ポータルを使用する必要があります。続行しますか?
- Dialog prompt for launching external apps
-
-
- アプリ
-
-
- アプリの設定
-
-
- アクティブ時間を設定し、このデバイスを通常使用する時間をお知らせください。アクティブ時間中は、自動的な再起動は行われません。
-
-
- 新しい開始時刻と終了時刻を保存できません。両方が同じ時刻であるためです。異なる時刻を新たに選択するか、機能を無効にしてください。
-
-
- 詳細オプション
- Advanced section title
-
-
- フェッチ、ダウンロード、インストールの各更新手順を制御します。
-
-
- 自動更新オプション
- Auto-Update section title
-
-
- アクティブ時間外に、アプリの更新プログラムのインストールをアプリで実行する
-
-
- アプリの更新
- App update display dialog header
-
-
- 最終確認日時: {0}、{1}
- {0} is date, {1} is time
-
-
- 更新プログラムを最後に確認したのがいつであるかを特定できません
-
-
- アプリの更新
- Label for setting item to check for app updates
-
-
- MSA と AAD にサインインする
-
-
- 組織のアカウントを使用して、AAD にサインインしてください。
-
-
- Azure AD (AAD) にサインイン
-
-
- AAD
-
-
- Microsoft Graph と他のリソースを認証します
-
-
- Microsoft Graph のみを認証します
-
-
- キャンセル
-
-
- 組織のアカウント
-
-
- サインインのいずれかの手順から先に進めなくなり、サインイン ウィザードを終了できない場合は、{0} 秒待機してから、アプリに戻ってください。
-
-
- サインインしています...
-
-
- サインアウトしています...
-
-
- ここで Microsoft アカウントにサインインします
-
-
- Microsoft アカウント (MSA) にサインイン
-
-
- MSA
-
-
- 認証
-
-
- Microsoft にサインイン
-
-
- サインインできませんでした ({0})
-
-
- サインインが成功しました ({0})
-
-
- サインイン
-
-
- サインアウト: {0}
-
-
- サインアウト
-
-
- 自動再生
- Music player page auto-play toggle text
-
-
- 自動サイズ調整
-
-
- バッテリー残量が少なくなっているため、更新できませんでした。
- App update error, low battery
-
-
- {0} ({1}) とのペアリングを試みています。
- Text displayed when a Bluetooth pairing attempt starts
-
-
- {0}({1}) とペアリングしています。
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- デバイスに表示されている PIN は、{0} と一致しますか?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- 不明
- Text displayed when the Bluetooth device name is unknown
-
-
- 現在ペアリング済み
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- ペアリングの準備完了
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 不明な状態
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- ペアリング先のデバイスで、次の PIN を入力してください: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- PIN を入力してください:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- {0} ({1}) からの受信ペアリング要求です。
- Text displayed when an inbound pairing request is received
-
-
- このデバイスは、受信ペアリング用に既に登録されています。(サポートされているセレモニー: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- 受信ペアリング用に登録できませんでした。
- Text displayed when Inbound pairing handler registration fails
-
-
- 受信ペアリング用に正常に登録されました。(サポートされているセレモニー: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- 入力された PIN が正しくありません。
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- このデバイスで使用可能な Bluetooth アダプターが見つかりません: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- ペアリング
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- {0} ({1}) とペアリングできませんでした。
- Text displayed when a Bluetooth pairing attempt fails
-
-
- {0} ({1}) とのペアリングに成功しました。
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- 既定
- Text label for the corresponding device pairing protection level
-
-
- 暗号化と認証
- Text label for the corresponding device pairing protection level
-
-
- 暗号化
- Text label for the corresponding device pairing protection level
-
-
- なし
- Text label for the corresponding device pairing protection level
-
-
- 使用しているデバイスは検出可能となっており、他の Bluetooth デバイスとペアリングする準備ができています。
- Text displayed when StartWatcher is invoked
-
-
- 使用しているデバイスは、他の Bluetooth デバイスを検索することができなくっています。
- Text displayed when StopWatcher is invoked
-
-
- ペアリングの解除
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- {0} ({1}) からペアリングを解除できませんでした。
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- {0} ({1}) から正常にペアリングを解除しました。
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- ホーム ページ
-
-
- Web ブラウザー
-
-
- キャンセル
-
-
- ディレクトリの変更は現在サポートされていません。コマンドの完全パスを使用してください。
-
-
- タイム ゾーン
- Time zone text
-
-
- 更新プログラムを確認しています...
- App update status
-
-
- 更新プログラムの確認
-
-
- アカウントの解除
-
-
- アカウントを解除しているときに問題が発生しました
-
-
- この操作により、次の Windows アカウントが解除されます:
-{0}
-
-続行しますか?
-
-
- アカウントが解除されました
-
-
- アカウントを解除しています...
-
-
- クリア
-
-
- 閉じる
-
-
- 使用しているデバイスではコマンド ライン プロセッサを実行できません。
-実行できるようにするには、デバイスで、"管理者" として次のコマンドを実行してください:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-このコマンドは、IoT Windows デバイス ポータルの [プロセス] ページで実行できます。または、PowerShell を使用して、Windows IoT デバイスに接続してください。
-詳細については、http://go.microsoft.com/fwlink/p/?LinkId=698488 をご覧ください
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- 管理者としてコマンドを実行できませんでした: {0}
-
-
- 使用しているデバイスで、コマンド ライン プロセッサ (cmd.exe) を有効にできませんでした: {0}
-
-
- お使いのデバイスで、コマンド ライン プロセッサ (cmd.exe) が有効になりました。
-
-
- タイルの色
-
-
- 戻る
- Back UI navigation
-
-
- デバイス情報の表示
-
-
- 進む
- Forward UI navigation
-
-
- 全画面表示に切り替え
-
-
- ビューの複製
- Clone current view to another display
-
-
- ログのクイック セーブ
-
-
- セッション ログ
-
-
- 既定のページを設定
-
-
- コマンドは取り消されました。
-
-
- コマンド ラインを入力してください
- Placeholder for command line input text box
-
-
- コマンド ラインの実行中にエラーが発生しました: {0}
-
-
- コマンド ライン
-
-
- コマンド ライン
- Title for command line page
-
-
- {0} 秒経過したため、コマンドがタイムアウトしました。何も出力されません。
-
-
- コンピューター名
-
-
- 確認
-
-
- 自動的に接続
-
-
- 自動的に接続
-
-
- 接続
-
-
- 接続
-
-
- 接続中のデバイス
-
-
- 更新できませんでした。Wi-Fi に接続して、もう一度お試しください。
- App update error, poor connection
-
-
- 続行
-
-
- コマンド出力を解析できませんでした
-
-
- 現在のリング
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- 既定のアプリ ページ
-
-
- 既定の言語を自動的に選択しています...
-
-
- {0} 件のログを削除
- {0} is plural number of logs
-
-
- {0} 件のログを削除
- {0} is singular number of logs
-
-
- {0} 件のログを削除しますか?
- {0} is singular number of logs
-
-
- {0} 件のログを削除しますか?
- {0} is plural number of logs
-
-
- 選択したものを削除
-
-
- Azure デバイス ID
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- デバイス ページに移動
-
-
- IPアドレス: {0}
-OS のバージョン: {1}
-アプリのバージョン: {2}
-
-
- アプリのバージョン
- Field label
-
-
- デバイス名
- Field label
-
-
- IP アドレス
- Field label
-
-
- ネットワーク
- Field label
-
-
- OS バージョン
- Label for OS Version field in main page
-
-
- にアクセスしてください
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- デバイス情報
-
-
- 開発を始めるには、
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- アクセスしようとしているページでは、Windows デバイス ポータル (WDP) API を使用する必要があります。続行するには、WDP 資格情報を使用してサインインしてください。
-
-
- サインイン中に問題が発生しました。
-
-
- デバイス ポータルに正常にサインインしました。
-
-
- デバイス ポータルの資格情報を検証しています....
-
-
- 天気の取得中に問題が発生しました。もう一度お試しください。
-
-
- 直接接続
-
-
- 切断
- This disconnects the connected network
-
-
- 表示言語が更新されました: {0}
-
-
- ドメイン
-
-
- ダウンロードが完了しました。
- App update status
-
-
- ダウンロードできませんでした。 後でもう一度お試しください。
-
-
- 更新プログラムをダウンロードしています
- App update status
-
-
- 更新プログラムのダウンロード
-
-
- 描画
-
-
- "{0} 件のログが {1} に送信されました"
- {0} is plural number of logs, {1} is email address
-
-
- "{0} 件のログが {1} に送信されました"
- {0} is singular number of logs, {1} is email address
-
-
- メール ログ
-
-
- {0} を自分自身にメールで送信しますか?
- {0} is filename
-
-
- ログをメールで送信しているときに問題が発生しました: {0}
- {0} is exception message
-
-
- ログは [ログ] ページで見つけることができます
-
-
- "{0} 件のログを自分自身にメールで送信しますか?"
- {0} is singular number of logs
-
-
- ログをメールで送信しているときに問題が発生しました: {0}
- {0} is an exception message
-
-
- {0} 件のログを自分自身にメールで送信しますか?
- {0} is plural number of logs
-
-
- メール ログ
-
-
- 選択したメール
-
-
- コマンド ライン プロセッサを有効にする
-
-
- スクリーンセーバー
- Toggle switch for enabling the screensaver
-
-
- 終了時刻
-
-
- エラー
-
-
- 天気情報の取得中に問題が発生しました
-
-
- イーサネット
- Field label
-
-
- ETW プロバイダー GUID: {0}
- Format string for app settings page
-
-
- DefaultAccount としてコマンドを実行中
-
-
- 探す
-
-
- ファイルを保存しました: {0}
- {0} is a filename
-
-
- フライティング
- Device servicing flighting
-
-
- フライティング情報
- Device servicing flighting
-
-
- フライト リングが {0} に変更されました。
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- フライト リングを変更しているときに問題が発生しました
-
-
- 天気予報
- Weather forecast
-
-
- 全画面表示モードに切り替えようとしています。終了するには、キーボードの Esc キーを押してください。続行しますか?
-
-
- 全画面表示モード
-
-
- 全画面表示モードを終了するには、Esc キーを押してください。
-
-
- 全般
-
-
- IoTEnterprise ボード
- A generic board name
-
-
- GitHub
-
-
- ヘルプ
-
-
- ヘルプ
-
-
- ヘルプ
-
-
- 入力キーボードの言語が更新されました: {0}
-
-
- インストールが完了しました。
- App update status
-
-
- インストールできませんでした。後でもう一度お試しください。
-
-
- 更新プログラムをインストールしています
- App update status
-
-
- 更新プログラムのインストール
-
-
- 資格情報が無効です
-
-
- '{0}' は無効な場所です。
- Format string for app settings page
-
-
- '{0}' は無効な値です。値は 1 以上にする必要があります。
- Format string for app settings page
-
-
- '{0}' は無効な値です。
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- キーボード レイアウト
- Field label
-
-
- このアプリを再起動して新しい設定を適用
-
-
- 言語
-
-
- 言語
- Field label
-
-
- 読み込んでいます...
-
-
- 天気情報を読み込んでいます...
-
-
- ログが {0} に送信されました
- {0} is email address
-
-
- ログの保存先: {0}
- {0} is filename
-
-
- ログ
-
-
- ログ
-
-
- デバイス名
- Field label
-
-
- IP アドレス
- Field label
-
-
- OS のバージョン
- Label for OS Version field in main page
-
-
- これは、プロトタイプ作成のみを目的として設計された Windows 10 IoT Enterprise のテスト イメージです。商品化を予定している場合は、最適なセキュリティを実現するために、カスタム FFU を使用する必要があります。
- Maker Imager Security Notice
-
-
- Bing マップ サービス トークン
-
-
- Bing マップ サービス トークンが必要です
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com、Hotmail、Live.com、MSN
-
-
- Microsoft アカウント (MSA)
-
-
- 現在再生中
- Music player page status text (currently playing)
-
-
- 曲を選択し、[再生] をクリックします。
- Music player page status text (default)
-
-
- 1 つ以上のオーディオ ファイルをミュージック フォルダーに追加してください。
-Windows デバイス ポータルでは、[アプリ] > [エクスプローラー] を使用して、音楽を追加できます。
- Music player page instructions text
-
-
- 音楽を読み込んでいます
- Music player page loading panel text
-
-
- 読み込み中
- Music player page status text (loading)
-
-
- 音楽が見つかりませんでした
- Music player page no music found prompt text
-
-
- やり直す
- Music player page reload button text (no files prompt)
-
-
- 音楽
-
-
- 音楽
-
-
- 一時停止中
- Music player page status text (paused)
-
-
- 再生中
- Music player page status text (playing)
-
-
- サインイン
-
-
- 不明
-
-
- メニュー
-
-
- ネットワーク アダプター
-
-
- 接続済み
-
-
- 接続済み
-
-
- ネットワークの要件を確認しています
-
-
- ネットワークの要件をチェックしています
-
-
- 制限付きインターネット アクセス
-
-
- ローカルとインターネット アクセス
-
-
- ローカル ネットワーク アクセスのみ
-
-
- 接続がありません
-
-
- ネットワーク情報
-
-
- ネットワークを利用できません
-
-
- ネットワーク セキュリティ キーを入力してください
-
-
- ネットワーク セキュリティ キーを入力してください
-
-
- ネットワークと Wi-Fi
-
-
- ネットワークと Wi-Fi
-
-
- ネットワークのプロパティを表示
-
-
- ネットワークのプロパティ
-
-
- この Wi-Fi ネットワークのキャプティブ ポータルへリダイレクトされようとしています。続行しますか?
-
-
- ネットワークのリダイレクト
-
-
- 次へ
-
-
- 次へ
-
-
- アカウントが見つかりませんでした
-
-
- いいえ
-
-
- デバイス名がありません
-
-
- インターネット接続がありません
-
-
- ログが選択されていません
-
-
- 音楽が見つかりませんでした
- Music player page panel text
-
-
- 見つかりません
-
-
- ダウンロードする保留中の更新プログラムはありません。
- App update status
-
-
- インストールする保留中の更新プログラムはありません。
- App update status
-
-
- N/A
-
-
- 通知
-
-
- 通知
-
-
- 新しい更新プログラムが見つかりませんでした。
- Format string displayed when no app updates are found
-
-
- OK
- Button content text for the Bluetooth settings page
-
-
- 言語を選択してください
-
-
- 接続しましょう
-
-
- Windows 10 IoT Enterprise へようこそ
-
-
- いくつか基本的なことを確認してみましょう。
-
-
- Windows 10 IoT Enterprise へようこそ
-
-
- OS のエディション ID
-
-
- OS のエディション
-
-
- OS の情報
-
-
- OS の情報
-
-
- 利用不可
- Text shown when we cannot retrieve the OS Version
-
-
- OS のバージョン
-
-
- パッケージ
- Software packages
-
-
- インストール済みパッケージ
- Software packages
-
-
- ページの設定
-
-
- ページ
-
-
- パスワード
-
-
- 画像を読み込んでいます
- Default text when no images are available
-
-
- 画像をピクチャ フォルダーに追加してください。
-Windows デバイス ポータルでは、[アプリ] > [エクスプローラー] を使用して、画像を追加できます。
-
-
- 画像が見つかりませんでした
- Default text when no images are available
-
-
- プラットフォーム
-
-
- プレイ/再生
-
-
- 電源オプション
- Label for Setting item to control Power (shutdown/restart)
-
-
- 基本: お使いのデバイス、その設定と機能、およびそれが正常に実行されているかどうかに関する情報のみを送信します。
-
-
- 完全: すべての基本的な診断データと共に、参照する Web サイトおよびアプリと機能の使用方法に関する情報、さらにデバイスの正常性、デバイスの動作、詳細エラー報告に関する追加情報を送信します。
-
-
- プライバシーの設定を変更できませんでした。ユーザー名とパスワードを確認してから、もう一度お試しください。
-
-
- Microsoft に送信する診断データの量を選択します。診断データは、Windows のセキュリティを維持し、問題のトラブルシューティングを行い、製品を改善するために使用されます。どのオプションを選択しても、デバイスは同じように安全になり、正常に動作します。
-
-
- 診断データ
- Label for Setting item to control Privacy
-
-
- このデバイスでのプライバシー レベルを設定するための資格情報を入力します。
-
-
- プライバシー レベルの設定
-
-
- 最新の情報に更新
- Refresh button
-
-
- 曲を繰り返す
- Music player page repeat toggle text
-
-
- 再起動
-
-
- 再起動
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- 使用法: RunAsAdmin コマンド
-
-例:
-> RunAsdmin TZUTIL /s "太平洋標準時"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- 保存
-
-
- スケール ファクター
-
-
- すべて選択
-
-
- 利用統計情報の送信
-
-
- 利用不可
-
-
- セッション ログ
-
-
- 既定のページを {0} に設定しているときに問題が発生しました。
- Format string for app settings page
-
-
- 設定
-
-
- シャッフル
- Music player page shuffle toggle text
-
-
- シャットダウン
-
-
- シャットダウン
- Shutdown entry in the shutdown menu
-
-
- この機能を使用するには Azure AD アカウントにサインインしてください。
-
-
- スキップ
-
-
- この手順をスキップする
-
-
- スライドショーの間隔 (秒)
-
-
- スライドショー
-
-
- スライドショー
-
-
- 開始
-
-
- 開始
-
-
- 開始時刻
-
-
- 状態
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- 送信
-
-
- 成功
-
-
- システム
-
-
- システム設定を更新しようとしているときに問題が発生しました。
- Used within system settings
-
-
- 製品利用統計情報のレベル
-
-
- 製品利用統計情報
-
-
- サイズの非常に大きな通知のテスト
-
-
- 通知のテスト
-
-
- Windows 10 IoT は Windows 10 ファミリのメンバーで、モノのインターネットに対して、エンタープライズ クラスの強力な機能、セキュリティ、管理容易性を実現します。Windows 10 IoT は、Windows に組み込まれているエクスペリエンス、エコシステム、クラウドの接続性を活用し、組織がセキュリティで保護されたデバイス (すばやいプロビジョニング、容易な管理、クラウド ストラテジー全体へのシームレスな接続が可能なデバイス) を使用して、組織独自のモノのインターネットを構築できるようにします。
-
-
- タイルの高さ
-
-
- 個人用設定
-
-
- タイルの幅
-
-
- 接続がタイムアウトしました
-
-
- タイム ゾーンが更新されました: {0}
-
-
- エラー: 天気サービスと通信できません
-
-
- 不明なエラーが発生したため、更新できませんでした。
- App update error, unknown
-
-
- すべて選択解除
-
-
- 特定できないエラー
-
-
- 詳細オプション
-
-
- 今すぐ確認
-
-
- 今すぐインストール
-
-
- 保留中の更新プログラムが {0} 個あります
- {0} is singular amount of updates
-
-
- {0} 個の新しい更新プログラムが見つかりました。
- Format string displayed when new app updates are found. {0} is a number
-
-
- 保留中の更新プログラムが {0} 個あります
- {0} is plural amount of updates
-
-
- MDL2 タイル アイコンの使用
-
-
- パスワードを使用してください
-
-
- ユーザー名
-
-
- Windows デバイス ポータル
-
-
- デバイス ポータルの設定
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows デバイス ポータル
-
-
- 現在の場所 ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- 現在地
-
-
- 現在地
- Label for map pin
-
-
- 不明な場所
- Label for map pin
-
-
- センサー:
- Label for temperature sensor output
-
-
- 天気
-
-
- 天気ページの読み込み中にエラーが発生しました。
-
-画面の右下にある [最新の情報に更新] ボタンをクリックして、このページをもう一度読み込んでください。
-
-天気 API キーを持っていない場合は、weatherunlocked.com にアクセスしてください。キーをこのアプリのローカル状態フォルダーにある "WeatherTokens.config" に保存します。その後で、このページを最新の情報に更新します。
-
-
- 天気情報の提供元:
-
-
- 天気
-
-
- Web アドレスを入力します
-
-
- Web ブラウザー
-
-
- Windows IoT Enterprise へようこそ
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- 最新の情報に更新
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 最終確認日時:
- For a timestamp
-
-
- 最終更新日時:
- For a timestamp
-
-
- 更新後の状態:
-
-
- ステータス メッセージ:
-
-
- Windows Update
-
-
- Windows Update
-
-
- 作業ディレクトリが無効です: {0}
-
-
- WPS
-
-
- このアプリに位置情報へのアクセスを許可
-
-
- 設定を選択し、[受け入れる] を選んで設定を保存します。これらの設定はいつでも変更できます。
-
-
- Microsoft が位置情報を使うことを許可する
-
-
- 自動的に続行しています...
-
-
- 受け入れる
-
-
- {0} が詳しい位置情報にアクセスすることを許可しますか?
- {0} is the name of a page
-
-
- 場所
-
-
- 後でこれを変更するには、[設定] > [アクセス許可] に移動してください。
-
-
- いいえ
-
-
- はい
-
-
- 地図や天気などの位置情報に基づいたエクスペリエンスを実現したり、位置情報を必要とするその他のサービスを利用したりすることができなくなります。
-
-
- 地図や天気などの位置情報に基づいた情報が取得できます。このアプリに位置情報を確認させましょう。Microsoft は位置情報データを位置情報サービス改善のために使用します。
-
-
- デバイス、設定、機能に関する情報のみを送信し、正常に動作しているかどうかを通知します。診断データは、Windows をセキュリティが確保された最新の状態に保ち、問題のトラブルシューティングを行い、製品の改善に役立てるために使用されます。[基本] と [完全] のどちらを選択しても、デバイスは同じように安全に保たれ、正常に動作します。
-
-
- 基本
-
-
- すべての基本的な診断データに加えて、閲覧した Web サイトおよびアプリと機能の使用方法に関する情報、さらに、デバイスの正常性、デバイスのアクティビティ、および拡張エラー報告についての追加情報を送信します。診断データは、Windows をセキュリティが確保された最新の状態に保ち、問題のトラブルシューティングを行い、製品の改善に役立てるために使用されます。[基本] と [完全] のどちらを選択しても、デバイスは同じように安全に保たれ、正常に動作します。
-
-
- 空きなし
-
-
- デバイスのプライバシーの設定を選択し、[受け入れる] を選んで設定を保存します。
-
-
- 診断データを Microsoft に送信する
-
-
- 診断
-
-
- アクセスを許可すると、アプリでデバイスの機能を利用して、ユーザーの場所を特定することができます。また、位置情報サービスを改善するために、Microsoft がユーザーの位置情報データを使用できるようになります。アクセスを拒否すると、Windows がこのアプリに位置情報を提供することをブロックします。
-
-
- プライバシー オプションを確認する
-
-
- この設定がプライバシーにどのように影響するかを確認します。
-
-
- これらの設定に関する詳細情報を表示する
-
-
- プライバシーに関する声明
-
-
- はい
-
-
- はい
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ AAD v2 を使用
+
+
+ アクセスが取り消されました
+
+
+ 説明:
+
+
+ DHCP サーバー
+
+
+ DNS:
+
+
+ ゲートウェイ アドレス:
+
+
+ IPv4 アドレス:
+
+
+ 名前:
+
+
+ 物理アドレス:
+
+
+ サブネット マスク
+
+
+ 種類:
+
+
+ アプリのバージョン
+
+
+ アプリ
+
+
+ 外部アプリを起動しようとしています。このアプリに戻るには、Windows デバイス ポータルを使用する必要があります。続行しますか?
+ Dialog prompt for launching external apps
+
+
+ アプリ
+
+
+ アプリの設定
+
+
+ アクティブ時間を設定し、このデバイスを通常使用する時間をお知らせください。アクティブ時間中は、自動的な再起動は行われません。
+
+
+ 新しい開始時刻と終了時刻を保存できません。両方が同じ時刻であるためです。異なる時刻を新たに選択するか、機能を無効にしてください。
+
+
+ 詳細オプション
+ Advanced section title
+
+
+ フェッチ、ダウンロード、インストールの各更新手順を制御します。
+
+
+ 自動更新オプション
+ Auto-Update section title
+
+
+ アクティブ時間外に、アプリの更新プログラムのインストールをアプリで実行する
+
+
+ アプリの更新
+ App update display dialog header
+
+
+ 最終確認日時: {0}、{1}
+ {0} is date, {1} is time
+
+
+ 更新プログラムを最後に確認したのがいつであるかを特定できません
+
+
+ アプリの更新
+ Label for setting item to check for app updates
+
+
+ MSA と AAD にサインインする
+
+
+ 組織のアカウントを使用して、AAD にサインインしてください。
+
+
+ Azure AD (AAD) にサインイン
+
+
+ AAD
+
+
+ Microsoft Graph と他のリソースを認証します
+
+
+ Microsoft Graph のみを認証します
+
+
+ キャンセル
+
+
+ 組織のアカウント
+
+
+ サインインのいずれかの手順から先に進めなくなり、サインイン ウィザードを終了できない場合は、{0} 秒待機してから、アプリに戻ってください。
+
+
+ サインインしています...
+
+
+ サインアウトしています...
+
+
+ ここで Microsoft アカウントにサインインします
+
+
+ Microsoft アカウント (MSA) にサインイン
+
+
+ MSA
+
+
+ 認証
+
+
+ Microsoft にサインイン
+
+
+ サインインできませんでした ({0})
+
+
+ サインインが成功しました ({0})
+
+
+ サインイン
+
+
+ サインアウト: {0}
+
+
+ サインアウト
+
+
+ 自動再生
+ Music player page auto-play toggle text
+
+
+ 自動サイズ調整
+
+
+ バッテリー残量が少なくなっているため、更新できませんでした。
+ App update error, low battery
+
+
+ {0} ({1}) とのペアリングを試みています。
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ {0}({1}) とペアリングしています。
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ デバイスに表示されている PIN は、{0} と一致しますか?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ 不明
+ Text displayed when the Bluetooth device name is unknown
+
+
+ 現在ペアリング済み
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ ペアリングの準備完了
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 不明な状態
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ ペアリング先のデバイスで、次の PIN を入力してください: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ PIN を入力してください:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ {0} ({1}) からの受信ペアリング要求です。
+ Text displayed when an inbound pairing request is received
+
+
+ このデバイスは、受信ペアリング用に既に登録されています。(サポートされているセレモニー: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ 受信ペアリング用に登録できませんでした。
+ Text displayed when Inbound pairing handler registration fails
+
+
+ 受信ペアリング用に正常に登録されました。(サポートされているセレモニー: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ 入力された PIN が正しくありません。
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ このデバイスで使用可能な Bluetooth アダプターが見つかりません: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ ペアリング
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ {0} ({1}) とペアリングできませんでした。
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ {0} ({1}) とのペアリングに成功しました。
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ 既定
+ Text label for the corresponding device pairing protection level
+
+
+ 暗号化と認証
+ Text label for the corresponding device pairing protection level
+
+
+ 暗号化
+ Text label for the corresponding device pairing protection level
+
+
+ なし
+ Text label for the corresponding device pairing protection level
+
+
+ 使用しているデバイスは検出可能となっており、他の Bluetooth デバイスとペアリングする準備ができています。
+ Text displayed when StartWatcher is invoked
+
+
+ 使用しているデバイスは、他の Bluetooth デバイスを検索することができなくっています。
+ Text displayed when StopWatcher is invoked
+
+
+ ペアリングの解除
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ {0} ({1}) からペアリングを解除できませんでした。
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ {0} ({1}) から正常にペアリングを解除しました。
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ ホーム ページ
+
+
+ Web ブラウザー
+
+
+ キャンセル
+
+
+ ディレクトリの変更は現在サポートされていません。コマンドの完全パスを使用してください。
+
+
+ タイム ゾーン
+ Time zone text
+
+
+ 更新プログラムを確認しています...
+ App update status
+
+
+ 更新プログラムの確認
+
+
+ アカウントの解除
+
+
+ アカウントを解除しているときに問題が発生しました
+
+
+ この操作により、次の Windows アカウントが解除されます:
+{0}
+
+続行しますか?
+
+
+ アカウントが解除されました
+
+
+ アカウントを解除しています...
+
+
+ クリア
+
+
+ 閉じる
+
+
+ 使用しているデバイスではコマンド ライン プロセッサを実行できません。
+実行できるようにするには、デバイスで、"管理者" として次のコマンドを実行してください:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+このコマンドは、IoT Windows デバイス ポータルの [プロセス] ページで実行できます。または、PowerShell を使用して、Windows IoT デバイスに接続してください。
+詳細については、http://go.microsoft.com/fwlink/p/?LinkId=698488 をご覧ください
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ 管理者としてコマンドを実行できませんでした: {0}
+
+
+ 使用しているデバイスで、コマンド ライン プロセッサ (cmd.exe) を有効にできませんでした: {0}
+
+
+ お使いのデバイスで、コマンド ライン プロセッサ (cmd.exe) が有効になりました。
+
+
+ タイルの色
+
+
+ 戻る
+ Back UI navigation
+
+
+ デバイス情報の表示
+
+
+ 進む
+ Forward UI navigation
+
+
+ 全画面表示に切り替え
+
+
+ ビューの複製
+ Clone current view to another display
+
+
+ ログのクイック セーブ
+
+
+ セッション ログ
+
+
+ 既定のページを設定
+
+
+ コマンドは取り消されました。
+
+
+ コマンド ラインを入力してください
+ Placeholder for command line input text box
+
+
+ コマンド ラインの実行中にエラーが発生しました: {0}
+
+
+ コマンド ライン
+
+
+ コマンド ライン
+ Title for command line page
+
+
+ {0} 秒経過したため、コマンドがタイムアウトしました。何も出力されません。
+
+
+ コンピューター名
+
+
+ 確認
+
+
+ 自動的に接続
+
+
+ 自動的に接続
+
+
+ 接続
+
+
+ 接続
+
+
+ 接続中のデバイス
+
+
+ 更新できませんでした。Wi-Fi に接続して、もう一度お試しください。
+ App update error, poor connection
+
+
+ 続行
+
+
+ コマンド出力を解析できませんでした
+
+
+ 現在のリング
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ 既定のアプリ ページ
+
+
+ 既定の言語を自動的に選択しています...
+
+
+ {0} 件のログを削除
+ {0} is plural number of logs
+
+
+ {0} 件のログを削除
+ {0} is singular number of logs
+
+
+ {0} 件のログを削除しますか?
+ {0} is singular number of logs
+
+
+ {0} 件のログを削除しますか?
+ {0} is plural number of logs
+
+
+ 選択したものを削除
+
+
+ Azure デバイス ID
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ デバイス ページに移動
+
+
+ IPアドレス: {0}
+OS のバージョン: {1}
+アプリのバージョン: {2}
+
+
+ アプリのバージョン
+ Field label
+
+
+ デバイス名
+ Field label
+
+
+ IP アドレス
+ Field label
+
+
+ ネットワーク
+ Field label
+
+
+ OS バージョン
+ Label for OS Version field in main page
+
+
+ にアクセスしてください
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ デバイス情報
+
+
+ 開発を始めるには、
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ アクセスしようとしているページでは、Windows デバイス ポータル (WDP) API を使用する必要があります。続行するには、WDP 資格情報を使用してサインインしてください。
+
+
+ サインイン中に問題が発生しました。
+
+
+ デバイス ポータルに正常にサインインしました。
+
+
+ デバイス ポータルの資格情報を検証しています....
+
+
+ 天気の取得中に問題が発生しました。もう一度お試しください。
+
+
+ 直接接続
+
+
+ 切断
+ This disconnects the connected network
+
+
+ 表示言語が更新されました: {0}
+
+
+ ドメイン
+
+
+ ダウンロードが完了しました。
+ App update status
+
+
+ ダウンロードできませんでした。 後でもう一度お試しください。
+
+
+ 更新プログラムをダウンロードしています
+ App update status
+
+
+ 更新プログラムのダウンロード
+
+
+ 描画
+
+
+ "{0} 件のログが {1} に送信されました"
+ {0} is plural number of logs, {1} is email address
+
+
+ "{0} 件のログが {1} に送信されました"
+ {0} is singular number of logs, {1} is email address
+
+
+ メール ログ
+
+
+ {0} を自分自身にメールで送信しますか?
+ {0} is filename
+
+
+ ログをメールで送信しているときに問題が発生しました: {0}
+ {0} is exception message
+
+
+ ログは [ログ] ページで見つけることができます
+
+
+ "{0} 件のログを自分自身にメールで送信しますか?"
+ {0} is singular number of logs
+
+
+ ログをメールで送信しているときに問題が発生しました: {0}
+ {0} is an exception message
+
+
+ {0} 件のログを自分自身にメールで送信しますか?
+ {0} is plural number of logs
+
+
+ メール ログ
+
+
+ 選択したメール
+
+
+ コマンド ライン プロセッサを有効にする
+
+
+ スクリーンセーバー
+ Toggle switch for enabling the screensaver
+
+
+ 終了時刻
+
+
+ エラー
+
+
+ 天気情報の取得中に問題が発生しました
+
+
+ イーサネット
+ Field label
+
+
+ ETW プロバイダー GUID: {0}
+ Format string for app settings page
+
+
+ DefaultAccount としてコマンドを実行中
+
+
+ 探す
+
+
+ ファイルを保存しました: {0}
+ {0} is a filename
+
+
+ フライティング
+ Device servicing flighting
+
+
+ フライティング情報
+ Device servicing flighting
+
+
+ フライト リングが {0} に変更されました。
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ フライト リングを変更しているときに問題が発生しました
+
+
+ 天気予報
+ Weather forecast
+
+
+ 全画面表示モードに切り替えようとしています。終了するには、キーボードの Esc キーを押してください。続行しますか?
+
+
+ 全画面表示モード
+
+
+ 全画面表示モードを終了するには、Esc キーを押してください。
+
+
+ 全般
+
+
+ IoTEnterprise ボード
+ A generic board name
+
+
+ GitHub
+
+
+ ヘルプ
+
+
+ ヘルプ
+
+
+ ヘルプ
+
+
+ 入力キーボードの言語が更新されました: {0}
+
+
+ インストールが完了しました。
+ App update status
+
+
+ インストールできませんでした。後でもう一度お試しください。
+
+
+ 更新プログラムをインストールしています
+ App update status
+
+
+ 更新プログラムのインストール
+
+
+ 資格情報が無効です
+
+
+ '{0}' は無効な場所です。
+ Format string for app settings page
+
+
+ '{0}' は無効な値です。値は 1 以上にする必要があります。
+ Format string for app settings page
+
+
+ '{0}' は無効な値です。
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ キーボード レイアウト
+ Field label
+
+
+ このアプリを再起動して新しい設定を適用
+
+
+ 言語
+
+
+ 言語
+ Field label
+
+
+ 読み込んでいます...
+
+
+ 天気情報を読み込んでいます...
+
+
+ ログが {0} に送信されました
+ {0} is email address
+
+
+ ログの保存先: {0}
+ {0} is filename
+
+
+ ログ
+
+
+ ログ
+
+
+ デバイス名
+ Field label
+
+
+ IP アドレス
+ Field label
+
+
+ OS のバージョン
+ Label for OS Version field in main page
+
+
+ これは、プロトタイプ作成のみを目的として設計された Windows 10 IoT Enterprise のテスト イメージです。商品化を予定している場合は、最適なセキュリティを実現するために、カスタム FFU を使用する必要があります。
+ Maker Imager Security Notice
+
+
+ Bing マップ サービス トークン
+
+
+ Bing マップ サービス トークンが必要です
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com、Hotmail、Live.com、MSN
+
+
+ Microsoft アカウント (MSA)
+
+
+ 現在再生中
+ Music player page status text (currently playing)
+
+
+ 曲を選択し、[再生] をクリックします。
+ Music player page status text (default)
+
+
+ 1 つ以上のオーディオ ファイルをミュージック フォルダーに追加してください。
+Windows デバイス ポータルでは、[アプリ] > [エクスプローラー] を使用して、音楽を追加できます。
+ Music player page instructions text
+
+
+ 音楽を読み込んでいます
+ Music player page loading panel text
+
+
+ 読み込み中
+ Music player page status text (loading)
+
+
+ 音楽が見つかりませんでした
+ Music player page no music found prompt text
+
+
+ やり直す
+ Music player page reload button text (no files prompt)
+
+
+ 音楽
+
+
+ 音楽
+
+
+ 一時停止中
+ Music player page status text (paused)
+
+
+ 再生中
+ Music player page status text (playing)
+
+
+ サインイン
+
+
+ 不明
+
+
+ メニュー
+
+
+ ネットワーク アダプター
+
+
+ 接続済み
+
+
+ 接続済み
+
+
+ ネットワークの要件を確認しています
+
+
+ ネットワークの要件をチェックしています
+
+
+ 制限付きインターネット アクセス
+
+
+ ローカルとインターネット アクセス
+
+
+ ローカル ネットワーク アクセスのみ
+
+
+ 接続がありません
+
+
+ ネットワーク情報
+
+
+ ネットワークを利用できません
+
+
+ ネットワーク セキュリティ キーを入力してください
+
+
+ ネットワーク セキュリティ キーを入力してください
+
+
+ ネットワークと Wi-Fi
+
+
+ ネットワークと Wi-Fi
+
+
+ ネットワークのプロパティを表示
+
+
+ ネットワークのプロパティ
+
+
+ この Wi-Fi ネットワークのキャプティブ ポータルへリダイレクトされようとしています。続行しますか?
+
+
+ ネットワークのリダイレクト
+
+
+ 次へ
+
+
+ 次へ
+
+
+ アカウントが見つかりませんでした
+
+
+ いいえ
+
+
+ デバイス名がありません
+
+
+ インターネット接続がありません
+
+
+ ログが選択されていません
+
+
+ 音楽が見つかりませんでした
+ Music player page panel text
+
+
+ 見つかりません
+
+
+ ダウンロードする保留中の更新プログラムはありません。
+ App update status
+
+
+ インストールする保留中の更新プログラムはありません。
+ App update status
+
+
+ N/A
+
+
+ 通知
+
+
+ 通知
+
+
+ 新しい更新プログラムが見つかりませんでした。
+ Format string displayed when no app updates are found
+
+
+ OK
+ Button content text for the Bluetooth settings page
+
+
+ 言語を選択してください
+
+
+ 接続しましょう
+
+
+ Windows 10 IoT Enterprise へようこそ
+
+
+ いくつか基本的なことを確認してみましょう。
+
+
+ Windows 10 IoT Enterprise へようこそ
+
+
+ OS のエディション ID
+
+
+ OS のエディション
+
+
+ OS の情報
+
+
+ OS の情報
+
+
+ 利用不可
+ Text shown when we cannot retrieve the OS Version
+
+
+ OS のバージョン
+
+
+ パッケージ
+ Software packages
+
+
+ インストール済みパッケージ
+ Software packages
+
+
+ ページの設定
+
+
+ ページ
+
+
+ パスワード
+
+
+ 画像を読み込んでいます
+ Default text when no images are available
+
+
+ 画像をピクチャ フォルダーに追加してください。
+Windows デバイス ポータルでは、[アプリ] > [エクスプローラー] を使用して、画像を追加できます。
+
+
+ 画像が見つかりませんでした
+ Default text when no images are available
+
+
+ プラットフォーム
+
+
+ プレイ/再生
+
+
+ 電源オプション
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ 基本: お使いのデバイス、その設定と機能、およびそれが正常に実行されているかどうかに関する情報のみを送信します。
+
+
+ 完全: すべての基本的な診断データと共に、参照する Web サイトおよびアプリと機能の使用方法に関する情報、さらにデバイスの正常性、デバイスの動作、詳細エラー報告に関する追加情報を送信します。
+
+
+ プライバシーの設定を変更できませんでした。ユーザー名とパスワードを確認してから、もう一度お試しください。
+
+
+ Microsoft に送信する診断データの量を選択します。診断データは、Windows のセキュリティを維持し、問題のトラブルシューティングを行い、製品を改善するために使用されます。どのオプションを選択しても、デバイスは同じように安全になり、正常に動作します。
+
+
+ 診断データ
+ Label for Setting item to control Privacy
+
+
+ このデバイスでのプライバシー レベルを設定するための資格情報を入力します。
+
+
+ プライバシー レベルの設定
+
+
+ 最新の情報に更新
+ Refresh button
+
+
+ 曲を繰り返す
+ Music player page repeat toggle text
+
+
+ 再起動
+
+
+ 再起動
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ 使用法: RunAsAdmin コマンド
+
+例:
+> RunAsdmin TZUTIL /s "太平洋標準時"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ 保存
+
+
+ スケール ファクター
+
+
+ すべて選択
+
+
+ 利用統計情報の送信
+
+
+ 利用不可
+
+
+ セッション ログ
+
+
+ 既定のページを {0} に設定しているときに問題が発生しました。
+ Format string for app settings page
+
+
+ 設定
+
+
+ シャッフル
+ Music player page shuffle toggle text
+
+
+ シャットダウン
+
+
+ シャットダウン
+ Shutdown entry in the shutdown menu
+
+
+ この機能を使用するには Azure AD アカウントにサインインしてください。
+
+
+ スキップ
+
+
+ この手順をスキップする
+
+
+ スライドショーの間隔 (秒)
+
+
+ スライドショー
+
+
+ スライドショー
+
+
+ 開始
+
+
+ 開始
+
+
+ 開始時刻
+
+
+ 状態
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ 送信
+
+
+ 成功
+
+
+ システム
+
+
+ システム設定を更新しようとしているときに問題が発生しました。
+ Used within system settings
+
+
+ 製品利用統計情報のレベル
+
+
+ 製品利用統計情報
+
+
+ サイズの非常に大きな通知のテスト
+
+
+ 通知のテスト
+
+
+ Windows 10 IoT は Windows 10 ファミリのメンバーで、モノのインターネットに対して、エンタープライズ クラスの強力な機能、セキュリティ、管理容易性を実現します。Windows 10 IoT は、Windows に組み込まれているエクスペリエンス、エコシステム、クラウドの接続性を活用し、組織がセキュリティで保護されたデバイス (すばやいプロビジョニング、容易な管理、クラウド ストラテジー全体へのシームレスな接続が可能なデバイス) を使用して、組織独自のモノのインターネットを構築できるようにします。
+
+
+ タイルの高さ
+
+
+ 個人用設定
+
+
+ タイルの幅
+
+
+ 接続がタイムアウトしました
+
+
+ タイム ゾーンが更新されました: {0}
+
+
+ エラー: 天気サービスと通信できません
+
+
+ 不明なエラーが発生したため、更新できませんでした。
+ App update error, unknown
+
+
+ すべて選択解除
+
+
+ 特定できないエラー
+
+
+ 詳細オプション
+
+
+ 今すぐ確認
+
+
+ 今すぐインストール
+
+
+ 保留中の更新プログラムが {0} 個あります
+ {0} is singular amount of updates
+
+
+ {0} 個の新しい更新プログラムが見つかりました。
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ 保留中の更新プログラムが {0} 個あります
+ {0} is plural amount of updates
+
+
+ MDL2 タイル アイコンの使用
+
+
+ パスワードを使用してください
+
+
+ ユーザー名
+
+
+ Windows デバイス ポータル
+
+
+ デバイス ポータルの設定
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows デバイス ポータル
+
+
+ 現在の場所 ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ 現在地
+
+
+ 現在地
+ Label for map pin
+
+
+ 不明な場所
+ Label for map pin
+
+
+ センサー:
+ Label for temperature sensor output
+
+
+ 天気
+
+
+ 天気ページの読み込み中にエラーが発生しました。
+
+画面の右下にある [最新の情報に更新] ボタンをクリックして、このページをもう一度読み込んでください。
+
+天気 API キーを持っていない場合は、weatherunlocked.com にアクセスしてください。キーをこのアプリのローカル状態フォルダーにある "WeatherTokens.config" に保存します。その後で、このページを最新の情報に更新します。
+
+
+ 天気情報の提供元:
+
+
+ 天気
+
+
+ Web アドレスを入力します
+
+
+ Web ブラウザー
+
+
+ Windows IoT Enterprise へようこそ
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ 最新の情報に更新
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 最終確認日時:
+ For a timestamp
+
+
+ 最終更新日時:
+ For a timestamp
+
+
+ 更新後の状態:
+
+
+ ステータス メッセージ:
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ 作業ディレクトリが無効です: {0}
+
+
+ WPS
+
+
+ このアプリに位置情報へのアクセスを許可
+
+
+ 設定を選択し、[受け入れる] を選んで設定を保存します。これらの設定はいつでも変更できます。
+
+
+ Microsoft が位置情報を使うことを許可する
+
+
+ 自動的に続行しています...
+
+
+ 受け入れる
+
+
+ {0} が詳しい位置情報にアクセスすることを許可しますか?
+ {0} is the name of a page
+
+
+ 場所
+
+
+ 後でこれを変更するには、[設定] > [アクセス許可] に移動してください。
+
+
+ いいえ
+
+
+ はい
+
+
+ 地図や天気などの位置情報に基づいたエクスペリエンスを実現したり、位置情報を必要とするその他のサービスを利用したりすることができなくなります。
+
+
+ 地図や天気などの位置情報に基づいた情報が取得できます。このアプリに位置情報を確認させましょう。Microsoft は位置情報データを位置情報サービス改善のために使用します。
+
+
+ デバイス、設定、機能に関する情報のみを送信し、正常に動作しているかどうかを通知します。診断データは、Windows をセキュリティが確保された最新の状態に保ち、問題のトラブルシューティングを行い、製品の改善に役立てるために使用されます。[基本] と [完全] のどちらを選択しても、デバイスは同じように安全に保たれ、正常に動作します。
+
+
+ 基本
+
+
+ すべての基本的な診断データに加えて、閲覧した Web サイトおよびアプリと機能の使用方法に関する情報、さらに、デバイスの正常性、デバイスのアクティビティ、および拡張エラー報告についての追加情報を送信します。診断データは、Windows をセキュリティが確保された最新の状態に保ち、問題のトラブルシューティングを行い、製品の改善に役立てるために使用されます。[基本] と [完全] のどちらを選択しても、デバイスは同じように安全に保たれ、正常に動作します。
+
+
+ 空きなし
+
+
+ デバイスのプライバシーの設定を選択し、[受け入れる] を選んで設定を保存します。
+
+
+ 診断データを Microsoft に送信する
+
+
+ 診断
+
+
+ アクセスを許可すると、アプリでデバイスの機能を利用して、ユーザーの場所を特定することができます。また、位置情報サービスを改善するために、Microsoft がユーザーの位置情報データを使用できるようになります。アクセスを拒否すると、Windows がこのアプリに位置情報を提供することをブロックします。
+
+
+ プライバシー オプションを確認する
+
+
+ この設定がプライバシーにどのように影響するかを確認します。
+
+
+ これらの設定に関する詳細情報を表示する
+
+
+ プライバシーに関する声明
+
+
+ はい
+
+
+ はい
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ko/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ko/Resources.resw
index d24b496eb..fc64a62c0 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ko/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ko/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- AAD v2 사용
-
-
- 연결 해지됨
-
-
- 설명:
-
-
- DHCP 서버:
-
-
- DNS:
-
-
- 게이트웨이 주소:
-
-
- IPv4 주소:
-
-
- 이름:
-
-
- 물리적 주소
-
-
- 서브넷 마스크:
-
-
- 유형:
-
-
- 앱 버전
-
-
- 앱
-
-
- 외부 앱을 시작하려고 합니다. 이 앱으로 돌아가려면 Windows 장치 포털을 사용해야 합니다. 계속하시겠습니까?
- Dialog prompt for launching external apps
-
-
- 앱
-
-
- 앱 설정
-
-
- 사용 시간을 설정하여 이 장치를 일반적으로 사용하는 시간을 알려주세요. 사용 시간 중에는 장치가 자동으로 다시 시작되지 않습니다.
-
-
- 새로운 시작 시간 및 종료 시간이 동일하므로 저장할 수 없습니다. 새로운 시간을 선택하거나 기능을 해제하세요.
-
-
- 고급 옵션
- Advanced section title
-
-
- 가져오기, 다운로드 및 설치 업데이트 단계 각각을 제어합니다.
-
-
- 자동 업데이트 옵션
- Auto-Update section title
-
-
- 앱이 사용 시간이 아닐 때 시간이 앱 업데이트를 설치하도록 허용
-
-
- 앱 업데이트
- App update display dialog header
-
-
- 마지막으로 확인한 날짜: {0}, {1}
- {0} is date, {1} is time
-
-
- 마지막으로 업데이트를 확인한 날짜를 파악할 수 없습니다.
-
-
- 앱 업데이트
- Label for setting item to check for app updates
-
-
- MSA 및 AAD에 로그인
-
-
- 조직 계정을 사용하여 AAD에 로그인하세요.
-
-
- Azure AD(AAD) 로그인
-
-
- AAD
-
-
- Microsoft Graph 및 기타 리소스 인증
-
-
- Microsoft Graph만 인증
-
-
- 취소
-
-
- 조직 계정
-
-
- 어떤 시점에서든 로그인 마법사가 멈추고 종료할 수 없으면 {0}초 기다려 주세요. 앱으로 돌아가야 합니다.
-
-
- 로그인 중...
-
-
- 로그아웃 중...
-
-
- 여기에서 Microsoft 계정에 로그인하세요.
-
-
- Microsoft 계정(MSA) 로그인
-
-
- MSA
-
-
- 인증
-
-
- Microsoft 로그인
-
-
- 로그인 실패 ({0})
-
-
- 로그인 성공 ({0})
-
-
- 로그인
-
-
- 로그아웃됨: {0}
-
-
- 로그아웃
-
-
- 자동 재생
- Music player page auto-play toggle text
-
-
- 자동 크기 조정
-
-
- 배터리 부족으로 업데이트가 실패했습니다.
- App update error, low battery
-
-
- {0}({1})과(와) 페어링하려는 중입니다.
- Text displayed when a Bluetooth pairing attempt starts
-
-
- {0}({1})과(와) 페어링 중입니다.
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- 장치에 표시된 PIN이 {0}과(와) 일치하나요?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- 알 수 없음
- Text displayed when the Bluetooth device name is unknown
-
-
- 현재 연결됨
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 연결 준비 완료
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 알 수 없는 상태
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 페어링할 장치에 다음 PIN을 입력하세요. {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- PIN 입력:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- {0}({1})의 인바운드 페어링 요청입니다.
- Text displayed when an inbound pairing request is received
-
-
- 이 장치는 인바운드 페어링에 대해 이미 등록되어 있습니다. (지원되는 양식: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- 인바운드 페어링에 대해 등록하지 못했습니다.
- Text displayed when Inbound pairing handler registration fails
-
-
- 인바운드 페어링에 대해 등록했습니다. (지원되는 양식: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- 입력한 PIN이 잘못되었습니다.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- 이 장치에서 사용 가능한 Bluetooth 어댑터를 찾을 수 없습니다. \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- 연결
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- {0}({1})과(와) 페어링하지 못했습니다.
- Text displayed when a Bluetooth pairing attempt fails
-
-
- {0}({1})과(와) 페어링되었습니다.
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- 기본값
- Text label for the corresponding device pairing protection level
-
-
- 암호화 및 인증
- Text label for the corresponding device pairing protection level
-
-
- 암호화
- Text label for the corresponding device pairing protection level
-
-
- 없음
- Text label for the corresponding device pairing protection level
-
-
- 이제 장치를 검색할 수 있으며 다른 Bluetooth 장치와 페어링할 준비가 완료되었습니다.
- Text displayed when StartWatcher is invoked
-
-
- 장치가 더 이상 다른 Bluetooth 장치를 검색하고 있지 않습니다.
- Text displayed when StopWatcher is invoked
-
-
- 연결 해제
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- {0} ({1})에서 언페어링하지 못했습니다.
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- {0}({1})에서 연결을 해제했습니다.
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- 홈페이지
-
-
- 웹 브라우저
-
-
- 취소
-
-
- 디렉터리 변경이 현재 지원되지 않습니다. 명령에 전체 경로를 사용하세요.
-
-
- 표준 시간대
- Time zone text
-
-
- 업데이트 확인 중...
- App update status
-
-
- 업데이트 확인
-
-
- 계정 지우기
-
-
- 계정을 지우는 동안 문제가 발생했습니다.
-
-
- 다음 Windows 계정이 지워집니다.
-{0}
-
-계속하시겠습니까?
-
-
- 계정을 지웠습니다.
-
-
- 계정을 지우는 중...
-
-
- 지우기
-
-
- 닫기
-
-
- 장치에서 명령줄 프로세서를 실행할 수 없습니다.
-실행하도록 하려면 장치에 "관리자"로 다음 명령을 실행하세요.
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-IoT Windows 장치 포털의 프로세스 페이지에서 명령을 실행하거나 PowerShell을 사용하여 Windows IoT 장치에 연결할 수 있습니다.
-자세한 내용은 http://go.microsoft.com/fwlink/p/?LinkId=698488을 참조하세요.
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- 관리자 권한으로 명령을 실행하지 못함: {0}
-
-
- 장치에서 명령줄 프로세서(cmd.exe)를 사용하도록 설정하지 못했습니다. {0}
-
-
- 디바이스에서 명령줄 프로세서(cmd.exe)를 사용하도록 설정했습니다.
-
-
- 타일 색
-
-
- 뒤로
- Back UI navigation
-
-
- 장치 정보 표시
-
-
- 앞으로
- Forward UI navigation
-
-
- 전체 화면 설정/해제
-
-
- 복제 보기
- Clone current view to another display
-
-
- 로그 빠른 저장
-
-
- 세션 로그
-
-
- 기본 페이지 설정
-
-
- 명령이 취소되었습니다.
-
-
- 명령줄 입력
- Placeholder for command line input text box
-
-
- 명령줄 실행 오류: {0}
-
-
- 명령줄
-
-
- 명령줄
- Title for command line page
-
-
- 출력이 없이 {0}초가 지난 후 명령이 시간 초과되었습니다.
-
-
- 컴퓨터 이름
-
-
- 확인
-
-
- 자동으로 연결
-
-
- 자동으로 연결
-
-
- 연결
-
-
- 연결
-
-
- 연결된 장치
-
-
- 업데이트가 실패했습니다. Wi-Fi에 연결하고 다시 시도하세요.
- App update error, poor connection
-
-
- 계속
-
-
- 명령 출력을 구문 분석할 수 없습니다.
-
-
- 현재 링
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- 기본 앱 페이지
-
-
- 기본 언어를 자동으로 선택하는 중...
-
-
- 로그 {0}개 삭제됨
- {0} is plural number of logs
-
-
- 로그 {0}개 삭제됨
- {0} is singular number of logs
-
-
- 로그 {0}개를 삭제할까요?
- {0} is singular number of logs
-
-
- 로그 {0}개를 삭제할까요?
- {0} is plural number of logs
-
-
- 선택한 항목 삭제
-
-
- Azure 장치 ID
- Field label
-
-
- Azure IoT Hub
- Field label
-
-
- 장치 페이지로 이동
-
-
- IP 주소: {0}
-OS 버전: {1}
-앱 버전: {2}
-
-
- 앱 버전
- Field label
-
-
- 장치 이름
- Field label
-
-
- IP 주소
- Field label
-
-
- 네트워크
- Field label
-
-
- OS 버전
- Label for OS Version field in main page
-
-
- 을 방문하세요.
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 장치 정보
-
-
- 개발을 시작하려면
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 해당 페이지에 액세스하려면 Windows 장치 포털(WDP) API를 사용해야 합니다. 계속하려면 WDP 자격 증명을 사용하여 로그인하세요.
-
-
- 로그인하는 중에 문제가 발생했습니다.
-
-
- 장치 포털에 로그인했습니다!
-
-
- 장치 포털 자격 증명을 확인하는 중...
-
-
- 날씨 정보를 가져오는 동안 문제가 발생했습니다. 다시 시도할까요?
-
-
- 직접 연결
-
-
- 연결 끊기
- This disconnects the connected network
-
-
- 표시 언어 업데이트됨: {0}
-
-
- 도메인
-
-
- 다운로드 완료!
- App update status
-
-
- 다운로드하지 못했습니다. 나중에 다시 시도하세요.
-
-
- 업데이트 다운로드 중
- App update status
-
-
- 다운로드 업데이트
-
-
- 그리기
-
-
- "로그 {0}개가 {1}(으)로 전송되었습니다."
- {0} is plural number of logs, {1} is email address
-
-
- "로그 {0}개가 {1}(으)로 전송되었습니다."
- {0} is singular number of logs, {1} is email address
-
-
- 로그 전자 메일로 보내기
-
-
- {0}을(를) 자신에게 전자 메일로 보내시겠습니까?
- {0} is filename
-
-
- 로그를 전자 메일로 보내는 동안 문제가 발생했습니다. {0}
- {0} is exception message
-
-
- 로그는 로그 페이지에서 찾을 수 있습니다.
-
-
- "로그 {0}개를 자신에게 전자 메일로 보내시겠습니까?"
- {0} is singular number of logs
-
-
- 로그를 전자 메일로 보내는 동안 문제가 발생했습니다. {0}
- {0} is an exception message
-
-
- 로그 {0}개를 자신에게 전자 메일로 보내시겠습니까?
- {0} is plural number of logs
-
-
- 로그 전자 메일로 보내기
-
-
- 선택한 항목 전자 메일로 보내기
-
-
- 명령줄 프로세서 사용
-
-
- 화면 보호기
- Toggle switch for enabling the screensaver
-
-
- 종료 시간
-
-
- 오류
-
-
- 날씨 정보를 검색하는 동안 문제가 발생했습니다.
-
-
- 이더넷
- Field label
-
-
- ETW 공급자 GUID: {0}
- Format string for app settings page
-
-
- DefaultAccount로 명령 실행 중
-
-
- 탐색
-
-
- 파일 저장됨: {0}
- {0} is a filename
-
-
- 플라이팅
- Device servicing flighting
-
-
- 플라이팅 정보
- Device servicing flighting
-
-
- 플라이트 링이 {0}(으)로 변경되었습니다!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- 플라이트 링을 변경하는 동안 문제가 발생했습니다.
-
-
- 예측
- Weather forecast
-
-
- 전체 화면 모드로 전환하려고 합니다. 종료하려면 키보드의 [Esc]를 눌러야 합니다. 계속하시겠습니까?
-
-
- 전체 화면 모드
-
-
- 전체 화면 모드를 끝내려면 [Esc]를 누르세요.
-
-
- 일반
-
-
- IoTEnterprise Board
- A generic board name
-
-
- GitHub
-
-
- 도움말
-
-
- 도움말
-
-
- 도움말
-
-
- 입력 키보드 언어 업데이트됨: {0}
-
-
- 설치 완료!
- App update status
-
-
- 설치하지 못했습니다. 나중에 다시 시도하세요.
-
-
- 업데이트 설치 중
- App update status
-
-
- 업데이트 설치
-
-
- 잘못된 자격 증명
-
-
- '{0}'은(는) 잘못된 위치입니다.
- Format string for app settings page
-
-
- '{0}'은(는) 잘못된 값입니다. 값은 1보다 크거나 같아야 합니다.
- Format string for app settings page
-
-
- '{0}'은(는) 잘못된 값입니다.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- 키보드 레이아웃
- Field label
-
-
- 새 설정을 적용하려면 이 앱을 다시 시작하세요.
-
-
- 언어
-
-
- 언어
- Field label
-
-
- 로드 중...
-
-
- 날씨 정보를 불러오는 중...
-
-
- 로그가 {0}(으)로 전송되었습니다.
- {0} is email address
-
-
- 로그가 {0}에 저장됨
- {0} is filename
-
-
- 로그
-
-
- 로그
-
-
- 장치 이름
- Field label
-
-
- IP 주소
- Field label
-
-
- OS 버전
- Label for OS Version field in main page
-
-
- 프로토타입만을 위해로 설계된 Windows 10 IoT Enterprise 테스트 이미지입니다. 장치를 상업용으로 사용하려면 장치의 보안을 최적화하기 위해 맞춤형 FFU를 사용해야 합니다.
- Maker Imager Security Notice
-
-
- Bing 지도 서비스 토큰
-
-
- Bing 지도 서비스 토큰 필요
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Microsoft 계정(MSA)
-
-
- 현재 재생 중
- Music player page status text (currently playing)
-
-
- 노래를 선택하고 [재생]을 클릭하세요.
- Music player page status text (default)
-
-
- 하나 이상의 오디오 파일을 음악 폴더에 추가하세요.
-앱 > 파일 탐색기를 사용하여 Windows 장치 포털에서 음악을 추가할 수 있습니다.
- Music player page instructions text
-
-
- 음악 불러오는 중
- Music player page loading panel text
-
-
- 불러오는 중
- Music player page status text (loading)
-
-
- 음악을 찾을 수 없음
- Music player page no music found prompt text
-
-
- 다시 시도
- Music player page reload button text (no files prompt)
-
-
- 음악
-
-
- 음악
-
-
- 일시 중지됨
- Music player page status text (paused)
-
-
- 재생 중
- Music player page status text (playing)
-
-
- 로그인
-
-
- 알 수 없음
-
-
- 메뉴
-
-
- 네트워크 어댑터
-
-
- 연결됨
-
-
- 연결됨
-
-
- 네트워크 요구 사항 확인 중
-
-
- 네트워크 요구 사항 확인 중
-
-
- 제한된 인터넷 액세스
-
-
- 로컬 및 인터넷 액세스
-
-
- 로컬 네트워크 액세스 전용
-
-
- 연결되지 않음
-
-
- 네트워크 정보
-
-
- 네트워크를 사용할 수 없음
-
-
- 네트워크 보안 키 입력
-
-
- 네트워크 보안 키 입력
-
-
- 네트워크 및 Wi-Fi
-
-
- 네트워크 및 Wi-Fi
-
-
- 네트워크 속성 보기
-
-
- 네트워크 속성
-
-
- 이 Wi-fi 네트워크의 종속 포털로 리디렉션됩니다. 계속하시겠습니까?
-
-
- 네트워크 리디렉션
-
-
- 다음
-
-
- 다음
-
-
- 계정을 찾을 수 없음
-
-
- 아니요
-
-
- 디바이스 이름 없음
-
-
- 인터넷 연결 없음
-
-
- 선택한 로그가 없습니다.
-
-
- 음악을 찾을 수 없음
- Music player page panel text
-
-
- 없음
-
-
- 다운로드 보류 중인 업데이트가 없습니다.
- App update status
-
-
- 설치 보류 중인 업데이트가 없습니다.
- App update status
-
-
- 해당 없음
-
-
- 알림
-
-
- 알림
-
-
- 새로운 업데이트가 없습니다.
- Format string displayed when no app updates are found
-
-
- 확인
- Button content text for the Bluetooth settings page
-
-
- 언어 선택
-
-
- 연결하기
-
-
- Windows 10 IoT Enterprise 시작
-
-
- 시작하기
-
-
- Windows 10 IoT Enterprise 시작
-
-
- OS 버전 ID
-
-
- OS 버전
-
-
- OS 정보
-
-
- OS 정보
-
-
- 사용할 수 없음
- Text shown when we cannot retrieve the OS Version
-
-
- OS 버전
-
-
- 패키지
- Software packages
-
-
- 설치된 패키지
- Software packages
-
-
- 페이지 설정
-
-
- 페이지
-
-
- 비밀번호
-
-
- 사진을 불러오는 중
- Default text when no images are available
-
-
- 하나 이상의 이미지를 사진 폴더에 추가하세요.
-앱 > 파일 탐색기를 사용하여 Windows 장치 포털에서 이미지를 추가할 수 있습니다.
-
-
- 이미지를 찾을 수 없음
- Default text when no images are available
-
-
- 플랫폼
-
-
- 재생
-
-
- 전원 옵션
- Label for Setting item to control Power (shutdown/restart)
-
-
- 기본: 장치에 대한 정보, 장치의 설정 및 기능, 장치가 제대로 수행되는지 여부만 보냅니다.
-
-
- 전체: 모든 기본 진단 데이터를 사용자가 탐색하는 웹 사이트에 대한 정보, 앱 및 기능을 사용하는 방법과 함께 장치 상태, 장치 활동 및 향상된 오류 보고에 대한 추가 정보를 포함하여 보냅니다.
-
-
- 개인 정보 설정을 변경할 수 없습니다. 사용자 이름과 비밀번호를 확인하고 다시 시도하세요.
-
-
- Microsoft에 진단 데이터를 얼마나 보낼지 선택합니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 선택하는 옵션에 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
-
-
- 진단 데이터
- Label for Setting item to control Privacy
-
-
- 이 장치의 개인 정보 수준을 설정하려면 자격 증명을 입력하세요.
-
-
- 개인 정보 수준 설정
-
-
- 새로 고침
- Refresh button
-
-
- 노래 반복
- Music player page repeat toggle text
-
-
- 다시 시작
-
-
- 다시 시작
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- 사용법: RunAsAdmin 명령
-
-예:
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- 저장
-
-
- 배율 인수
-
-
- 모두 선택
-
-
- 원격 분석 보내기
-
-
- 사용할 수 없음
-
-
- 세션 로그
-
-
- 기본 페이지를 {0}(으)로 설정하는 중에 문제가 발생했습니다.
- Format string for app settings page
-
-
- 설정
-
-
- 무작위 재생
- Music player page shuffle toggle text
-
-
- 종료
-
-
- 종료
- Shutdown entry in the shutdown menu
-
-
- 이 기능을 사용하려면 Azure AD 계정에 로그인하세요.
-
-
- 건너뛰기
-
-
- 이 단계 건너뛰기
-
-
- 슬라이드 쇼 간격(초)
-
-
- 슬라이드 쇼
-
-
- 슬라이드 쇼
-
-
- 시작
-
-
- 시작
-
-
- 시작 시간
-
-
- 상태
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- 제출
-
-
- 성공
-
-
- 시스템
-
-
- 시스템 설정을 업데이트하는 동안 문제가 발생했습니다.
- Used within system settings
-
-
- 원격 분석 수준
-
-
- 원격 분석
-
-
- 점보 알림 테스트
-
-
- 테스트 알림
-
-
- Windows 10 IoT는 사물 인터넷에 엔터프라이즈 수준의 강력한 기능, 보안 및 관리 기능을 제공하는 Windows 10 제품군입니다. Windows의 내장된 환경, 생태계 및 클라우드 연결을 활용하기 때문에 조직에서는 신속하게 프로비저닝하고 쉽게 관리할 수 있으며 전체 클라우드 전략에 원활하게 연결할 수 있는 보안 장치를 사용하여 사물 인터넷을 만들 수 있습니다.
-
-
- 타일 높이
-
-
- 개인 설정
-
-
- 타일 너비
-
-
- 연결 시간 초과
-
-
- 표준 시간대 업데이트됨: {0}
-
-
- 오류: 날씨 서비스와 통신할 수 없습니다.
-
-
- 알 수 없는 오류로 인해 업데이트가 실패했습니다.
- App update error, unknown
-
-
- 모두 선택 취소
-
-
- 미지정된 오류
-
-
- 고급 옵션
-
-
- 지금 확인
-
-
- 지금 설치
-
-
- 보류 중인 업데이트 {0}개
- {0} is singular amount of updates
-
-
- {0}개의 새 업데이트가 있습니다.
- Format string displayed when new app updates are found. {0} is a number
-
-
- 보류 중인 업데이트 {0}개
- {0} is plural amount of updates
-
-
- MDL2 타일 아이콘 사용
-
-
- 암호 사용
-
-
- 사용자 이름
-
-
- Windows 장치 포털
-
-
- 장치 포털 설정
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows 장치 포털
-
-
- 현재 위치({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- 사용자의 위치
-
-
- 사용자의 위치
- Label for map pin
-
-
- 알 수 없는 위치
- Label for map pin
-
-
- 센서:
- Label for temperature sensor output
-
-
- 날씨
-
-
- 날씨 페이지를 로드하는 중 오류가 발생했습니다.
-
-이 페이지를 다시 로드하려면 화면 오른쪽 하단에 있는 새로 고침 버튼을 클릭하세요.
-
-날씨 API 키가 없는 경우 weatherunlocked.com으로 이동하세요. 이 앱의 로컬 상태 폴더에 있는 "WeatherTokens.config"에 키를 저장한 다음 페이지를 새로 고치세요.
-
-
- 날씨 제공:
-
-
- 날씨
-
-
- 웹 주소 입력
-
-
- 웹 브라우저
-
-
- Windows IoT Enterprise 시작
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- 새로 고침
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 마지막으로 확인한 날짜:
- For a timestamp
-
-
- 마지막으로 업데이트한 날짜
- For a timestamp
-
-
- 업데이트된 상태:
-
-
- 상태 메시지:
-
-
- Windows 업데이트
-
-
- Windows 업데이트
-
-
- 잘못된 작업 디렉토리: {0}
-
-
- WPS
-
-
- 이 앱에서 위치에 액세스하도록 허용
-
-
- 설정을 선택한 다음 '수락'을 선택하여 설정을 저장하세요. 이 설정은 언제든지 변경할 수 있습니다.
-
-
- Microsoft에서 위치를 사용하도록 허용
-
-
- 자동으로 계속하는 중...
-
-
- 수락
-
-
- {0}의 정확한 위치 액세스를 허용할까요?
- {0} is the name of a page
-
-
- 위치
-
-
- 나중에 변경하려면 설정> 권한으로 이동하세요.
-
-
- 아니요
-
-
- 예
-
-
- 지도와 날씨 같은 위치 기반 서비스를 경험하거나 사용자의 위치 정보가 필요한 다른 서비스를 즐길 수 없습니다.
-
-
- 지도 및 날씨 같은 위치 기반 서비스를 경험해 보세요. 이 앱에서 위치를 요청하도록 허용하세요. Microsoft에서 위치 데이터를 사용하여 위치 서비스를 개선합니다.
-
-
- 장치에 대한 정보, 장치의 설정 및 기능, 장치가 제대로 수행되는지 여부만 보냅니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 기본 또는 전체 중 어떤 것을 선택하든 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
-
-
- 기본
-
-
- 모든 기본 진단 데이터를 사용자가 탐색하는 웹 사이트에 대한 정보, 앱 및 기능을 사용하는 방법과 함께 장치 상태, 장치 활동 및 향상된 오류 보고에 대한 추가 정보를 포함하여 보냅니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 기본 또는 전체 중 어떤 것을 선택하든 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
-
-
- 전체
-
-
- 장치에 대한 개인 정보 설정을 선택한 다음 '동의'를 선택하여 저장하세요.
-
-
- 진단 데이터를 Microsoft에 보내기
-
-
- 진단
-
-
- 액세스를 허용하면 이 앱에서 장치의 기능을 사용하여 위치를 파악할 수 있으며 Microsoft에서는 위치 데이터를 사용하여 위치 서비스를 개선합니다. 액세스를 거부하면 Windows가 이 앱에 위치 정보를 제공하는 것을 차단합니다.
-
-
- 개인 정보 옵션 알아보기
-
-
- 이 설정이 개인 정보에 어떤 영향을 주는지 알아보세요.
-
-
- 이 설정에 대한 자세한 정보 보기
-
-
- 개인정보처리방침
-
-
- 예
-
-
- 예
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ AAD v2 사용
+
+
+ 연결 해지됨
+
+
+ 설명:
+
+
+ DHCP 서버:
+
+
+ DNS:
+
+
+ 게이트웨이 주소:
+
+
+ IPv4 주소:
+
+
+ 이름:
+
+
+ 물리적 주소
+
+
+ 서브넷 마스크:
+
+
+ 유형:
+
+
+ 앱 버전
+
+
+ 앱
+
+
+ 외부 앱을 시작하려고 합니다. 이 앱으로 돌아가려면 Windows 장치 포털을 사용해야 합니다. 계속하시겠습니까?
+ Dialog prompt for launching external apps
+
+
+ 앱
+
+
+ 앱 설정
+
+
+ 사용 시간을 설정하여 이 장치를 일반적으로 사용하는 시간을 알려주세요. 사용 시간 중에는 장치가 자동으로 다시 시작되지 않습니다.
+
+
+ 새로운 시작 시간 및 종료 시간이 동일하므로 저장할 수 없습니다. 새로운 시간을 선택하거나 기능을 해제하세요.
+
+
+ 고급 옵션
+ Advanced section title
+
+
+ 가져오기, 다운로드 및 설치 업데이트 단계 각각을 제어합니다.
+
+
+ 자동 업데이트 옵션
+ Auto-Update section title
+
+
+ 앱이 사용 시간이 아닐 때 시간이 앱 업데이트를 설치하도록 허용
+
+
+ 앱 업데이트
+ App update display dialog header
+
+
+ 마지막으로 확인한 날짜: {0}, {1}
+ {0} is date, {1} is time
+
+
+ 마지막으로 업데이트를 확인한 날짜를 파악할 수 없습니다.
+
+
+ 앱 업데이트
+ Label for setting item to check for app updates
+
+
+ MSA 및 AAD에 로그인
+
+
+ 조직 계정을 사용하여 AAD에 로그인하세요.
+
+
+ Azure AD(AAD) 로그인
+
+
+ AAD
+
+
+ Microsoft Graph 및 기타 리소스 인증
+
+
+ Microsoft Graph만 인증
+
+
+ 취소
+
+
+ 조직 계정
+
+
+ 어떤 시점에서든 로그인 마법사가 멈추고 종료할 수 없으면 {0}초 기다려 주세요. 앱으로 돌아가야 합니다.
+
+
+ 로그인 중...
+
+
+ 로그아웃 중...
+
+
+ 여기에서 Microsoft 계정에 로그인하세요.
+
+
+ Microsoft 계정(MSA) 로그인
+
+
+ MSA
+
+
+ 인증
+
+
+ Microsoft 로그인
+
+
+ 로그인 실패 ({0})
+
+
+ 로그인 성공 ({0})
+
+
+ 로그인
+
+
+ 로그아웃됨: {0}
+
+
+ 로그아웃
+
+
+ 자동 재생
+ Music player page auto-play toggle text
+
+
+ 자동 크기 조정
+
+
+ 배터리 부족으로 업데이트가 실패했습니다.
+ App update error, low battery
+
+
+ {0}({1})과(와) 페어링하려는 중입니다.
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ {0}({1})과(와) 페어링 중입니다.
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ 장치에 표시된 PIN이 {0}과(와) 일치하나요?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ 알 수 없음
+ Text displayed when the Bluetooth device name is unknown
+
+
+ 현재 연결됨
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 연결 준비 완료
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 알 수 없는 상태
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 페어링할 장치에 다음 PIN을 입력하세요. {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ PIN 입력:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ {0}({1})의 인바운드 페어링 요청입니다.
+ Text displayed when an inbound pairing request is received
+
+
+ 이 장치는 인바운드 페어링에 대해 이미 등록되어 있습니다. (지원되는 양식: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ 인바운드 페어링에 대해 등록하지 못했습니다.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ 인바운드 페어링에 대해 등록했습니다. (지원되는 양식: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ 입력한 PIN이 잘못되었습니다.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ 이 장치에서 사용 가능한 Bluetooth 어댑터를 찾을 수 없습니다. \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ 연결
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ {0}({1})과(와) 페어링하지 못했습니다.
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ {0}({1})과(와) 페어링되었습니다.
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ 기본값
+ Text label for the corresponding device pairing protection level
+
+
+ 암호화 및 인증
+ Text label for the corresponding device pairing protection level
+
+
+ 암호화
+ Text label for the corresponding device pairing protection level
+
+
+ 없음
+ Text label for the corresponding device pairing protection level
+
+
+ 이제 장치를 검색할 수 있으며 다른 Bluetooth 장치와 페어링할 준비가 완료되었습니다.
+ Text displayed when StartWatcher is invoked
+
+
+ 장치가 더 이상 다른 Bluetooth 장치를 검색하고 있지 않습니다.
+ Text displayed when StopWatcher is invoked
+
+
+ 연결 해제
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ {0} ({1})에서 언페어링하지 못했습니다.
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ {0}({1})에서 연결을 해제했습니다.
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ 홈페이지
+
+
+ 웹 브라우저
+
+
+ 취소
+
+
+ 디렉터리 변경이 현재 지원되지 않습니다. 명령에 전체 경로를 사용하세요.
+
+
+ 표준 시간대
+ Time zone text
+
+
+ 업데이트 확인 중...
+ App update status
+
+
+ 업데이트 확인
+
+
+ 계정 지우기
+
+
+ 계정을 지우는 동안 문제가 발생했습니다.
+
+
+ 다음 Windows 계정이 지워집니다.
+{0}
+
+계속하시겠습니까?
+
+
+ 계정을 지웠습니다.
+
+
+ 계정을 지우는 중...
+
+
+ 지우기
+
+
+ 닫기
+
+
+ 장치에서 명령줄 프로세서를 실행할 수 없습니다.
+실행하도록 하려면 장치에 "관리자"로 다음 명령을 실행하세요.
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+IoT Windows 장치 포털의 프로세스 페이지에서 명령을 실행하거나 PowerShell을 사용하여 Windows IoT 장치에 연결할 수 있습니다.
+자세한 내용은 http://go.microsoft.com/fwlink/p/?LinkId=698488을 참조하세요.
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ 관리자 권한으로 명령을 실행하지 못함: {0}
+
+
+ 장치에서 명령줄 프로세서(cmd.exe)를 사용하도록 설정하지 못했습니다. {0}
+
+
+ 디바이스에서 명령줄 프로세서(cmd.exe)를 사용하도록 설정했습니다.
+
+
+ 타일 색
+
+
+ 뒤로
+ Back UI navigation
+
+
+ 장치 정보 표시
+
+
+ 앞으로
+ Forward UI navigation
+
+
+ 전체 화면 설정/해제
+
+
+ 복제 보기
+ Clone current view to another display
+
+
+ 로그 빠른 저장
+
+
+ 세션 로그
+
+
+ 기본 페이지 설정
+
+
+ 명령이 취소되었습니다.
+
+
+ 명령줄 입력
+ Placeholder for command line input text box
+
+
+ 명령줄 실행 오류: {0}
+
+
+ 명령줄
+
+
+ 명령줄
+ Title for command line page
+
+
+ 출력이 없이 {0}초가 지난 후 명령이 시간 초과되었습니다.
+
+
+ 컴퓨터 이름
+
+
+ 확인
+
+
+ 자동으로 연결
+
+
+ 자동으로 연결
+
+
+ 연결
+
+
+ 연결
+
+
+ 연결된 장치
+
+
+ 업데이트가 실패했습니다. Wi-Fi에 연결하고 다시 시도하세요.
+ App update error, poor connection
+
+
+ 계속
+
+
+ 명령 출력을 구문 분석할 수 없습니다.
+
+
+ 현재 링
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ 기본 앱 페이지
+
+
+ 기본 언어를 자동으로 선택하는 중...
+
+
+ 로그 {0}개 삭제됨
+ {0} is plural number of logs
+
+
+ 로그 {0}개 삭제됨
+ {0} is singular number of logs
+
+
+ 로그 {0}개를 삭제할까요?
+ {0} is singular number of logs
+
+
+ 로그 {0}개를 삭제할까요?
+ {0} is plural number of logs
+
+
+ 선택한 항목 삭제
+
+
+ Azure 장치 ID
+ Field label
+
+
+ Azure IoT Hub
+ Field label
+
+
+ 장치 페이지로 이동
+
+
+ IP 주소: {0}
+OS 버전: {1}
+앱 버전: {2}
+
+
+ 앱 버전
+ Field label
+
+
+ 장치 이름
+ Field label
+
+
+ IP 주소
+ Field label
+
+
+ 네트워크
+ Field label
+
+
+ OS 버전
+ Label for OS Version field in main page
+
+
+ 을 방문하세요.
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 장치 정보
+
+
+ 개발을 시작하려면
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 해당 페이지에 액세스하려면 Windows 장치 포털(WDP) API를 사용해야 합니다. 계속하려면 WDP 자격 증명을 사용하여 로그인하세요.
+
+
+ 로그인하는 중에 문제가 발생했습니다.
+
+
+ 장치 포털에 로그인했습니다!
+
+
+ 장치 포털 자격 증명을 확인하는 중...
+
+
+ 날씨 정보를 가져오는 동안 문제가 발생했습니다. 다시 시도할까요?
+
+
+ 직접 연결
+
+
+ 연결 끊기
+ This disconnects the connected network
+
+
+ 표시 언어 업데이트됨: {0}
+
+
+ 도메인
+
+
+ 다운로드 완료!
+ App update status
+
+
+ 다운로드하지 못했습니다. 나중에 다시 시도하세요.
+
+
+ 업데이트 다운로드 중
+ App update status
+
+
+ 다운로드 업데이트
+
+
+ 그리기
+
+
+ "로그 {0}개가 {1}(으)로 전송되었습니다."
+ {0} is plural number of logs, {1} is email address
+
+
+ "로그 {0}개가 {1}(으)로 전송되었습니다."
+ {0} is singular number of logs, {1} is email address
+
+
+ 로그 전자 메일로 보내기
+
+
+ {0}을(를) 자신에게 전자 메일로 보내시겠습니까?
+ {0} is filename
+
+
+ 로그를 전자 메일로 보내는 동안 문제가 발생했습니다. {0}
+ {0} is exception message
+
+
+ 로그는 로그 페이지에서 찾을 수 있습니다.
+
+
+ "로그 {0}개를 자신에게 전자 메일로 보내시겠습니까?"
+ {0} is singular number of logs
+
+
+ 로그를 전자 메일로 보내는 동안 문제가 발생했습니다. {0}
+ {0} is an exception message
+
+
+ 로그 {0}개를 자신에게 전자 메일로 보내시겠습니까?
+ {0} is plural number of logs
+
+
+ 로그 전자 메일로 보내기
+
+
+ 선택한 항목 전자 메일로 보내기
+
+
+ 명령줄 프로세서 사용
+
+
+ 화면 보호기
+ Toggle switch for enabling the screensaver
+
+
+ 종료 시간
+
+
+ 오류
+
+
+ 날씨 정보를 검색하는 동안 문제가 발생했습니다.
+
+
+ 이더넷
+ Field label
+
+
+ ETW 공급자 GUID: {0}
+ Format string for app settings page
+
+
+ DefaultAccount로 명령 실행 중
+
+
+ 탐색
+
+
+ 파일 저장됨: {0}
+ {0} is a filename
+
+
+ 플라이팅
+ Device servicing flighting
+
+
+ 플라이팅 정보
+ Device servicing flighting
+
+
+ 플라이트 링이 {0}(으)로 변경되었습니다!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ 플라이트 링을 변경하는 동안 문제가 발생했습니다.
+
+
+ 예측
+ Weather forecast
+
+
+ 전체 화면 모드로 전환하려고 합니다. 종료하려면 키보드의 [Esc]를 눌러야 합니다. 계속하시겠습니까?
+
+
+ 전체 화면 모드
+
+
+ 전체 화면 모드를 끝내려면 [Esc]를 누르세요.
+
+
+ 일반
+
+
+ IoTEnterprise Board
+ A generic board name
+
+
+ GitHub
+
+
+ 도움말
+
+
+ 도움말
+
+
+ 도움말
+
+
+ 입력 키보드 언어 업데이트됨: {0}
+
+
+ 설치 완료!
+ App update status
+
+
+ 설치하지 못했습니다. 나중에 다시 시도하세요.
+
+
+ 업데이트 설치 중
+ App update status
+
+
+ 업데이트 설치
+
+
+ 잘못된 자격 증명
+
+
+ '{0}'은(는) 잘못된 위치입니다.
+ Format string for app settings page
+
+
+ '{0}'은(는) 잘못된 값입니다. 값은 1보다 크거나 같아야 합니다.
+ Format string for app settings page
+
+
+ '{0}'은(는) 잘못된 값입니다.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ 키보드 레이아웃
+ Field label
+
+
+ 새 설정을 적용하려면 이 앱을 다시 시작하세요.
+
+
+ 언어
+
+
+ 언어
+ Field label
+
+
+ 로드 중...
+
+
+ 날씨 정보를 불러오는 중...
+
+
+ 로그가 {0}(으)로 전송되었습니다.
+ {0} is email address
+
+
+ 로그가 {0}에 저장됨
+ {0} is filename
+
+
+ 로그
+
+
+ 로그
+
+
+ 장치 이름
+ Field label
+
+
+ IP 주소
+ Field label
+
+
+ OS 버전
+ Label for OS Version field in main page
+
+
+ 프로토타입만을 위해로 설계된 Windows 10 IoT Enterprise 테스트 이미지입니다. 장치를 상업용으로 사용하려면 장치의 보안을 최적화하기 위해 맞춤형 FFU를 사용해야 합니다.
+ Maker Imager Security Notice
+
+
+ Bing 지도 서비스 토큰
+
+
+ Bing 지도 서비스 토큰 필요
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Microsoft 계정(MSA)
+
+
+ 현재 재생 중
+ Music player page status text (currently playing)
+
+
+ 노래를 선택하고 [재생]을 클릭하세요.
+ Music player page status text (default)
+
+
+ 하나 이상의 오디오 파일을 음악 폴더에 추가하세요.
+앱 > 파일 탐색기를 사용하여 Windows 장치 포털에서 음악을 추가할 수 있습니다.
+ Music player page instructions text
+
+
+ 음악 불러오는 중
+ Music player page loading panel text
+
+
+ 불러오는 중
+ Music player page status text (loading)
+
+
+ 음악을 찾을 수 없음
+ Music player page no music found prompt text
+
+
+ 다시 시도
+ Music player page reload button text (no files prompt)
+
+
+ 음악
+
+
+ 음악
+
+
+ 일시 중지됨
+ Music player page status text (paused)
+
+
+ 재생 중
+ Music player page status text (playing)
+
+
+ 로그인
+
+
+ 알 수 없음
+
+
+ 메뉴
+
+
+ 네트워크 어댑터
+
+
+ 연결됨
+
+
+ 연결됨
+
+
+ 네트워크 요구 사항 확인 중
+
+
+ 네트워크 요구 사항 확인 중
+
+
+ 제한된 인터넷 액세스
+
+
+ 로컬 및 인터넷 액세스
+
+
+ 로컬 네트워크 액세스 전용
+
+
+ 연결되지 않음
+
+
+ 네트워크 정보
+
+
+ 네트워크를 사용할 수 없음
+
+
+ 네트워크 보안 키 입력
+
+
+ 네트워크 보안 키 입력
+
+
+ 네트워크 및 Wi-Fi
+
+
+ 네트워크 및 Wi-Fi
+
+
+ 네트워크 속성 보기
+
+
+ 네트워크 속성
+
+
+ 이 Wi-fi 네트워크의 종속 포털로 리디렉션됩니다. 계속하시겠습니까?
+
+
+ 네트워크 리디렉션
+
+
+ 다음
+
+
+ 다음
+
+
+ 계정을 찾을 수 없음
+
+
+ 아니요
+
+
+ 디바이스 이름 없음
+
+
+ 인터넷 연결 없음
+
+
+ 선택한 로그가 없습니다.
+
+
+ 음악을 찾을 수 없음
+ Music player page panel text
+
+
+ 없음
+
+
+ 다운로드 보류 중인 업데이트가 없습니다.
+ App update status
+
+
+ 설치 보류 중인 업데이트가 없습니다.
+ App update status
+
+
+ 해당 없음
+
+
+ 알림
+
+
+ 알림
+
+
+ 새로운 업데이트가 없습니다.
+ Format string displayed when no app updates are found
+
+
+ 확인
+ Button content text for the Bluetooth settings page
+
+
+ 언어 선택
+
+
+ 연결하기
+
+
+ Windows 10 IoT Enterprise 시작
+
+
+ 시작하기
+
+
+ Windows 10 IoT Enterprise 시작
+
+
+ OS 버전 ID
+
+
+ OS 버전
+
+
+ OS 정보
+
+
+ OS 정보
+
+
+ 사용할 수 없음
+ Text shown when we cannot retrieve the OS Version
+
+
+ OS 버전
+
+
+ 패키지
+ Software packages
+
+
+ 설치된 패키지
+ Software packages
+
+
+ 페이지 설정
+
+
+ 페이지
+
+
+ 비밀번호
+
+
+ 사진을 불러오는 중
+ Default text when no images are available
+
+
+ 하나 이상의 이미지를 사진 폴더에 추가하세요.
+앱 > 파일 탐색기를 사용하여 Windows 장치 포털에서 이미지를 추가할 수 있습니다.
+
+
+ 이미지를 찾을 수 없음
+ Default text when no images are available
+
+
+ 플랫폼
+
+
+ 재생
+
+
+ 전원 옵션
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ 기본: 장치에 대한 정보, 장치의 설정 및 기능, 장치가 제대로 수행되는지 여부만 보냅니다.
+
+
+ 전체: 모든 기본 진단 데이터를 사용자가 탐색하는 웹 사이트에 대한 정보, 앱 및 기능을 사용하는 방법과 함께 장치 상태, 장치 활동 및 향상된 오류 보고에 대한 추가 정보를 포함하여 보냅니다.
+
+
+ 개인 정보 설정을 변경할 수 없습니다. 사용자 이름과 비밀번호를 확인하고 다시 시도하세요.
+
+
+ Microsoft에 진단 데이터를 얼마나 보낼지 선택합니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 선택하는 옵션에 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
+
+
+ 진단 데이터
+ Label for Setting item to control Privacy
+
+
+ 이 장치의 개인 정보 수준을 설정하려면 자격 증명을 입력하세요.
+
+
+ 개인 정보 수준 설정
+
+
+ 새로 고침
+ Refresh button
+
+
+ 노래 반복
+ Music player page repeat toggle text
+
+
+ 다시 시작
+
+
+ 다시 시작
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ 사용법: RunAsAdmin 명령
+
+예:
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ 저장
+
+
+ 배율 인수
+
+
+ 모두 선택
+
+
+ 원격 분석 보내기
+
+
+ 사용할 수 없음
+
+
+ 세션 로그
+
+
+ 기본 페이지를 {0}(으)로 설정하는 중에 문제가 발생했습니다.
+ Format string for app settings page
+
+
+ 설정
+
+
+ 무작위 재생
+ Music player page shuffle toggle text
+
+
+ 종료
+
+
+ 종료
+ Shutdown entry in the shutdown menu
+
+
+ 이 기능을 사용하려면 Azure AD 계정에 로그인하세요.
+
+
+ 건너뛰기
+
+
+ 이 단계 건너뛰기
+
+
+ 슬라이드 쇼 간격(초)
+
+
+ 슬라이드 쇼
+
+
+ 슬라이드 쇼
+
+
+ 시작
+
+
+ 시작
+
+
+ 시작 시간
+
+
+ 상태
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ 제출
+
+
+ 성공
+
+
+ 시스템
+
+
+ 시스템 설정을 업데이트하는 동안 문제가 발생했습니다.
+ Used within system settings
+
+
+ 원격 분석 수준
+
+
+ 원격 분석
+
+
+ 점보 알림 테스트
+
+
+ 테스트 알림
+
+
+ Windows 10 IoT는 사물 인터넷에 엔터프라이즈 수준의 강력한 기능, 보안 및 관리 기능을 제공하는 Windows 10 제품군입니다. Windows의 내장된 환경, 생태계 및 클라우드 연결을 활용하기 때문에 조직에서는 신속하게 프로비저닝하고 쉽게 관리할 수 있으며 전체 클라우드 전략에 원활하게 연결할 수 있는 보안 장치를 사용하여 사물 인터넷을 만들 수 있습니다.
+
+
+ 타일 높이
+
+
+ 개인 설정
+
+
+ 타일 너비
+
+
+ 연결 시간 초과
+
+
+ 표준 시간대 업데이트됨: {0}
+
+
+ 오류: 날씨 서비스와 통신할 수 없습니다.
+
+
+ 알 수 없는 오류로 인해 업데이트가 실패했습니다.
+ App update error, unknown
+
+
+ 모두 선택 취소
+
+
+ 미지정된 오류
+
+
+ 고급 옵션
+
+
+ 지금 확인
+
+
+ 지금 설치
+
+
+ 보류 중인 업데이트 {0}개
+ {0} is singular amount of updates
+
+
+ {0}개의 새 업데이트가 있습니다.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ 보류 중인 업데이트 {0}개
+ {0} is plural amount of updates
+
+
+ MDL2 타일 아이콘 사용
+
+
+ 암호 사용
+
+
+ 사용자 이름
+
+
+ Windows 장치 포털
+
+
+ 장치 포털 설정
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows 장치 포털
+
+
+ 현재 위치({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ 사용자의 위치
+
+
+ 사용자의 위치
+ Label for map pin
+
+
+ 알 수 없는 위치
+ Label for map pin
+
+
+ 센서:
+ Label for temperature sensor output
+
+
+ 날씨
+
+
+ 날씨 페이지를 로드하는 중 오류가 발생했습니다.
+
+이 페이지를 다시 로드하려면 화면 오른쪽 하단에 있는 새로 고침 버튼을 클릭하세요.
+
+날씨 API 키가 없는 경우 weatherunlocked.com으로 이동하세요. 이 앱의 로컬 상태 폴더에 있는 "WeatherTokens.config"에 키를 저장한 다음 페이지를 새로 고치세요.
+
+
+ 날씨 제공:
+
+
+ 날씨
+
+
+ 웹 주소 입력
+
+
+ 웹 브라우저
+
+
+ Windows IoT Enterprise 시작
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ 새로 고침
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 마지막으로 확인한 날짜:
+ For a timestamp
+
+
+ 마지막으로 업데이트한 날짜
+ For a timestamp
+
+
+ 업데이트된 상태:
+
+
+ 상태 메시지:
+
+
+ Windows 업데이트
+
+
+ Windows 업데이트
+
+
+ 잘못된 작업 디렉토리: {0}
+
+
+ WPS
+
+
+ 이 앱에서 위치에 액세스하도록 허용
+
+
+ 설정을 선택한 다음 '수락'을 선택하여 설정을 저장하세요. 이 설정은 언제든지 변경할 수 있습니다.
+
+
+ Microsoft에서 위치를 사용하도록 허용
+
+
+ 자동으로 계속하는 중...
+
+
+ 수락
+
+
+ {0}의 정확한 위치 액세스를 허용할까요?
+ {0} is the name of a page
+
+
+ 위치
+
+
+ 나중에 변경하려면 설정> 권한으로 이동하세요.
+
+
+ 아니요
+
+
+ 예
+
+
+ 지도와 날씨 같은 위치 기반 서비스를 경험하거나 사용자의 위치 정보가 필요한 다른 서비스를 즐길 수 없습니다.
+
+
+ 지도 및 날씨 같은 위치 기반 서비스를 경험해 보세요. 이 앱에서 위치를 요청하도록 허용하세요. Microsoft에서 위치 데이터를 사용하여 위치 서비스를 개선합니다.
+
+
+ 장치에 대한 정보, 장치의 설정 및 기능, 장치가 제대로 수행되는지 여부만 보냅니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 기본 또는 전체 중 어떤 것을 선택하든 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
+
+
+ 기본
+
+
+ 모든 기본 진단 데이터를 사용자가 탐색하는 웹 사이트에 대한 정보, 앱 및 기능을 사용하는 방법과 함께 장치 상태, 장치 활동 및 향상된 오류 보고에 대한 추가 정보를 포함하여 보냅니다. 진단 데이터는 Windows를 안전한 최신 상태로 유지하고 문제를 해결하며 제품을 향상시키는 데 사용됩니다. 기본 또는 전체 중 어떤 것을 선택하든 관계없이 장치는 동일하게 안전하며 정상적으로 작동할 것입니다.
+
+
+ 전체
+
+
+ 장치에 대한 개인 정보 설정을 선택한 다음 '동의'를 선택하여 저장하세요.
+
+
+ 진단 데이터를 Microsoft에 보내기
+
+
+ 진단
+
+
+ 액세스를 허용하면 이 앱에서 장치의 기능을 사용하여 위치를 파악할 수 있으며 Microsoft에서는 위치 데이터를 사용하여 위치 서비스를 개선합니다. 액세스를 거부하면 Windows가 이 앱에 위치 정보를 제공하는 것을 차단합니다.
+
+
+ 개인 정보 옵션 알아보기
+
+
+ 이 설정이 개인 정보에 어떤 영향을 주는지 알아보세요.
+
+
+ 이 설정에 대한 자세한 정보 보기
+
+
+ 개인정보처리방침
+
+
+ 예
+
+
+ 예
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/pt-BR/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/pt-BR/Resources.resw
index e7ac492c5..519f27a6f 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/pt-BR/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/pt-BR/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Usar AAD v2
-
-
- Acesso Revogado
-
-
- Descrição:
-
-
- Servidor DHCP:
-
-
- DNS:
-
-
- Endereço do Gateway:
-
-
- Endereço IPv4:
-
-
- Nome:
-
-
- Endereço Físico:
-
-
- Máscara de Sub-rede:
-
-
- Tipo:
-
-
- Versão do App
-
-
- Apps
-
-
- Você está prestes a iniciar um app externo. Você precisará usar o Portal de Dispositivos do Windows para voltar ao app. Continuar?
- Dialog prompt for launching external apps
-
-
- Apps
-
-
- Configurações de App
-
-
- Defina o horário ativo para nos informar quando você normalmente usa este dispositivo. Nós não o reiniciaremos automaticamente durante o horário ativo.
-
-
- Não é possível salvar os novos horários inicial e final, pois eles são iguais. Escolha outros horários ou desative o recurso.
-
-
- Opções Avançadas
- Advanced section title
-
-
- Controle cada uma das etapas de atualização de Busca, Download e Instalação.
-
-
- Opções de Atualização Automática
- Auto-Update section title
-
-
- Permitir que o aplicativo instale as atualizações de app fora do horário ativo
-
-
- Atualizações de App
- App update display dialog header
-
-
- Última verificação: {0}, {1}
- {0} is date, {1} is time
-
-
- Não é possível determinar a última verificação de atualizações
-
-
- Atualizações de App
- Label for setting item to check for app updates
-
-
- Entrar no MSA e no AAD
-
-
- Entre no AAD usando a conta da sua organização.
-
-
- Credenciais do Azure AD (AAD)
-
-
- AAD
-
-
- Autentica o Microsoft Graph e outros recursos
-
-
- Autentica somente o Microsoft Graph
-
-
- Cancelar
-
-
- Conta da sua organização
-
-
- Caso não consiga prosseguir nem sair do assistente de entrada, aguarde {0} segundos e você deverá retornar ao app.
-
-
- Entrando
-
-
- Saindo
-
-
- Entre com sua Conta Microsoft aqui
-
-
- Credenciais da MSA (Conta Microsoft)
-
-
- MSA
-
-
- Autenticação
-
-
- Credenciais da Microsoft
-
-
- Falha ao entrar ({0})
-
-
- Entrada bem-sucedida ({0})
-
-
- Entrar
-
-
- Saída: {0}
-
-
- Sair
-
-
- Reprodução Automática
- Music player page auto-play toggle text
-
-
- Dimensionamento Automático
-
-
- Ocorreu falha na atualização devido à bateria fraca.
- App update error, low battery
-
-
- Tentando emparelhar com {0} ({1}).
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Emparelhando com {0} ({1}).
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- O PIN mostrado no dispositivo corresponde a: {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Desconhecido
- Text displayed when the Bluetooth device name is unknown
-
-
- Atualmente emparelhado
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Pronto para emparelhar
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Estado desconhecido
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Digite o seguinte PIN no dispositivo que você deseja emparelhar: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Digite o PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Solicitação de emparelhamento de entrada de {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Este dispositivo está registrado para emparelhamento de entrada. (Cerimônias com suporte: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Falha ao registrar emparelhamento de entrada.
- Text displayed when Inbound pairing handler registration fails
-
-
- Emparelhamento de entrada registrado com êxito. (Cerimônias com suporte: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- O PIN inserido está incorreto.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- Nenhum adaptador Bluetooth utilizável encontrado neste dispositivo: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Emparelhar
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Falha ao emparelhar com {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Emparelhado com êxito com {0} ({1}).
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- Padrão
- Text label for the corresponding device pairing protection level
-
-
- Criptografia e autenticação
- Text label for the corresponding device pairing protection level
-
-
- Criptografia
- Text label for the corresponding device pairing protection level
-
-
- Nenhum
- Text label for the corresponding device pairing protection level
-
-
- Agora seu dispositivo é detectável e pronto para emparelhar com outros dispositivos Bluetooth.
- Text displayed when StartWatcher is invoked
-
-
- Seu dispositivo não está mais procurando outros dispositivos Bluetooth.
- Text displayed when StopWatcher is invoked
-
-
- Desemparelhar
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Falha ao desemparelhar de {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Desemparelhado com êxito de {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Home Page
-
-
- Navegador da Web
-
-
- Cancelar
-
-
- Não há suporte para alteração de diretório no momento. Use caminhos completos em seus comandos.
-
-
- Fuso horário
- Time zone text
-
-
- Verificando atualizações...
- App update status
-
-
- Verificar se há atualizações
-
-
- Limpar Contas
-
-
- Ocorreu um problema ao limpar as contas
-
-
- Isso limpará as seguintes contas do Windows:
-{0}
-
-Continuar?
-
-
- As contas foram limpas
-
-
- Limpando contas...
-
-
- Limpar
-
-
- Fechar
-
-
- O dispositivo não tem permissão para executar o processador de linha de comando.
-Para habilitá-lo, execute o seguinte comando como "Administrador" no dispositivo:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Você pode executar o comando na página Processos do Portal de Dispositivos do Windows IoT ou usar o PowerShell para conectar o dispositivo Windows IoT.
-Para obter mais informações, acesse http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Falha ao executar o comando como Administrador: {0}
-
-
- Falha ao habilitar o Processador de Linha de Comando (cmd.exe) no dispositivo: {0}
-
-
- O Processador de Linha de Comando (cmd.exe) foi habilitado com êxito o no seu dispositivo.
-
-
- Cor do Bloco
-
-
- Voltar
- Back UI navigation
-
-
- Mostrar Informações do Dispositivo
-
-
- Avançar
- Forward UI navigation
-
-
- Ativar/Desativar Tela Inteira
-
-
- Visualização do Clone
- Clone current view to another display
-
-
- Log de Salvamento Rápido
-
-
- Log da Sessão
-
-
- Definir Página Padrão
-
-
- Comando cancelado.
-
-
- Digitar a linha de comando
- Placeholder for command line input text box
-
-
- Erro ao executar a linha de comando: {0}
-
-
- Linha de Comando
-
-
- Linha de comando
- Title for command line page
-
-
- O tempo de espera do comando expirou após {0} segundos sem produzir saída.
-
-
- Nome do Computador
-
-
- Confirmação
-
-
- Conectar automaticamente
-
-
- Conectar automaticamente
-
-
- Conectar
-
-
- Conectar
-
-
- Dispositivos Conectados
-
-
- Falha na atualização. Conecte-se à rede Wi-Fi e tente novamente.
- App update error, poor connection
-
-
- Continuar
-
-
- Não foi possível analisar a saída do comando
-
-
- Anel Atual
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Página de App Padrão
-
-
- Estamos escolhendo o idioma padrão automaticamente...
-
-
- {0} logs excluídos
- {0} is plural number of logs
-
-
- {0} log excluído
- {0} is singular number of logs
-
-
- Excluir {0} log?
- {0} is singular number of logs
-
-
- Excluir {0} logs?
- {0} is plural number of logs
-
-
- Excluir Seleção
-
-
- ID do Dispositivo Azure
- Field label
-
-
- Hub do Azure IoT
- Field label
-
-
- Ir para a Página do Dispositivo
-
-
- Endereço IP: {0}
-Versão do SO: {1}
-Versão do App: {2}
-
-
- Versão do App
- Field label
-
-
- Nome do Dispositivo
- Field label
-
-
- Endereço IP
- Field label
-
-
- Rede
- Field label
-
-
- Versão do sistema operacional
- Label for OS Version field in main page
-
-
- para começar a desenvolver
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Informações do Dispositivo
-
-
- Visite
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- A página que você está tentando acessar requer o uso das APIs do WDP (Portal de Dispositivos do Windows). Entre usando as credenciais do WDP para continuar.
-
-
- Ocorreu um problema ao entrar no serviço.
-
-
- A entrada no Portal de Dispositivos foi bem-sucedida.
-
-
- Verificando as Credenciais do Portal de Dispositivos...
-
-
- Ocorreu um problema ao obter o clima. Tentar novamente?
-
-
- Conexões diretas
-
-
- Desconectar
- This disconnects the connected network
-
-
- Idioma de exibição atualizado: {0}
-
-
- Domínio
-
-
- Download Concluído.
- App update status
-
-
- Falha no download. Tente mais tarde.
-
-
- Baixando Atualização
- App update status
-
-
- Baixar atualizações
-
-
- Desenhar
-
-
- "{0} logs enviado para {1}"
- {0} is plural number of logs, {1} is email address
-
-
- "{0} log enviado para {1}"
- {0} is singular number of logs, {1} is email address
-
-
- Enviar Log por Email
-
-
- Você gostaria de enviar {0} por email para si mesmo?
- {0} is filename
-
-
- Ocorreu um problema para enviar seu log por email: {0}
- {0} is exception message
-
-
- Você pode encontrar seus logs na página Logs
-
-
- "Enviar {0} log por email para si mesmo?"
- {0} is singular number of logs
-
-
- Ocorreu um problema para enviar seus logs por email: {0}
- {0} is an exception message
-
-
- Enviar por email os {0} logs para você mesmo?
- {0} is plural number of logs
-
-
- Enviar Logs por Email
-
-
- Enviar Seleção por Email
-
-
- Habilitar o Processador de Linha de Comando
-
-
- Proteção de Tela
- Toggle switch for enabling the screensaver
-
-
- Hora de término
-
-
- Erro
-
-
- Ocorreu um problema ao recuperar informações sobre o clima
-
-
- Ethernet
- Field label
-
-
- GUID do Provedor do ETW: {0}
- Format string for app settings page
-
-
- Executando comandos como DefaultAccount
-
-
- Explorar
-
-
- Arquivo salvo: {0}
- {0} is a filename
-
-
- Liberação de versões de pré-lançamento
- Device servicing flighting
-
-
- Informações de liberação de versões de pré-lançamento
- Device servicing flighting
-
-
- Anel de Versão de Pré-lançamento foi alterado para {0}!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- Ocorreu um problema ao alterar seu anel de versão de pré-lançamento
-
-
- Previsão
- Weather forecast
-
-
- Você está prestes a entrar no modo de tela inteira. Para sair, você deve pressionar [Esc] no teclado. Continuar?
-
-
- Modo de Tela Inteira
-
-
- Pressione [Esc] para sair do modo de tela inteira.
-
-
- Geral
-
-
- Placa do IoTEnterprise
- A generic board name
-
-
- GitHub
-
-
- Ajuda
-
-
- Ajuda
-
-
- Ajuda
-
-
- Idioma do teclado de entrada atualizado: {0}
-
-
- Instalação concluída.
- App update status
-
-
- Falha na instalação. Tente mais tarde.
-
-
- Instalando Atualização
- App update status
-
-
- Instalar atualizações
-
-
- Credencial Inválida
-
-
- '{0}' é um local inválido.
- Format string for app settings page
-
-
- '{0}' é um valor inválido. O valor deve ser maior ou igual a 1.
- Format string for app settings page
-
-
- '{0}' é um valor inválido.
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Layout do teclado
- Field label
-
-
- Reiniciar este app para aplicar as novas alterações
-
-
- Idioma
-
-
- Idioma
- Field label
-
-
- Carregando...
-
-
- Carregando informações do clima...
-
-
- O log foi enviado para {0}
- {0} is email address
-
-
- Log salvo em: {0}
- {0} is filename
-
-
- Logs
-
-
- Logs
-
-
- Nome do Dispositivo
- Field label
-
-
- Endereço IP
- Field label
-
-
- Versão do Sistema Operacional
- Label for OS Version field in main page
-
-
- Esta é uma imagem de teste do Windows 10 IoT Enterprise destinada a protótipos. Se você estiver pensando em comercializar seu dispositivo, use um FFU personalizado para otimizar a segurança.
- Maker Imager Security Notice
-
-
- Token de Serviço do Bing Mapas
-
-
- Token de Serviço do Bing Mapas Obrigatório
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- MSA (Conta Microsoft)
-
-
- Reproduzindo no momento
- Music player page status text (currently playing)
-
-
- Selecione uma música e clique em Reproduzir.
- Music player page status text (default)
-
-
- Adicione um ou mais arquivos de áudio à pasta Música.
-Adicione as músicas no Portal de Dispositivos do Windows usando Apps > Explorador de Arquivos.
- Music player page instructions text
-
-
- Carregando Música
- Music player page loading panel text
-
-
- Carregando
- Music player page status text (loading)
-
-
- Nenhuma música encontrada
- Music player page no music found prompt text
-
-
- Tentar Novamente
- Music player page reload button text (no files prompt)
-
-
- Música
-
-
- Música
-
-
- Em Pausa
- Music player page status text (paused)
-
-
- Reproduzindo
- Music player page status text (playing)
-
-
- Entrar
-
-
- Desconhecido
-
-
- Menu
-
-
- Adaptadores de Rede
-
-
- Conectado
-
-
- Conectado
-
-
- Verificando requisitos de rede
-
-
- Verificando requisitos de rede
-
-
- Acesso à Internet limitado
-
-
- Acesso local e à Internet
-
-
- Acesso à rede local somente
-
-
- Sem conectividade
-
-
- INFORMAÇÕES DA REDE
-
-
- Rede Não Disponível
-
-
- Digitar a chave de segurança da rede
-
-
- Digite a chave de segurança da rede
-
-
- Rede e Wi-Fi
-
-
- Rede e Wi-Fi
-
-
- Exibir as propriedades da rede
-
-
- Propriedades da Rede
-
-
- Você está prestes a ser redirecionado para o portal cativo da rede Wi-Fi. Continuar?
-
-
- Redirecionamento de Rede
-
-
- Avançar
-
-
- Avançar
-
-
- Nenhuma conta encontrada
-
-
- Não
-
-
- nenhum nome de dispositivo
-
-
- sem conexão com a Internet
-
-
- Nenhum log selecionado
-
-
- Nenhuma música encontrada
- Music player page panel text
-
-
- Nenhum localizado
-
-
- Não há nenhuma atualização pendente para download.
- App update status
-
-
- Não há nenhuma atualização pendente para instalar.
- App update status
-
-
- N/D
-
-
- Notificações
-
-
- Notificações
-
-
- Nenhuma nova atualização encontrada.
- Format string displayed when no app updates are found
-
-
- OK
- Button content text for the Bluetooth settings page
-
-
- Escolha seu idioma
-
-
- Vamos nos conectar
-
-
- Bem-vindo ao Windows 10 IoT Enterprise
-
-
- Vamos resolver algumas etapas básicas.
-
-
- Bem-vindo ao Windows 10 IoT Enterprise
-
-
- ID da Edição do Sistema Operacional
-
-
- Edição do Sistema Operacional
-
-
- Informações do SO
-
-
- Informações do SO
-
-
- Não Disponível
- Text shown when we cannot retrieve the OS Version
-
-
- Versão do Sistema Operacional
-
-
- Pacotes
- Software packages
-
-
- Pacotes Instalados
- Software packages
-
-
- Configurações da Página
-
-
- Páginas
-
-
- Senha
-
-
- Carregando Imagens
- Default text when no images are available
-
-
- Adicione imagens à pasta Imagens.
-Adicione as imagens no Portal de Dispositivos do Windows usando Apps > Explorador de Arquivos.
-
-
- Nenhuma imagem encontrada
- Default text when no images are available
-
-
- Plataforma
-
-
- Executar
-
-
- Opções de Energia
- Label for Setting item to control Power (shutdown/restart)
-
-
- Básico: Envie apenas informações sobre seu dispositivo, as configurações e funcionalidades dele, e se ele está funcionando corretamente.
-
-
- Completo: Envie todos os dados do diagnóstico Básico juntamente com informações sobre os sites em que você navega e como você usa apps e recursos, mais informações adicionais sobre a integridade do dispositivo, a atividade do dispositivo e um relatório avançado de erros.
-
-
- Não foi possível alterar a configuração de privacidade. Verifique seu nome de usuário e a senha e tente novamente.
-
-
- Escolha a quantidade de dados de diagnóstico que deseja enviar para a Microsoft. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente da opção selecionada, o dispositivo será igualmente seguro e funcionará normalmente.
-
-
- Dados de Diagnóstico
- Label for Setting item to control Privacy
-
-
- Digite as credenciais para definir o nível de privacidade neste dispositivo.
-
-
- Definir seu nível de privacidade
-
-
- Atualizar
- Refresh button
-
-
- Repetir a Música
- Music player page repeat toggle text
-
-
- Reiniciar
-
-
- Reiniciar
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Uso: comando RunAsAdmin
-
-Exemplos:
-> RunAsdmin TZUTIL /s "Horário Padrão do Pacífico"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Salvar
-
-
- Fator de Escala
-
-
- Selecionar Tudo
-
-
- Enviar Telemetria
-
-
- Não disponível
-
-
- Log da Sessão
-
-
- Ocorreu um problema ao configurar a página padrão como {0}.
- Format string for app settings page
-
-
- Configurações
-
-
- Ordem Aleatória
- Music player page shuffle toggle text
-
-
- Desligar
-
-
- Desligar
- Shutdown entry in the shutdown menu
-
-
- Entre com a conta do Azure AD para usar este recurso.
-
-
- Ignorar
-
-
- Ignorar esta etapa
-
-
- Intervalo da Apresentação de Slides (segundos)
-
-
- Apresentação de Slides
-
-
- Apresentação de Slides
-
-
- Iniciar
-
-
- Iniciar
-
-
- Hora de início
-
-
- Status
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Enviar
-
-
- Êxito
-
-
- Sistema
-
-
- Ocorreu um problema ao tentar atualizar as configurações do sistema.
- Used within system settings
-
-
- Nível de Telemetria
-
-
- Telemetria
-
-
- Testar Notificação Jumbo
-
-
- Testar Notificação
-
-
- O Windows 10 IoT é membro da família Windows 10 que oferece capacidade, segurança e gerenciamento de classe empresarial para a Internet das Coisas. Ele utiliza o ecossistema integrado do Windows e a conectividade na nuvem, permitindo que as organizações criem a própria Internet das Coisas com dispositivos seguros que possam ser rapidamente provisionados, facilmente gerenciados e conectados diretamente a uma estratégia geral de nuvem.
-
-
- Altura Bloco
-
-
- Personalização
-
-
- Largura do Bloco
-
-
- Tempo Limite de Conexão Atingido
-
-
- Fuso horário atualizado: {0}
-
-
- Erro: Não é possível comunicar-se com o serviço do clima
-
-
- Ocorreu uma falha por motivo desconhecido.
- App update error, unknown
-
-
- Desmarcar Tudo
-
-
- Falha Não Especificada
-
-
- Opções Avançadas
-
-
- Verificar Agora
-
-
- Instalar Agora
-
-
- {0} atualização pendente
- {0} is singular amount of updates
-
-
- {0} novas atualizações encontradas.
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} atualizações pendentes
- {0} is plural amount of updates
-
-
- Usar Ícones de Bloco MDL2
-
-
- Usar senha
-
-
- Nome de Usuário
-
-
- Portal de Dispositivos do Windows
-
-
- Configurações do Portal de Dispositivos
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Portal de Dispositivos do Windows
-
-
- Localização Atual ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Seu Local
-
-
- Seu Local
- Label for map pin
-
-
- Local Desconhecido
- Label for map pin
-
-
- Sensor:
- Label for temperature sensor output
-
-
- Clima
-
-
- Erro ao carregar a página Clima.
-
-Clique no botão Atualizar no canto inferior direito da tela para recarregar esta página.
-
-Se você não tiver chaves da API Clima, navegue até weatherunlocked.com. Salve as chaves em "WeatherTokens.config" na pasta Estado Local deste App. Depois, atualize a página.
-
-
- Dados de clima fornecidos por:
-
-
- Clima
-
-
- Digite um endereço web
-
-
- Navegador da Web
-
-
- Bem-vindo ao Windows IoT Enterprise
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Atualizar
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Última Verificação:
- For a timestamp
-
-
- Última Atualização:
- For a timestamp
-
-
- Estado Atualizado:
-
-
- Mensagem de Status:
-
-
- Windows Update
-
-
- Windows Update
-
-
- Diretório de trabalho inválido: {0}
-
-
- WPS
-
-
- Permitir que este app acesse sua localização
-
-
- Escolha as configurações e selecione 'Aceitar' para salvá-las. Você pode alterar essas configurações a qualquer momento.
-
-
- Permitir que a Microsoft use sua localização
-
-
- Continuando automaticamente...
-
-
- Aceitar
-
-
- Permitir que {0} acesse sua localização precisa?
- {0} is the name of a page
-
-
- Localização
-
-
- Para mudar isso depois, vá para Configurações > Permissões.
-
-
- Não
-
-
- Sim
-
-
- Você não poderá obter experiências baseadas em localização, como mapas e previsão do tempo, nem usar outros serviços que precisam de sua localização para funcionar.
-
-
- Obtenha experiências baseadas na localização, como mapas e clima. Permita que este app solicite sua localização. A Microsoft usará seus dados de localização para melhorar os serviços de localização.
-
-
- Envie apenas informações sobre seu dispositivo, as configurações e funcionalidades dele, e se ele está funcionando corretamente. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente de você selecionar Básico ou Completo, seu dispositivo será igualmente seguro e funcionará normalmente.
-
-
- Básico
-
-
- Envie todos os dados do diagnóstico Básico juntamente com informações sobre os sites em que você navega e como você usa apps e recursos, mais informações adicionais sobre a integridade do dispositivo, a atividade do dispositivo e um relatório avançado de erros. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente de você selecionar Básico ou Completo, seu dispositivo será igualmente seguro e funcionará normalmente.
-
-
- Completo
-
-
- Escolha a configuração de privacidade para o dispositivo e selecione 'Aceitar' para salvá-la.
-
-
- Enviar dados de diagnóstico para a Microsoft
-
-
- Diagnóstico
-
-
- Se você permitir o acesso, permitirá que este app use os recursos do dispositivo para determinar sua localização, e a Microsoft usará seus dados de localização para melhorar os serviços de localização. Negar o acesso impede que o Windows forneça a localização a este app.
-
-
- Conheça as opções de privacidade
-
-
- Saiba como esta configuração afeta sua privacidade.
-
-
- Obter mais informações sobre estas configurações
-
-
- Política de privacidade
-
-
- Sim
-
-
- Sim
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Usar AAD v2
+
+
+ Acesso Revogado
+
+
+ Descrição:
+
+
+ Servidor DHCP:
+
+
+ DNS:
+
+
+ Endereço do Gateway:
+
+
+ Endereço IPv4:
+
+
+ Nome:
+
+
+ Endereço Físico:
+
+
+ Máscara de Sub-rede:
+
+
+ Tipo:
+
+
+ Versão do App
+
+
+ Apps
+
+
+ Você está prestes a iniciar um app externo. Você precisará usar o Portal de Dispositivos do Windows para voltar ao app. Continuar?
+ Dialog prompt for launching external apps
+
+
+ Apps
+
+
+ Configurações de App
+
+
+ Defina o horário ativo para nos informar quando você normalmente usa este dispositivo. Nós não o reiniciaremos automaticamente durante o horário ativo.
+
+
+ Não é possível salvar os novos horários inicial e final, pois eles são iguais. Escolha outros horários ou desative o recurso.
+
+
+ Opções Avançadas
+ Advanced section title
+
+
+ Controle cada uma das etapas de atualização de Busca, Download e Instalação.
+
+
+ Opções de Atualização Automática
+ Auto-Update section title
+
+
+ Permitir que o aplicativo instale as atualizações de app fora do horário ativo
+
+
+ Atualizações de App
+ App update display dialog header
+
+
+ Última verificação: {0}, {1}
+ {0} is date, {1} is time
+
+
+ Não é possível determinar a última verificação de atualizações
+
+
+ Atualizações de App
+ Label for setting item to check for app updates
+
+
+ Entrar no MSA e no AAD
+
+
+ Entre no AAD usando a conta da sua organização.
+
+
+ Credenciais do Azure AD (AAD)
+
+
+ AAD
+
+
+ Autentica o Microsoft Graph e outros recursos
+
+
+ Autentica somente o Microsoft Graph
+
+
+ Cancelar
+
+
+ Conta da sua organização
+
+
+ Caso não consiga prosseguir nem sair do assistente de entrada, aguarde {0} segundos e você deverá retornar ao app.
+
+
+ Entrando
+
+
+ Saindo
+
+
+ Entre com sua Conta Microsoft aqui
+
+
+ Credenciais da MSA (Conta Microsoft)
+
+
+ MSA
+
+
+ Autenticação
+
+
+ Credenciais da Microsoft
+
+
+ Falha ao entrar ({0})
+
+
+ Entrada bem-sucedida ({0})
+
+
+ Entrar
+
+
+ Saída: {0}
+
+
+ Sair
+
+
+ Reprodução Automática
+ Music player page auto-play toggle text
+
+
+ Dimensionamento Automático
+
+
+ Ocorreu falha na atualização devido à bateria fraca.
+ App update error, low battery
+
+
+ Tentando emparelhar com {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Emparelhando com {0} ({1}).
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ O PIN mostrado no dispositivo corresponde a: {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Desconhecido
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Atualmente emparelhado
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Pronto para emparelhar
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Estado desconhecido
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Digite o seguinte PIN no dispositivo que você deseja emparelhar: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Digite o PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Solicitação de emparelhamento de entrada de {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Este dispositivo está registrado para emparelhamento de entrada. (Cerimônias com suporte: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Falha ao registrar emparelhamento de entrada.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Emparelhamento de entrada registrado com êxito. (Cerimônias com suporte: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ O PIN inserido está incorreto.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ Nenhum adaptador Bluetooth utilizável encontrado neste dispositivo: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Emparelhar
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Falha ao emparelhar com {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Emparelhado com êxito com {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ Padrão
+ Text label for the corresponding device pairing protection level
+
+
+ Criptografia e autenticação
+ Text label for the corresponding device pairing protection level
+
+
+ Criptografia
+ Text label for the corresponding device pairing protection level
+
+
+ Nenhum
+ Text label for the corresponding device pairing protection level
+
+
+ Agora seu dispositivo é detectável e pronto para emparelhar com outros dispositivos Bluetooth.
+ Text displayed when StartWatcher is invoked
+
+
+ Seu dispositivo não está mais procurando outros dispositivos Bluetooth.
+ Text displayed when StopWatcher is invoked
+
+
+ Desemparelhar
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Falha ao desemparelhar de {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Desemparelhado com êxito de {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Home Page
+
+
+ Navegador da Web
+
+
+ Cancelar
+
+
+ Não há suporte para alteração de diretório no momento. Use caminhos completos em seus comandos.
+
+
+ Fuso horário
+ Time zone text
+
+
+ Verificando atualizações...
+ App update status
+
+
+ Verificar se há atualizações
+
+
+ Limpar Contas
+
+
+ Ocorreu um problema ao limpar as contas
+
+
+ Isso limpará as seguintes contas do Windows:
+{0}
+
+Continuar?
+
+
+ As contas foram limpas
+
+
+ Limpando contas...
+
+
+ Limpar
+
+
+ Fechar
+
+
+ O dispositivo não tem permissão para executar o processador de linha de comando.
+Para habilitá-lo, execute o seguinte comando como "Administrador" no dispositivo:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Você pode executar o comando na página Processos do Portal de Dispositivos do Windows IoT ou usar o PowerShell para conectar o dispositivo Windows IoT.
+Para obter mais informações, acesse http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Falha ao executar o comando como Administrador: {0}
+
+
+ Falha ao habilitar o Processador de Linha de Comando (cmd.exe) no dispositivo: {0}
+
+
+ O Processador de Linha de Comando (cmd.exe) foi habilitado com êxito o no seu dispositivo.
+
+
+ Cor do Bloco
+
+
+ Voltar
+ Back UI navigation
+
+
+ Mostrar Informações do Dispositivo
+
+
+ Avançar
+ Forward UI navigation
+
+
+ Ativar/Desativar Tela Inteira
+
+
+ Visualização do Clone
+ Clone current view to another display
+
+
+ Log de Salvamento Rápido
+
+
+ Log da Sessão
+
+
+ Definir Página Padrão
+
+
+ Comando cancelado.
+
+
+ Digitar a linha de comando
+ Placeholder for command line input text box
+
+
+ Erro ao executar a linha de comando: {0}
+
+
+ Linha de Comando
+
+
+ Linha de comando
+ Title for command line page
+
+
+ O tempo de espera do comando expirou após {0} segundos sem produzir saída.
+
+
+ Nome do Computador
+
+
+ Confirmação
+
+
+ Conectar automaticamente
+
+
+ Conectar automaticamente
+
+
+ Conectar
+
+
+ Conectar
+
+
+ Dispositivos Conectados
+
+
+ Falha na atualização. Conecte-se à rede Wi-Fi e tente novamente.
+ App update error, poor connection
+
+
+ Continuar
+
+
+ Não foi possível analisar a saída do comando
+
+
+ Anel Atual
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Página de App Padrão
+
+
+ Estamos escolhendo o idioma padrão automaticamente...
+
+
+ {0} logs excluídos
+ {0} is plural number of logs
+
+
+ {0} log excluído
+ {0} is singular number of logs
+
+
+ Excluir {0} log?
+ {0} is singular number of logs
+
+
+ Excluir {0} logs?
+ {0} is plural number of logs
+
+
+ Excluir Seleção
+
+
+ ID do Dispositivo Azure
+ Field label
+
+
+ Hub do Azure IoT
+ Field label
+
+
+ Ir para a Página do Dispositivo
+
+
+ Endereço IP: {0}
+Versão do SO: {1}
+Versão do App: {2}
+
+
+ Versão do App
+ Field label
+
+
+ Nome do Dispositivo
+ Field label
+
+
+ Endereço IP
+ Field label
+
+
+ Rede
+ Field label
+
+
+ Versão do sistema operacional
+ Label for OS Version field in main page
+
+
+ para começar a desenvolver
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Informações do Dispositivo
+
+
+ Visite
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ A página que você está tentando acessar requer o uso das APIs do WDP (Portal de Dispositivos do Windows). Entre usando as credenciais do WDP para continuar.
+
+
+ Ocorreu um problema ao entrar no serviço.
+
+
+ A entrada no Portal de Dispositivos foi bem-sucedida.
+
+
+ Verificando as Credenciais do Portal de Dispositivos...
+
+
+ Ocorreu um problema ao obter o clima. Tentar novamente?
+
+
+ Conexões diretas
+
+
+ Desconectar
+ This disconnects the connected network
+
+
+ Idioma de exibição atualizado: {0}
+
+
+ Domínio
+
+
+ Download Concluído.
+ App update status
+
+
+ Falha no download. Tente mais tarde.
+
+
+ Baixando Atualização
+ App update status
+
+
+ Baixar atualizações
+
+
+ Desenhar
+
+
+ "{0} logs enviado para {1}"
+ {0} is plural number of logs, {1} is email address
+
+
+ "{0} log enviado para {1}"
+ {0} is singular number of logs, {1} is email address
+
+
+ Enviar Log por Email
+
+
+ Você gostaria de enviar {0} por email para si mesmo?
+ {0} is filename
+
+
+ Ocorreu um problema para enviar seu log por email: {0}
+ {0} is exception message
+
+
+ Você pode encontrar seus logs na página Logs
+
+
+ "Enviar {0} log por email para si mesmo?"
+ {0} is singular number of logs
+
+
+ Ocorreu um problema para enviar seus logs por email: {0}
+ {0} is an exception message
+
+
+ Enviar por email os {0} logs para você mesmo?
+ {0} is plural number of logs
+
+
+ Enviar Logs por Email
+
+
+ Enviar Seleção por Email
+
+
+ Habilitar o Processador de Linha de Comando
+
+
+ Proteção de Tela
+ Toggle switch for enabling the screensaver
+
+
+ Hora de término
+
+
+ Erro
+
+
+ Ocorreu um problema ao recuperar informações sobre o clima
+
+
+ Ethernet
+ Field label
+
+
+ GUID do Provedor do ETW: {0}
+ Format string for app settings page
+
+
+ Executando comandos como DefaultAccount
+
+
+ Explorar
+
+
+ Arquivo salvo: {0}
+ {0} is a filename
+
+
+ Liberação de versões de pré-lançamento
+ Device servicing flighting
+
+
+ Informações de liberação de versões de pré-lançamento
+ Device servicing flighting
+
+
+ Anel de Versão de Pré-lançamento foi alterado para {0}!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ Ocorreu um problema ao alterar seu anel de versão de pré-lançamento
+
+
+ Previsão
+ Weather forecast
+
+
+ Você está prestes a entrar no modo de tela inteira. Para sair, você deve pressionar [Esc] no teclado. Continuar?
+
+
+ Modo de Tela Inteira
+
+
+ Pressione [Esc] para sair do modo de tela inteira.
+
+
+ Geral
+
+
+ Placa do IoTEnterprise
+ A generic board name
+
+
+ GitHub
+
+
+ Ajuda
+
+
+ Ajuda
+
+
+ Ajuda
+
+
+ Idioma do teclado de entrada atualizado: {0}
+
+
+ Instalação concluída.
+ App update status
+
+
+ Falha na instalação. Tente mais tarde.
+
+
+ Instalando Atualização
+ App update status
+
+
+ Instalar atualizações
+
+
+ Credencial Inválida
+
+
+ '{0}' é um local inválido.
+ Format string for app settings page
+
+
+ '{0}' é um valor inválido. O valor deve ser maior ou igual a 1.
+ Format string for app settings page
+
+
+ '{0}' é um valor inválido.
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Layout do teclado
+ Field label
+
+
+ Reiniciar este app para aplicar as novas alterações
+
+
+ Idioma
+
+
+ Idioma
+ Field label
+
+
+ Carregando...
+
+
+ Carregando informações do clima...
+
+
+ O log foi enviado para {0}
+ {0} is email address
+
+
+ Log salvo em: {0}
+ {0} is filename
+
+
+ Logs
+
+
+ Logs
+
+
+ Nome do Dispositivo
+ Field label
+
+
+ Endereço IP
+ Field label
+
+
+ Versão do Sistema Operacional
+ Label for OS Version field in main page
+
+
+ Esta é uma imagem de teste do Windows 10 IoT Enterprise destinada a protótipos. Se você estiver pensando em comercializar seu dispositivo, use um FFU personalizado para otimizar a segurança.
+ Maker Imager Security Notice
+
+
+ Token de Serviço do Bing Mapas
+
+
+ Token de Serviço do Bing Mapas Obrigatório
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ MSA (Conta Microsoft)
+
+
+ Reproduzindo no momento
+ Music player page status text (currently playing)
+
+
+ Selecione uma música e clique em Reproduzir.
+ Music player page status text (default)
+
+
+ Adicione um ou mais arquivos de áudio à pasta Música.
+Adicione as músicas no Portal de Dispositivos do Windows usando Apps > Explorador de Arquivos.
+ Music player page instructions text
+
+
+ Carregando Música
+ Music player page loading panel text
+
+
+ Carregando
+ Music player page status text (loading)
+
+
+ Nenhuma música encontrada
+ Music player page no music found prompt text
+
+
+ Tentar Novamente
+ Music player page reload button text (no files prompt)
+
+
+ Música
+
+
+ Música
+
+
+ Em Pausa
+ Music player page status text (paused)
+
+
+ Reproduzindo
+ Music player page status text (playing)
+
+
+ Entrar
+
+
+ Desconhecido
+
+
+ Menu
+
+
+ Adaptadores de Rede
+
+
+ Conectado
+
+
+ Conectado
+
+
+ Verificando requisitos de rede
+
+
+ Verificando requisitos de rede
+
+
+ Acesso à Internet limitado
+
+
+ Acesso local e à Internet
+
+
+ Acesso à rede local somente
+
+
+ Sem conectividade
+
+
+ INFORMAÇÕES DA REDE
+
+
+ Rede Não Disponível
+
+
+ Digitar a chave de segurança da rede
+
+
+ Digite a chave de segurança da rede
+
+
+ Rede e Wi-Fi
+
+
+ Rede e Wi-Fi
+
+
+ Exibir as propriedades da rede
+
+
+ Propriedades da Rede
+
+
+ Você está prestes a ser redirecionado para o portal cativo da rede Wi-Fi. Continuar?
+
+
+ Redirecionamento de Rede
+
+
+ Avançar
+
+
+ Avançar
+
+
+ Nenhuma conta encontrada
+
+
+ Não
+
+
+ nenhum nome de dispositivo
+
+
+ sem conexão com a Internet
+
+
+ Nenhum log selecionado
+
+
+ Nenhuma música encontrada
+ Music player page panel text
+
+
+ Nenhum localizado
+
+
+ Não há nenhuma atualização pendente para download.
+ App update status
+
+
+ Não há nenhuma atualização pendente para instalar.
+ App update status
+
+
+ N/D
+
+
+ Notificações
+
+
+ Notificações
+
+
+ Nenhuma nova atualização encontrada.
+ Format string displayed when no app updates are found
+
+
+ OK
+ Button content text for the Bluetooth settings page
+
+
+ Escolha seu idioma
+
+
+ Vamos nos conectar
+
+
+ Bem-vindo ao Windows 10 IoT Enterprise
+
+
+ Vamos resolver algumas etapas básicas.
+
+
+ Bem-vindo ao Windows 10 IoT Enterprise
+
+
+ ID da Edição do Sistema Operacional
+
+
+ Edição do Sistema Operacional
+
+
+ Informações do SO
+
+
+ Informações do SO
+
+
+ Não Disponível
+ Text shown when we cannot retrieve the OS Version
+
+
+ Versão do Sistema Operacional
+
+
+ Pacotes
+ Software packages
+
+
+ Pacotes Instalados
+ Software packages
+
+
+ Configurações da Página
+
+
+ Páginas
+
+
+ Senha
+
+
+ Carregando Imagens
+ Default text when no images are available
+
+
+ Adicione imagens à pasta Imagens.
+Adicione as imagens no Portal de Dispositivos do Windows usando Apps > Explorador de Arquivos.
+
+
+ Nenhuma imagem encontrada
+ Default text when no images are available
+
+
+ Plataforma
+
+
+ Executar
+
+
+ Opções de Energia
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Básico: Envie apenas informações sobre seu dispositivo, as configurações e funcionalidades dele, e se ele está funcionando corretamente.
+
+
+ Completo: Envie todos os dados do diagnóstico Básico juntamente com informações sobre os sites em que você navega e como você usa apps e recursos, mais informações adicionais sobre a integridade do dispositivo, a atividade do dispositivo e um relatório avançado de erros.
+
+
+ Não foi possível alterar a configuração de privacidade. Verifique seu nome de usuário e a senha e tente novamente.
+
+
+ Escolha a quantidade de dados de diagnóstico que deseja enviar para a Microsoft. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente da opção selecionada, o dispositivo será igualmente seguro e funcionará normalmente.
+
+
+ Dados de Diagnóstico
+ Label for Setting item to control Privacy
+
+
+ Digite as credenciais para definir o nível de privacidade neste dispositivo.
+
+
+ Definir seu nível de privacidade
+
+
+ Atualizar
+ Refresh button
+
+
+ Repetir a Música
+ Music player page repeat toggle text
+
+
+ Reiniciar
+
+
+ Reiniciar
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Uso: comando RunAsAdmin
+
+Exemplos:
+> RunAsdmin TZUTIL /s "Horário Padrão do Pacífico"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Salvar
+
+
+ Fator de Escala
+
+
+ Selecionar Tudo
+
+
+ Enviar Telemetria
+
+
+ Não disponível
+
+
+ Log da Sessão
+
+
+ Ocorreu um problema ao configurar a página padrão como {0}.
+ Format string for app settings page
+
+
+ Configurações
+
+
+ Ordem Aleatória
+ Music player page shuffle toggle text
+
+
+ Desligar
+
+
+ Desligar
+ Shutdown entry in the shutdown menu
+
+
+ Entre com a conta do Azure AD para usar este recurso.
+
+
+ Ignorar
+
+
+ Ignorar esta etapa
+
+
+ Intervalo da Apresentação de Slides (segundos)
+
+
+ Apresentação de Slides
+
+
+ Apresentação de Slides
+
+
+ Iniciar
+
+
+ Iniciar
+
+
+ Hora de início
+
+
+ Status
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Enviar
+
+
+ Êxito
+
+
+ Sistema
+
+
+ Ocorreu um problema ao tentar atualizar as configurações do sistema.
+ Used within system settings
+
+
+ Nível de Telemetria
+
+
+ Telemetria
+
+
+ Testar Notificação Jumbo
+
+
+ Testar Notificação
+
+
+ O Windows 10 IoT é membro da família Windows 10 que oferece capacidade, segurança e gerenciamento de classe empresarial para a Internet das Coisas. Ele utiliza o ecossistema integrado do Windows e a conectividade na nuvem, permitindo que as organizações criem a própria Internet das Coisas com dispositivos seguros que possam ser rapidamente provisionados, facilmente gerenciados e conectados diretamente a uma estratégia geral de nuvem.
+
+
+ Altura Bloco
+
+
+ Personalização
+
+
+ Largura do Bloco
+
+
+ Tempo Limite de Conexão Atingido
+
+
+ Fuso horário atualizado: {0}
+
+
+ Erro: Não é possível comunicar-se com o serviço do clima
+
+
+ Ocorreu uma falha por motivo desconhecido.
+ App update error, unknown
+
+
+ Desmarcar Tudo
+
+
+ Falha Não Especificada
+
+
+ Opções Avançadas
+
+
+ Verificar Agora
+
+
+ Instalar Agora
+
+
+ {0} atualização pendente
+ {0} is singular amount of updates
+
+
+ {0} novas atualizações encontradas.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} atualizações pendentes
+ {0} is plural amount of updates
+
+
+ Usar Ícones de Bloco MDL2
+
+
+ Usar senha
+
+
+ Nome de Usuário
+
+
+ Portal de Dispositivos do Windows
+
+
+ Configurações do Portal de Dispositivos
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Portal de Dispositivos do Windows
+
+
+ Localização Atual ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Seu Local
+
+
+ Seu Local
+ Label for map pin
+
+
+ Local Desconhecido
+ Label for map pin
+
+
+ Sensor:
+ Label for temperature sensor output
+
+
+ Clima
+
+
+ Erro ao carregar a página Clima.
+
+Clique no botão Atualizar no canto inferior direito da tela para recarregar esta página.
+
+Se você não tiver chaves da API Clima, navegue até weatherunlocked.com. Salve as chaves em "WeatherTokens.config" na pasta Estado Local deste App. Depois, atualize a página.
+
+
+ Dados de clima fornecidos por:
+
+
+ Clima
+
+
+ Digite um endereço web
+
+
+ Navegador da Web
+
+
+ Bem-vindo ao Windows IoT Enterprise
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Atualizar
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Última Verificação:
+ For a timestamp
+
+
+ Última Atualização:
+ For a timestamp
+
+
+ Estado Atualizado:
+
+
+ Mensagem de Status:
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ Diretório de trabalho inválido: {0}
+
+
+ WPS
+
+
+ Permitir que este app acesse sua localização
+
+
+ Escolha as configurações e selecione 'Aceitar' para salvá-las. Você pode alterar essas configurações a qualquer momento.
+
+
+ Permitir que a Microsoft use sua localização
+
+
+ Continuando automaticamente...
+
+
+ Aceitar
+
+
+ Permitir que {0} acesse sua localização precisa?
+ {0} is the name of a page
+
+
+ Localização
+
+
+ Para mudar isso depois, vá para Configurações > Permissões.
+
+
+ Não
+
+
+ Sim
+
+
+ Você não poderá obter experiências baseadas em localização, como mapas e previsão do tempo, nem usar outros serviços que precisam de sua localização para funcionar.
+
+
+ Obtenha experiências baseadas na localização, como mapas e clima. Permita que este app solicite sua localização. A Microsoft usará seus dados de localização para melhorar os serviços de localização.
+
+
+ Envie apenas informações sobre seu dispositivo, as configurações e funcionalidades dele, e se ele está funcionando corretamente. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente de você selecionar Básico ou Completo, seu dispositivo será igualmente seguro e funcionará normalmente.
+
+
+ Básico
+
+
+ Envie todos os dados do diagnóstico Básico juntamente com informações sobre os sites em que você navega e como você usa apps e recursos, mais informações adicionais sobre a integridade do dispositivo, a atividade do dispositivo e um relatório avançado de erros. Os dados de diagnóstico são usados para ajudar a manter o Windows seguro e atualizado, solucionar problemas e fazer melhorias no produto. Independentemente de você selecionar Básico ou Completo, seu dispositivo será igualmente seguro e funcionará normalmente.
+
+
+ Completo
+
+
+ Escolha a configuração de privacidade para o dispositivo e selecione 'Aceitar' para salvá-la.
+
+
+ Enviar dados de diagnóstico para a Microsoft
+
+
+ Diagnóstico
+
+
+ Se você permitir o acesso, permitirá que este app use os recursos do dispositivo para determinar sua localização, e a Microsoft usará seus dados de localização para melhorar os serviços de localização. Negar o acesso impede que o Windows forneça a localização a este app.
+
+
+ Conheça as opções de privacidade
+
+
+ Saiba como esta configuração afeta sua privacidade.
+
+
+ Obter mais informações sobre estas configurações
+
+
+ Política de privacidade
+
+
+ Sim
+
+
+ Sim
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ru-RU/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ru-RU/Resources.resw
index bc071066a..dd4790a6c 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ru-RU/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/ru-RU/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- Использовать AAD версии 2
-
-
- Доступ отменен
-
-
- Описание:
-
-
- DHCP-сервер:
-
-
- DNS:
-
-
- Адрес шлюза:
-
-
- IPv4-адрес:
-
-
- Имя:
-
-
- Физический адрес:
-
-
- Маска подсети:
-
-
- Тип:
-
-
- Версия приложения
-
-
- Приложения
-
-
- Вы собираетесь запустить внешнее приложение. Чтобы вернуть к этому приложению вам необходимо будет воспользоваться порталом устройств Windows. Продолжить?
- Dialog prompt for launching external apps
-
-
- Приложения
-
-
- Параметры приложения
-
-
- Задайте период активности, чтобы сообщить нам, когда вы обычно используете это устройство. В этот период мы не будем автоматически перезапускать его.
-
-
- Не удается сохранить новое время начала и окончания, поскольку они совпадают. Выберите новое время или отключите эту функцию.
-
-
- Дополнительные параметры
- Advanced section title
-
-
- Управляйте каждым этапом обновления (получение, загрузка и установка).
-
-
- Параметры автоматического обновления
- Auto-Update section title
-
-
- Разрешить приложению устанавливать обновления вне периода активности
-
-
- Обновления приложений
- App update display dialog header
-
-
- Последняя проверка: {0}, {1}
- {0} is date, {1} is time
-
-
- Не удается определить время последней проверки наличия обновлений
-
-
- Обновления приложений
- Label for setting item to check for app updates
-
-
- Вход в MSA и AAD
-
-
- Войдите в AAD с помощью учетной записи организации.
-
-
- Вход в Azure AD (AAD)
-
-
- AAD
-
-
- Проверяет подлинность Microsoft Graph и других ресурсов
-
-
- Проверяет только подлинность Microsoft Graph
-
-
- Отмена
-
-
- Учетная запись организации
-
-
- Если вы застрянете на каком-либо этапе и не сможете выйти из мастера входа, подождите {0} с. После этого вы должны будете вернуться в приложение.
-
-
- Выполняется вход...
-
-
- Выполняется выход...
-
-
- Войдите в свою учетную запись Майкрософт здесь
-
-
- Вход в учетную запись Майкрософт (MSA)
-
-
- MSA
-
-
- Аутентификация
-
-
- Вход в учетную запись Майкрософт
-
-
- Не удалось выполнить вход ({0})
-
-
- Вход выполнен успешно ({0})
-
-
- Войти
-
-
- Выполнен выход: {0}
-
-
- Выйти
-
-
- Автоматическое воспроизведение
- Music player page auto-play toggle text
-
-
- Автоматическое масштабирование
-
-
- Не удалось выполнить обновление из-за низкого заряда батареи.
- App update error, low battery
-
-
- Попытка установить связь с {0} ({1}).
- Text displayed when a Bluetooth pairing attempt starts
-
-
- Связывание с {0} ({1}).
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- Совпадает ли ПИН-код, показанный на устройстве, с {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- Неизвестно
- Text displayed when the Bluetooth device name is unknown
-
-
- Связь установлена
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Готово к связыванию
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Неизвестное состояние
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- Введите этот ПИН-код на устройстве, с которым необходимо установить связь: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- Введите ПИН-код:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- Входящий запрос связи от: {0} ({1}).
- Text displayed when an inbound pairing request is received
-
-
- Этой устройство уже зарегистрировано для входящего связывания (поддерживаемые церемонии: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- Не удалось зарегистрировать для входящего связывания.
- Text displayed when Inbound pairing handler registration fails
-
-
- Регистрация для входящего связывания успешно выполнена (поддерживаемые церемонии: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- Введен неправильный ПИН-код.
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- На этом устройстве не удается найти подходящий адаптер Bluetooth: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- Связать
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- Не удалось установить связь с {0} ({1}).
- Text displayed when a Bluetooth pairing attempt fails
-
-
- Связь с {0} успешно установлена ({1}).
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- Bluetooth
- Title for Bluetooth settings page
-
-
- По умолчанию
- Text label for the corresponding device pairing protection level
-
-
- Шифрование и проверка подлинности
- Text label for the corresponding device pairing protection level
-
-
- Шифрование
- Text label for the corresponding device pairing protection level
-
-
- Нет
- Text label for the corresponding device pairing protection level
-
-
- Устройство доступно для обнаружения и готово к связыванию с другими устройствами Bluetooth.
- Text displayed when StartWatcher is invoked
-
-
- Устройство больше не ищет другие устройства Bluetooth.
- Text displayed when StopWatcher is invoked
-
-
- Разорвать соединение
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- Не удалось разорвать соединение с {0} ({1}).
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- Соединение с {0} успешно разорвано ({1}).
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- Bluetooth
- Header label for the Bluetooth watcher toggle switch
-
-
- Домашняя страница
-
-
- Веб-браузер
-
-
- Отмена
-
-
- Изменение каталога пока не поддерживается. Используйте в командах полные пути.
-
-
- Часовой пояс
- Time zone text
-
-
- Поиск обновлений...
- App update status
-
-
- Проверить наличие обновлений
-
-
- Удалить учетные записи
-
-
- Произошла проблема при удалении ваших учетных записей
-
-
- Будут удалены следующие учетные записи Windows:
-{0}
-
-Продолжить?
-
-
- Учетные записи удалены
-
-
- Удаление учетных записей...
-
-
- Очистить
-
-
- Закрыть
-
-
- На устройстве не разрешено запускать процессор командной строки.
-Чтобы включить его, выполните на своем устройстве от имени администратора следующую команду:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-Эту команду можно выполнить на странице процессов портала IoT Windows Device. Для подключения к устройству с Windows IoT также можно использовать PowerShell.
-Дополнительные сведения см. на веб-странице http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- Не удалось запустить команду от имени администратора: {0}
-
-
- Не удалось включить на устройстве процессор командной строки (cmd.exe): {0}
-
-
- На устройстве успешно включен процессор командной строки (cmd.exe).
-
-
- Цвет плитки
-
-
- Назад
- Back UI navigation
-
-
- Показать информацию об устройстве
-
-
- Вперед
- Forward UI navigation
-
-
- Переключить полноэкранный режим
-
-
- Клонировать представление
- Clone current view to another display
-
-
- Быстро сохранить журнал
-
-
- Журнал сеансов
-
-
- Задать стандартную страницу
-
-
- Команда отменена.
-
-
- Введите командную строку
- Placeholder for command line input text box
-
-
- Ошибка при запуске командной строки: {0}
-
-
- Командная строка
-
-
- Командная строка
- Title for command line page
-
-
- Время ожидания команды истекло через {0} с отсутствия выходных данных.
-
-
- Имя компьютера
-
-
- Подтверждение
-
-
- Подключаться автоматически
-
-
- Подключаться автоматически
-
-
- Подключить
-
-
- Подключить
-
-
- Подключенные устройства
-
-
- Ошибка обновления. Подключитесь к сети Wi-Fi и повторите попытку.
- App update error, poor connection
-
-
- Продолжить
-
-
- Не удалось проанализировать выходные данные команды
-
-
- Текущий круг
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- Страница приложения по умолчанию
-
-
- Язык по умолчанию выбирается автоматически…
-
-
- Удалено несколько журналов ({0})
- {0} is plural number of logs
-
-
- Удален {0} журнал
- {0} is singular number of logs
-
-
- Удалить {0} журнал?
- {0} is singular number of logs
-
-
- Удалить следующее количество журналов: {0}?
- {0} is plural number of logs
-
-
- Нажата кнопка "Удалить"
-
-
- Код устройства Azure
- Field label
-
-
- Центр IoT Azure
- Field label
-
-
- Перейти на страницу устройств
-
-
- IP-адрес: {0}
-Версия ОС: {1}
-Версия приложения: {2}
-
-
- Версия приложения
- Field label
-
-
- Имя устройства
- Field label
-
-
- IP-адрес
- Field label
-
-
- Сеть
- Field label
-
-
- Версия ОС
- Label for OS Version field in main page
-
-
- для начала разработки
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Информация об устройстве
-
-
- Посетите веб-сайт
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Чтобы открыть эту страницу, требуются API Windows Device Portal (WDP). Войдите, используя учетные данные WDP, чтобы продолжить.
-
-
- Возникла проблема со входом в систему.
-
-
- Вы успешно вошли в портал устройств!
-
-
- Проверка учетных данных портала устройств...
-
-
- Произошла ошибка при получении прогноза погоды. Повторить попытку?
-
-
- Прямые подключения
-
-
- Отключить
- This disconnects the connected network
-
-
- Язык интерфейса обновлен: {0}
-
-
- Домен
-
-
- Загрузка завершена!
- App update status
-
-
- Сбой загрузки. Повторите попытку позже!
-
-
- Скачивание обновления
- App update status
-
-
- Скачать обновления
-
-
- Рисование
-
-
- "На адрес {1} отправлены журналы ({0})"
- {0} is plural number of logs, {1} is email address
-
-
- "На адрес {1} отправлен {0} журнал"
- {0} is singular number of logs, {1} is email address
-
-
- Отправка журнала по электронной почте
-
-
- Вы хотите отправить файл "{0}" себе по электронной почте?
- {0} is filename
-
-
- При отправке себе журнала по электронной почте возникла проблема: {0}
- {0} is exception message
-
-
- Журналы можно найти на странице "Журналы"
-
-
- "Отправить {0} журнал себе по электронной почте?"
- {0} is singular number of logs
-
-
- При отправке себе журналов по электронной почте возникла проблема: {0}
- {0} is an exception message
-
-
- Отправить журналы ({0}) себе по электронной почте?
- {0} is plural number of logs
-
-
- Отправить журналы по электронной почте
-
-
- Выбран адрес электронной почты
-
-
- Включить процессор командной строки
-
-
- Заставка
- Toggle switch for enabling the screensaver
-
-
- Время окончания
-
-
- Ошибка
-
-
- При получении сведений о погоде произошла ошибка
-
-
- Ethernet
- Field label
-
-
- GUID поставщика трассировки событий Windows: {0}
- Format string for app settings page
-
-
- Выполнение команд в роли DefaultAccount
-
-
- Обзор
-
-
- Файл сохранен: {0}
- {0} is a filename
-
-
- Фокус-тестирование
- Device servicing flighting
-
-
- Информация о фокус-тестировании
- Device servicing flighting
-
-
- Круг тестируемых возможностей изменен на {0}!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- При изменении круга тестируемых возможностей возникла проблема
-
-
- Прогноз
- Weather forecast
-
-
- Вы собираетесь войти в полноэкранный режим. Чтобы выйти из него, необходимо нажать клавишу [Esc] на клавиатуре. Продолжить?
-
-
- Полноэкранный режим
-
-
- Нажмите клавишу [Esc] для выхода из полноэкранного режима.
-
-
- Общие
-
-
- Плата IoTEnterprise
- A generic board name
-
-
- GitHub
-
-
- Справка
-
-
- Справка
-
-
- Справка
-
-
- Язык ввода с клавиатуры обновлен: {0}
-
-
- Установка завершена!
- App update status
-
-
- Сбой установки. Повторите попытку позже!
-
-
- Установка обновления
- App update status
-
-
- Установить обновления
-
-
- Недопустимые учетные данные
-
-
- Недопустимое расположение: "{0}".
- Format string for app settings page
-
-
- Недопустимое значение: "{0}". Значение должно быть больше или равно 1.
- Format string for app settings page
-
-
- Недопустимое значение: "{0}".
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- Раскладка клавиатуры
- Field label
-
-
- Перезапустить приложение, чтобы применить новые параметры
-
-
- Язык
-
-
- Язык
- Field label
-
-
- Загрузка...
-
-
- Загрузка сведений о погоде...
-
-
- Журнал отправлен на адрес {0}
- {0} is email address
-
-
- Журнал сохранен здесь: {0}
- {0} is filename
-
-
- Журналы
-
-
- Журналы
-
-
- Имя устройства
- Field label
-
-
- IP-адрес
- Field label
-
-
- Версия ОС
- Label for OS Version field in main page
-
-
- Это тестовый образ Windows 10 IoT Enterprise, созданный только для моделирования. Если вы хотите получать прибыль с его помощью, воспользуйтесь настраиваемым средством для пакетного применения образов, чтобы оптимизировать защиту на этом устройстве.
- Maker Imager Security Notice
-
-
- Маркер службы карт Bing
-
-
- Требуется маркер службы карт Bing
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com, Hotmail, Live.com, MSN
-
-
- Учетная запись Майкрософт (MSA)
-
-
- Сейчас воспроизводится
- Music player page status text (currently playing)
-
-
- Выберите песню и нажмите "Воспроизвести".
- Music player page status text (default)
-
-
- Добавьте один или несколько звуковых файлов в папку "Музыка".
-Вы можете добавить музыку на портале устройств Windows в разделе "Приложения" > "Проводник".
- Music player page instructions text
-
-
- Загрузка музыки
- Music player page loading panel text
-
-
- Загрузка
- Music player page status text (loading)
-
-
- Музыка не найдена
- Music player page no music found prompt text
-
-
- Повторить попытку
- Music player page reload button text (no files prompt)
-
-
- Музыка
-
-
- Музыка
-
-
- Приостановлено
- Music player page status text (paused)
-
-
- Воспроизведение
- Music player page status text (playing)
-
-
- Войти
-
-
- Неизвестно
-
-
- Меню
-
-
- Сетевые адаптеры
-
-
- Подключено
-
-
- Подключено
-
-
- Проверка требований сети
-
-
- Проверка требований сети
-
-
- Ограниченный доступ к Интернету
-
-
- Локальная сеть и Интернет
-
-
- Только локальная сеть
-
-
- Отсутствует подключение
-
-
- СВЕДЕНИЯ О СЕТИ
-
-
- Нет доступа к сети
-
-
- Введите ключ безопасности сети
-
-
- Введите ключ безопасности сети
-
-
- Сеть и Wi-Fi
-
-
- Сеть и Wi-Fi
-
-
- Просмотреть свойства сети
-
-
- Свойства сети
-
-
- Сейчас вы будете перенаправлены на портал перехвата этой сети Wi-Fi. Продолжить?
-
-
- Перенаправление сети
-
-
- Далее
-
-
- Далее
-
-
- Учетные записи не найдены
-
-
- Нет
-
-
- нет имени устройства
-
-
- отсутствует подключение к Интернету
-
-
- Не выбран ни один журнал
-
-
- Музыка не найдена
- Music player page panel text
-
-
- Ничего не найдено
-
-
- Нет ожидающих обновлений для загрузки.
- App update status
-
-
- Нет ожидающих обновлений для установки.
- App update status
-
-
- Н/Д
-
-
- Уведомления
-
-
- Уведомления
-
-
- Новые обновления не найдены.
- Format string displayed when no app updates are found
-
-
- ОК
- Button content text for the Bluetooth settings page
-
-
- Выберите язык
-
-
- Давайте подключимся
-
-
- Добро пожаловать в Windows 10 IoT Базовую
-
-
- Давайте разберемся с некоторыми основными моментами.
-
-
- Добро пожаловать в Windows 10 IoT Базовую
-
-
- ИД выпуска ОС
-
-
- Выпуск ОС
-
-
- Информация об ОС
-
-
- Информация об ОС
-
-
- Недоступно
- Text shown when we cannot retrieve the OS Version
-
-
- Версия ОС
-
-
- Пакеты
- Software packages
-
-
- Установленные пакеты
- Software packages
-
-
- Параметры страниц
-
-
- Страницы
-
-
- Пароль
-
-
- Загрузка изображений
- Default text when no images are available
-
-
- Добавьте изображения в папку "Изображения".
-Можно добавить изображения на портале устройств Windows в разделе "Приложения" > "Проводник".
-
-
- Изображения не найдены
- Default text when no images are available
-
-
- Платформа
-
-
- Воспроизведение
-
-
- Параметры электропитания
- Label for Setting item to control Power (shutdown/restart)
-
-
- Основные: отправляются только сведения о вашем устройстве, его настройках, возможностях и исправности.
-
-
- Полный: помимо диагностических данных с базового уровня, отправляются сведения о посещаемых веб-сайтах и способах использования приложений и функций, а также дополнительная информация о работоспособности и действиях на устройстве и расширенные отчеты об ошибках.
-
-
- Не удалось изменить этот параметр конфиденциальности. Проверьте имя пользователя и пароль и повторите попытку.
-
-
- Выберите объем диагностических данных, которые следует отправлять в корпорацию Майкрософт. Диагностические данные позволяют поддерживать Windows в безопасном и актуальном состоянии, устранять неполадки и улучшать продукты. Степень безопасности и исправность устройства не зависит от того, какой объем диагностических данных выбран.
-
-
- Диагностические данные
- Label for Setting item to control Privacy
-
-
- Введите свои учетные данные, чтобы установить уровень конфиденциальности на этом устройстве.
-
-
- Выбор уровня конфиденциальности
-
-
- Обновить
- Refresh button
-
-
- Повторить песню
- Music player page repeat toggle text
-
-
- Перезапустить
-
-
- Перезапуск
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- Использование: команда RunAsAdmin
-
-Примеры:
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- Сохранить
-
-
- Коэффициент масштабирования
-
-
- Выделить все
-
-
- Отправить телеметрию
-
-
- Недоступно
-
-
- Журнал сеансов
-
-
- Возникла проблема при выборе "{0}" в качестве страницы по умолчанию.
- Format string for app settings page
-
-
- Параметры
-
-
- В случайном порядке
- Music player page shuffle toggle text
-
-
- Завершение работы
-
-
- Завершение работы
- Shutdown entry in the shutdown menu
-
-
- Чтобы использовать эту функцию, войдите в свою учетную запись Azure AD.
-
-
- Пропустить
-
-
- Пропустить этот шаг
-
-
- Интервал слайд-шоу (сек)
-
-
- Слайд-шоу
-
-
- Слайд-шоу
-
-
- Пуск
-
-
- Пуск
-
-
- Время начала
-
-
- Состояние
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- Отправить
-
-
- Выполнено
-
-
- Система
-
-
- При попытке обновления параметров системы возникла проблема.
- Used within system settings
-
-
- Уровень телеметрии
-
-
- Телеметрия
-
-
- Протестировать крупное уведомление
-
-
- Протестировать уведомление
-
-
- Windows 10 IoT — операционная система из семейства Windows 10, благодаря которой Интернет вещей получает эффективные возможности, функции безопасности и легкость управления, присущие корпоративным решениям. В этой системе используются такие преимущества Windows, как взаимодействие со встроенными устройствами, экосистема и подключение к облаку. Это позволяет организациям создать собственный Интернет вещей на основе безопасных устройств, которые предусматривают быстрое развертывание, легкое управление и беспроблемное встраивание в общую стратегию использования облачных технологий.
-
-
- Высота плитки
-
-
- Персонализация
-
-
- Ширина плитки
-
-
- Истекло время ожидания подключения
-
-
- Часовой пояс обновлен: {0}
-
-
- Ошибка: не удается установить связь со службой погоды
-
-
- Сбой обновления из-за неизвестной ошибки.
- App update error, unknown
-
-
- Отменить выбор всех элементов
-
-
- Неопределенная ошибка
-
-
- Дополнительные параметры
-
-
- Проверить сейчас
-
-
- Установить сейчас
-
-
- {0} ожидающее обновление
- {0} is singular amount of updates
-
-
- Найдены новые обновления: {0}.
- Format string displayed when new app updates are found. {0} is a number
-
-
- Ожидающих обновлений: {0}
- {0} is plural amount of updates
-
-
- Использовать значки плитки MDL2
-
-
- Использовать пароль
-
-
- Имя пользователя
-
-
- Портал устройств Windows
-
-
- Параметры портала устройств
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Портал устройств Windows
-
-
- Текущее расположение ({0}, {1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- Ваше расположение
-
-
- Ваше расположение
- Label for map pin
-
-
- Неизвестное расположение
- Label for map pin
-
-
- Датчик:
- Label for temperature sensor output
-
-
- Погода
-
-
- Ошибка загрузки страницы погоды.
-
-Нажмите кнопку "Обновить" в нижней правой части экрана, чтобы перезагрузить страницу.
-
-Если у вас нет ключей API приложения "Погода", перейдите на веб-сайт weatherunlocked.com. Сохраните ключи в "WeatherTokens.config" папке локального состояния приложения. Затем обновите страницу.
-
-
- Данные о погоде предоставляются службой
-
-
- Погода
-
-
- Введите веб-адрес
-
-
- Веб-браузер
-
-
- Добро пожаловать в Windows IoT Базовую
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- Обновить
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- Последняя проверка:
- For a timestamp
-
-
- Последнее обновление:
- For a timestamp
-
-
- Обновленное состояние:
-
-
- Сообщение о состоянии:
-
-
- Центр обновления Windows
-
-
- Центр обновления Windows
-
-
- Недопустимый рабочий каталог: {0}
-
-
- WPS
-
-
- Разрешить этому приложению получать доступ к вашему местоположению
-
-
- Выберите параметры, а затем нажмите "Принять". Эти параметры можно изменить в любое время.
-
-
- Разрешить корпорации Майкрософт использовать данные о вашем расположении
-
-
- Автоматическое продолжение...
-
-
- Принять
-
-
- Разрешить {0} доступ к сведениям о вашем точном местоположении?
- {0} is the name of a page
-
-
- Местоположение
-
-
- Позже вы можете изменить этот параметр, перейдя в раздел "Параметры" > "Разрешения".
-
-
- Нет
-
-
- Да
-
-
- Вы не сможете автоматически получать карты и прогноз погоды на основе текущего местоположения или пользоваться другими службами, которым для правильной работы требуется ваше местоположение.
-
-
- Получите функциональные возможности на основе местоположения, например предоставление местного прогноза погоды и карт. Корпорация Майкрософт будет использовать данные о вашем местоположении для улучшения служб определения местоположения.
-
-
- Отправляются только сведения о вашем устройстве, его настройках, возможностях и исправности. Диагностические данные используются, чтобы поддерживать Windows в безопасном и актуальном состоянии, устранять неполадки и улучшать продукты. Степень безопасности устройства не зависит от того, какой уровень диагностических данных выбран — базовый или полный. Кроме того, и на том, и на другом уровне устройство будет работать в обычном порядке.
-
-
- Базовый
-
-
- Помимо диагностических данных с базового уровня, отправляются сведения о посещаемых веб-сайтах и способах использования приложений и функций, а также дополнительная информация о работоспособности и применении устройства и расширенные отчеты об ошибках. Диагностические данные помогают обеспечивать безопасность и актуальность Windows, устранять неполадки и улучшать продукты. Степень безопасности устройства не зависит от того, какой выбран уровень — базовый или полный. Кроме того, и на том, и на другом уровне устройство будет работать в обычном порядке.
-
-
- Полный
-
-
- Выберите параметр конфиденциальности для своего устройства, а затем нажмите кнопку "Принять", чтобы сохранить его.
-
-
- Отправлять данные диагностики в корпорацию Майкрософт
-
-
- Диагностика
-
-
- Если доступ разрешен, вы разрешите этому приложению использовать возможности устройства для определения вашего местоположения, а корпорация Майкрософт будет использовать данные о местоположении для улучшения служб определения местоположения. Если доступ запрещен, Windows заблокирует доступ к вашему местоположению только для этого приложения.
-
-
- Узнайте свои настройки конфиденциальности
-
-
- Узнайте, как этот параметр влияет на конфиденциальность.
-
-
- Дополнительные сведения об этих параметрах
-
-
- Заявление о конфиденциальности
-
-
- Да
-
-
- Да
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ Использовать AAD версии 2
+
+
+ Доступ отменен
+
+
+ Описание:
+
+
+ DHCP-сервер:
+
+
+ DNS:
+
+
+ Адрес шлюза:
+
+
+ IPv4-адрес:
+
+
+ Имя:
+
+
+ Физический адрес:
+
+
+ Маска подсети:
+
+
+ Тип:
+
+
+ Версия приложения
+
+
+ Приложения
+
+
+ Вы собираетесь запустить внешнее приложение. Чтобы вернуть к этому приложению вам необходимо будет воспользоваться порталом устройств Windows. Продолжить?
+ Dialog prompt for launching external apps
+
+
+ Приложения
+
+
+ Параметры приложения
+
+
+ Задайте период активности, чтобы сообщить нам, когда вы обычно используете это устройство. В этот период мы не будем автоматически перезапускать его.
+
+
+ Не удается сохранить новое время начала и окончания, поскольку они совпадают. Выберите новое время или отключите эту функцию.
+
+
+ Дополнительные параметры
+ Advanced section title
+
+
+ Управляйте каждым этапом обновления (получение, загрузка и установка).
+
+
+ Параметры автоматического обновления
+ Auto-Update section title
+
+
+ Разрешить приложению устанавливать обновления вне периода активности
+
+
+ Обновления приложений
+ App update display dialog header
+
+
+ Последняя проверка: {0}, {1}
+ {0} is date, {1} is time
+
+
+ Не удается определить время последней проверки наличия обновлений
+
+
+ Обновления приложений
+ Label for setting item to check for app updates
+
+
+ Вход в MSA и AAD
+
+
+ Войдите в AAD с помощью учетной записи организации.
+
+
+ Вход в Azure AD (AAD)
+
+
+ AAD
+
+
+ Проверяет подлинность Microsoft Graph и других ресурсов
+
+
+ Проверяет только подлинность Microsoft Graph
+
+
+ Отмена
+
+
+ Учетная запись организации
+
+
+ Если вы застрянете на каком-либо этапе и не сможете выйти из мастера входа, подождите {0} с. После этого вы должны будете вернуться в приложение.
+
+
+ Выполняется вход...
+
+
+ Выполняется выход...
+
+
+ Войдите в свою учетную запись Майкрософт здесь
+
+
+ Вход в учетную запись Майкрософт (MSA)
+
+
+ MSA
+
+
+ Аутентификация
+
+
+ Вход в учетную запись Майкрософт
+
+
+ Не удалось выполнить вход ({0})
+
+
+ Вход выполнен успешно ({0})
+
+
+ Войти
+
+
+ Выполнен выход: {0}
+
+
+ Выйти
+
+
+ Автоматическое воспроизведение
+ Music player page auto-play toggle text
+
+
+ Автоматическое масштабирование
+
+
+ Не удалось выполнить обновление из-за низкого заряда батареи.
+ App update error, low battery
+
+
+ Попытка установить связь с {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ Связывание с {0} ({1}).
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ Совпадает ли ПИН-код, показанный на устройстве, с {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ Неизвестно
+ Text displayed when the Bluetooth device name is unknown
+
+
+ Связь установлена
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Готово к связыванию
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Неизвестное состояние
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ Введите этот ПИН-код на устройстве, с которым необходимо установить связь: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ Введите ПИН-код:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ Входящий запрос связи от: {0} ({1}).
+ Text displayed when an inbound pairing request is received
+
+
+ Этой устройство уже зарегистрировано для входящего связывания (поддерживаемые церемонии: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ Не удалось зарегистрировать для входящего связывания.
+ Text displayed when Inbound pairing handler registration fails
+
+
+ Регистрация для входящего связывания успешно выполнена (поддерживаемые церемонии: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ Введен неправильный ПИН-код.
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ На этом устройстве не удается найти подходящий адаптер Bluetooth: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ Связать
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ Не удалось установить связь с {0} ({1}).
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ Связь с {0} успешно установлена ({1}).
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ Bluetooth
+ Title for Bluetooth settings page
+
+
+ По умолчанию
+ Text label for the corresponding device pairing protection level
+
+
+ Шифрование и проверка подлинности
+ Text label for the corresponding device pairing protection level
+
+
+ Шифрование
+ Text label for the corresponding device pairing protection level
+
+
+ Нет
+ Text label for the corresponding device pairing protection level
+
+
+ Устройство доступно для обнаружения и готово к связыванию с другими устройствами Bluetooth.
+ Text displayed when StartWatcher is invoked
+
+
+ Устройство больше не ищет другие устройства Bluetooth.
+ Text displayed when StopWatcher is invoked
+
+
+ Разорвать соединение
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ Не удалось разорвать соединение с {0} ({1}).
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ Соединение с {0} успешно разорвано ({1}).
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ Bluetooth
+ Header label for the Bluetooth watcher toggle switch
+
+
+ Домашняя страница
+
+
+ Веб-браузер
+
+
+ Отмена
+
+
+ Изменение каталога пока не поддерживается. Используйте в командах полные пути.
+
+
+ Часовой пояс
+ Time zone text
+
+
+ Поиск обновлений...
+ App update status
+
+
+ Проверить наличие обновлений
+
+
+ Удалить учетные записи
+
+
+ Произошла проблема при удалении ваших учетных записей
+
+
+ Будут удалены следующие учетные записи Windows:
+{0}
+
+Продолжить?
+
+
+ Учетные записи удалены
+
+
+ Удаление учетных записей...
+
+
+ Очистить
+
+
+ Закрыть
+
+
+ На устройстве не разрешено запускать процессор командной строки.
+Чтобы включить его, выполните на своем устройстве от имени администратора следующую команду:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+Эту команду можно выполнить на странице процессов портала IoT Windows Device. Для подключения к устройству с Windows IoT также можно использовать PowerShell.
+Дополнительные сведения см. на веб-странице http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ Не удалось запустить команду от имени администратора: {0}
+
+
+ Не удалось включить на устройстве процессор командной строки (cmd.exe): {0}
+
+
+ На устройстве успешно включен процессор командной строки (cmd.exe).
+
+
+ Цвет плитки
+
+
+ Назад
+ Back UI navigation
+
+
+ Показать информацию об устройстве
+
+
+ Вперед
+ Forward UI navigation
+
+
+ Переключить полноэкранный режим
+
+
+ Клонировать представление
+ Clone current view to another display
+
+
+ Быстро сохранить журнал
+
+
+ Журнал сеансов
+
+
+ Задать стандартную страницу
+
+
+ Команда отменена.
+
+
+ Введите командную строку
+ Placeholder for command line input text box
+
+
+ Ошибка при запуске командной строки: {0}
+
+
+ Командная строка
+
+
+ Командная строка
+ Title for command line page
+
+
+ Время ожидания команды истекло через {0} с отсутствия выходных данных.
+
+
+ Имя компьютера
+
+
+ Подтверждение
+
+
+ Подключаться автоматически
+
+
+ Подключаться автоматически
+
+
+ Подключить
+
+
+ Подключить
+
+
+ Подключенные устройства
+
+
+ Ошибка обновления. Подключитесь к сети Wi-Fi и повторите попытку.
+ App update error, poor connection
+
+
+ Продолжить
+
+
+ Не удалось проанализировать выходные данные команды
+
+
+ Текущий круг
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ Страница приложения по умолчанию
+
+
+ Язык по умолчанию выбирается автоматически…
+
+
+ Удалено несколько журналов ({0})
+ {0} is plural number of logs
+
+
+ Удален {0} журнал
+ {0} is singular number of logs
+
+
+ Удалить {0} журнал?
+ {0} is singular number of logs
+
+
+ Удалить следующее количество журналов: {0}?
+ {0} is plural number of logs
+
+
+ Нажата кнопка "Удалить"
+
+
+ Код устройства Azure
+ Field label
+
+
+ Центр IoT Azure
+ Field label
+
+
+ Перейти на страницу устройств
+
+
+ IP-адрес: {0}
+Версия ОС: {1}
+Версия приложения: {2}
+
+
+ Версия приложения
+ Field label
+
+
+ Имя устройства
+ Field label
+
+
+ IP-адрес
+ Field label
+
+
+ Сеть
+ Field label
+
+
+ Версия ОС
+ Label for OS Version field in main page
+
+
+ для начала разработки
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Информация об устройстве
+
+
+ Посетите веб-сайт
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Чтобы открыть эту страницу, требуются API Windows Device Portal (WDP). Войдите, используя учетные данные WDP, чтобы продолжить.
+
+
+ Возникла проблема со входом в систему.
+
+
+ Вы успешно вошли в портал устройств!
+
+
+ Проверка учетных данных портала устройств...
+
+
+ Произошла ошибка при получении прогноза погоды. Повторить попытку?
+
+
+ Прямые подключения
+
+
+ Отключить
+ This disconnects the connected network
+
+
+ Язык интерфейса обновлен: {0}
+
+
+ Домен
+
+
+ Загрузка завершена!
+ App update status
+
+
+ Сбой загрузки. Повторите попытку позже!
+
+
+ Скачивание обновления
+ App update status
+
+
+ Скачать обновления
+
+
+ Рисование
+
+
+ "На адрес {1} отправлены журналы ({0})"
+ {0} is plural number of logs, {1} is email address
+
+
+ "На адрес {1} отправлен {0} журнал"
+ {0} is singular number of logs, {1} is email address
+
+
+ Отправка журнала по электронной почте
+
+
+ Вы хотите отправить файл "{0}" себе по электронной почте?
+ {0} is filename
+
+
+ При отправке себе журнала по электронной почте возникла проблема: {0}
+ {0} is exception message
+
+
+ Журналы можно найти на странице "Журналы"
+
+
+ "Отправить {0} журнал себе по электронной почте?"
+ {0} is singular number of logs
+
+
+ При отправке себе журналов по электронной почте возникла проблема: {0}
+ {0} is an exception message
+
+
+ Отправить журналы ({0}) себе по электронной почте?
+ {0} is plural number of logs
+
+
+ Отправить журналы по электронной почте
+
+
+ Выбран адрес электронной почты
+
+
+ Включить процессор командной строки
+
+
+ Заставка
+ Toggle switch for enabling the screensaver
+
+
+ Время окончания
+
+
+ Ошибка
+
+
+ При получении сведений о погоде произошла ошибка
+
+
+ Ethernet
+ Field label
+
+
+ GUID поставщика трассировки событий Windows: {0}
+ Format string for app settings page
+
+
+ Выполнение команд в роли DefaultAccount
+
+
+ Обзор
+
+
+ Файл сохранен: {0}
+ {0} is a filename
+
+
+ Фокус-тестирование
+ Device servicing flighting
+
+
+ Информация о фокус-тестировании
+ Device servicing flighting
+
+
+ Круг тестируемых возможностей изменен на {0}!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ При изменении круга тестируемых возможностей возникла проблема
+
+
+ Прогноз
+ Weather forecast
+
+
+ Вы собираетесь войти в полноэкранный режим. Чтобы выйти из него, необходимо нажать клавишу [Esc] на клавиатуре. Продолжить?
+
+
+ Полноэкранный режим
+
+
+ Нажмите клавишу [Esc] для выхода из полноэкранного режима.
+
+
+ Общие
+
+
+ Плата IoTEnterprise
+ A generic board name
+
+
+ GitHub
+
+
+ Справка
+
+
+ Справка
+
+
+ Справка
+
+
+ Язык ввода с клавиатуры обновлен: {0}
+
+
+ Установка завершена!
+ App update status
+
+
+ Сбой установки. Повторите попытку позже!
+
+
+ Установка обновления
+ App update status
+
+
+ Установить обновления
+
+
+ Недопустимые учетные данные
+
+
+ Недопустимое расположение: "{0}".
+ Format string for app settings page
+
+
+ Недопустимое значение: "{0}". Значение должно быть больше или равно 1.
+ Format string for app settings page
+
+
+ Недопустимое значение: "{0}".
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ Раскладка клавиатуры
+ Field label
+
+
+ Перезапустить приложение, чтобы применить новые параметры
+
+
+ Язык
+
+
+ Язык
+ Field label
+
+
+ Загрузка...
+
+
+ Загрузка сведений о погоде...
+
+
+ Журнал отправлен на адрес {0}
+ {0} is email address
+
+
+ Журнал сохранен здесь: {0}
+ {0} is filename
+
+
+ Журналы
+
+
+ Журналы
+
+
+ Имя устройства
+ Field label
+
+
+ IP-адрес
+ Field label
+
+
+ Версия ОС
+ Label for OS Version field in main page
+
+
+ Это тестовый образ Windows 10 IoT Enterprise, созданный только для моделирования. Если вы хотите получать прибыль с его помощью, воспользуйтесь настраиваемым средством для пакетного применения образов, чтобы оптимизировать защиту на этом устройстве.
+ Maker Imager Security Notice
+
+
+ Маркер службы карт Bing
+
+
+ Требуется маркер службы карт Bing
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com, Hotmail, Live.com, MSN
+
+
+ Учетная запись Майкрософт (MSA)
+
+
+ Сейчас воспроизводится
+ Music player page status text (currently playing)
+
+
+ Выберите песню и нажмите "Воспроизвести".
+ Music player page status text (default)
+
+
+ Добавьте один или несколько звуковых файлов в папку "Музыка".
+Вы можете добавить музыку на портале устройств Windows в разделе "Приложения" > "Проводник".
+ Music player page instructions text
+
+
+ Загрузка музыки
+ Music player page loading panel text
+
+
+ Загрузка
+ Music player page status text (loading)
+
+
+ Музыка не найдена
+ Music player page no music found prompt text
+
+
+ Повторить попытку
+ Music player page reload button text (no files prompt)
+
+
+ Музыка
+
+
+ Музыка
+
+
+ Приостановлено
+ Music player page status text (paused)
+
+
+ Воспроизведение
+ Music player page status text (playing)
+
+
+ Войти
+
+
+ Неизвестно
+
+
+ Меню
+
+
+ Сетевые адаптеры
+
+
+ Подключено
+
+
+ Подключено
+
+
+ Проверка требований сети
+
+
+ Проверка требований сети
+
+
+ Ограниченный доступ к Интернету
+
+
+ Локальная сеть и Интернет
+
+
+ Только локальная сеть
+
+
+ Отсутствует подключение
+
+
+ СВЕДЕНИЯ О СЕТИ
+
+
+ Нет доступа к сети
+
+
+ Введите ключ безопасности сети
+
+
+ Введите ключ безопасности сети
+
+
+ Сеть и Wi-Fi
+
+
+ Сеть и Wi-Fi
+
+
+ Просмотреть свойства сети
+
+
+ Свойства сети
+
+
+ Сейчас вы будете перенаправлены на портал перехвата этой сети Wi-Fi. Продолжить?
+
+
+ Перенаправление сети
+
+
+ Далее
+
+
+ Далее
+
+
+ Учетные записи не найдены
+
+
+ Нет
+
+
+ нет имени устройства
+
+
+ отсутствует подключение к Интернету
+
+
+ Не выбран ни один журнал
+
+
+ Музыка не найдена
+ Music player page panel text
+
+
+ Ничего не найдено
+
+
+ Нет ожидающих обновлений для загрузки.
+ App update status
+
+
+ Нет ожидающих обновлений для установки.
+ App update status
+
+
+ Н/Д
+
+
+ Уведомления
+
+
+ Уведомления
+
+
+ Новые обновления не найдены.
+ Format string displayed when no app updates are found
+
+
+ ОК
+ Button content text for the Bluetooth settings page
+
+
+ Выберите язык
+
+
+ Давайте подключимся
+
+
+ Добро пожаловать в Windows 10 IoT Базовую
+
+
+ Давайте разберемся с некоторыми основными моментами.
+
+
+ Добро пожаловать в Windows 10 IoT Базовую
+
+
+ ИД выпуска ОС
+
+
+ Выпуск ОС
+
+
+ Информация об ОС
+
+
+ Информация об ОС
+
+
+ Недоступно
+ Text shown when we cannot retrieve the OS Version
+
+
+ Версия ОС
+
+
+ Пакеты
+ Software packages
+
+
+ Установленные пакеты
+ Software packages
+
+
+ Параметры страниц
+
+
+ Страницы
+
+
+ Пароль
+
+
+ Загрузка изображений
+ Default text when no images are available
+
+
+ Добавьте изображения в папку "Изображения".
+Можно добавить изображения на портале устройств Windows в разделе "Приложения" > "Проводник".
+
+
+ Изображения не найдены
+ Default text when no images are available
+
+
+ Платформа
+
+
+ Воспроизведение
+
+
+ Параметры электропитания
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ Основные: отправляются только сведения о вашем устройстве, его настройках, возможностях и исправности.
+
+
+ Полный: помимо диагностических данных с базового уровня, отправляются сведения о посещаемых веб-сайтах и способах использования приложений и функций, а также дополнительная информация о работоспособности и действиях на устройстве и расширенные отчеты об ошибках.
+
+
+ Не удалось изменить этот параметр конфиденциальности. Проверьте имя пользователя и пароль и повторите попытку.
+
+
+ Выберите объем диагностических данных, которые следует отправлять в корпорацию Майкрософт. Диагностические данные позволяют поддерживать Windows в безопасном и актуальном состоянии, устранять неполадки и улучшать продукты. Степень безопасности и исправность устройства не зависит от того, какой объем диагностических данных выбран.
+
+
+ Диагностические данные
+ Label for Setting item to control Privacy
+
+
+ Введите свои учетные данные, чтобы установить уровень конфиденциальности на этом устройстве.
+
+
+ Выбор уровня конфиденциальности
+
+
+ Обновить
+ Refresh button
+
+
+ Повторить песню
+ Music player page repeat toggle text
+
+
+ Перезапустить
+
+
+ Перезапуск
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ Использование: команда RunAsAdmin
+
+Примеры:
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ Сохранить
+
+
+ Коэффициент масштабирования
+
+
+ Выделить все
+
+
+ Отправить телеметрию
+
+
+ Недоступно
+
+
+ Журнал сеансов
+
+
+ Возникла проблема при выборе "{0}" в качестве страницы по умолчанию.
+ Format string for app settings page
+
+
+ Параметры
+
+
+ В случайном порядке
+ Music player page shuffle toggle text
+
+
+ Завершение работы
+
+
+ Завершение работы
+ Shutdown entry in the shutdown menu
+
+
+ Чтобы использовать эту функцию, войдите в свою учетную запись Azure AD.
+
+
+ Пропустить
+
+
+ Пропустить этот шаг
+
+
+ Интервал слайд-шоу (сек)
+
+
+ Слайд-шоу
+
+
+ Слайд-шоу
+
+
+ Пуск
+
+
+ Пуск
+
+
+ Время начала
+
+
+ Состояние
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ Отправить
+
+
+ Выполнено
+
+
+ Система
+
+
+ При попытке обновления параметров системы возникла проблема.
+ Used within system settings
+
+
+ Уровень телеметрии
+
+
+ Телеметрия
+
+
+ Протестировать крупное уведомление
+
+
+ Протестировать уведомление
+
+
+ Windows 10 IoT — операционная система из семейства Windows 10, благодаря которой Интернет вещей получает эффективные возможности, функции безопасности и легкость управления, присущие корпоративным решениям. В этой системе используются такие преимущества Windows, как взаимодействие со встроенными устройствами, экосистема и подключение к облаку. Это позволяет организациям создать собственный Интернет вещей на основе безопасных устройств, которые предусматривают быстрое развертывание, легкое управление и беспроблемное встраивание в общую стратегию использования облачных технологий.
+
+
+ Высота плитки
+
+
+ Персонализация
+
+
+ Ширина плитки
+
+
+ Истекло время ожидания подключения
+
+
+ Часовой пояс обновлен: {0}
+
+
+ Ошибка: не удается установить связь со службой погоды
+
+
+ Сбой обновления из-за неизвестной ошибки.
+ App update error, unknown
+
+
+ Отменить выбор всех элементов
+
+
+ Неопределенная ошибка
+
+
+ Дополнительные параметры
+
+
+ Проверить сейчас
+
+
+ Установить сейчас
+
+
+ {0} ожидающее обновление
+ {0} is singular amount of updates
+
+
+ Найдены новые обновления: {0}.
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ Ожидающих обновлений: {0}
+ {0} is plural amount of updates
+
+
+ Использовать значки плитки MDL2
+
+
+ Использовать пароль
+
+
+ Имя пользователя
+
+
+ Портал устройств Windows
+
+
+ Параметры портала устройств
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Портал устройств Windows
+
+
+ Текущее расположение ({0}, {1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ Ваше расположение
+
+
+ Ваше расположение
+ Label for map pin
+
+
+ Неизвестное расположение
+ Label for map pin
+
+
+ Датчик:
+ Label for temperature sensor output
+
+
+ Погода
+
+
+ Ошибка загрузки страницы погоды.
+
+Нажмите кнопку "Обновить" в нижней правой части экрана, чтобы перезагрузить страницу.
+
+Если у вас нет ключей API приложения "Погода", перейдите на веб-сайт weatherunlocked.com. Сохраните ключи в "WeatherTokens.config" папке локального состояния приложения. Затем обновите страницу.
+
+
+ Данные о погоде предоставляются службой
+
+
+ Погода
+
+
+ Введите веб-адрес
+
+
+ Веб-браузер
+
+
+ Добро пожаловать в Windows IoT Базовую
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ Обновить
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ Последняя проверка:
+ For a timestamp
+
+
+ Последнее обновление:
+ For a timestamp
+
+
+ Обновленное состояние:
+
+
+ Сообщение о состоянии:
+
+
+ Центр обновления Windows
+
+
+ Центр обновления Windows
+
+
+ Недопустимый рабочий каталог: {0}
+
+
+ WPS
+
+
+ Разрешить этому приложению получать доступ к вашему местоположению
+
+
+ Выберите параметры, а затем нажмите "Принять". Эти параметры можно изменить в любое время.
+
+
+ Разрешить корпорации Майкрософт использовать данные о вашем расположении
+
+
+ Автоматическое продолжение...
+
+
+ Принять
+
+
+ Разрешить {0} доступ к сведениям о вашем точном местоположении?
+ {0} is the name of a page
+
+
+ Местоположение
+
+
+ Позже вы можете изменить этот параметр, перейдя в раздел "Параметры" > "Разрешения".
+
+
+ Нет
+
+
+ Да
+
+
+ Вы не сможете автоматически получать карты и прогноз погоды на основе текущего местоположения или пользоваться другими службами, которым для правильной работы требуется ваше местоположение.
+
+
+ Получите функциональные возможности на основе местоположения, например предоставление местного прогноза погоды и карт. Корпорация Майкрософт будет использовать данные о вашем местоположении для улучшения служб определения местоположения.
+
+
+ Отправляются только сведения о вашем устройстве, его настройках, возможностях и исправности. Диагностические данные используются, чтобы поддерживать Windows в безопасном и актуальном состоянии, устранять неполадки и улучшать продукты. Степень безопасности устройства не зависит от того, какой уровень диагностических данных выбран — базовый или полный. Кроме того, и на том, и на другом уровне устройство будет работать в обычном порядке.
+
+
+ Базовый
+
+
+ Помимо диагностических данных с базового уровня, отправляются сведения о посещаемых веб-сайтах и способах использования приложений и функций, а также дополнительная информация о работоспособности и применении устройства и расширенные отчеты об ошибках. Диагностические данные помогают обеспечивать безопасность и актуальность Windows, устранять неполадки и улучшать продукты. Степень безопасности устройства не зависит от того, какой выбран уровень — базовый или полный. Кроме того, и на том, и на другом уровне устройство будет работать в обычном порядке.
+
+
+ Полный
+
+
+ Выберите параметр конфиденциальности для своего устройства, а затем нажмите кнопку "Принять", чтобы сохранить его.
+
+
+ Отправлять данные диагностики в корпорацию Майкрософт
+
+
+ Диагностика
+
+
+ Если доступ разрешен, вы разрешите этому приложению использовать возможности устройства для определения вашего местоположения, а корпорация Майкрософт будет использовать данные о местоположении для улучшения служб определения местоположения. Если доступ запрещен, Windows заблокирует доступ к вашему местоположению только для этого приложения.
+
+
+ Узнайте свои настройки конфиденциальности
+
+
+ Узнайте, как этот параметр влияет на конфиденциальность.
+
+
+ Дополнительные сведения об этих параметрах
+
+
+ Заявление о конфиденциальности
+
+
+ Да
+
+
+ Да
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-TW/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-TW/Resources.resw
index df07034f3..c1b73a8a2 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-TW/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-TW/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- 使用 AAD v2
-
-
- 存取已撤銷
-
-
- 描述:
-
-
- DHCP 伺服器:
-
-
- DNS:
-
-
- 閘道位址:
-
-
- IPv4 位址:
-
-
- 名稱:
-
-
- 實體位址:
-
-
- 子網路遮罩:
-
-
- 類型:
-
-
- 應用程式版本
-
-
- 應用程式
-
-
- 您即將啟動外部應用程式。您必須使用 Windows 裝置入口網站回到此應用程式。是否要繼續？
- Dialog prompt for launching external apps
-
-
- App
-
-
- App 設定
-
-
- 設定使用時間，讓我們知道您平常使用此裝置的時間。我們不會在使用時間期間自動重新開機。
-
-
- 無法儲存新的開始及結束時間，因為它們是相同的。請選擇新的時間，或關閉功能。
-
-
- 進階選項
- Advanced section title
-
-
- 控制每個擷取、下載和安裝更新步驟。
-
-
- 自動更新選項
- Auto-Update section title
-
-
- 讓 App 在使用時間外安裝 App 更新
-
-
- App 更新
- App update display dialog header
-
-
- 上次檢查: {0} {1}
- {0} is date, {1} is time
-
-
- 無法判斷上次檢查更新的時間
-
-
- App 更新
- Label for setting item to check for app updates
-
-
- 登入 MSA 和 AAD
-
-
- 請使用您的組織帳戶登入 AAD。
-
-
- Azure AD (AAD) 登入
-
-
- AAD
-
-
- 驗證 Microsoft Graph 與其他資源
-
-
- 僅驗證 Microsoft Graph
-
-
- 取消
-
-
- 您的組織帳戶
-
-
- 如果您在任何時候受困，無法結束登入精靈，請等待 {0} 秒後應該會返回應用程式。
-
-
- 正在登入...
-
-
- 正在登出...
-
-
- 在這裡登入您的 Microsoft 帳戶
-
-
- Microsoft 帳戶 (MSA) 登入
-
-
- MSA
-
-
- 驗證
-
-
- Microsoft 登入
-
-
- 登入失敗 ({0})
-
-
- 登入成功 ({0})
-
-
- 登入
-
-
- 已登出: {0}
-
-
- 登出
-
-
- 自動播放
- Music player page auto-play toggle text
-
-
- 自動縮放
-
-
- 更新失敗，因為電力偏低。
- App update error, low battery
-
-
- 正在嘗試與 {0} ({1}) 配對。
- Text displayed when a Bluetooth pairing attempt starts
-
-
- 正在與 {0} ({1}) 配對。
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- 裝置上顯示的 PIN 是否符合: {0}?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- 不明
- Text displayed when the Bluetooth device name is unknown
-
-
- 目前已配對
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 準備好進行配對
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 未知的狀態
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 請在您要配對的裝置上輸入下列 PIN: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- 輸入 PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- 來自 {0} ({1}) 的連入配對要求。
- Text displayed when an inbound pairing request is received
-
-
- 此裝置已針對連入配對註冊。(支援的模式: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- 無法針對連入配對註冊
- Text displayed when Inbound pairing handler registration fails
-
-
- 已順利針對連入配對註冊。(支援的模式: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- 您輸入的 PIN 不正確。
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- 在此裝置上找不到可用的藍牙介面卡: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- 配對
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- 無法與 {0} ({1}) 配對。
- Text displayed when a Bluetooth pairing attempt fails
-
-
- 已順利與 {0} ({1}) 配對。
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- 藍牙
- Title for Bluetooth settings page
-
-
- 預設
- Text label for the corresponding device pairing protection level
-
-
- 加密與驗證
- Text label for the corresponding device pairing protection level
-
-
- 加密
- Text label for the corresponding device pairing protection level
-
-
- 無
- Text label for the corresponding device pairing protection level
-
-
- 您的裝置目前可供探索，而且已準備好與其他藍牙裝置配對。
- Text displayed when StartWatcher is invoked
-
-
- 您的裝置不會再搜尋其他藍牙裝置。
- Text displayed when StopWatcher is invoked
-
-
- 解除配對
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- 無法從 {0} ({1}) 解除配對。
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- 已順利從 {0} ({1}) 解除配對。
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- 藍牙
- Header label for the Bluetooth watcher toggle switch
-
-
- 首頁
-
-
- 網頁瀏覽器
-
-
- 取消
-
-
- 目前不支援變更目錄。請在您的命令中使用完整路徑。
-
-
- 時區
- Time zone text
-
-
- 正在檢查更新...
- App update status
-
-
- 檢查更新
-
-
- 清除帳戶
-
-
- 清除您的帳戶時發生問題
-
-
- 這將會清除下列的 Windows 帳戶:
-{0}
-
-要繼續嗎?
-
-
- 已清除帳戶
-
-
- 正在清除帳戶...
-
-
- 清除
-
-
- 關閉
-
-
- 不允許裝置執行命令列處理程式。
-若要啟用此功能，請在裝置上以「系統管理員」身分執行以下命令:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-您可以在 IoT Windows 裝置入口網站的 [處理程序] 頁面中執行此命令，或使用 PowerShell 連線到您的 Windows IoT 裝置。
-如需詳細資訊，請瀏覽 http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- 無法以系統管理員身分執行命令: {0}
-
-
- 無法啟用裝置上的命令列處理程式 (cmd.exe): {0}
-
-
- 已成功啟用裝置上的命令列處理程式 (cmd.exe)。
-
-
- 磚色彩
-
-
- 返回
- Back UI navigation
-
-
- 顯示裝置資訊
-
-
- 向前
- Forward UI navigation
-
-
- 切換全螢幕
-
-
- 複製檢視
- Clone current view to another display
-
-
- 快速儲存記錄
-
-
- 工作階段記錄
-
-
- 設定預設頁面
-
-
- 已取消命令。
-
-
- 輸入命令列
- Placeholder for command line input text box
-
-
- 執行命令列時發生錯誤: {0}
-
-
- 命令列
-
-
- 命令列
- Title for command line page
-
-
- 在沒有輸出 {0} 秒後，命令逾時。
-
-
- 電腦名稱
-
-
- 確認
-
-
- 自動連線
-
-
- 自動連線
-
-
- 連線
-
-
- 連線
-
-
- 已連線的裝置
-
-
- 更新失敗。請連線到 Wi-Fi，然後再試一次。
- App update error, poor connection
-
-
- 繼續
-
-
- 無法剖析命令輸出
-
-
- 目前通道
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- 預設 App 頁面
-
-
- 我們將會自動選擇預設語言...
-
-
- 已刪除 {0} 個記錄
- {0} is plural number of logs
-
-
- 已刪除 {0} 個記錄
- {0} is singular number of logs
-
-
- 要刪除 {0} 個記錄嗎?
- {0} is singular number of logs
-
-
- 要刪除 {0} 個記錄嗎?
- {0} is plural number of logs
-
-
- 已刪除選取項目
-
-
- Azure 裝置識別碼
- Field label
-
-
- Azure IoT 中樞
- Field label
-
-
- 前往裝置頁面
-
-
- IP 位址: {0}
-作業系統版本: {1}
-應用程式版本: {2}
-
-
- App 版本
- Field label
-
-
- 裝置名稱
- Field label
-
-
- IP 位址
- Field label
-
-
- 網路
- Field label
-
-
- OS 版本
- Label for OS Version field in main page
-
-
- 開始開發
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 裝置資訊
-
-
- 瀏覽
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 您嘗試存取的頁面要求使用 Windows 裝置入口網站 (WDP) API。請使用 WDP 認證登入以繼續。
-
-
- 登入時發生問題。
-
-
- 已成功登入裝置入口網站!
-
-
- 正在驗證裝置入口網站認證...
-
-
- 取得天氣時發生問題，再試一次?
-
-
- 直接連線
-
-
- 中斷連線
- This disconnects the connected network
-
-
- 已更新顯示語言: {0}
-
-
- 網域
-
-
- 下載完成!
- App update status
-
-
- 下載失敗。請稍後再試!
-
-
- 正在下載更新
- App update status
-
-
- 下載更新
-
-
- 繪圖
-
-
- 「{0} 個記錄檔已傳送至 {1}」
- {0} is plural number of logs, {1} is email address
-
-
- 「{0} 個記錄已傳送至 {1}」
- {0} is singular number of logs, {1} is email address
-
-
- 電子郵件記錄
-
-
- 您想要以電子郵件傳送 {0} 給自己嗎?
- {0} is filename
-
-
- 以電子郵件傳送您的記錄時發生問題: {0}
- {0} is exception message
-
-
- 您可在 [記錄] 頁面找到您的記錄
-
-
- 「要傳送 {0} 個記錄給您自己嗎?」
- {0} is singular number of logs
-
-
- 以電子郵件傳送您的記錄時發生問題: {0}
- {0} is an exception message
-
-
- 要以電子郵件傳送 {0} 個記錄檔給自己嗎?
- {0} is plural number of logs
-
-
- 電子郵件記錄
-
-
- 已選取電子郵件
-
-
- 啟用命令列處理程式
-
-
- 螢幕保護裝置
- Toggle switch for enabling the screensaver
-
-
- 結束時間
-
-
- 錯誤
-
-
- 擷取天氣資訊時發生問題
-
-
- 乙太網路
- Field label
-
-
- ETW 提供者 GUID: {0}
- Format string for app settings page
-
-
- 正在以 DefaultAccount 的身分執行命令
-
-
- 探索
-
-
- 已儲存檔案: {0}
- {0} is a filename
-
-
- 正式發行前小眾測試
- Device servicing flighting
-
-
- 正式發行前小眾測試資訊
- Device servicing flighting
-
-
- 正式發行前小眾測試版通道已變更至 {0}!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- 變更您的正式發行前小眾測試版通道時發生錯誤
-
-
- 預測
- Weather forecast
-
-
- 您即將進入全螢幕模式。若要結束，您必須按鍵盤上的 [Esc]。要繼續嗎?
-
-
- 全螢幕模式
-
-
- 按下 [Esc] 結束全螢幕模式。
-
-
- 一般
-
-
- IoTEnterprise 電路板
- A generic board name
-
-
- GitHub
-
-
- 說明
-
-
- 說明
-
-
- 說明
-
-
- 已更新輸入鍵盤語言: {0}
-
-
- 安裝完成!
- App update status
-
-
- 安裝失敗。請稍後再試!
-
-
- 正在安裝更新
- App update status
-
-
- 安裝更新
-
-
- 無效的認證
-
-
- '{0}' 是無效的位置。
- Format string for app settings page
-
-
- '{0}' 是無效的值。值必須大於或等於 1。
- Format string for app settings page
-
-
- '{0}' 是無效的值。
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- 鍵盤配置
- Field label
-
-
- 重新啟動這個應用程式以套用新設定
-
-
- 語言
-
-
- 語言
- Field label
-
-
- 正在載入...
-
-
- 正在載入天氣資訊...
-
-
- 記錄已經傳送至 {0}
- {0} is email address
-
-
- 記錄已儲存至: {0}
- {0} is filename
-
-
- 記錄
-
-
- 記錄
-
-
- 裝置名稱
- Field label
-
-
- IP 位址
- Field label
-
-
- 作業系統版本
- Label for OS Version field in main page
-
-
- 這是專為建立原型而設計的 Windows 10 IoT 核心版測試映像。如果您打算商業化，則必須使用自訂 FFU，以獲得最佳安全性。
- Maker Imager Security Notice
-
-
- Bing 地圖服務權杖
-
-
- 需要 Bing 地圖服務權杖
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com、Hotmail、Live.com、MSN
-
-
- Microsoft 帳戶 (MSA)
-
-
- 目前正在播放
- Music player page status text (currently playing)
-
-
- 選取一首歌曲，然後按一下 [播放]。
- Music player page status text (default)
-
-
- 請將一個或多個音訊檔案新增至 [音樂] 資料夾。
-您可以在 Windows 裝置入口網站使用 [App] > [檔案總管] 新增音樂。
- Music player page instructions text
-
-
- 正在載入音樂
- Music player page loading panel text
-
-
- 正在載入
- Music player page status text (loading)
-
-
- 找不到任何音樂
- Music player page no music found prompt text
-
-
- 再試一次
- Music player page reload button text (no files prompt)
-
-
- 音樂
-
-
- 音樂
-
-
- 已暫停
- Music player page status text (paused)
-
-
- 正在播放
- Music player page status text (playing)
-
-
- 登入
-
-
- 不明
-
-
- 功能表
-
-
- 網路介面卡
-
-
- 已連線
-
-
- 已連線
-
-
- 正在檢查網路需求
-
-
- 正在檢查網路需求
-
-
- 受限的網際網路存取
-
-
- 本機和網際網路存取
-
-
- 僅限本機網路存取
-
-
- 沒有連線能力
-
-
- 網路資訊
-
-
- 網路無法使用
-
-
- 輸入網路安全性金鑰
-
-
- 輸入網路安全性金鑰
-
-
- 網路與 Wi-Fi
-
-
- 網路與 Wi-Fi
-
-
- 檢視網路內容
-
-
- 網路內容
-
-
- 您即將被重新導向到此 Wi-Fi 網路的網頁驗證入口網站。要繼續嗎?
-
-
- 網路重新導向
-
-
- 下一步
-
-
- 下一步
-
-
- 找不到帳戶
-
-
- 否
-
-
- 無裝置名稱
-
-
- 沒有網際網路連線
-
-
- 未選取任何記錄
-
-
- 找不到任何音樂
- Music player page panel text
-
-
- 找不到任何網路
-
-
- 沒有可下載的擱置中更新。
- App update status
-
-
- 沒有可安裝的擱置中更新。
- App update status
-
-
- N/A
-
-
- 通知
-
-
- 通知
-
-
- 找不到新更新。
- Format string displayed when no app updates are found
-
-
- 確定
- Button content text for the Bluetooth settings page
-
-
- 選擇語言
-
-
- 讓我們開始連線
-
-
- 歡迎使用 Windows 10 IoT 核心版
-
-
- 讓我們先了解一些基礎知識。
-
-
- 歡迎使用 Windows 10 IoT 核心版
-
-
- 作業系統版本識別碼
-
-
- 作業系統版本
-
-
- 作業系統資訊
-
-
- 作業系統資訊
-
-
- 無法使用
- Text shown when we cannot retrieve the OS Version
-
-
- 作業系統版本
-
-
- 套件
- Software packages
-
-
- 已安裝套件
- Software packages
-
-
- 頁面設定
-
-
- 頁面
-
-
- 密碼
-
-
- 正在載入圖片
- Default text when no images are available
-
-
- 請將影像新增至 [圖片] 資料夾。
-您可以在 Windows 裝置入口網站使用 [App] > [檔案總管] 新增影像。
-
-
- 找不到影像
- Default text when no images are available
-
-
- 平台
-
-
- 播放
-
-
- 電源選項
- Label for Setting item to control Power (shutdown/restart)
-
-
- 基本：傳送與您的裝置、設定和功能相關的資訊，並確認是否正確執行。
-
-
- 完整：傳送所有基本診斷資料，您瀏覽的網站和使用應用程式與功能的方式，以及有關裝置健康情況、裝置活動和更進一步的錯誤報告等額外資訊。
-
-
- 我們無法變更隱私權設定。請驗證您的使用者名稱和密碼，並再試一次。
-
-
- 選取您想傳送給 Microsoft 的診斷資料數量。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
-
-
- 診斷資料
- Label for Setting item to control Privacy
-
-
- 請輸入您的認證，設定此裝置的隱私權等級。
-
-
- 設定您的隱私權等級
-
-
- 重新整理
- Refresh button
-
-
- 重複歌曲
- Music player page repeat toggle text
-
-
- 重新啟動
-
-
- 重新啟動
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- 使用方式: RunAsAdmin command
-
-範例:
-> RunAsdmin TZUTIL /s "Pacific Standard Time"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- 儲存
-
-
- 縮放係數
-
-
- 全選
-
-
- 傳送遙測
-
-
- 無法使用
-
-
- 工作階段記錄
-
-
- 將預設頁面設定為 {0} 時發生問題。
- Format string for app settings page
-
-
- 設定
-
-
- 隨機播放
- Music player page shuffle toggle text
-
-
- 關機
-
-
- 關機
- Shutdown entry in the shutdown menu
-
-
- 登入您的 Azure AD 帳戶以使用此功能。
-
-
- 跳過
-
-
- 跳過此步驟
-
-
- 投影片放映間隔 (秒)
-
-
- 幻燈片秀
-
-
- 幻燈片秀
-
-
- 開始
-
-
- 開始
-
-
- 開始時間
-
-
- 狀態
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- 提交
-
-
- 成功
-
-
- 系統
-
-
- 嘗試更新您的系統設定時發生問題。
- Used within system settings
-
-
- 遙測層級
-
-
- 遙測
-
-
- 測試大型通知
-
-
- 測試通知
-
-
- Windows 10 IoT 是 Windows 10 家族的成員，它為物聯網帶來了企業級的助力、安全性和管理性，此外亦利用了 Windows 的內嵌體驗、生態系統及雲端連線能力，讓組織可以安全、可快速佈建、可輕鬆管理，且與整體雲端策略完美匹配的裝置來打造自己的物聯網。
-
-
- 磚高度
-
-
- 個人化
-
-
- 磚寬度
-
-
- 連線逾時
-
-
- 已更新時區: {0}
-
-
- 錯誤: 無法與天氣服務進行通訊
-
-
- 由於不明錯誤，更新失敗。
- App update error, unknown
-
-
- 取消全選
-
-
- 未指定的失敗
-
-
- 進階選項
-
-
- 立即檢查
-
-
- 立即安裝
-
-
- {0} 個暫止的更新
- {0} is singular amount of updates
-
-
- 找到 {0} 個新更新。
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} 個暫止的更新
- {0} is plural amount of updates
-
-
- 使用 MDL2 磚圖示
-
-
- 使用密碼
-
-
- 使用者名稱
-
-
- Windows 裝置入口網站
-
-
- 裝置入口網站設定
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows 裝置入口網站
-
-
- 目前位置 ({0}，{1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- 您的位置
-
-
- 您的位置
- Label for map pin
-
-
- 未知的位置
- Label for map pin
-
-
- 感應器:
- Label for temperature sensor output
-
-
- 天氣
-
-
- 載入天氣頁面時發生錯誤。
-
-請按畫面右下方的 [重新整理] 按鈕，重新載入此頁面。
-
-如果您沒有天氣 API 金鑰，請瀏覽 weatherunlocked.com。將金鑰儲存在應用程式本地狀態資料夾中的 "WeatherTokens.config" 中。然後重新整理頁面。
-
-
- 天氣資料提供者:
-
-
- 天氣
-
-
- 輸入網址
-
-
- 網頁瀏覽器
-
-
- 歡迎使用 Windows IoT 核心版
-
-
- Wi-Fi
- Label for Wi-Fi list in options page
-
-
- 重新整理
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 上次檢查：
- For a timestamp
-
-
- 上次更新：
- For a timestamp
-
-
- 更新狀態：
-
-
- 狀態訊息：
-
-
- Windows Update
-
-
- Windows Update
-
-
- 無效的工作目錄: {0}
-
-
- WPS
-
-
- 允許這個應用程式存取您的位置
-
-
- 選擇設定，選取 [接受] 以保存。您可以隨時變更這些設定。
-
-
- 讓 Microsoft 使用您所在的位置
-
-
- 自動繼續…
-
-
- 接受
-
-
- 是否讓 {0} 存取您的精確位置？
- {0} is the name of a page
-
-
- 位置
-
-
- 若要稍後變更，請至設定 > 權限。
-
-
- 否
-
-
- 是
-
-
- 您無法體驗以位置為基礎的相關服務，例如地圖和天氣，或其他需要取得您所在地才能運作的服務。
-
-
- 取得像地圖與天氣等以位置為基礎的相關服務。讓應用程式取得您的所在位置。Microsoft 將使用您的位置資料改善位置相關服務。
-
-
- 僅傳送有關您裝置的設定、功能以及是否正常運行等資訊。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
-
-
- 基本
-
-
- 傳送所有基本診斷資料，您瀏覽的網站和使用應用程式與功能的方式，以及有關裝置健康情況、裝置活動狀況和更進一步的錯誤報告等額外資訊。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
-
-
- 完整
-
-
- 為您的裝置選擇隱私權設定，然後選取 [接受] 來儲存它。
-
-
- 傳送診斷資料給 Microsoft
-
-
- 診斷
-
-
- 若您允許存取，您將授權此應用程式使用您裝置上的功能，以此判定您的位置， Microsoft 將使用您位置的資料來改善位置服務。拒絕存取會阻止 Windows 提供位置給此應用程式。
-
-
- 了解您的隱私權選項
-
-
- 了解這項設定將如何影響您的隱私權。
-
-
- 取得更多關於這些設定的詳細資訊
-
-
- 隱私權聲明
-
-
- 是
-
-
- 是
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ 使用 AAD v2
+
+
+ 存取已撤銷
+
+
+ 描述:
+
+
+ DHCP 伺服器:
+
+
+ DNS:
+
+
+ 閘道位址:
+
+
+ IPv4 位址:
+
+
+ 名稱:
+
+
+ 實體位址:
+
+
+ 子網路遮罩:
+
+
+ 類型:
+
+
+ 應用程式版本
+
+
+ 應用程式
+
+
+ 您即將啟動外部應用程式。您必須使用 Windows 裝置入口網站回到此應用程式。是否要繼續？
+ Dialog prompt for launching external apps
+
+
+ App
+
+
+ App 設定
+
+
+ 設定使用時間，讓我們知道您平常使用此裝置的時間。我們不會在使用時間期間自動重新開機。
+
+
+ 無法儲存新的開始及結束時間，因為它們是相同的。請選擇新的時間，或關閉功能。
+
+
+ 進階選項
+ Advanced section title
+
+
+ 控制每個擷取、下載和安裝更新步驟。
+
+
+ 自動更新選項
+ Auto-Update section title
+
+
+ 讓 App 在使用時間外安裝 App 更新
+
+
+ App 更新
+ App update display dialog header
+
+
+ 上次檢查: {0} {1}
+ {0} is date, {1} is time
+
+
+ 無法判斷上次檢查更新的時間
+
+
+ App 更新
+ Label for setting item to check for app updates
+
+
+ 登入 MSA 和 AAD
+
+
+ 請使用您的組織帳戶登入 AAD。
+
+
+ Azure AD (AAD) 登入
+
+
+ AAD
+
+
+ 驗證 Microsoft Graph 與其他資源
+
+
+ 僅驗證 Microsoft Graph
+
+
+ 取消
+
+
+ 您的組織帳戶
+
+
+ 如果您在任何時候受困，無法結束登入精靈，請等待 {0} 秒後應該會返回應用程式。
+
+
+ 正在登入...
+
+
+ 正在登出...
+
+
+ 在這裡登入您的 Microsoft 帳戶
+
+
+ Microsoft 帳戶 (MSA) 登入
+
+
+ MSA
+
+
+ 驗證
+
+
+ Microsoft 登入
+
+
+ 登入失敗 ({0})
+
+
+ 登入成功 ({0})
+
+
+ 登入
+
+
+ 已登出: {0}
+
+
+ 登出
+
+
+ 自動播放
+ Music player page auto-play toggle text
+
+
+ 自動縮放
+
+
+ 更新失敗，因為電力偏低。
+ App update error, low battery
+
+
+ 正在嘗試與 {0} ({1}) 配對。
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ 正在與 {0} ({1}) 配對。
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ 裝置上顯示的 PIN 是否符合: {0}?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ 不明
+ Text displayed when the Bluetooth device name is unknown
+
+
+ 目前已配對
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 準備好進行配對
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 未知的狀態
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 請在您要配對的裝置上輸入下列 PIN: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ 輸入 PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ 來自 {0} ({1}) 的連入配對要求。
+ Text displayed when an inbound pairing request is received
+
+
+ 此裝置已針對連入配對註冊。(支援的模式: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ 無法針對連入配對註冊
+ Text displayed when Inbound pairing handler registration fails
+
+
+ 已順利針對連入配對註冊。(支援的模式: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ 您輸入的 PIN 不正確。
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ 在此裝置上找不到可用的藍牙介面卡: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ 配對
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ 無法與 {0} ({1}) 配對。
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ 已順利與 {0} ({1}) 配對。
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ 藍牙
+ Title for Bluetooth settings page
+
+
+ 預設
+ Text label for the corresponding device pairing protection level
+
+
+ 加密與驗證
+ Text label for the corresponding device pairing protection level
+
+
+ 加密
+ Text label for the corresponding device pairing protection level
+
+
+ 無
+ Text label for the corresponding device pairing protection level
+
+
+ 您的裝置目前可供探索，而且已準備好與其他藍牙裝置配對。
+ Text displayed when StartWatcher is invoked
+
+
+ 您的裝置不會再搜尋其他藍牙裝置。
+ Text displayed when StopWatcher is invoked
+
+
+ 解除配對
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ 無法從 {0} ({1}) 解除配對。
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ 已順利從 {0} ({1}) 解除配對。
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ 藍牙
+ Header label for the Bluetooth watcher toggle switch
+
+
+ 首頁
+
+
+ 網頁瀏覽器
+
+
+ 取消
+
+
+ 目前不支援變更目錄。請在您的命令中使用完整路徑。
+
+
+ 時區
+ Time zone text
+
+
+ 正在檢查更新...
+ App update status
+
+
+ 檢查更新
+
+
+ 清除帳戶
+
+
+ 清除您的帳戶時發生問題
+
+
+ 這將會清除下列的 Windows 帳戶:
+{0}
+
+要繼續嗎?
+
+
+ 已清除帳戶
+
+
+ 正在清除帳戶...
+
+
+ 清除
+
+
+ 關閉
+
+
+ 不允許裝置執行命令列處理程式。
+若要啟用此功能，請在裝置上以「系統管理員」身分執行以下命令:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+您可以在 IoT Windows 裝置入口網站的 [處理程序] 頁面中執行此命令，或使用 PowerShell 連線到您的 Windows IoT 裝置。
+如需詳細資訊，請瀏覽 http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ 無法以系統管理員身分執行命令: {0}
+
+
+ 無法啟用裝置上的命令列處理程式 (cmd.exe): {0}
+
+
+ 已成功啟用裝置上的命令列處理程式 (cmd.exe)。
+
+
+ 磚色彩
+
+
+ 返回
+ Back UI navigation
+
+
+ 顯示裝置資訊
+
+
+ 向前
+ Forward UI navigation
+
+
+ 切換全螢幕
+
+
+ 複製檢視
+ Clone current view to another display
+
+
+ 快速儲存記錄
+
+
+ 工作階段記錄
+
+
+ 設定預設頁面
+
+
+ 已取消命令。
+
+
+ 輸入命令列
+ Placeholder for command line input text box
+
+
+ 執行命令列時發生錯誤: {0}
+
+
+ 命令列
+
+
+ 命令列
+ Title for command line page
+
+
+ 在沒有輸出 {0} 秒後，命令逾時。
+
+
+ 電腦名稱
+
+
+ 確認
+
+
+ 自動連線
+
+
+ 自動連線
+
+
+ 連線
+
+
+ 連線
+
+
+ 已連線的裝置
+
+
+ 更新失敗。請連線到 Wi-Fi，然後再試一次。
+ App update error, poor connection
+
+
+ 繼續
+
+
+ 無法剖析命令輸出
+
+
+ 目前通道
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ 預設 App 頁面
+
+
+ 我們將會自動選擇預設語言...
+
+
+ 已刪除 {0} 個記錄
+ {0} is plural number of logs
+
+
+ 已刪除 {0} 個記錄
+ {0} is singular number of logs
+
+
+ 要刪除 {0} 個記錄嗎?
+ {0} is singular number of logs
+
+
+ 要刪除 {0} 個記錄嗎?
+ {0} is plural number of logs
+
+
+ 已刪除選取項目
+
+
+ Azure 裝置識別碼
+ Field label
+
+
+ Azure IoT 中樞
+ Field label
+
+
+ 前往裝置頁面
+
+
+ IP 位址: {0}
+作業系統版本: {1}
+應用程式版本: {2}
+
+
+ App 版本
+ Field label
+
+
+ 裝置名稱
+ Field label
+
+
+ IP 位址
+ Field label
+
+
+ 網路
+ Field label
+
+
+ OS 版本
+ Label for OS Version field in main page
+
+
+ 開始開發
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 裝置資訊
+
+
+ 瀏覽
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 您嘗試存取的頁面要求使用 Windows 裝置入口網站 (WDP) API。請使用 WDP 認證登入以繼續。
+
+
+ 登入時發生問題。
+
+
+ 已成功登入裝置入口網站!
+
+
+ 正在驗證裝置入口網站認證...
+
+
+ 取得天氣時發生問題，再試一次?
+
+
+ 直接連線
+
+
+ 中斷連線
+ This disconnects the connected network
+
+
+ 已更新顯示語言: {0}
+
+
+ 網域
+
+
+ 下載完成!
+ App update status
+
+
+ 下載失敗。請稍後再試!
+
+
+ 正在下載更新
+ App update status
+
+
+ 下載更新
+
+
+ 繪圖
+
+
+ 「{0} 個記錄檔已傳送至 {1}」
+ {0} is plural number of logs, {1} is email address
+
+
+ 「{0} 個記錄已傳送至 {1}」
+ {0} is singular number of logs, {1} is email address
+
+
+ 電子郵件記錄
+
+
+ 您想要以電子郵件傳送 {0} 給自己嗎?
+ {0} is filename
+
+
+ 以電子郵件傳送您的記錄時發生問題: {0}
+ {0} is exception message
+
+
+ 您可在 [記錄] 頁面找到您的記錄
+
+
+ 「要傳送 {0} 個記錄給您自己嗎?」
+ {0} is singular number of logs
+
+
+ 以電子郵件傳送您的記錄時發生問題: {0}
+ {0} is an exception message
+
+
+ 要以電子郵件傳送 {0} 個記錄檔給自己嗎?
+ {0} is plural number of logs
+
+
+ 電子郵件記錄
+
+
+ 已選取電子郵件
+
+
+ 啟用命令列處理程式
+
+
+ 螢幕保護裝置
+ Toggle switch for enabling the screensaver
+
+
+ 結束時間
+
+
+ 錯誤
+
+
+ 擷取天氣資訊時發生問題
+
+
+ 乙太網路
+ Field label
+
+
+ ETW 提供者 GUID: {0}
+ Format string for app settings page
+
+
+ 正在以 DefaultAccount 的身分執行命令
+
+
+ 探索
+
+
+ 已儲存檔案: {0}
+ {0} is a filename
+
+
+ 正式發行前小眾測試
+ Device servicing flighting
+
+
+ 正式發行前小眾測試資訊
+ Device servicing flighting
+
+
+ 正式發行前小眾測試版通道已變更至 {0}!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ 變更您的正式發行前小眾測試版通道時發生錯誤
+
+
+ 預測
+ Weather forecast
+
+
+ 您即將進入全螢幕模式。若要結束，您必須按鍵盤上的 [Esc]。要繼續嗎?
+
+
+ 全螢幕模式
+
+
+ 按下 [Esc] 結束全螢幕模式。
+
+
+ 一般
+
+
+ IoTEnterprise 電路板
+ A generic board name
+
+
+ GitHub
+
+
+ 說明
+
+
+ 說明
+
+
+ 說明
+
+
+ 已更新輸入鍵盤語言: {0}
+
+
+ 安裝完成!
+ App update status
+
+
+ 安裝失敗。請稍後再試!
+
+
+ 正在安裝更新
+ App update status
+
+
+ 安裝更新
+
+
+ 無效的認證
+
+
+ '{0}' 是無效的位置。
+ Format string for app settings page
+
+
+ '{0}' 是無效的值。值必須大於或等於 1。
+ Format string for app settings page
+
+
+ '{0}' 是無效的值。
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ 鍵盤配置
+ Field label
+
+
+ 重新啟動這個應用程式以套用新設定
+
+
+ 語言
+
+
+ 語言
+ Field label
+
+
+ 正在載入...
+
+
+ 正在載入天氣資訊...
+
+
+ 記錄已經傳送至 {0}
+ {0} is email address
+
+
+ 記錄已儲存至: {0}
+ {0} is filename
+
+
+ 記錄
+
+
+ 記錄
+
+
+ 裝置名稱
+ Field label
+
+
+ IP 位址
+ Field label
+
+
+ 作業系統版本
+ Label for OS Version field in main page
+
+
+ 這是專為建立原型而設計的 Windows 10 IoT 核心版測試映像。如果您打算商業化，則必須使用自訂 FFU，以獲得最佳安全性。
+ Maker Imager Security Notice
+
+
+ Bing 地圖服務權杖
+
+
+ 需要 Bing 地圖服務權杖
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com、Hotmail、Live.com、MSN
+
+
+ Microsoft 帳戶 (MSA)
+
+
+ 目前正在播放
+ Music player page status text (currently playing)
+
+
+ 選取一首歌曲，然後按一下 [播放]。
+ Music player page status text (default)
+
+
+ 請將一個或多個音訊檔案新增至 [音樂] 資料夾。
+您可以在 Windows 裝置入口網站使用 [App] > [檔案總管] 新增音樂。
+ Music player page instructions text
+
+
+ 正在載入音樂
+ Music player page loading panel text
+
+
+ 正在載入
+ Music player page status text (loading)
+
+
+ 找不到任何音樂
+ Music player page no music found prompt text
+
+
+ 再試一次
+ Music player page reload button text (no files prompt)
+
+
+ 音樂
+
+
+ 音樂
+
+
+ 已暫停
+ Music player page status text (paused)
+
+
+ 正在播放
+ Music player page status text (playing)
+
+
+ 登入
+
+
+ 不明
+
+
+ 功能表
+
+
+ 網路介面卡
+
+
+ 已連線
+
+
+ 已連線
+
+
+ 正在檢查網路需求
+
+
+ 正在檢查網路需求
+
+
+ 受限的網際網路存取
+
+
+ 本機和網際網路存取
+
+
+ 僅限本機網路存取
+
+
+ 沒有連線能力
+
+
+ 網路資訊
+
+
+ 網路無法使用
+
+
+ 輸入網路安全性金鑰
+
+
+ 輸入網路安全性金鑰
+
+
+ 網路與 Wi-Fi
+
+
+ 網路與 Wi-Fi
+
+
+ 檢視網路內容
+
+
+ 網路內容
+
+
+ 您即將被重新導向到此 Wi-Fi 網路的網頁驗證入口網站。要繼續嗎?
+
+
+ 網路重新導向
+
+
+ 下一步
+
+
+ 下一步
+
+
+ 找不到帳戶
+
+
+ 否
+
+
+ 無裝置名稱
+
+
+ 沒有網際網路連線
+
+
+ 未選取任何記錄
+
+
+ 找不到任何音樂
+ Music player page panel text
+
+
+ 找不到任何網路
+
+
+ 沒有可下載的擱置中更新。
+ App update status
+
+
+ 沒有可安裝的擱置中更新。
+ App update status
+
+
+ N/A
+
+
+ 通知
+
+
+ 通知
+
+
+ 找不到新更新。
+ Format string displayed when no app updates are found
+
+
+ 確定
+ Button content text for the Bluetooth settings page
+
+
+ 選擇語言
+
+
+ 讓我們開始連線
+
+
+ 歡迎使用 Windows 10 IoT 核心版
+
+
+ 讓我們先了解一些基礎知識。
+
+
+ 歡迎使用 Windows 10 IoT 核心版
+
+
+ 作業系統版本識別碼
+
+
+ 作業系統版本
+
+
+ 作業系統資訊
+
+
+ 作業系統資訊
+
+
+ 無法使用
+ Text shown when we cannot retrieve the OS Version
+
+
+ 作業系統版本
+
+
+ 套件
+ Software packages
+
+
+ 已安裝套件
+ Software packages
+
+
+ 頁面設定
+
+
+ 頁面
+
+
+ 密碼
+
+
+ 正在載入圖片
+ Default text when no images are available
+
+
+ 請將影像新增至 [圖片] 資料夾。
+您可以在 Windows 裝置入口網站使用 [App] > [檔案總管] 新增影像。
+
+
+ 找不到影像
+ Default text when no images are available
+
+
+ 平台
+
+
+ 播放
+
+
+ 電源選項
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ 基本：傳送與您的裝置、設定和功能相關的資訊，並確認是否正確執行。
+
+
+ 完整：傳送所有基本診斷資料，您瀏覽的網站和使用應用程式與功能的方式，以及有關裝置健康情況、裝置活動和更進一步的錯誤報告等額外資訊。
+
+
+ 我們無法變更隱私權設定。請驗證您的使用者名稱和密碼，並再試一次。
+
+
+ 選取您想傳送給 Microsoft 的診斷資料數量。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
+
+
+ 診斷資料
+ Label for Setting item to control Privacy
+
+
+ 請輸入您的認證，設定此裝置的隱私權等級。
+
+
+ 設定您的隱私權等級
+
+
+ 重新整理
+ Refresh button
+
+
+ 重複歌曲
+ Music player page repeat toggle text
+
+
+ 重新啟動
+
+
+ 重新啟動
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ 使用方式: RunAsAdmin command
+
+範例:
+> RunAsdmin TZUTIL /s "Pacific Standard Time"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ 儲存
+
+
+ 縮放係數
+
+
+ 全選
+
+
+ 傳送遙測
+
+
+ 無法使用
+
+
+ 工作階段記錄
+
+
+ 將預設頁面設定為 {0} 時發生問題。
+ Format string for app settings page
+
+
+ 設定
+
+
+ 隨機播放
+ Music player page shuffle toggle text
+
+
+ 關機
+
+
+ 關機
+ Shutdown entry in the shutdown menu
+
+
+ 登入您的 Azure AD 帳戶以使用此功能。
+
+
+ 跳過
+
+
+ 跳過此步驟
+
+
+ 投影片放映間隔 (秒)
+
+
+ 幻燈片秀
+
+
+ 幻燈片秀
+
+
+ 開始
+
+
+ 開始
+
+
+ 開始時間
+
+
+ 狀態
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ 提交
+
+
+ 成功
+
+
+ 系統
+
+
+ 嘗試更新您的系統設定時發生問題。
+ Used within system settings
+
+
+ 遙測層級
+
+
+ 遙測
+
+
+ 測試大型通知
+
+
+ 測試通知
+
+
+ Windows 10 IoT 是 Windows 10 家族的成員，它為物聯網帶來了企業級的助力、安全性和管理性，此外亦利用了 Windows 的內嵌體驗、生態系統及雲端連線能力，讓組織可以安全、可快速佈建、可輕鬆管理，且與整體雲端策略完美匹配的裝置來打造自己的物聯網。
+
+
+ 磚高度
+
+
+ 個人化
+
+
+ 磚寬度
+
+
+ 連線逾時
+
+
+ 已更新時區: {0}
+
+
+ 錯誤: 無法與天氣服務進行通訊
+
+
+ 由於不明錯誤，更新失敗。
+ App update error, unknown
+
+
+ 取消全選
+
+
+ 未指定的失敗
+
+
+ 進階選項
+
+
+ 立即檢查
+
+
+ 立即安裝
+
+
+ {0} 個暫止的更新
+ {0} is singular amount of updates
+
+
+ 找到 {0} 個新更新。
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} 個暫止的更新
+ {0} is plural amount of updates
+
+
+ 使用 MDL2 磚圖示
+
+
+ 使用密碼
+
+
+ 使用者名稱
+
+
+ Windows 裝置入口網站
+
+
+ 裝置入口網站設定
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows 裝置入口網站
+
+
+ 目前位置 ({0}，{1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ 您的位置
+
+
+ 您的位置
+ Label for map pin
+
+
+ 未知的位置
+ Label for map pin
+
+
+ 感應器:
+ Label for temperature sensor output
+
+
+ 天氣
+
+
+ 載入天氣頁面時發生錯誤。
+
+請按畫面右下方的 [重新整理] 按鈕，重新載入此頁面。
+
+如果您沒有天氣 API 金鑰，請瀏覽 weatherunlocked.com。將金鑰儲存在應用程式本地狀態資料夾中的 "WeatherTokens.config" 中。然後重新整理頁面。
+
+
+ 天氣資料提供者:
+
+
+ 天氣
+
+
+ 輸入網址
+
+
+ 網頁瀏覽器
+
+
+ 歡迎使用 Windows IoT 核心版
+
+
+ Wi-Fi
+ Label for Wi-Fi list in options page
+
+
+ 重新整理
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 上次檢查：
+ For a timestamp
+
+
+ 上次更新：
+ For a timestamp
+
+
+ 更新狀態：
+
+
+ 狀態訊息：
+
+
+ Windows Update
+
+
+ Windows Update
+
+
+ 無效的工作目錄: {0}
+
+
+ WPS
+
+
+ 允許這個應用程式存取您的位置
+
+
+ 選擇設定，選取 [接受] 以保存。您可以隨時變更這些設定。
+
+
+ 讓 Microsoft 使用您所在的位置
+
+
+ 自動繼續…
+
+
+ 接受
+
+
+ 是否讓 {0} 存取您的精確位置？
+ {0} is the name of a page
+
+
+ 位置
+
+
+ 若要稍後變更，請至設定 > 權限。
+
+
+ 否
+
+
+ 是
+
+
+ 您無法體驗以位置為基礎的相關服務，例如地圖和天氣，或其他需要取得您所在地才能運作的服務。
+
+
+ 取得像地圖與天氣等以位置為基礎的相關服務。讓應用程式取得您的所在位置。Microsoft 將使用您的位置資料改善位置相關服務。
+
+
+ 僅傳送有關您裝置的設定、功能以及是否正常運行等資訊。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
+
+
+ 基本
+
+
+ 傳送所有基本診斷資料，您瀏覽的網站和使用應用程式與功能的方式，以及有關裝置健康情況、裝置活動狀況和更進一步的錯誤報告等額外資訊。診斷資料用於協助維持 Windows 的安全性和最新資訊、疑難排解和改善產品。無論您選擇的是 [基本] 或是 [完整]，您的裝置都將享有同樣的安全性並且可正常運作。
+
+
+ 完整
+
+
+ 為您的裝置選擇隱私權設定，然後選取 [接受] 來儲存它。
+
+
+ 傳送診斷資料給 Microsoft
+
+
+ 診斷
+
+
+ 若您允許存取，您將授權此應用程式使用您裝置上的功能，以此判定您的位置， Microsoft 將使用您位置的資料來改善位置服務。拒絕存取會阻止 Windows 提供位置給此應用程式。
+
+
+ 了解您的隱私權選項
+
+
+ 了解這項設定將如何影響您的隱私權。
+
+
+ 取得更多關於這些設定的詳細資訊
+
+
+ 隱私權聲明
+
+
+ 是
+
+
+ 是
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-hans/Resources.resw b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-hans/Resources.resw
index 551e30195..29cc06b9e 100644
--- a/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-hans/Resources.resw
+++ b/samples/IoTEnterpriseDefault/CS/SmartDisplay/Strings/zh-hans/Resources.resw
@@ -1,1509 +1,1509 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- text/microsoft-resx
-
-
- 2.0
-
-
- System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-
-
- 使用 AAD v2
-
-
- 已撤消访问
-
-
- 描述:
-
-
- DHCP 服务器:
-
-
- DNS:
-
-
- 网关地址:
-
-
- IPv4 地址:
-
-
- 名称:
-
-
- 物理地址:
-
-
- 子网掩码:
-
-
- 类型:
-
-
- 应用版本
-
-
- 应用
-
-
- 你将启动外部应用。需要使用 Windows 设备门户才能返回到此应用。是否继续?
- Dialog prompt for launching external apps
-
-
- 应用
-
-
- 应用设置
-
-
- 设置活动时间，以便我们了解你通常何时使用此设备。活动时间内不会自动重启。
-
-
- 无法保存新的开始和结束时间，因为它们相同。请选择新的时间或关闭功能。
-
-
- 高级选项
- Advanced section title
-
-
- 控制获取、下载和安装更新步骤中的每一步。
-
-
- 自动更新选项
- Auto-Update section title
-
-
- 允许应用在活动时间之外安装应用更新
-
-
- 应用更新
- App update display dialog header
-
-
- 上次检查时间: {0}，{1}
- {0} is date, {1} is time
-
-
- 无法确定上次检查更新的时间
-
-
- 应用更新
- Label for setting item to check for app updates
-
-
- 登录 MSA 和 AAD
-
-
- 请使用你的组织帐户登录到 AAD。
-
-
- Azure AD (AAD)登录
-
-
- AAD
-
-
- 验证 Microsoft Graph 和其他资源
-
-
- 仅验证 Microsoft Graph
-
-
- 取消
-
-
- 你的组织帐户
-
-
- 如果遇到问题无法退出登录向导，请等待 {0} 秒，此后应该可以返回至应用。
-
-
- 正在登录...
-
-
- 正在注销...
-
-
- 在此处登录 Microsoft 帐户
-
-
- Microsoft 帐户(MSA)登录
-
-
- MSA
-
-
- 身份验证
-
-
- Microsoft 登录
-
-
- 登录失败({0})
-
-
- 登录成功({0})
-
-
- 登录
-
-
- 已注销: {0}
-
-
- 注销
-
-
- 自动播放
- Music player page auto-play toggle text
-
-
- 自动缩放
-
-
- 电池电量不足，更新失败。
- App update error, low battery
-
-
- 正在尝试与 {0} ({1})配对。
- Text displayed when a Bluetooth pairing attempt starts
-
-
- 正在与 {0} ({1})配对。
- Text displayed when ConfirmOnly ceremony is invoked
-
-
- 设备上显示的 PIN 是否与 {0} 匹配?
- Text displayed when ConfirmPinMatch ceremony is invoked
-
-
- 未知
- Text displayed when the Bluetooth device name is unknown
-
-
- 当前已配对
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 准备配对
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 未知状态
- Text displayed for labeling the pairing status of a Bluetooth device
-
-
- 请在要配对的设备上输入以下 PIN: {0}
- Text displayed when DisplayPin ceremony is invoked
-
-
- 输入 PIN:
- Text displayed on prompt for user to enter a pairing PIN
-
-
- 来自 {0} ({1})的入站配对请求。
- Text displayed when an inbound pairing request is received
-
-
- 此设备已注册为入站配对。(支持的规则: {0})
- Text displayed when inbound pairing handler registration has already been completed
-
-
- 无法为入站配对进行注册。
- Text displayed when Inbound pairing handler registration fails
-
-
- 已成功注册入站配对。(支持的规则: {0})
- Text displayed when inbound pairing handler registration succeeds
-
-
- 输入的 PIN 不正确。
- Text displayed after user enters a PIN that does not match the device PIN
-
-
- 在此设备上找不到可用的蓝牙适配器: \n{0}
- Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
-
-
- 配对
- Text displayed on the button used to pair the selected Bluetooth device
-
-
- 无法与 {0} ({1})配对。
- Text displayed when a Bluetooth pairing attempt fails
-
-
- 已成功与 {0} ({1})配对。
- Text displayed when a Bluetooth pairing attempt succeeds
-
-
- 蓝牙
- Title for Bluetooth settings page
-
-
- 默认
- Text label for the corresponding device pairing protection level
-
-
- 加密和身份验证
- Text label for the corresponding device pairing protection level
-
-
- 加密
- Text label for the corresponding device pairing protection level
-
-
- 无
- Text label for the corresponding device pairing protection level
-
-
- 你的设备现已进入可检测到模式，可以与其他蓝牙设备配对。
- Text displayed when StartWatcher is invoked
-
-
- 你的设备不再搜索其他蓝牙设备。
- Text displayed when StopWatcher is invoked
-
-
- 取消配对
- Text displayed on the button used to unpair the selected Bluetooth device
-
-
- 无法从 {0} ({1})取消配对。
- Text displayed when a Bluetooth unpairing attempt fails
-
-
- 已成功从 {0} ({1})取消配对。
- Text displayed when a Bluetooth unpairing attempt succeeds
-
-
- 蓝牙
- Header label for the Bluetooth watcher toggle switch
-
-
- 主页
-
-
- Web 浏览器
-
-
- 取消
-
-
- 更改当前不支持的目录。请在命令中使用完整路径。
-
-
- 时区
- Time zone text
-
-
- 正在检查更新...
- App update status
-
-
- 检查更新
-
-
- 清除帐户
-
-
- 清除帐户时出现问题
-
-
- 这将清除以下 Windows 帐户:
-{0}
-
-是否继续?
-
-
- 已清除帐户
-
-
- 正在清除帐户...
-
-
- 清除
-
-
- 关闭
-
-
- 系统不允许你的设备运行命令行处理器。
-要允许运行，请在你的设备上以“管理员”身份运行以下命令:
-
- reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
-
-你可以在 IoT Windows 设备门户的“进程”页面中运行该命令，或者使用 PowerShell 连接到 Windows IoT 设备。
-有关详细信息，请访问 http://go.microsoft.com/fwlink/p/?LinkId=698488
-
- New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
-
-
- 无法以管理员身份运行命令: {0}
-
-
- 无法在你的设备上启用命令行处理器(cmd.exe): {0}
-
-
- 已在你的设备上成功启用命令行处理器 (cmd.exe)。
-
-
- 磁贴颜色
-
-
- 返回
- Back UI navigation
-
-
- 显示设备信息
-
-
- 前进
- Forward UI navigation
-
-
- 切换全屏
-
-
- 克隆视图
- Clone current view to another display
-
-
- 快速保存日志
-
-
- 会话日志
-
-
- 设置默认页面
-
-
- 命令已取消。
-
-
- 输入命令行
- Placeholder for command line input text box
-
-
- 运行命令行时出错: {0}
-
-
- 命令行
-
-
- 命令行
- Title for command line page
-
-
- 无输出状态持续 {0} 秒即表示命令超时。
-
-
- 计算机名称
-
-
- 确认
-
-
- 自动连接
-
-
- 自动连接
-
-
- 连接
-
-
- 连接
-
-
- 已连接设备
-
-
- 更新失败。请连接到 WLAN 并重试。
- App update error, poor connection
-
-
- 继续
-
-
- 无法分析命令输出
-
-
- 当前圈
- ring is flight ring of device
-
-
- DragonBoard 410c
- Board name
-
-
- 默认应用页面
-
-
- 正在自动选择默认语言...
-
-
- 已删除 {0} 条日志
- {0} is plural number of logs
-
-
- 已删除 {0} 条日志
- {0} is singular number of logs
-
-
- 删除 {0} 条日志?
- {0} is singular number of logs
-
-
- 删除 {0} 条日志?
- {0} is plural number of logs
-
-
- 删除已选中项目
-
-
- Azure 设备 ID
- Field label
-
-
- Azure IoT 中心
- Field label
-
-
- 转到设备页面
-
-
- IP 地址: {0}
-操作系统版本: {1}
-应用版本: {2}
-
-
- 应用版本
- Field label
-
-
- 设备名称
- Field label
-
-
- IP 地址
- Field label
-
-
- 网络
- Field label
-
-
- OS 版本
- Label for OS Version field in main page
-
-
- 开始开发
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 设备信息
-
-
- 访问
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 你尝试访问的页面需要使用 Windows 设备门户(WDP) API。请使用你的 WDP 凭据登录以继续。
-
-
- 登录时出现问题。
-
-
- 已成功登录到设备门户!
-
-
- 正在验证设备门户凭据...
-
-
- 获取天气信息时出现问题，是否重试?
-
-
- 直接连接
-
-
- 断开连接
- This disconnects the connected network
-
-
- 已更新显示语言: {0}
-
-
- 域
-
-
- 下载完成!
- App update status
-
-
- 下载失败。请稍后重试!
-
-
- 正在下载更新
- App update status
-
-
- 下载更新
-
-
- 绘制
-
-
- “{0} 条日志已发送到 {1}”
- {0} is plural number of logs, {1} is email address
-
-
- “{0} 条日志已发送到 {1}”
- {0} is singular number of logs, {1} is email address
-
-
- 电子邮件日志
-
-
- 你是否希望将 {0} 通过电子邮件发送给自己?
- {0} is filename
-
-
- 通过电子邮件发送日志时出现问题: {0}
- {0} is exception message
-
-
- 你可以在日志页面找到日志
-
-
- “将 {0} 条日志通过电子邮件发送给自己?”
- {0} is singular number of logs
-
-
- 通过电子邮件发送日志时出现问题: {0}
- {0} is an exception message
-
-
- 将 {0} 条日志通过电子邮件发送给自己?
- {0} is plural number of logs
-
-
- 通过电子邮件发送日志
-
-
- 通过电子邮件发送已选中项目
-
-
- 启用命令行处理器
-
-
- 屏幕保护程序
- Toggle switch for enabling the screensaver
-
-
- 结束时间
-
-
- 错误
-
-
- 检索天气信息时出现问题
-
-
- 以太网
- Field label
-
-
- ETW 提供程序 GUID: {0}
- Format string for app settings page
-
-
- 正在以 DefaultAccount 身份执行命令
-
-
- 浏览
-
-
- 文件已保存: {0}
- {0} is a filename
-
-
- 外部测试
- Device servicing flighting
-
-
- 外部测试信息
- Device servicing flighting
-
-
- 外部测试版圈已更改为 {0}!
- Success message to change the flight ring of the device. {0} is the flight ring name.
-
-
- 更改外部测试版圈时出现问题
-
-
- 预测
- Weather forecast
-
-
- 即将进入全屏模式。按键盘上的 [Esc] 可退出。是否继续?
-
-
- 全屏模式
-
-
- 按 [Esc] 退出全屏模式。
-
-
- 常规
-
-
- IoT 核心板
- A generic board name
-
-
- GitHub
-
-
- 帮助
-
-
- 帮助
-
-
- 帮助
-
-
- 已更新输入键盘语言: {0}
-
-
- 安装完成!
- App update status
-
-
- 安装失败。请稍后重试!
-
-
- 正在安装更新
- App update status
-
-
- 安装更新
-
-
- 凭据无效
-
-
- “{0}”是无效位置。
- Format string for app settings page
-
-
- “{0}”是无效值。值必须大于或等于 1。
- Format string for app settings page
-
-
- “{0}”是无效值。
- Format string for app settings page
-
-
- IPv4
- Field label
-
-
- IPv6
- Field label
-
-
- 键盘布局
- Field label
-
-
- 重启此应用以应用新设置
-
-
- 语言
-
-
- 语言
- Field label
-
-
- 正在加载...
-
-
- 正在加载天气信息...
-
-
- 日志已发送到 {0}
- {0} is email address
-
-
- 日志已保存到: {0}
- {0} is filename
-
-
- 日志
-
-
- 日志
-
-
- 设备名称
- Field label
-
-
- IP 地址
- Field label
-
-
- 操作系统版本
- Label for OS Version field in main page
-
-
- Windows 10 IoT 核心版测试映像仅用于原型测试。如果你希望进行商业化，则必须使用定制的 FFU，以获得最佳安全性。
- Maker Imager Security Notice
-
-
- 必应地图服务令牌
-
-
- 需要必应地图服务令牌
-
-
- http://go.microsoft.com/fwlink/p/?LinkId=614880
-
-
- MinnowBoard Max
- Board name
-
-
- Outlook.com、Hotmail、Live.com、MSN
-
-
- Microsoft 帐户(MSA)
-
-
- 当前正在播放
- Music player page status text (currently playing)
-
-
- 选择一首歌曲，然后单击“播放”。
- Music player page status text (default)
-
-
- 请将一个或多个音频文件添加到“音乐”文件夹。
-你可以通过“应用”>“文件资源管理器”在 Windows 设备门户中添加音乐。
- Music player page instructions text
-
-
- 正在加载音乐
- Music player page loading panel text
-
-
- 正在加载
- Music player page status text (loading)
-
-
- 未找到音乐
- Music player page no music found prompt text
-
-
- 重试
- Music player page reload button text (no files prompt)
-
-
- 音乐
-
-
- 音乐
-
-
- 已暂停
- Music player page status text (paused)
-
-
- 正在播放
- Music player page status text (playing)
-
-
- 登录
-
-
- 未知
-
-
- 菜单
-
-
- 网络适配器
-
-
- 已连接
-
-
- 已连接
-
-
- 正在检查网络要求
-
-
- 正在检查网络要求
-
-
- 受限 Internet 访问
-
-
- 本地和 Internet 访问
-
-
- 仅限本地网络访问
-
-
- 无连接
-
-
- 网络信息
-
-
- 网络不可用
-
-
- 输入网络安全密钥
-
-
- 输入网络安全密钥
-
-
- 网络和 WLAN
-
-
- 网络和 WLAN
-
-
- 查看网络属性
-
-
- 网络属性
-
-
- 即将重定向到此 WLAN 网络的强制网络门户。是否继续?
-
-
- 网络重定向
-
-
- 下一步
-
-
- 下一步
-
-
- 未找到帐户
-
-
- 否
-
-
- 无设备名称
-
-
- 无 Internet 连接
-
-
- 未选中日志
-
-
- 未找到音乐
- Music player page panel text
-
-
- 未找到
-
-
- 没有待下载的更新。
- App update status
-
-
- 没有待安装的更新。
- App update status
-
-
- N/A
-
-
- 通知
-
-
- 通知
-
-
- 未找到新更新。
- Format string displayed when no app updates are found
-
-
- 确定
- Button content text for the Bluetooth settings page
-
-
- 选择语言
-
-
- 让我们进行连接
-
-
- 欢迎使用 Windows 10 IoT 核心版
-
-
- 让我们进行一些基本设置。
-
-
- 欢迎使用 Windows 10 IoT 核心版
-
-
- 操作系统版本 ID
-
-
- 操作系统版本
-
-
- 操作系统信息
-
-
- 操作系统信息
-
-
- 不可用
- Text shown when we cannot retrieve the OS Version
-
-
- 操作系统版本
-
-
- 程序包
- Software packages
-
-
- 已安装程序包
- Software packages
-
-
- 页面设置
-
-
- 页面
-
-
- 密码
-
-
- 正在加载图片
- Default text when no images are available
-
-
- 请将图像添加到“图片”文件夹。
-你可以通过“应用”>“文件资源管理器”在 Windows 设备门户中添加图像。
-
-
- 未找到图像
- Default text when no images are available
-
-
- 平台
-
-
- 播放
-
-
- 电源选项
- Label for Setting item to control Power (shutdown/restart)
-
-
- 基本版本: 只发送有关设备、其设置和功能以及它是否正常运行的信息。
-
-
- 完整版本: 发送所有基本版本诊断数据及有关你浏览的网站和如何使用应用和功能的信息，以及有关设备运行状况、设备使用情况和增强版本错误报告的额外信息。
-
-
- 我们无法更改隐私设置。请验证你的用户名和密码，然后重试。
-
-
- 选择想要向 Microsoft 发送多少诊断数据。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择何种选项，设备会同样安全并正常运行。
-
-
- 诊断数据
- Label for Setting item to control Privacy
-
-
- 输入你的凭据以设置此设备上的隐私级别。
-
-
- 设置你的隐私级别
-
-
- 刷新
- Refresh button
-
-
- 重复播放歌曲
- Music player page repeat toggle text
-
-
- 重启
-
-
- 重新启动
- Restart entry in the shutdown menu
-
-
- Raspberry Pi 2
- Board name
-
-
- Raspberry Pi 3
- Board name
-
-
- 用法: RunAsAdmin 命令
-
-示例:
-> RunAsdmin TZUTIL /s "太平洋标准时间"
-> RunAsdmin SetComputerName MyNewDeviceName
-
-
- 保存
-
-
- 比例因数
-
-
- 全选
-
-
- 发送遥测
-
-
- 不可用
-
-
- 会话日志
-
-
- 将默认页面设置为 {0} 时出现问题。
- Format string for app settings page
-
-
- 设置
-
-
- 随机播放
- Music player page shuffle toggle text
-
-
- 关闭
-
-
- 关闭
- Shutdown entry in the shutdown menu
-
-
- 登录到你的 Azure AD 帐户以使用此功能。
-
-
- 跳过
-
-
- 跳过此步骤
-
-
- 幻灯片放映间隔(秒)
-
-
- 幻灯片放映
-
-
- 幻灯片放映
-
-
- 开始
-
-
- 开始
-
-
- 开始时间
-
-
- 状态
- Status of the network connection (e.g. not connected, limited, etc.)
-
-
- 提交
-
-
- 成功
-
-
- 系统
-
-
- 尝试更新系统设置时出现问题。
- Used within system settings
-
-
- 遥测级别
-
-
- 遥测
-
-
- 测试大型通知
-
-
- 测试通知
-
-
- Windows 10 IoT 是 Windows 10 系列产品，能为物联网提供企业级的性能、安全性和可管理性。它利用 Windows 的嵌入式体验、生态系统和云连接性，允许组织通过创建自己的物联网来保护设备安全，并能够根据总体云策略对设备进行快速预配、轻松管理和无缝连接。
-
-
- 磁贴高度
-
-
- 个性化
-
-
- 磁贴宽度
-
-
- 连接超时
-
-
- 已更新时区: {0}
-
-
- 错误: 无法连接天气服务
-
-
- 由于出现未知错误，更新失败。
- App update error, unknown
-
-
- 取消全选
-
-
- 未知故障
-
-
- 高级选项
-
-
- 立即检查
-
-
- 立即安装
-
-
- {0} 个挂起的更新
- {0} is singular amount of updates
-
-
- 找到 {0} 个新更新。
- Format string displayed when new app updates are found. {0} is a number
-
-
- {0} 个挂起的更新
- {0} is plural amount of updates
-
-
- 使用 MDL2 磁贴图标
-
-
- 使用密码
-
-
- 用户名
-
-
- Windows 设备门户
-
-
- 设备门户设置
- Label for Setting item to control Device Portal settings (time zone)
-
-
- Windows 设备门户
-
-
- 当前位置({0}、{1})
- {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
-
-
- 你的位置
-
-
- 你的位置
- Label for map pin
-
-
- 未知的位置
- Label for map pin
-
-
- 传感器:
- Label for temperature sensor output
-
-
- 天气
-
-
- 在加载“天气”页面时出错。
-
-单击屏幕右下角的“刷新”按钮以重新加载此页面。
-
-如果你没有天气 API 密钥，请导航到 weatherunlocked.com。将“WeatherTokens.config”中的密钥保存在此应用的本地状态文件夹中。然后刷新该页面。
-
-
- 天气数据提供者:
-
-
- 天气
-
-
- 输入 Web 地址
-
-
- Web 浏览器
-
-
- 欢迎使用 Windows IoT 核心版
-
-
- WLAN
- Label for Wi-Fi list in options page
-
-
- 刷新
- Refresh button
-
-
- www.windowsondevices.com
- Part of "Visit www.windowsondevices.com to start developing"
-
-
- 上次检查时间:
- For a timestamp
-
-
- 上次更新时间:
- For a timestamp
-
-
- 更新状态:
-
-
- 状态消息:
-
-
- Windows 更新
-
-
- Windows 更新
-
-
- 工作目录无效: {0}
-
-
- WPS
-
-
- 允许此应用访问你的位置
-
-
- 选择你的设置，然后选择“接受”以保存。你随时可以更改这些设置。
-
-
- 允许 Microsoft 使用你的位置
-
-
- 自动继续...
-
-
- 接受
-
-
- 是否允许 {0} 访问你的精确位置?
- {0} is the name of a page
-
-
- 位置
-
-
- 若要以后对此进行更改，请转到“设置”>“权限”。
-
-
- 否
-
-
- 是
-
-
- 你将无法获取地图和天气等基于位置的体验，也无法享受其他需要你的位置才能正常工作的服务。
-
-
- 获取地图和天气等基于位置的体验。允许此应用请求你的位置。Microsoft 将使用位置数据改进定位服务。
-
-
- 只发送有关设备、其设置和功能以及它是否正常运行的信息。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择基本版本还是完整版本，设备会同样安全并正常运行。
-
-
- 基本版本
-
-
- 发送所有基本版本诊断数据及有关你浏览的网站和如何使用应用和功能的信息，以及有关设备运行状况、设备使用情况和增强版本错误报告的额外信息。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择基本版本还是完整版本，设备会同样安全并正常运行。
-
-
- 完整版本
-
-
- 为你的设备选择隐私设置，然后选择“接受”以保存设置。
-
-
- 向 Microsoft 发送诊断数据
-
-
- 诊断
-
-
- 如果你允许访问，则允许此应用使用你的设备功能来确定你的位置，Microsoft 将使用你的位置数据来改进定位服务。拒绝访问将阻止 Windows 向此应用提供位置。
-
-
- 了解你的隐私选项
-
-
- 了解此设置如何影响你的隐私。
-
-
- 获取有关这些设置的详细信息
-
-
- 隐私声明
-
-
- 是
-
-
- 是
- Button content text for the Bluetooth settings page
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ text/microsoft-resx
+
+
+ 2.0
+
+
+ System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
+
+
+ 使用 AAD v2
+
+
+ 已撤消访问
+
+
+ 描述:
+
+
+ DHCP 服务器:
+
+
+ DNS:
+
+
+ 网关地址:
+
+
+ IPv4 地址:
+
+
+ 名称:
+
+
+ 物理地址:
+
+
+ 子网掩码:
+
+
+ 类型:
+
+
+ 应用版本
+
+
+ 应用
+
+
+ 你将启动外部应用。需要使用 Windows 设备门户才能返回到此应用。是否继续?
+ Dialog prompt for launching external apps
+
+
+ 应用
+
+
+ 应用设置
+
+
+ 设置活动时间，以便我们了解你通常何时使用此设备。活动时间内不会自动重启。
+
+
+ 无法保存新的开始和结束时间，因为它们相同。请选择新的时间或关闭功能。
+
+
+ 高级选项
+ Advanced section title
+
+
+ 控制获取、下载和安装更新步骤中的每一步。
+
+
+ 自动更新选项
+ Auto-Update section title
+
+
+ 允许应用在活动时间之外安装应用更新
+
+
+ 应用更新
+ App update display dialog header
+
+
+ 上次检查时间: {0}，{1}
+ {0} is date, {1} is time
+
+
+ 无法确定上次检查更新的时间
+
+
+ 应用更新
+ Label for setting item to check for app updates
+
+
+ 登录 MSA 和 AAD
+
+
+ 请使用你的组织帐户登录到 AAD。
+
+
+ Azure AD (AAD)登录
+
+
+ AAD
+
+
+ 验证 Microsoft Graph 和其他资源
+
+
+ 仅验证 Microsoft Graph
+
+
+ 取消
+
+
+ 你的组织帐户
+
+
+ 如果遇到问题无法退出登录向导，请等待 {0} 秒，此后应该可以返回至应用。
+
+
+ 正在登录...
+
+
+ 正在注销...
+
+
+ 在此处登录 Microsoft 帐户
+
+
+ Microsoft 帐户(MSA)登录
+
+
+ MSA
+
+
+ 身份验证
+
+
+ Microsoft 登录
+
+
+ 登录失败({0})
+
+
+ 登录成功({0})
+
+
+ 登录
+
+
+ 已注销: {0}
+
+
+ 注销
+
+
+ 自动播放
+ Music player page auto-play toggle text
+
+
+ 自动缩放
+
+
+ 电池电量不足，更新失败。
+ App update error, low battery
+
+
+ 正在尝试与 {0} ({1})配对。
+ Text displayed when a Bluetooth pairing attempt starts
+
+
+ 正在与 {0} ({1})配对。
+ Text displayed when ConfirmOnly ceremony is invoked
+
+
+ 设备上显示的 PIN 是否与 {0} 匹配?
+ Text displayed when ConfirmPinMatch ceremony is invoked
+
+
+ 未知
+ Text displayed when the Bluetooth device name is unknown
+
+
+ 当前已配对
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 准备配对
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 未知状态
+ Text displayed for labeling the pairing status of a Bluetooth device
+
+
+ 请在要配对的设备上输入以下 PIN: {0}
+ Text displayed when DisplayPin ceremony is invoked
+
+
+ 输入 PIN:
+ Text displayed on prompt for user to enter a pairing PIN
+
+
+ 来自 {0} ({1})的入站配对请求。
+ Text displayed when an inbound pairing request is received
+
+
+ 此设备已注册为入站配对。(支持的规则: {0})
+ Text displayed when inbound pairing handler registration has already been completed
+
+
+ 无法为入站配对进行注册。
+ Text displayed when Inbound pairing handler registration fails
+
+
+ 已成功注册入站配对。(支持的规则: {0})
+ Text displayed when inbound pairing handler registration succeeds
+
+
+ 输入的 PIN 不正确。
+ Text displayed after user enters a PIN that does not match the device PIN
+
+
+ 在此设备上找不到可用的蓝牙适配器: \n{0}
+ Text displayed on systems which do not have a Bluetooth adapter (the new line before {0} is deliberate and should be kept)
+
+
+ 配对
+ Text displayed on the button used to pair the selected Bluetooth device
+
+
+ 无法与 {0} ({1})配对。
+ Text displayed when a Bluetooth pairing attempt fails
+
+
+ 已成功与 {0} ({1})配对。
+ Text displayed when a Bluetooth pairing attempt succeeds
+
+
+ 蓝牙
+ Title for Bluetooth settings page
+
+
+ 默认
+ Text label for the corresponding device pairing protection level
+
+
+ 加密和身份验证
+ Text label for the corresponding device pairing protection level
+
+
+ 加密
+ Text label for the corresponding device pairing protection level
+
+
+ 无
+ Text label for the corresponding device pairing protection level
+
+
+ 你的设备现已进入可检测到模式，可以与其他蓝牙设备配对。
+ Text displayed when StartWatcher is invoked
+
+
+ 你的设备不再搜索其他蓝牙设备。
+ Text displayed when StopWatcher is invoked
+
+
+ 取消配对
+ Text displayed on the button used to unpair the selected Bluetooth device
+
+
+ 无法从 {0} ({1})取消配对。
+ Text displayed when a Bluetooth unpairing attempt fails
+
+
+ 已成功从 {0} ({1})取消配对。
+ Text displayed when a Bluetooth unpairing attempt succeeds
+
+
+ 蓝牙
+ Header label for the Bluetooth watcher toggle switch
+
+
+ 主页
+
+
+ Web 浏览器
+
+
+ 取消
+
+
+ 更改当前不支持的目录。请在命令中使用完整路径。
+
+
+ 时区
+ Time zone text
+
+
+ 正在检查更新...
+ App update status
+
+
+ 检查更新
+
+
+ 清除帐户
+
+
+ 清除帐户时出现问题
+
+
+ 这将清除以下 Windows 帐户:
+{0}
+
+是否继续?
+
+
+ 已清除帐户
+
+
+ 正在清除帐户...
+
+
+ 清除
+
+
+ 关闭
+
+
+ 系统不允许你的设备运行命令行处理器。
+要允许运行，请在你的设备上以“管理员”身份运行以下命令:
+
+ reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"
+
+你可以在 IoT Windows 设备门户的“进程”页面中运行该命令，或者使用 PowerShell 连接到 Windows IoT 设备。
+有关详细信息，请访问 http://go.microsoft.com/fwlink/p/?LinkId=698488
+
+ New lines need to be preserved {Locked='reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EmbeddedMode\ProcessLauncher" /v AllowedExecutableFilesList /t REG_MULTI_SZ /d "c:\windows\system32\cmd.exe\0"', 'Windows', 'PowerShell', 'http://go.microsoft.com/fwlink/p/?LinkId=698488'}
+
+
+ 无法以管理员身份运行命令: {0}
+
+
+ 无法在你的设备上启用命令行处理器(cmd.exe): {0}
+
+
+ 已在你的设备上成功启用命令行处理器 (cmd.exe)。
+
+
+ 磁贴颜色
+
+
+ 返回
+ Back UI navigation
+
+
+ 显示设备信息
+
+
+ 前进
+ Forward UI navigation
+
+
+ 切换全屏
+
+
+ 克隆视图
+ Clone current view to another display
+
+
+ 快速保存日志
+
+
+ 会话日志
+
+
+ 设置默认页面
+
+
+ 命令已取消。
+
+
+ 输入命令行
+ Placeholder for command line input text box
+
+
+ 运行命令行时出错: {0}
+
+
+ 命令行
+
+
+ 命令行
+ Title for command line page
+
+
+ 无输出状态持续 {0} 秒即表示命令超时。
+
+
+ 计算机名称
+
+
+ 确认
+
+
+ 自动连接
+
+
+ 自动连接
+
+
+ 连接
+
+
+ 连接
+
+
+ 已连接设备
+
+
+ 更新失败。请连接到 WLAN 并重试。
+ App update error, poor connection
+
+
+ 继续
+
+
+ 无法分析命令输出
+
+
+ 当前圈
+ ring is flight ring of device
+
+
+ DragonBoard 410c
+ Board name
+
+
+ 默认应用页面
+
+
+ 正在自动选择默认语言...
+
+
+ 已删除 {0} 条日志
+ {0} is plural number of logs
+
+
+ 已删除 {0} 条日志
+ {0} is singular number of logs
+
+
+ 删除 {0} 条日志?
+ {0} is singular number of logs
+
+
+ 删除 {0} 条日志?
+ {0} is plural number of logs
+
+
+ 删除已选中项目
+
+
+ Azure 设备 ID
+ Field label
+
+
+ Azure IoT 中心
+ Field label
+
+
+ 转到设备页面
+
+
+ IP 地址: {0}
+操作系统版本: {1}
+应用版本: {2}
+
+
+ 应用版本
+ Field label
+
+
+ 设备名称
+ Field label
+
+
+ IP 地址
+ Field label
+
+
+ 网络
+ Field label
+
+
+ OS 版本
+ Label for OS Version field in main page
+
+
+ 开始开发
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 设备信息
+
+
+ 访问
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 你尝试访问的页面需要使用 Windows 设备门户(WDP) API。请使用你的 WDP 凭据登录以继续。
+
+
+ 登录时出现问题。
+
+
+ 已成功登录到设备门户!
+
+
+ 正在验证设备门户凭据...
+
+
+ 获取天气信息时出现问题，是否重试?
+
+
+ 直接连接
+
+
+ 断开连接
+ This disconnects the connected network
+
+
+ 已更新显示语言: {0}
+
+
+ 域
+
+
+ 下载完成!
+ App update status
+
+
+ 下载失败。请稍后重试!
+
+
+ 正在下载更新
+ App update status
+
+
+ 下载更新
+
+
+ 绘制
+
+
+ “{0} 条日志已发送到 {1}”
+ {0} is plural number of logs, {1} is email address
+
+
+ “{0} 条日志已发送到 {1}”
+ {0} is singular number of logs, {1} is email address
+
+
+ 电子邮件日志
+
+
+ 你是否希望将 {0} 通过电子邮件发送给自己?
+ {0} is filename
+
+
+ 通过电子邮件发送日志时出现问题: {0}
+ {0} is exception message
+
+
+ 你可以在日志页面找到日志
+
+
+ “将 {0} 条日志通过电子邮件发送给自己?”
+ {0} is singular number of logs
+
+
+ 通过电子邮件发送日志时出现问题: {0}
+ {0} is an exception message
+
+
+ 将 {0} 条日志通过电子邮件发送给自己?
+ {0} is plural number of logs
+
+
+ 通过电子邮件发送日志
+
+
+ 通过电子邮件发送已选中项目
+
+
+ 启用命令行处理器
+
+
+ 屏幕保护程序
+ Toggle switch for enabling the screensaver
+
+
+ 结束时间
+
+
+ 错误
+
+
+ 检索天气信息时出现问题
+
+
+ 以太网
+ Field label
+
+
+ ETW 提供程序 GUID: {0}
+ Format string for app settings page
+
+
+ 正在以 DefaultAccount 身份执行命令
+
+
+ 浏览
+
+
+ 文件已保存: {0}
+ {0} is a filename
+
+
+ 外部测试
+ Device servicing flighting
+
+
+ 外部测试信息
+ Device servicing flighting
+
+
+ 外部测试版圈已更改为 {0}!
+ Success message to change the flight ring of the device. {0} is the flight ring name.
+
+
+ 更改外部测试版圈时出现问题
+
+
+ 预测
+ Weather forecast
+
+
+ 即将进入全屏模式。按键盘上的 [Esc] 可退出。是否继续?
+
+
+ 全屏模式
+
+
+ 按 [Esc] 退出全屏模式。
+
+
+ 常规
+
+
+ IoT 核心板
+ A generic board name
+
+
+ GitHub
+
+
+ 帮助
+
+
+ 帮助
+
+
+ 帮助
+
+
+ 已更新输入键盘语言: {0}
+
+
+ 安装完成!
+ App update status
+
+
+ 安装失败。请稍后重试!
+
+
+ 正在安装更新
+ App update status
+
+
+ 安装更新
+
+
+ 凭据无效
+
+
+ “{0}”是无效位置。
+ Format string for app settings page
+
+
+ “{0}”是无效值。值必须大于或等于 1。
+ Format string for app settings page
+
+
+ “{0}”是无效值。
+ Format string for app settings page
+
+
+ IPv4
+ Field label
+
+
+ IPv6
+ Field label
+
+
+ 键盘布局
+ Field label
+
+
+ 重启此应用以应用新设置
+
+
+ 语言
+
+
+ 语言
+ Field label
+
+
+ 正在加载...
+
+
+ 正在加载天气信息...
+
+
+ 日志已发送到 {0}
+ {0} is email address
+
+
+ 日志已保存到: {0}
+ {0} is filename
+
+
+ 日志
+
+
+ 日志
+
+
+ 设备名称
+ Field label
+
+
+ IP 地址
+ Field label
+
+
+ 操作系统版本
+ Label for OS Version field in main page
+
+
+ Windows 10 IoT 核心版测试映像仅用于原型测试。如果你希望进行商业化，则必须使用定制的 FFU，以获得最佳安全性。
+ Maker Imager Security Notice
+
+
+ 必应地图服务令牌
+
+
+ 需要必应地图服务令牌
+
+
+ http://go.microsoft.com/fwlink/p/?LinkId=614880
+
+
+ MinnowBoard Max
+ Board name
+
+
+ Outlook.com、Hotmail、Live.com、MSN
+
+
+ Microsoft 帐户(MSA)
+
+
+ 当前正在播放
+ Music player page status text (currently playing)
+
+
+ 选择一首歌曲，然后单击“播放”。
+ Music player page status text (default)
+
+
+ 请将一个或多个音频文件添加到“音乐”文件夹。
+你可以通过“应用”>“文件资源管理器”在 Windows 设备门户中添加音乐。
+ Music player page instructions text
+
+
+ 正在加载音乐
+ Music player page loading panel text
+
+
+ 正在加载
+ Music player page status text (loading)
+
+
+ 未找到音乐
+ Music player page no music found prompt text
+
+
+ 重试
+ Music player page reload button text (no files prompt)
+
+
+ 音乐
+
+
+ 音乐
+
+
+ 已暂停
+ Music player page status text (paused)
+
+
+ 正在播放
+ Music player page status text (playing)
+
+
+ 登录
+
+
+ 未知
+
+
+ 菜单
+
+
+ 网络适配器
+
+
+ 已连接
+
+
+ 已连接
+
+
+ 正在检查网络要求
+
+
+ 正在检查网络要求
+
+
+ 受限 Internet 访问
+
+
+ 本地和 Internet 访问
+
+
+ 仅限本地网络访问
+
+
+ 无连接
+
+
+ 网络信息
+
+
+ 网络不可用
+
+
+ 输入网络安全密钥
+
+
+ 输入网络安全密钥
+
+
+ 网络和 WLAN
+
+
+ 网络和 WLAN
+
+
+ 查看网络属性
+
+
+ 网络属性
+
+
+ 即将重定向到此 WLAN 网络的强制网络门户。是否继续?
+
+
+ 网络重定向
+
+
+ 下一步
+
+
+ 下一步
+
+
+ 未找到帐户
+
+
+ 否
+
+
+ 无设备名称
+
+
+ 无 Internet 连接
+
+
+ 未选中日志
+
+
+ 未找到音乐
+ Music player page panel text
+
+
+ 未找到
+
+
+ 没有待下载的更新。
+ App update status
+
+
+ 没有待安装的更新。
+ App update status
+
+
+ N/A
+
+
+ 通知
+
+
+ 通知
+
+
+ 未找到新更新。
+ Format string displayed when no app updates are found
+
+
+ 确定
+ Button content text for the Bluetooth settings page
+
+
+ 选择语言
+
+
+ 让我们进行连接
+
+
+ 欢迎使用 Windows 10 IoT 核心版
+
+
+ 让我们进行一些基本设置。
+
+
+ 欢迎使用 Windows 10 IoT 核心版
+
+
+ 操作系统版本 ID
+
+
+ 操作系统版本
+
+
+ 操作系统信息
+
+
+ 操作系统信息
+
+
+ 不可用
+ Text shown when we cannot retrieve the OS Version
+
+
+ 操作系统版本
+
+
+ 程序包
+ Software packages
+
+
+ 已安装程序包
+ Software packages
+
+
+ 页面设置
+
+
+ 页面
+
+
+ 密码
+
+
+ 正在加载图片
+ Default text when no images are available
+
+
+ 请将图像添加到“图片”文件夹。
+你可以通过“应用”>“文件资源管理器”在 Windows 设备门户中添加图像。
+
+
+ 未找到图像
+ Default text when no images are available
+
+
+ 平台
+
+
+ 播放
+
+
+ 电源选项
+ Label for Setting item to control Power (shutdown/restart)
+
+
+ 基本版本: 只发送有关设备、其设置和功能以及它是否正常运行的信息。
+
+
+ 完整版本: 发送所有基本版本诊断数据及有关你浏览的网站和如何使用应用和功能的信息，以及有关设备运行状况、设备使用情况和增强版本错误报告的额外信息。
+
+
+ 我们无法更改隐私设置。请验证你的用户名和密码，然后重试。
+
+
+ 选择想要向 Microsoft 发送多少诊断数据。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择何种选项，设备会同样安全并正常运行。
+
+
+ 诊断数据
+ Label for Setting item to control Privacy
+
+
+ 输入你的凭据以设置此设备上的隐私级别。
+
+
+ 设置你的隐私级别
+
+
+ 刷新
+ Refresh button
+
+
+ 重复播放歌曲
+ Music player page repeat toggle text
+
+
+ 重启
+
+
+ 重新启动
+ Restart entry in the shutdown menu
+
+
+ Raspberry Pi 2
+ Board name
+
+
+ Raspberry Pi 3
+ Board name
+
+
+ 用法: RunAsAdmin 命令
+
+示例:
+> RunAsdmin TZUTIL /s "太平洋标准时间"
+> RunAsdmin SetComputerName MyNewDeviceName
+
+
+ 保存
+
+
+ 比例因数
+
+
+ 全选
+
+
+ 发送遥测
+
+
+ 不可用
+
+
+ 会话日志
+
+
+ 将默认页面设置为 {0} 时出现问题。
+ Format string for app settings page
+
+
+ 设置
+
+
+ 随机播放
+ Music player page shuffle toggle text
+
+
+ 关闭
+
+
+ 关闭
+ Shutdown entry in the shutdown menu
+
+
+ 登录到你的 Azure AD 帐户以使用此功能。
+
+
+ 跳过
+
+
+ 跳过此步骤
+
+
+ 幻灯片放映间隔(秒)
+
+
+ 幻灯片放映
+
+
+ 幻灯片放映
+
+
+ 开始
+
+
+ 开始
+
+
+ 开始时间
+
+
+ 状态
+ Status of the network connection (e.g. not connected, limited, etc.)
+
+
+ 提交
+
+
+ 成功
+
+
+ 系统
+
+
+ 尝试更新系统设置时出现问题。
+ Used within system settings
+
+
+ 遥测级别
+
+
+ 遥测
+
+
+ 测试大型通知
+
+
+ 测试通知
+
+
+ Windows 10 IoT 是 Windows 10 系列产品，能为物联网提供企业级的性能、安全性和可管理性。它利用 Windows 的嵌入式体验、生态系统和云连接性，允许组织通过创建自己的物联网来保护设备安全，并能够根据总体云策略对设备进行快速预配、轻松管理和无缝连接。
+
+
+ 磁贴高度
+
+
+ 个性化
+
+
+ 磁贴宽度
+
+
+ 连接超时
+
+
+ 已更新时区: {0}
+
+
+ 错误: 无法连接天气服务
+
+
+ 由于出现未知错误，更新失败。
+ App update error, unknown
+
+
+ 取消全选
+
+
+ 未知故障
+
+
+ 高级选项
+
+
+ 立即检查
+
+
+ 立即安装
+
+
+ {0} 个挂起的更新
+ {0} is singular amount of updates
+
+
+ 找到 {0} 个新更新。
+ Format string displayed when new app updates are found. {0} is a number
+
+
+ {0} 个挂起的更新
+ {0} is plural amount of updates
+
+
+ 使用 MDL2 磁贴图标
+
+
+ 使用密码
+
+
+ 用户名
+
+
+ Windows 设备门户
+
+
+ 设备门户设置
+ Label for Setting item to control Device Portal settings (time zone)
+
+
+ Windows 设备门户
+
+
+ 当前位置({0}、{1})
+ {0}, {1} are latitude and longitude numbers rounded to 1 decimal place
+
+
+ 你的位置
+
+
+ 你的位置
+ Label for map pin
+
+
+ 未知的位置
+ Label for map pin
+
+
+ 传感器:
+ Label for temperature sensor output
+
+
+ 天气
+
+
+ 在加载“天气”页面时出错。
+
+单击屏幕右下角的“刷新”按钮以重新加载此页面。
+
+如果你没有天气 API 密钥，请导航到 weatherunlocked.com。将“WeatherTokens.config”中的密钥保存在此应用的本地状态文件夹中。然后刷新该页面。
+
+
+ 天气数据提供者:
+
+
+ 天气
+
+
+ 输入 Web 地址
+
+
+ Web 浏览器
+
+
+ 欢迎使用 Windows IoT 核心版
+
+
+ WLAN
+ Label for Wi-Fi list in options page
+
+
+ 刷新
+ Refresh button
+
+
+ www.windowsondevices.com
+ Part of "Visit www.windowsondevices.com to start developing"
+
+
+ 上次检查时间:
+ For a timestamp
+
+
+ 上次更新时间:
+ For a timestamp
+
+
+ 更新状态:
+
+
+ 状态消息:
+
+
+ Windows 更新
+
+
+ Windows 更新
+
+
+ 工作目录无效: {0}
+
+
+ WPS
+
+
+ 允许此应用访问你的位置
+
+
+ 选择你的设置，然后选择“接受”以保存。你随时可以更改这些设置。
+
+
+ 允许 Microsoft 使用你的位置
+
+
+ 自动继续...
+
+
+ 接受
+
+
+ 是否允许 {0} 访问你的精确位置?
+ {0} is the name of a page
+
+
+ 位置
+
+
+ 若要以后对此进行更改，请转到“设置”>“权限”。
+
+
+ 否
+
+
+ 是
+
+
+ 你将无法获取地图和天气等基于位置的体验，也无法享受其他需要你的位置才能正常工作的服务。
+
+
+ 获取地图和天气等基于位置的体验。允许此应用请求你的位置。Microsoft 将使用位置数据改进定位服务。
+
+
+ 只发送有关设备、其设置和功能以及它是否正常运行的信息。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择基本版本还是完整版本，设备会同样安全并正常运行。
+
+
+ 基本版本
+
+
+ 发送所有基本版本诊断数据及有关你浏览的网站和如何使用应用和功能的信息，以及有关设备运行状况、设备使用情况和增强版本错误报告的额外信息。诊断数据用于帮助保护和及时更新 Windows、解决问题并改进产品。无论你选择基本版本还是完整版本，设备会同样安全并正常运行。
+
+
+ 完整版本
+
+
+ 为你的设备选择隐私设置，然后选择“接受”以保存设置。
+
+
+ 向 Microsoft 发送诊断数据
+
+
+ 诊断
+
+
+ 如果你允许访问，则允许此应用使用你的设备功能来确定你的位置，Microsoft 将使用你的位置数据来改进定位服务。拒绝访问将阻止 Windows 向此应用提供位置。
+
+
+ 了解你的隐私选项
+
+
+ 了解此设置如何影响你的隐私。
+
+
+ 获取有关这些设置的详细信息
+
+
+ 隐私声明
+
+
+ 是
+
+
+ 是
+ Button content text for the Bluetooth settings page
+
+
diff --git a/samples/IoTEnterpriseDefault/README.md b/samples/IoTEnterpriseDefault/README.md
index df52efc04..cd41a3246 100644
--- a/samples/IoTEnterpriseDefault/README.md
+++ b/samples/IoTEnterpriseDefault/README.md
@@ -1,167 +1,167 @@
----
-page_type: sample
-urlFragment: iotcore-defaultapp
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: The current IoT Core Default App, a fully featured sample app for Windows 10 IoT Enterprise.
----
-
-# Windows 10 IoT Enterprise Default App Overview
-
-This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
-
-Windows 10 IoT Enterprise Default App looks like this:
-
-
-
-This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
-
-## Leveraging the Windows IoT Enterprise Default App
-
-The Windows IoT Enterprise Default App can be customized and extended, or you can use the source code as an example for your own app.
-
-To try this out for yourself, download the zip of our samples or check out the code for the Windows IoT Enterprise Default App. Open the project from Visual Studio 2019.
-
-For UP Board, set the target architecture to 'x64'.
-
-### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-Click the Start button to search for the app by name, and then launch it.
-
-As shown below, in some cases you may configure default settings and features on your customer system on behalf of the end user. However, if you turn these settings and features on by default or if diagnostics are above the basic setting, you must:
-
-* Notify the end user that these features have been enable and provide the end user with the link to Microsoft's Privacy Statement web page [here](http://go.microsoft.com/fwlink/?LinkId=521839).
-* Secure consent from the relevant end user to enable such features by default (as required by applicable law).
-* Provide end users the ability to change the Diagnostics setting back to the basic setting.
-* If you enable Microsoft Accounts and you have access to end user data, if the end user deletes the Microsoft Account, you must enable simultaneous deletion of all the end user's Microsoft Account data on the device.
-
-## Out-of-Box Experience (OOBE)
-
-The out-of-box experience for the IoT Enterprise Default App is as lean as it gets. The first pages will ask for a default language and wi-fi settings. From there, in order for your app to be GDPR-compliant, you must have a diagnostic data screen and, if you're planning to track location, you will need to have a location permissions screen too. Examples of both are shown below.
-
-
-
-
-## Command Bar
-The Command Bar is the persistant horizonatal bar located at the bottom of the screen. This provides easy access to the following funtionality:
-- Forward and backward page navigation
-- Basic device info without leaving the current page
-- Turning fullscreen mode on or off
-- Advance shortcuts
-- Page specific buttons
-
-There are a lot buttons in the Command Bar, and sometimes those buttons can be confusing or hidden. To expand the Command Bar and access those buttons, please press the menu button in the bottom right:
-
-
-
-## Start Menu - Play
-
-The Start Menu is where most plug and play features live.
-
-### Weather
-Using data from the National Weather Service, the weather page renders weather information in your current location.
-
-### Web Browser
-The web browser allows you to pull up most sites from the web.
-
-### Music
-This page will play MP3 and WAV files from the **Music Library**, that can be accessed from the web
-
-### Slideshow
-This page will display any PNG or JPEG image files from the **Pictures Library**, that can be accessed from the web
-
-### Draw
-This page allows you to test out Windows 10 IoT Enterprise's inking capabilities.
-
-## Start Menu - Explore
-
-### Apps
-This page allows you to launch other foreground applications installed on the device. Launching an application will suspend IoT Enterprise Default App, which can be relaunched by using App Packages.
-
-Nothing special is needed to have your foreground application listed in the page, simply install or deploy the application. After successful installation or deployment, re-navigate to the Apps page to refresh the list of applications.
-
-Note that there are a couple of auto-generated OS related applications that we filter out, you can find the list of app names in the samples.
-
-### Notifications
-This page will list the past 20 notifications since IoT Enterprise Default App was launched. When IoT Enterprise Default App is running in debug mode, buttons are added that will create test notifications.
-
-### Logs
-This page will list any auto-generated crash or error logs, which then can be taken off the device and analyzed.
-
-### GitHub
-This page will take you to the open-sourced GitHub location of the IoT Enterprise Default App code.
-
-## Start Menu - Windows Device Portal
-
-The pages in this section leverage the Windows Device Portal REST APIs, which requires you to sign in using your Windows Device Portal credentials.
-
-## Device Information
-
-This page allows you to see the different features for your device including Ethernet, OS version, connected devices, and more.
-
-## Command Line
-
-This page allows you to run commands directly on your device.
-
-To enable this feature you have to set a registry key so that the app can run the commands.
-
-Some commands require administrator access. For security purposes the app uses a non-admin account by default to run commands. If you need to run a command as an admin you can type "RunAsAdmin " in the command line prompt.
-
-## Settings
-You'll be able to configure a number of settings here including Wi-Fi, Bluetooth, power options, and more.
-
-### App Settings
-The **App Settings** section allows you to configure various settings for pages in the app.
-
-Some of the settings you can customize are:
-
-##### Weather Settings
-* Change the location
- > This feature is only enabled if you have provided a valid [Bing Map Service Token](https://msdn.microsoft.com/en-us/library/ff428642.aspx). To pass the token to the app, create a **MapToken.config** file in the LocalState folder of the app (e.g. C:\Data\USERS\\[User Account]\AppData\Packages\\[Package Full Name]\LocalState\MapToken.config) and restart the app.
-* Expand the map
-* Enable/disable map flipping so that the map and the weather switch places periodically to prevent screen burn-in
-
-##### Web Browser Settings
-* Set the home page for the Web Browser
-
-##### Slideshow Settings
-* Set the slideshow interval
-
-##### Appearance
-* Use MDL2 Assets instead of Emojis for the tile icons
-* Set the tile width and height
-* Set UI scaling - Automatic scaling is set by default
-* Set the tile color
-
-#### System
-Change the language, keyboard layout, and time zone.
-
-#### Network & Wi-Fi
-View network adapter properties or connect to an available Wi-Fi network.
-
-#### Bluetooth
-Pair with a Bluetooth device.
-
-#### App Updates
-Check for app updates or change automatic update settings.
-
-#### Power Options
-Restart or shutdown the device.
-
-#### Diagnostics
-Select the amount of diagnostic data you wish to provide Microsoft. We encourage users to opt into **Full** diagnostic data so we can diagnose issues quickly and make improvements to the product.
-
-##### Basic
-Send only info about your device, its settings and capabilities, and whether it is performing properly.
-
-##### Full
-Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
-
-#### Location
-Allow or deny the app access to your location.
+---
+page_type: sample
+urlFragment: iotcore-defaultapp
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: The current IoT Core Default App, a fully featured sample app for Windows 10 IoT Enterprise.
+---
+
+# Windows 10 IoT Enterprise Default App Overview
+
+This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
+
+Windows 10 IoT Enterprise Default App looks like this:
+
+
+
+This article will give you a rundown of the different features that the Windows 10 IoT Enterprise Default App offers as well as how you can leverage these different features for your own applications.
+
+## Leveraging the Windows IoT Enterprise Default App
+
+The Windows IoT Enterprise Default App can be customized and extended, or you can use the source code as an example for your own app.
+
+To try this out for yourself, download the zip of our samples or check out the code for the Windows IoT Enterprise Default App. Open the project from Visual Studio 2019.
+
+For UP Board, set the target architecture to 'x64'.
+
+### [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+### [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+Click the Start button to search for the app by name, and then launch it.
+
+As shown below, in some cases you may configure default settings and features on your customer system on behalf of the end user. However, if you turn these settings and features on by default or if diagnostics are above the basic setting, you must:
+
+* Notify the end user that these features have been enable and provide the end user with the link to Microsoft's Privacy Statement web page [here](http://go.microsoft.com/fwlink/?LinkId=521839).
+* Secure consent from the relevant end user to enable such features by default (as required by applicable law).
+* Provide end users the ability to change the Diagnostics setting back to the basic setting.
+* If you enable Microsoft Accounts and you have access to end user data, if the end user deletes the Microsoft Account, you must enable simultaneous deletion of all the end user's Microsoft Account data on the device.
+
+## Out-of-Box Experience (OOBE)
+
+The out-of-box experience for the IoT Enterprise Default App is as lean as it gets. The first pages will ask for a default language and wi-fi settings. From there, in order for your app to be GDPR-compliant, you must have a diagnostic data screen and, if you're planning to track location, you will need to have a location permissions screen too. Examples of both are shown below.
+
+
+
+
+## Command Bar
+The Command Bar is the persistant horizonatal bar located at the bottom of the screen. This provides easy access to the following funtionality:
+- Forward and backward page navigation
+- Basic device info without leaving the current page
+- Turning fullscreen mode on or off
+- Advance shortcuts
+- Page specific buttons
+
+There are a lot buttons in the Command Bar, and sometimes those buttons can be confusing or hidden. To expand the Command Bar and access those buttons, please press the menu button in the bottom right:
+
+
+
+## Start Menu - Play
+
+The Start Menu is where most plug and play features live.
+
+### Weather
+Using data from the National Weather Service, the weather page renders weather information in your current location.
+
+### Web Browser
+The web browser allows you to pull up most sites from the web.
+
+### Music
+This page will play MP3 and WAV files from the **Music Library**, that can be accessed from the web
+
+### Slideshow
+This page will display any PNG or JPEG image files from the **Pictures Library**, that can be accessed from the web
+
+### Draw
+This page allows you to test out Windows 10 IoT Enterprise's inking capabilities.
+
+## Start Menu - Explore
+
+### Apps
+This page allows you to launch other foreground applications installed on the device. Launching an application will suspend IoT Enterprise Default App, which can be relaunched by using App Packages.
+
+Nothing special is needed to have your foreground application listed in the page, simply install or deploy the application. After successful installation or deployment, re-navigate to the Apps page to refresh the list of applications.
+
+Note that there are a couple of auto-generated OS related applications that we filter out, you can find the list of app names in the samples.
+
+### Notifications
+This page will list the past 20 notifications since IoT Enterprise Default App was launched. When IoT Enterprise Default App is running in debug mode, buttons are added that will create test notifications.
+
+### Logs
+This page will list any auto-generated crash or error logs, which then can be taken off the device and analyzed.
+
+### GitHub
+This page will take you to the open-sourced GitHub location of the IoT Enterprise Default App code.
+
+## Start Menu - Windows Device Portal
+
+The pages in this section leverage the Windows Device Portal REST APIs, which requires you to sign in using your Windows Device Portal credentials.
+
+## Device Information
+
+This page allows you to see the different features for your device including Ethernet, OS version, connected devices, and more.
+
+## Command Line
+
+This page allows you to run commands directly on your device.
+
+To enable this feature you have to set a registry key so that the app can run the commands.
+
+Some commands require administrator access. For security purposes the app uses a non-admin account by default to run commands. If you need to run a command as an admin you can type "RunAsAdmin " in the command line prompt.
+
+## Settings
+You'll be able to configure a number of settings here including Wi-Fi, Bluetooth, power options, and more.
+
+### App Settings
+The **App Settings** section allows you to configure various settings for pages in the app.
+
+Some of the settings you can customize are:
+
+##### Weather Settings
+* Change the location
+ > This feature is only enabled if you have provided a valid [Bing Map Service Token](https://msdn.microsoft.com/en-us/library/ff428642.aspx). To pass the token to the app, create a **MapToken.config** file in the LocalState folder of the app (e.g. C:\Data\USERS\\[User Account]\AppData\Packages\\[Package Full Name]\LocalState\MapToken.config) and restart the app.
+* Expand the map
+* Enable/disable map flipping so that the map and the weather switch places periodically to prevent screen burn-in
+
+##### Web Browser Settings
+* Set the home page for the Web Browser
+
+##### Slideshow Settings
+* Set the slideshow interval
+
+##### Appearance
+* Use MDL2 Assets instead of Emojis for the tile icons
+* Set the tile width and height
+* Set UI scaling - Automatic scaling is set by default
+* Set the tile color
+
+#### System
+Change the language, keyboard layout, and time zone.
+
+#### Network & Wi-Fi
+View network adapter properties or connect to an available Wi-Fi network.
+
+#### Bluetooth
+Pair with a Bluetooth device.
+
+#### App Updates
+Check for app updates or change automatic update settings.
+
+#### Power Options
+Restart or shutdown the device.
+
+#### Diagnostics
+Select the amount of diagnostic data you wish to provide Microsoft. We encourage users to opt into **Full** diagnostic data so we can diagnose issues quickly and make improvements to the product.
+
+##### Basic
+Send only info about your device, its settings and capabilities, and whether it is performing properly.
+
+##### Full
+Send all Basic diagnostic data, along with info about websites you browse and how you use apps and features, plus additional info about device health, device activity, and enhanced error reporting.
+
+#### Location
+Allow or deny the app access to your location.
diff --git a/samples/IoTHubClients/CS/Assets/test b/samples/IoTHubClients/CS/Assets/test
index d3f5a12fa..8b1378917 100644
--- a/samples/IoTHubClients/CS/Assets/test
+++ b/samples/IoTHubClients/CS/Assets/test
@@ -1 +1 @@
-
+
diff --git a/samples/IoTHubClients/CS/Properties/Default.rd.xml b/samples/IoTHubClients/CS/Properties/Default.rd.xml
index c0439a0a0..16232c238 100644
--- a/samples/IoTHubClients/CS/Properties/Default.rd.xml
+++ b/samples/IoTHubClients/CS/Properties/Default.rd.xml
@@ -1,31 +1,31 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/samples/IoTHubClients/CS/README.md b/samples/IoTHubClients/CS/README.md
index 9c08baca0..66c53f21c 100644
--- a/samples/IoTHubClients/CS/README.md
+++ b/samples/IoTHubClients/CS/README.md
@@ -1,76 +1,76 @@
----
-page_type: sample
-urlFragment: IoTHubClients
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
----
-
-# Azure IoT Hub Client Sample
-
-This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
-
-The sample is Microsoft IoT Central compatible. See below for a complete walk-through.
-
-# Walk-through: Connecting to Microsoft IoT Central
-
-This article describes how, as a device developer, to connect a device running a Windows 10 IoT Enterprise device to your Microsoft IoT Central application using the C# programming language.
-
-### Before you begin
-
-To complete the steps in this article, you need the following:
-
-- A Microsoft IoT Central application created from the Sample Devkits application template. For more information, see [Create your Microsoft IoT Central Application](https://docs.microsoft.com/en-us/microsoft-iot-central/howto-create-application).
-- A device running the [Windows 10 IoT Enterprise OS](https://docs.microsoft.com/windows/iot/iot-enterprise/downloads). For this walkthrough, we will use an UP Board.
-- [Visual Studio 2019](https://www.visualstudio.com/downloads/) installed (only needed if you are going to build/deploy the source code).
- - With 'The Universal Windows Platform development' workload installed.
-
-## Step 1: Add a Real Device in Microsoft IoT Central
-
-In Microsoft IoT Central,
-
-- Make a note of the device connection string. For more information, see Add a real device to your [Microsoft IoT Central application](https://docs.microsoft.com/en-us/microsoft-iot-central/tutorial-add-device).
-
-## Step 2: Setup A Physical Device
-
-To setup a physical device, we need:
-
-- A device running Windows IoT Enterprise operating system.
- - To do that, follow the steps described [here](https://developer.microsoft.com/en-us/windows/iot/getstarted/prototype/setupdevice).
-- A client application that can communicate with Microsoft IoT Central.
- - You can either build your own custom application using the Azure SDK and deploy it to your device (using Visual Studio). OR
- - You can download a pre-built sample and simply deploy and run it on the device.
-
-## Step 3: Deploy The Pre-built Sample Client Application to The Device
-
-To deploy the client application to your Windows IoT Device,
-
-- Ensure the connection string is stored on the device for the client application to use.
- - On the desktop, save the connection string in a text file named connection.string.iothub.
- - Copy the text file to the device’s document folder:
- - [device-IP-address]\C$\Data\Users\DefaultAccount\Documents\connection.string.iothub
-
-## Step 4: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 5: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-The application should launch on the device, and will look something like this:
-
-
-
-In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
-
-- On the Measurements page for your real device, you can see the telemetry.
-- On the Properties page, you can see the value of the reported Die Number property.
-
-## Source Code
-
-You can find the source code for this sample by downloading a zip of all of our samples.
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
-
+---
+page_type: sample
+urlFragment: IoTHubClients
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
+---
+
+# Azure IoT Hub Client Sample
+
+This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
+
+The sample is Microsoft IoT Central compatible. See below for a complete walk-through.
+
+# Walk-through: Connecting to Microsoft IoT Central
+
+This article describes how, as a device developer, to connect a device running a Windows 10 IoT Enterprise device to your Microsoft IoT Central application using the C# programming language.
+
+### Before you begin
+
+To complete the steps in this article, you need the following:
+
+- A Microsoft IoT Central application created from the Sample Devkits application template. For more information, see [Create your Microsoft IoT Central Application](https://docs.microsoft.com/en-us/microsoft-iot-central/howto-create-application).
+- A device running the [Windows 10 IoT Enterprise OS](https://docs.microsoft.com/windows/iot/iot-enterprise/downloads). For this walkthrough, we will use an UP Board.
+- [Visual Studio 2019](https://www.visualstudio.com/downloads/) installed (only needed if you are going to build/deploy the source code).
+ - With 'The Universal Windows Platform development' workload installed.
+
+## Step 1: Add a Real Device in Microsoft IoT Central
+
+In Microsoft IoT Central,
+
+- Make a note of the device connection string. For more information, see Add a real device to your [Microsoft IoT Central application](https://docs.microsoft.com/en-us/microsoft-iot-central/tutorial-add-device).
+
+## Step 2: Setup A Physical Device
+
+To setup a physical device, we need:
+
+- A device running Windows IoT Enterprise operating system.
+ - To do that, follow the steps described [here](https://developer.microsoft.com/en-us/windows/iot/getstarted/prototype/setupdevice).
+- A client application that can communicate with Microsoft IoT Central.
+ - You can either build your own custom application using the Azure SDK and deploy it to your device (using Visual Studio). OR
+ - You can download a pre-built sample and simply deploy and run it on the device.
+
+## Step 3: Deploy The Pre-built Sample Client Application to The Device
+
+To deploy the client application to your Windows IoT Device,
+
+- Ensure the connection string is stored on the device for the client application to use.
+ - On the desktop, save the connection string in a text file named connection.string.iothub.
+ - Copy the text file to the device’s document folder:
+ - [device-IP-address]\C$\Data\Users\DefaultAccount\Documents\connection.string.iothub
+
+## Step 4: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 5: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+The application should launch on the device, and will look something like this:
+
+
+
+In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
+
+- On the Measurements page for your real device, you can see the telemetry.
+- On the Properties page, you can see the value of the reported Die Number property.
+
+## Source Code
+
+You can find the source code for this sample by downloading a zip of all of our samples.
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+
diff --git a/samples/IoTHubClients/README.md b/samples/IoTHubClients/README.md
index cc9a4831c..a804b024c 100644
--- a/samples/IoTHubClients/README.md
+++ b/samples/IoTHubClients/README.md
@@ -1,76 +1,76 @@
----
-page_type: sample
-urlFragment: IoTHubClients
-languages:
- - csharp
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
----
-
-# Azure IoT Hub Client Sample
-
-This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
-
-The sample is Microsoft IoT Central compatible. See below for a complete walk-through.
-
-# Walk-through: Connecting to Microsoft IoT Central
-
-This article describes how, as a device developer, to connect a device running a Windows 10 IoT Enterprise device to your Microsoft IoT Central application using the C# programming language.
-
-### Before you begin
-
-To complete the steps in this article, you need the following:
-
-- A Microsoft IoT Central application created from the Sample Devkits application template. For more information, see [Create your Microsoft IoT Central Application](https://docs.microsoft.com/en-us/microsoft-iot-central/howto-create-application).
-- A device running the [Windows 10 IoT Enterprise OS](https://docs.microsoft.com/windows/iot/iot-enterprise/downloads). For this walkthrough, we will use an UP Board.
-- [Visual Studio 2019](https://www.visualstudio.com/downloads/) installed (only needed if you are going to build/deploy the source code).
- - With 'The Universal Windows Platform development' workload installed.
-
-## Step 1: Add a Real Device in Microsoft IoT Central
-
-In Microsoft IoT Central,
-
-- Make a note of the device connection string. For more information, see Add a real device to your [Microsoft IoT Central application](https://docs.microsoft.com/en-us/microsoft-iot-central/tutorial-add-device).
-
-## Step 2: Setup A Physical Device
-
-To setup a physical device, we need:
-
-- A device running Windows IoT Enterprise operating system.
- - To do that, follow the steps described [here](https://developer.microsoft.com/en-us/windows/iot/getstarted/prototype/setupdevice).
-- A client application that can communicate with Microsoft IoT Central.
- - You can either build your own custom application using the Azure SDK and deploy it to your device (using Visual Studio). OR
- - You can download a pre-built sample and simply deploy and run it on the device.
-
-## Step 3: Deploy The Pre-built Sample Client Application to The Device
-
-To deploy the client application to your Windows IoT Device,
-
-- Ensure the connection string is stored on the device for the client application to use.
- - On the desktop, save the connection string in a text file named connection.string.iothub.
- - Copy the text file to the device’s document folder:
- - [device-IP-address]\C$\Data\Users\DefaultAccount\Documents\connection.string.iothub
-
-## Step 4: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-## Step 5: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-The application should launch on the device, and will look something like this:
-
-
-
-In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
-
-- On the Measurements page for your real device, you can see the telemetry.
-- On the Properties page, you can see the value of the reported Die Number property.
-
-## Source Code
-
-You can find the source code for this sample by downloading a zip of all of our samples.
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
-
+---
+page_type: sample
+urlFragment: IoTHubClients
+languages:
+ - csharp
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
+---
+
+# Azure IoT Hub Client Sample
+
+This sample demonstrates how to connect to IoT Hub, send telemetry, and monitor and respond to device twin state changes.
+
+The sample is Microsoft IoT Central compatible. See below for a complete walk-through.
+
+# Walk-through: Connecting to Microsoft IoT Central
+
+This article describes how, as a device developer, to connect a device running a Windows 10 IoT Enterprise device to your Microsoft IoT Central application using the C# programming language.
+
+### Before you begin
+
+To complete the steps in this article, you need the following:
+
+- A Microsoft IoT Central application created from the Sample Devkits application template. For more information, see [Create your Microsoft IoT Central Application](https://docs.microsoft.com/en-us/microsoft-iot-central/howto-create-application).
+- A device running the [Windows 10 IoT Enterprise OS](https://docs.microsoft.com/windows/iot/iot-enterprise/downloads). For this walkthrough, we will use an UP Board.
+- [Visual Studio 2019](https://www.visualstudio.com/downloads/) installed (only needed if you are going to build/deploy the source code).
+ - With 'The Universal Windows Platform development' workload installed.
+
+## Step 1: Add a Real Device in Microsoft IoT Central
+
+In Microsoft IoT Central,
+
+- Make a note of the device connection string. For more information, see Add a real device to your [Microsoft IoT Central application](https://docs.microsoft.com/en-us/microsoft-iot-central/tutorial-add-device).
+
+## Step 2: Setup A Physical Device
+
+To setup a physical device, we need:
+
+- A device running Windows IoT Enterprise operating system.
+ - To do that, follow the steps described [here](https://developer.microsoft.com/en-us/windows/iot/getstarted/prototype/setupdevice).
+- A client application that can communicate with Microsoft IoT Central.
+ - You can either build your own custom application using the Azure SDK and deploy it to your device (using Visual Studio). OR
+ - You can download a pre-built sample and simply deploy and run it on the device.
+
+## Step 3: Deploy The Pre-built Sample Client Application to The Device
+
+To deploy the client application to your Windows IoT Device,
+
+- Ensure the connection string is stored on the device for the client application to use.
+ - On the desktop, save the connection string in a text file named connection.string.iothub.
+ - Copy the text file to the device’s document folder:
+ - [device-IP-address]\C$\Data\Users\DefaultAccount\Documents\connection.string.iothub
+
+## Step 4: [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+## Step 5: [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+The application should launch on the device, and will look something like this:
+
+
+
+In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
+
+- On the Measurements page for your real device, you can see the telemetry.
+- On the Properties page, you can see the value of the reported Die Number property.
+
+## Source Code
+
+You can find the source code for this sample by downloading a zip of all of our samples.
+
+This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.
+
diff --git a/samples/MemoryStatus/README.md b/samples/MemoryStatus/README.md
index fc3a85036..431062840 100644
--- a/samples/MemoryStatus/README.md
+++ b/samples/MemoryStatus/README.md
@@ -1,168 +1,168 @@
----
-page_type: sample
-urlFragment: memory-status
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: Create a console app that monitors memory usage on devices running Windows 10 IoT Enterprise.
----
-
-# Memory Status Monitor
-
-This sample is intended to show how to create a console application that can be used to query the memory usage on your Windows 10 IoT Enterprise device.
-
-
-## Step 1: Load the project in Visual Studio 2019
-1. Open the application in Visual Studio 2019
-2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select x64.
-3. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-
-
-## Step 2: Deploy your app
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-1. If you are using an UP Board, you have to setup the BIOS UART configuration.
-
- 1. Once you power on the UP board, select the Del or F7 key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to Boot > OS Image ID tab, and select Windows 10 IoT Core.
-
- 1. Navigate to the Advance tab and select the Hat Configuration and select GPIO Configuration in Pin Order.
-
- 1. Configure the Pins you are using in the sample as INPUT or OUTPUT.
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-1. Click the Start button to search for the app by name, and then launch it.
-
-* To add some functionality to our console, add the following memory status query and display code:
-
-```C++
-#include "pch.h"
-
-#include
-#include
-#include
-
-using namespace std;
-
-// Use to convert bytes to KB
-#define DIV 1024
-
-// Specify the width of the field in which to print the numbers.
-#define MESSAGE_WIDTH 30
-#define NUMERIC_WIDTH 10
-
-void printMessage(LPCSTR msg, bool addColon)
-{
- cout.width(MESSAGE_WIDTH);
- cout << msg ;
- if (addColon)
- {
- cout << " : ";
- }
-}
-
-void printMessageLine(LPCSTR msg)
-{
- printMessage(msg, false);
- cout << endl;
-}
-
-void printMessageLine(LPCSTR msg, DWORD value)
-{
- printMessage(msg, true);
- cout.width(NUMERIC_WIDTH);
- cout << right << value << endl;
-}
-
-void printMessageLine(LPCSTR msg, DWORDLONG value)
-{
- printMessage(msg, true);
- cout.width(NUMERIC_WIDTH);
- cout << right << value << endl;
-}
-
-void checkInput(HANDLE exitEvent)
-{
- for (;;)
- {
- char character;
- cin.get(character);
- if (character == 'q')
- {
- ::SetEvent(exitEvent);
- break;
- }
- }
-}
-
-int main(int argc, char **argv)
-{
- printMessageLine("Starting to monitor memory consumption! Press enter to start monitoring");
- printMessageLine("You can press q and enter at anytime to exit");
- cin.get();
- HANDLE exitEvent = ::CreateEvent(NULL, FALSE, FALSE, NULL);
- if (NULL == exitEvent)
- {
- printMessageLine("Failed to create exitEvent.");
- return -1;
- }
- std::thread inputThread(checkInput, exitEvent);
- for (;;)
- {
- MEMORYSTATUSEX statex;
- statex.dwLength = sizeof(statex);
-
- BOOL success = ::GlobalMemoryStatusEx(&statex);
- if (!success)
- {
- DWORD error = GetLastError();
- printMessageLine("*************************************************");
- printMessageLine("Error getting memory information", error);
- printMessageLine("*************************************************");
- }
- else
- {
- DWORD load = statex.dwMemoryLoad;
- DWORDLONG physKb = statex.ullTotalPhys / DIV;
- DWORDLONG freePhysKb = statex.ullAvailPhys / DIV;
- DWORDLONG pageKb = statex.ullTotalPageFile / DIV;
- DWORDLONG freePageKb = statex.ullAvailPageFile / DIV;
- DWORDLONG virtualKb = statex.ullTotalVirtual / DIV;
- DWORDLONG freeVirtualKb = statex.ullAvailVirtual / DIV;
- DWORDLONG freeExtKb = statex.ullAvailExtendedVirtual / DIV;
-
- printMessageLine("*************************************************");
-
- printMessageLine("Percent of memory in use", load);
- printMessageLine("KB of physical memory", physKb);
- printMessageLine("KB of free physical memory", freePhysKb);
- printMessageLine("KB of paging file", pageKb);
- printMessageLine("KB of free paging file", freePageKb);
- printMessageLine("KB of virtual memory", virtualKb);
- printMessageLine("KB of free virtual memory", freeVirtualKb);
- printMessageLine("KB of free extended memory", freeExtKb);
-
- printMessageLine("*************************************************");
-
- }
-
- if (WAIT_OBJECT_0 == ::WaitForSingleObject(exitEvent, 100))
- {
- break;
- }
- }
-
- inputThread.join();
- ::CloseHandle(exitEvent);
- printMessageLine("No longer monitoring memory consumption!");
-}
-```
-
-* Make sure the app builds correctly invoking the Build \| Build Solution menu command.
+---
+page_type: sample
+urlFragment: memory-status
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: Create a console app that monitors memory usage on devices running Windows 10 IoT Enterprise.
+---
+
+# Memory Status Monitor
+
+This sample is intended to show how to create a console application that can be used to query the memory usage on your Windows 10 IoT Enterprise device.
+
+
+## Step 1: Load the project in Visual Studio 2019
+1. Open the application in Visual Studio 2019
+2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select x64.
+3. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+
+
+## Step 2: Deploy your app
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+1. If you are using an UP Board, you have to setup the BIOS UART configuration.
+
+ 1. Once you power on the UP board, select the Del or F7 key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to Boot > OS Image ID tab, and select Windows 10 IoT Core.
+
+ 1. Navigate to the Advance tab and select the Hat Configuration and select GPIO Configuration in Pin Order.
+
+ 1. Configure the Pins you are using in the sample as INPUT or OUTPUT.
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+1. Click the Start button to search for the app by name, and then launch it.
+
+* To add some functionality to our console, add the following memory status query and display code:
+
+```C++
+#include "pch.h"
+
+#include
+#include
+#include
+
+using namespace std;
+
+// Use to convert bytes to KB
+#define DIV 1024
+
+// Specify the width of the field in which to print the numbers.
+#define MESSAGE_WIDTH 30
+#define NUMERIC_WIDTH 10
+
+void printMessage(LPCSTR msg, bool addColon)
+{
+ cout.width(MESSAGE_WIDTH);
+ cout << msg ;
+ if (addColon)
+ {
+ cout << " : ";
+ }
+}
+
+void printMessageLine(LPCSTR msg)
+{
+ printMessage(msg, false);
+ cout << endl;
+}
+
+void printMessageLine(LPCSTR msg, DWORD value)
+{
+ printMessage(msg, true);
+ cout.width(NUMERIC_WIDTH);
+ cout << right << value << endl;
+}
+
+void printMessageLine(LPCSTR msg, DWORDLONG value)
+{
+ printMessage(msg, true);
+ cout.width(NUMERIC_WIDTH);
+ cout << right << value << endl;
+}
+
+void checkInput(HANDLE exitEvent)
+{
+ for (;;)
+ {
+ char character;
+ cin.get(character);
+ if (character == 'q')
+ {
+ ::SetEvent(exitEvent);
+ break;
+ }
+ }
+}
+
+int main(int argc, char **argv)
+{
+ printMessageLine("Starting to monitor memory consumption! Press enter to start monitoring");
+ printMessageLine("You can press q and enter at anytime to exit");
+ cin.get();
+ HANDLE exitEvent = ::CreateEvent(NULL, FALSE, FALSE, NULL);
+ if (NULL == exitEvent)
+ {
+ printMessageLine("Failed to create exitEvent.");
+ return -1;
+ }
+ std::thread inputThread(checkInput, exitEvent);
+ for (;;)
+ {
+ MEMORYSTATUSEX statex;
+ statex.dwLength = sizeof(statex);
+
+ BOOL success = ::GlobalMemoryStatusEx(&statex);
+ if (!success)
+ {
+ DWORD error = GetLastError();
+ printMessageLine("*************************************************");
+ printMessageLine("Error getting memory information", error);
+ printMessageLine("*************************************************");
+ }
+ else
+ {
+ DWORD load = statex.dwMemoryLoad;
+ DWORDLONG physKb = statex.ullTotalPhys / DIV;
+ DWORDLONG freePhysKb = statex.ullAvailPhys / DIV;
+ DWORDLONG pageKb = statex.ullTotalPageFile / DIV;
+ DWORDLONG freePageKb = statex.ullAvailPageFile / DIV;
+ DWORDLONG virtualKb = statex.ullTotalVirtual / DIV;
+ DWORDLONG freeVirtualKb = statex.ullAvailVirtual / DIV;
+ DWORDLONG freeExtKb = statex.ullAvailExtendedVirtual / DIV;
+
+ printMessageLine("*************************************************");
+
+ printMessageLine("Percent of memory in use", load);
+ printMessageLine("KB of physical memory", physKb);
+ printMessageLine("KB of free physical memory", freePhysKb);
+ printMessageLine("KB of paging file", pageKb);
+ printMessageLine("KB of free paging file", freePageKb);
+ printMessageLine("KB of virtual memory", virtualKb);
+ printMessageLine("KB of free virtual memory", freeVirtualKb);
+ printMessageLine("KB of free extended memory", freeExtKb);
+
+ printMessageLine("*************************************************");
+
+ }
+
+ if (WAIT_OBJECT_0 == ::WaitForSingleObject(exitEvent, 100))
+ {
+ break;
+ }
+ }
+
+ inputThread.join();
+ ::CloseHandle(exitEvent);
+ printMessageLine("No longer monitoring memory consumption!");
+}
+```
+
+* Make sure the app builds correctly invoking the Build \| Build Solution menu command.
diff --git a/samples/MemoryStatus/cpp/README.md b/samples/MemoryStatus/cpp/README.md
index fc3a85036..431062840 100644
--- a/samples/MemoryStatus/cpp/README.md
+++ b/samples/MemoryStatus/cpp/README.md
@@ -1,168 +1,168 @@
----
-page_type: sample
-urlFragment: memory-status
-languages:
- - cpp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: Create a console app that monitors memory usage on devices running Windows 10 IoT Enterprise.
----
-
-# Memory Status Monitor
-
-This sample is intended to show how to create a console application that can be used to query the memory usage on your Windows 10 IoT Enterprise device.
-
-
-## Step 1: Load the project in Visual Studio 2019
-1. Open the application in Visual Studio 2019
-2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select x64.
-3. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
-
-
-## Step 2: Deploy your app
-1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
-
-1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
-
-1. If you are using an UP Board, you have to setup the BIOS UART configuration.
-
- 1. Once you power on the UP board, select the Del or F7 key on your keyboard to enter the BIOS setting.
-
- 1. Navigate to Boot > OS Image ID tab, and select Windows 10 IoT Core.
-
- 1. Navigate to the Advance tab and select the Hat Configuration and select GPIO Configuration in Pin Order.
-
- 1. Configure the Pins you are using in the sample as INPUT or OUTPUT.
-
- 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
-
-1. Click the Start button to search for the app by name, and then launch it.
-
-* To add some functionality to our console, add the following memory status query and display code:
-
-```C++
-#include "pch.h"
-
-#include
-#include
-#include
-
-using namespace std;
-
-// Use to convert bytes to KB
-#define DIV 1024
-
-// Specify the width of the field in which to print the numbers.
-#define MESSAGE_WIDTH 30
-#define NUMERIC_WIDTH 10
-
-void printMessage(LPCSTR msg, bool addColon)
-{
- cout.width(MESSAGE_WIDTH);
- cout << msg ;
- if (addColon)
- {
- cout << " : ";
- }
-}
-
-void printMessageLine(LPCSTR msg)
-{
- printMessage(msg, false);
- cout << endl;
-}
-
-void printMessageLine(LPCSTR msg, DWORD value)
-{
- printMessage(msg, true);
- cout.width(NUMERIC_WIDTH);
- cout << right << value << endl;
-}
-
-void printMessageLine(LPCSTR msg, DWORDLONG value)
-{
- printMessage(msg, true);
- cout.width(NUMERIC_WIDTH);
- cout << right << value << endl;
-}
-
-void checkInput(HANDLE exitEvent)
-{
- for (;;)
- {
- char character;
- cin.get(character);
- if (character == 'q')
- {
- ::SetEvent(exitEvent);
- break;
- }
- }
-}
-
-int main(int argc, char **argv)
-{
- printMessageLine("Starting to monitor memory consumption! Press enter to start monitoring");
- printMessageLine("You can press q and enter at anytime to exit");
- cin.get();
- HANDLE exitEvent = ::CreateEvent(NULL, FALSE, FALSE, NULL);
- if (NULL == exitEvent)
- {
- printMessageLine("Failed to create exitEvent.");
- return -1;
- }
- std::thread inputThread(checkInput, exitEvent);
- for (;;)
- {
- MEMORYSTATUSEX statex;
- statex.dwLength = sizeof(statex);
-
- BOOL success = ::GlobalMemoryStatusEx(&statex);
- if (!success)
- {
- DWORD error = GetLastError();
- printMessageLine("*************************************************");
- printMessageLine("Error getting memory information", error);
- printMessageLine("*************************************************");
- }
- else
- {
- DWORD load = statex.dwMemoryLoad;
- DWORDLONG physKb = statex.ullTotalPhys / DIV;
- DWORDLONG freePhysKb = statex.ullAvailPhys / DIV;
- DWORDLONG pageKb = statex.ullTotalPageFile / DIV;
- DWORDLONG freePageKb = statex.ullAvailPageFile / DIV;
- DWORDLONG virtualKb = statex.ullTotalVirtual / DIV;
- DWORDLONG freeVirtualKb = statex.ullAvailVirtual / DIV;
- DWORDLONG freeExtKb = statex.ullAvailExtendedVirtual / DIV;
-
- printMessageLine("*************************************************");
-
- printMessageLine("Percent of memory in use", load);
- printMessageLine("KB of physical memory", physKb);
- printMessageLine("KB of free physical memory", freePhysKb);
- printMessageLine("KB of paging file", pageKb);
- printMessageLine("KB of free paging file", freePageKb);
- printMessageLine("KB of virtual memory", virtualKb);
- printMessageLine("KB of free virtual memory", freeVirtualKb);
- printMessageLine("KB of free extended memory", freeExtKb);
-
- printMessageLine("*************************************************");
-
- }
-
- if (WAIT_OBJECT_0 == ::WaitForSingleObject(exitEvent, 100))
- {
- break;
- }
- }
-
- inputThread.join();
- ::CloseHandle(exitEvent);
- printMessageLine("No longer monitoring memory consumption!");
-}
-```
-
-* Make sure the app builds correctly invoking the Build \| Build Solution menu command.
+---
+page_type: sample
+urlFragment: memory-status
+languages:
+ - cpp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: Create a console app that monitors memory usage on devices running Windows 10 IoT Enterprise.
+---
+
+# Memory Status Monitor
+
+This sample is intended to show how to create a console application that can be used to query the memory usage on your Windows 10 IoT Enterprise device.
+
+
+## Step 1: Load the project in Visual Studio 2019
+1. Open the application in Visual Studio 2019
+2. Set the architecture in the toolbar dropdown. If you’re building for the UP Board, select x64.
+3. Select **Local Machine** to point to IoT device and hit F5 to deploy to your device.
+
+
+## Step 2: Deploy your app
+1. [Generate an app package](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#generate-an-app-package)
+
+1. [Install your app package using an install script](https://docs.microsoft.com/windows/msix/package/packaging-uwp-apps#install-your-app-package-using-an-install-script)
+
+1. If you are using an UP Board, you have to setup the BIOS UART configuration.
+
+ 1. Once you power on the UP board, select the Del or F7 key on your keyboard to enter the BIOS setting.
+
+ 1. Navigate to Boot > OS Image ID tab, and select Windows 10 IoT Core.
+
+ 1. Navigate to the Advance tab and select the Hat Configuration and select GPIO Configuration in Pin Order.
+
+ 1. Configure the Pins you are using in the sample as INPUT or OUTPUT.
+
+ 1. For more information, please review the [UP Board Firmware Settings](https://www.annabooks.com/Articles/Articles_IoT10/Windows-10-IoT-UP-Board-BIOS-RHPROXY-Rev1.3.pdf).
+
+1. Click the Start button to search for the app by name, and then launch it.
+
+* To add some functionality to our console, add the following memory status query and display code:
+
+```C++
+#include "pch.h"
+
+#include
+#include
+#include
+
+using namespace std;
+
+// Use to convert bytes to KB
+#define DIV 1024
+
+// Specify the width of the field in which to print the numbers.
+#define MESSAGE_WIDTH 30
+#define NUMERIC_WIDTH 10
+
+void printMessage(LPCSTR msg, bool addColon)
+{
+ cout.width(MESSAGE_WIDTH);
+ cout << msg ;
+ if (addColon)
+ {
+ cout << " : ";
+ }
+}
+
+void printMessageLine(LPCSTR msg)
+{
+ printMessage(msg, false);
+ cout << endl;
+}
+
+void printMessageLine(LPCSTR msg, DWORD value)
+{
+ printMessage(msg, true);
+ cout.width(NUMERIC_WIDTH);
+ cout << right << value << endl;
+}
+
+void printMessageLine(LPCSTR msg, DWORDLONG value)
+{
+ printMessage(msg, true);
+ cout.width(NUMERIC_WIDTH);
+ cout << right << value << endl;
+}
+
+void checkInput(HANDLE exitEvent)
+{
+ for (;;)
+ {
+ char character;
+ cin.get(character);
+ if (character == 'q')
+ {
+ ::SetEvent(exitEvent);
+ break;
+ }
+ }
+}
+
+int main(int argc, char **argv)
+{
+ printMessageLine("Starting to monitor memory consumption! Press enter to start monitoring");
+ printMessageLine("You can press q and enter at anytime to exit");
+ cin.get();
+ HANDLE exitEvent = ::CreateEvent(NULL, FALSE, FALSE, NULL);
+ if (NULL == exitEvent)
+ {
+ printMessageLine("Failed to create exitEvent.");
+ return -1;
+ }
+ std::thread inputThread(checkInput, exitEvent);
+ for (;;)
+ {
+ MEMORYSTATUSEX statex;
+ statex.dwLength = sizeof(statex);
+
+ BOOL success = ::GlobalMemoryStatusEx(&statex);
+ if (!success)
+ {
+ DWORD error = GetLastError();
+ printMessageLine("*************************************************");
+ printMessageLine("Error getting memory information", error);
+ printMessageLine("*************************************************");
+ }
+ else
+ {
+ DWORD load = statex.dwMemoryLoad;
+ DWORDLONG physKb = statex.ullTotalPhys / DIV;
+ DWORDLONG freePhysKb = statex.ullAvailPhys / DIV;
+ DWORDLONG pageKb = statex.ullTotalPageFile / DIV;
+ DWORDLONG freePageKb = statex.ullAvailPageFile / DIV;
+ DWORDLONG virtualKb = statex.ullTotalVirtual / DIV;
+ DWORDLONG freeVirtualKb = statex.ullAvailVirtual / DIV;
+ DWORDLONG freeExtKb = statex.ullAvailExtendedVirtual / DIV;
+
+ printMessageLine("*************************************************");
+
+ printMessageLine("Percent of memory in use", load);
+ printMessageLine("KB of physical memory", physKb);
+ printMessageLine("KB of free physical memory", freePhysKb);
+ printMessageLine("KB of paging file", pageKb);
+ printMessageLine("KB of free paging file", freePageKb);
+ printMessageLine("KB of virtual memory", virtualKb);
+ printMessageLine("KB of free virtual memory", freeVirtualKb);
+ printMessageLine("KB of free extended memory", freeExtKb);
+
+ printMessageLine("*************************************************");
+
+ }
+
+ if (WAIT_OBJECT_0 == ::WaitForSingleObject(exitEvent, 100))
+ {
+ break;
+ }
+ }
+
+ inputThread.join();
+ ::CloseHandle(exitEvent);
+ printMessageLine("No longer monitoring memory consumption!");
+}
+```
+
+* Make sure the app builds correctly invoking the Build \| Build Solution menu command.
diff --git a/samples/NTServiceRpc/README.md b/samples/NTServiceRpc/README.md
index 589645edc..72a1fc71f 100644
--- a/samples/NTServiceRpc/README.md
+++ b/samples/NTServiceRpc/README.md
@@ -1,43 +1,43 @@
----
-page_type: sample
-urlFragment: NTService-RPC
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates the use of a NT service with an UWP app and Windows 10 IoT Enterprise.
----
-
-# NT Service example
-
-This sample demonstrates the use of a NT service with an UWP app. Communication between the app and the service is done through RPC.
-
-## Goal
-
-This sample shows how UWP can communicate with a NT service, allowing it to perform privileged actions. In this sample, the UWP app will check the status of services and start/stop them.
-
-## Security
-
-The NT service must be not open to any application, since an untrusted application would have control of system services. We can limit the access with Access Control Lists (ACL) on the RPC server.
-
-The ACL can contain, for example, rules to require the existence of a capability (e.g. only applications with the system management capability, or with a custom capability) or a specific Package Family Name (PFN). In this example, only a specific PFN will be able to connect to the service.
-
-## Platforms
-
-This sample can run on ARM, x64 and x86, on both Windows for IoT and Desktop.
-
-## Projects
-
-This solution has three projects:
-
-* **RpcInterface**: Has a IDL file ([Interface Definition Language](https://msdn.microsoft.com/en-us/library/windows/desktop/aa367091(v=vs.85).aspx)) with the definition of the RPC interface (functions and its arguments).
-* **RpcServer**: RPC server. Runs as a NT service and receives RPC calls to return the status, start or stop other NT services.
-* **NTServiceRpc**: Sample UWP app consuming the NT service.
-
-
-## Further information
-
-* [Add a service component to Windows Universal OEM Packages](https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-packages#add-a-service-component)
-* To create an OEM package that includes a service. For a sample of such usage, see [this sample on iot-adk-addonkit](https://github.com/ms-iot/iot-adk-addonkit/blob/26738284601eceeebc9989f884a411ae452d2f3a/Source-arm/Packages/AzureDM.Services/AzureDM.Services.wm.xml).
+---
+page_type: sample
+urlFragment: NTService-RPC
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates the use of a NT service with an UWP app and Windows 10 IoT Enterprise.
+---
+
+# NT Service example
+
+This sample demonstrates the use of a NT service with an UWP app. Communication between the app and the service is done through RPC.
+
+## Goal
+
+This sample shows how UWP can communicate with a NT service, allowing it to perform privileged actions. In this sample, the UWP app will check the status of services and start/stop them.
+
+## Security
+
+The NT service must be not open to any application, since an untrusted application would have control of system services. We can limit the access with Access Control Lists (ACL) on the RPC server.
+
+The ACL can contain, for example, rules to require the existence of a capability (e.g. only applications with the system management capability, or with a custom capability) or a specific Package Family Name (PFN). In this example, only a specific PFN will be able to connect to the service.
+
+## Platforms
+
+This sample can run on ARM, x64 and x86, on both Windows for IoT and Desktop.
+
+## Projects
+
+This solution has three projects:
+
+* **RpcInterface**: Has a IDL file ([Interface Definition Language](https://msdn.microsoft.com/en-us/library/windows/desktop/aa367091(v=vs.85).aspx)) with the definition of the RPC interface (functions and its arguments).
+* **RpcServer**: RPC server. Runs as a NT service and receives RPC calls to return the status, start or stop other NT services.
+* **NTServiceRpc**: Sample UWP app consuming the NT service.
+
+
+## Further information
+
+* [Add a service component to Windows Universal OEM Packages](https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-packages#add-a-service-component)
+* To create an OEM package that includes a service. For a sample of such usage, see [this sample on iot-adk-addonkit](https://github.com/ms-iot/iot-adk-addonkit/blob/26738284601eceeebc9989f884a411ae452d2f3a/Source-arm/Packages/AzureDM.Services/AzureDM.Services.wm.xml).
diff --git a/samples/NTServiceRpc/cpp/README.md b/samples/NTServiceRpc/cpp/README.md
index 589645edc..72a1fc71f 100644
--- a/samples/NTServiceRpc/cpp/README.md
+++ b/samples/NTServiceRpc/cpp/README.md
@@ -1,43 +1,43 @@
----
-page_type: sample
-urlFragment: NTService-RPC
-languages:
- - csharp
-products:
- - Windows 10
- - Windows IoT
- - Windows 10 IoT Enterprise
-description: This sample demonstrates the use of a NT service with an UWP app and Windows 10 IoT Enterprise.
----
-
-# NT Service example
-
-This sample demonstrates the use of a NT service with an UWP app. Communication between the app and the service is done through RPC.
-
-## Goal
-
-This sample shows how UWP can communicate with a NT service, allowing it to perform privileged actions. In this sample, the UWP app will check the status of services and start/stop them.
-
-## Security
-
-The NT service must be not open to any application, since an untrusted application would have control of system services. We can limit the access with Access Control Lists (ACL) on the RPC server.
-
-The ACL can contain, for example, rules to require the existence of a capability (e.g. only applications with the system management capability, or with a custom capability) or a specific Package Family Name (PFN). In this example, only a specific PFN will be able to connect to the service.
-
-## Platforms
-
-This sample can run on ARM, x64 and x86, on both Windows for IoT and Desktop.
-
-## Projects
-
-This solution has three projects:
-
-* **RpcInterface**: Has a IDL file ([Interface Definition Language](https://msdn.microsoft.com/en-us/library/windows/desktop/aa367091(v=vs.85).aspx)) with the definition of the RPC interface (functions and its arguments).
-* **RpcServer**: RPC server. Runs as a NT service and receives RPC calls to return the status, start or stop other NT services.
-* **NTServiceRpc**: Sample UWP app consuming the NT service.
-
-
-## Further information
-
-* [Add a service component to Windows Universal OEM Packages](https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-packages#add-a-service-component)
-* To create an OEM package that includes a service. For a sample of such usage, see [this sample on iot-adk-addonkit](https://github.com/ms-iot/iot-adk-addonkit/blob/26738284601eceeebc9989f884a411ae452d2f3a/Source-arm/Packages/AzureDM.Services/AzureDM.Services.wm.xml).
+---
+page_type: sample
+urlFragment: NTService-RPC
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample demonstrates the use of a NT service with an UWP app and Windows 10 IoT Enterprise.
+---
+
+# NT Service example
+
+This sample demonstrates the use of a NT service with an UWP app. Communication between the app and the service is done through RPC.
+
+## Goal
+
+This sample shows how UWP can communicate with a NT service, allowing it to perform privileged actions. In this sample, the UWP app will check the status of services and start/stop them.
+
+## Security
+
+The NT service must be not open to any application, since an untrusted application would have control of system services. We can limit the access with Access Control Lists (ACL) on the RPC server.
+
+The ACL can contain, for example, rules to require the existence of a capability (e.g. only applications with the system management capability, or with a custom capability) or a specific Package Family Name (PFN). In this example, only a specific PFN will be able to connect to the service.
+
+## Platforms
+
+This sample can run on ARM, x64 and x86, on both Windows for IoT and Desktop.
+
+## Projects
+
+This solution has three projects:
+
+* **RpcInterface**: Has a IDL file ([Interface Definition Language](https://msdn.microsoft.com/en-us/library/windows/desktop/aa367091(v=vs.85).aspx)) with the definition of the RPC interface (functions and its arguments).
+* **RpcServer**: RPC server. Runs as a NT service and receives RPC calls to return the status, start or stop other NT services.
+* **NTServiceRpc**: Sample UWP app consuming the NT service.
+
+
+## Further information
+
+* [Add a service component to Windows Universal OEM Packages](https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-packages#add-a-service-component)
+* To create an OEM package that includes a service. For a sample of such usage, see [this sample on iot-adk-addonkit](https://github.com/ms-iot/iot-adk-addonkit/blob/26738284601eceeebc9989f884a411ae452d2f3a/Source-arm/Packages/AzureDM.Services/AzureDM.Services.wm.xml).
diff --git a/samples/NTServiceRpc/cpp/Service/Interface/RpcInterface.acf b/samples/NTServiceRpc/cpp/Service/Interface/RpcInterface.acf
index a7ebe55e6..d00ed5afc 100644
--- a/samples/NTServiceRpc/cpp/Service/Interface/RpcInterface.acf
+++ b/samples/NTServiceRpc/cpp/Service/Interface/RpcInterface.acf
@@ -1,17 +1,17 @@
-//*********************************************************
-//
-// Copyright (c) Microsoft. All rights reserved.
-// This code is licensed under the Microsoft Public License.
-// THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF
-// ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY
-// IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR
-// PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
-//
-//*********************************************************
-
-
-interface RpcInterface
-{
- // We need the RPC to call rundown when the client goes away
- typedef [context_handle_noserialize] PCONTEXT_HANDLE_TYPE;
-}
+//*********************************************************
+//
+// Copyright (c) Microsoft. All rights reserved.
+// This code is licensed under the Microsoft Public License.
+// THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF
+// ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY
+// IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR
+// PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
+//
+//*********************************************************
+
+
+interface RpcInterface
+{
+ // We need the RPC to call rundown when the client goes away
+ typedef [context_handle_noserialize] PCONTEXT_HANDLE_TYPE;
+}
diff --git a/samples/NTServiceRpc/cpp/docs/ACL.md b/samples/NTServiceRpc/cpp/docs/ACL.md
index 679d72e66..d72fb59a4 100644
--- a/samples/NTServiceRpc/cpp/docs/ACL.md
+++ b/samples/NTServiceRpc/cpp/docs/ACL.md
@@ -1,78 +1,78 @@
-# Using ACLs to limit access to the NT service
-
-In the RPC server of the NT service, we want to allow access only from known applications. We can
-limit the access with Access Control Lists (ACL).
-
-The ACL can contain, for example, rules to require the existence of a capability (e.g. only
-applications with the system management capability, or with a custom capability) or a specific
-Package Family Name (PFN). For an example using a custom capability, see [this Windows universal sample](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/CustomCapability)
-and [documentation to create and reserve a custom capability](https://docs.microsoft.com/en-us/windows-hardware/drivers/devapps/creating-a-custom-capability-to-pair-driver-with-hsa).
-In this sample, only a specific PFN will be able to connect to the service. In [RpcServer.cpp](../../cpp/Service/Server/RpcServer.cpp),
-we have a function (`BuildAcl`) to create the ACL:
-
-* First, it gets a security identifier for everyone running outside an AppContainer. Non-sandboxed
-apps will have access to the service.
-* Then, it gets a security identifier for our app name.
-* An ACL is built from these two entries.
-
-```cpp
-const PWSTR AllowedPackageFamilyName = L"Microsoft.SDKSamples.NTServiceRpc.CPP_8wekyb3d8bbwe";
-
-PACL BuildAcl()
-{
- SID_IDENTIFIER_AUTHORITY SIDAuthWorld = SECURITY_WORLD_SID_AUTHORITY;
- PSID everyoneSid = nullptr;
- EXPLICIT_ACCESS ea[2] = {};
-
- // Get the SID that represents 'everyone' (this doesn't include AppContainers)
- if (!AllocateAndInitializeSid(
- &SIDAuthWorld, 1,
- SECURITY_WORLD_RID,
- 0, 0, 0, 0, 0, 0, 0,
- &everyoneSid))
- {
- ThrowLastError("AllocateAndInitializeSid");
- }
- // Everyone GENERIC_ALL access
- ea[0].grfAccessMode = SET_ACCESS;
- ea[0].grfAccessPermissions = GENERIC_ALL;
- ea[0].grfInheritance = NO_INHERITANCE;
- ea[0].Trustee.TrusteeForm = TRUSTEE_IS_SID;
- ea[0].Trustee.TrusteeType = TRUSTEE_IS_WELL_KNOWN_GROUP;
- ea[0].Trustee.ptstrName = static_cast(everyoneSid);
-
- // When creating the RPC endpoint we want it to allow connections from the UWA with a
- // specific package family name. By default, RPC endpoints don't allow UWAs (AppContainer processes)
- // to connect to them, so we need to set the security on the endpoint to allow access to our specific
- // UWA.
- //
- // To do this we'll perform the following steps:
- // 1) Create a SID for the allowed package family name
- // 2) Create a security descriptor using that SID
- // 3) Create the RPC endpoint using that security descriptor
- PSID pfnSid = nullptr;
- HRESULT hResult = DeriveAppContainerSidFromAppContainerName(AllowedPackageFamilyName, &pfnSid);
- FreeSid(everyoneSid);
- if (hResult != S_OK)
- {
- ThrowLastError("DeriveAppContainerSidFromAppContainerName", hResult);
- }
-
- ea[1].grfAccessMode = SET_ACCESS;
- ea[1].grfAccessPermissions = GENERIC_ALL;
- ea[1].grfInheritance = NO_INHERITANCE;
- ea[1].Trustee.TrusteeForm = TRUSTEE_IS_SID;
- ea[1].Trustee.TrusteeType = TRUSTEE_IS_UNKNOWN;
- ea[1].Trustee.ptstrName = static_cast(pfnSid);
- PACL acl = nullptr;
- hResult = SetEntriesInAcl(ARRAYSIZE(ea), ea, nullptr, &acl);
- FreeSid(pfnSid);
- if (hResult != ERROR_SUCCESS)
- {
- ThrowLastError("DeriveAppContainerSidFromAppContainerName", hResult);
- }
- return acl;
-}
-```
-
-The `RpcServerStart` function will start a RPC server using the ACL returned by `BuildAcl`.
+# Using ACLs to limit access to the NT service
+
+In the RPC server of the NT service, we want to allow access only from known applications. We can
+limit the access with Access Control Lists (ACL).
+
+The ACL can contain, for example, rules to require the existence of a capability (e.g. only
+applications with the system management capability, or with a custom capability) or a specific
+Package Family Name (PFN). For an example using a custom capability, see [this Windows universal sample](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/CustomCapability)
+and [documentation to create and reserve a custom capability](https://docs.microsoft.com/en-us/windows-hardware/drivers/devapps/creating-a-custom-capability-to-pair-driver-with-hsa).
+In this sample, only a specific PFN will be able to connect to the service. In [RpcServer.cpp](../../cpp/Service/Server/RpcServer.cpp),
+we have a function (`BuildAcl`) to create the ACL:
+
+* First, it gets a security identifier for everyone running outside an AppContainer. Non-sandboxed
+apps will have access to the service.
+* Then, it gets a security identifier for our app name.
+* An ACL is built from these two entries.
+
+```cpp
+const PWSTR AllowedPackageFamilyName = L"Microsoft.SDKSamples.NTServiceRpc.CPP_8wekyb3d8bbwe";
+
+PACL BuildAcl()
+{
+ SID_IDENTIFIER_AUTHORITY SIDAuthWorld = SECURITY_WORLD_SID_AUTHORITY;
+ PSID everyoneSid = nullptr;
+ EXPLICIT_ACCESS ea[2] = {};
+
+ // Get the SID that represents 'everyone' (this doesn't include AppContainers)
+ if (!AllocateAndInitializeSid(
+ &SIDAuthWorld, 1,
+ SECURITY_WORLD_RID,
+ 0, 0, 0, 0, 0, 0, 0,
+ &everyoneSid))
+ {
+ ThrowLastError("AllocateAndInitializeSid");
+ }
+ // Everyone GENERIC_ALL access
+ ea[0].grfAccessMode = SET_ACCESS;
+ ea[0].grfAccessPermissions = GENERIC_ALL;
+ ea[0].grfInheritance = NO_INHERITANCE;
+ ea[0].Trustee.TrusteeForm = TRUSTEE_IS_SID;
+ ea[0].Trustee.TrusteeType = TRUSTEE_IS_WELL_KNOWN_GROUP;
+ ea[0].Trustee.ptstrName = static_cast(everyoneSid);
+
+ // When creating the RPC endpoint we want it to allow connections from the UWA with a
+ // specific package family name. By default, RPC endpoints don't allow UWAs (AppContainer processes)
+ // to connect to them, so we need to set the security on the endpoint to allow access to our specific
+ // UWA.
+ //
+ // To do this we'll perform the following steps:
+ // 1) Create a SID for the allowed package family name
+ // 2) Create a security descriptor using that SID
+ // 3) Create the RPC endpoint using that security descriptor
+ PSID pfnSid = nullptr;
+ HRESULT hResult = DeriveAppContainerSidFromAppContainerName(AllowedPackageFamilyName, &pfnSid);
+ FreeSid(everyoneSid);
+ if (hResult != S_OK)
+ {
+ ThrowLastError("DeriveAppContainerSidFromAppContainerName", hResult);
+ }
+
+ ea[1].grfAccessMode = SET_ACCESS;
+ ea[1].grfAccessPermissions = GENERIC_ALL;
+ ea[1].grfInheritance = NO_INHERITANCE;
+ ea[1].Trustee.TrusteeForm = TRUSTEE_IS_SID;
+ ea[1].Trustee.TrusteeType = TRUSTEE_IS_UNKNOWN;
+ ea[1].Trustee.ptstrName = static_cast(pfnSid);
+ PACL acl = nullptr;
+ hResult = SetEntriesInAcl(ARRAYSIZE(ea), ea, nullptr, &acl);
+ FreeSid(pfnSid);
+ if (hResult != ERROR_SUCCESS)
+ {
+ ThrowLastError("DeriveAppContainerSidFromAppContainerName", hResult);
+ }
+ return acl;
+}
+```
+
+The `RpcServerStart` function will start a RPC server using the ACL returned by `BuildAcl`.
diff --git a/samples/NTServiceRpc/cpp/docs/Client.md b/samples/NTServiceRpc/cpp/docs/Client.md
index 6158d54c4..5adcdabf8 100644
--- a/samples/NTServiceRpc/cpp/docs/Client.md
+++ b/samples/NTServiceRpc/cpp/docs/Client.md
@@ -1,19 +1,19 @@
-# Client connection to RPC
-
-The client is an usual UWP app. The file [RpcClient.cpp](../RpcClient.cpp) has function `Initialize`, which opens the RPC connection passing a pointer to a pointer to a context for the service to use. The service will allocate whatever it wants as a context and write the pointer. All other functions simply call RPC interfaces passing the context and any arguments.
-
-However, the RPC functions can block and can't be called from the UI thread. Calling a blocking operation on the UI thread is forbidden in UWP to keep the UI responsive. We can use asynchronous tasks to call the RPC endpoints and update the UI whenever they return. This behavior is implemented in [RpcAsyncWrapper.cpp](../RpcAsyncWrapper.cpp), which is a wrapper returning `Concurrency::task` instances.
-
-From the application, we can now use the asynchronous functions and give them completion callbacks. For example, in `MainPage.xaml.cpp`, the code for the `Start` button calls our wrapper, catches exceptions and shows them in the UI, or updates the UI with the result:
-
-```cpp
-void MainPage::Start_Click(Object^, RoutedEventArgs^)
-{
- rpc.RunService(ServiceNameTextBox->Text->Data()).then([this](Concurrency::task t)
- {
- CatchRpcException(t, static_cast>([this]() {
- NotifyUser("Service started");
- }));
- });
-}
-```
+# Client connection to RPC
+
+The client is an usual UWP app. The file [RpcClient.cpp](../RpcClient.cpp) has function `Initialize`, which opens the RPC connection passing a pointer to a pointer to a context for the service to use. The service will allocate whatever it wants as a context and write the pointer. All other functions simply call RPC interfaces passing the context and any arguments.
+
+However, the RPC functions can block and can't be called from the UI thread. Calling a blocking operation on the UI thread is forbidden in UWP to keep the UI responsive. We can use asynchronous tasks to call the RPC endpoints and update the UI whenever they return. This behavior is implemented in [RpcAsyncWrapper.cpp](../RpcAsyncWrapper.cpp), which is a wrapper returning `Concurrency::task` instances.
+
+From the application, we can now use the asynchronous functions and give them completion callbacks. For example, in `MainPage.xaml.cpp`, the code for the `Start` button calls our wrapper, catches exceptions and shows them in the UI, or updates the UI with the result:
+
+```cpp
+void MainPage::Start_Click(Object^, RoutedEventArgs^)
+{
+ rpc.RunService(ServiceNameTextBox->Text->Data()).then([this](Concurrency::task t)
+ {
+ CatchRpcException(t, static_cast>([this]() {
+ NotifyUser("Service started");
+ }));
+ });
+}
+```
diff --git a/samples/NTServiceRpc/cpp/docs/IoT.md b/samples/NTServiceRpc/cpp/docs/IoT.md
index 8e47559ef..6a5828f87 100644
--- a/samples/NTServiceRpc/cpp/docs/IoT.md
+++ b/samples/NTServiceRpc/cpp/docs/IoT.md
@@ -1,9 +1,9 @@
-# Running the service and app in IoT
-
-To run the projects in Windows for IoT:
-
-* Set the target platform according to your device (in this example, we're building for a Raspberry Pi 3, so the platform is set to ARM) and build all the projects (Ctrl + Shift + B or Build > Build Solution).
-* Copy the service executable to the board. The executable can be found at `cpp//
+---
+page_type: sample
+urlFragment: DMMockPortal
+languages:
+ - csharp
+products:
+ - Windows 10
+ - Windows IoT
+ - Windows 10 IoT Enterprise
+description: This sample tool allows the user to update devices individually or in bulk in Azure ADM service.
+---
+
+# DM Mock Portal
+
+This tool allows the user to update devices individually or in bulk. It utilizes [Azure's ADM](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-auto-device-config) service.
+
+While you may find this tool useful, it was primary developed as a sample to show how an operator's flow might look like - specifically when it comes to bulk updates.
+
+## Individual Update
+
+- After inserting the iothubowner connection string, click `Refresh`.
+- Select the `All` deployment.
+- In the `Deployment Details` pane, click the `Target Devices` button.
+- Select the device of your choice, and paste the JSON you want applied.
+
+## Bulk Update
+
+Bulk update is possible using this tool by specifying three different pieces:
+
+1. The configuration to deploy (a JSON blob).
+2. What criteria a device should satisfy to be a target of that configuration.
+3. What criteria a device should satisfy to be considered successful in applying the configuration.
+
+For example, let's say we want to set the telemetry level to `basic` for arm devices, while we want to set it to `security` for x64 device. To do that we will:
+
+1. Define two configurations,
+
+ - For x64
+ 
-
-In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
-
-- On the Measurements page for your real device, you can see the telemetry.
-- On the Properties page, you can see the value of the reported Die Number property.
-
-## Source Code
-
-You can find the source code for this sample by downloading a zip of all of our samples.
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact 
-
-In Microsoft IoT Central, you can see how the code running on the Up-Board interacts with the application:
-
-- On the Measurements page for your real device, you can see the telemetry.
-- On the Properties page, you can see the value of the reported Die Number property.
-
-## Source Code
-
-You can find the source code for this sample by downloading a zip of all of our samples.
-
-This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact