Projection sample

This sample demonstrates how to display two different views of your app UI on different screens, as users might do when projecting your app in a meeting or conference.

5 Star
4,337 times
Add to favorites
E-mail Twitter Digg Facebook
Sign in to ask a question

  • UI Thread to 100%
    1 Posts | Last post December 17, 2015
    • When using the example (and this code in my application) the UI thread usage goes to 100% and stays there while projection is activated. This is causing fps issues. There is a similar issue reported on github:
  • StartProjectingAsync throws ArgumentException
    1 Posts | Last post January 18, 2015
    • I have downloaded the sample app and am getting the following exception.  I have tried with multiple types of monitors.  I also had a colleague download and run the sample, and he also received the same exception; so to validate on another Win8.1 system.  What may be causing this?
      Scenario1.xaml.cs - Line 71 :
      await ProjectionManager.StartProjectingAsync(rootPage.ProjectionViewPageControl.Id, thisViewId);
      {System.ArgumentException: Value does not fall within the expected range.
         at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
         at Projection.Scenario1.<StartProjecting_Click>d__3.MoveNext()}
  • How to have mainView to set value on a control in ProjectionView?
    2 Posts | Last post September 20, 2013
    • If in the ProjectionViewPage, there is a TextBox or a MediaElement, I want to have a button in Scenario1 Page, and once i click on the button, the TextBox in ProjectionViewPage will display something, or the MediaElement on the ProjectionViewPage can play a video, how to do that? can you provide some demo code?
    • Figured it out, just need to have a public CoreDispatcher in ProjectionViewPage, and use that dispatcher to handle the MediaElement, works~!