Shows how to use the Windows.Media.Casting and Windows.Media.DialProtocol namespaces. Also shows how to use the Windows.UI.ViewManagement.ProjectionManager and Windows.Devices.Enumeration.DevicePicker APIs to render media on a remote device. It covers sending media to various devices: Miracast, DLNA, DIAL, and Bluetooth.
Note: This sample is part of a large collection of UWP feature samples. If you are unfamiliar with Git and GitHub, you can download the entire collection as a ZIP file, 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. For more samples, see the Samples portal on the Windows Dev Center.
For an intro to casting, see the Basic Media Casting Sample.
Scenario 1: Media Element Casting 101:
Press the Cast button next to the progress bar in the video element. Select the device you'd like to cast to.
This is an example of the built in casting that comes with the media element transport controls. This will enable casting to Miracast, DLNA, and Bluetooth devices.
Scenario 2: Casting APIs and a Custom Cast Button:
Press the Cast button next to the progress bar in the video element. Select the device you'd like to cast to.
This is very similar to the first scenario, however, in this case, the Windows.Media.Casting APIs are used manually to create a custom cast button that's then included in the media transport controls.
Scenario 3: DIAL Sender Universal Windows App
For this scenario you'll need a device that supports Dial. You can set the application name and arguments in the fields provided and then use the cast button in the transport controls to launch the app on the remote device.
In this scenario, the Windows.Media.DialProtocol APIs are illustrated.
Scenario 4: DIAL Receiver Windows Universal App This scenario is used to illustrate how a developer would write a universal app that supports being launched by DIAL. This app can be launched with the APIs used in Scenario 3. Currently this scenario is only valid for select Xbox configurations.
Scenario 5: Multi-View Media Application Again, the cast button is used here to send a video to a second screen. In this case, however the Windows.UI.ViewManagement.ProjectionManager API is used. This allows the developer to customize their second screen experience. This API works with wired monitors and Miracast devices.
Scenario 6: Combine Casting Methods This scenario brings all the prior scenarios together and shows how to use them all at the same time in order to reach the widest set of devices. Windows.Devices.Enumeration.DevicePicker is used to build a picker to show all the different devices in one place.
Windows.Media.Casting namespace Windows.Media.DialProtocol namespace Windows.UI.ViewManagement.ProjectionManager API Windows.Devices.Enumeration.DevicePicker API
Client: Windows 10
Phone: Windows 10
- If you download the samples ZIP, be sure to unzip the entire archive, not just the folder with the sample you want to build.
- Start Microsoft Visual Studio 2015 and select File > Open > Project/Solution.
- Starting in the folder where you unzipped the samples, go to the Samples subfolder, then the subfolder for this specific sample, then the subfolder for your preferred language (C++, C#, or JavaScript). Double-click the Visual Studio 2015 Solution (.sln) file.
- Press Ctrl+Shift+B, or select Build > Build Solution.
The next steps depend on whether you just want to deploy the sample or you want to both deploy and run it.
Deploying the sample
- Select Build > Deploy Solution.
Deploying and running the sample
- To debug the sample and then run it, press F5 or select Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or selectDebug > Start Without Debugging.