Building and Using DisplayCast in Windows 7

DisplayCast edited this page Jun 1, 2012 · 2 revisions

Using DisplayCast

DisplayCast Streamer and Player are installed by default in the FXPAL/DisplayCast application folder. These programs are automatically started on a system reboot and appear on the task bar system tray.

Both these applications allow the user to customize the names so that other components can locate them. For example, Sam's Desktop might be a good name for a Streamer and Sam's laptop could be useful for his Player.

The Streamer allows itself to be shown on a Player using the Project Me command, while it can be archived to an Archiver using the Archive Me command. When a supported Bluetooth device was available in the Player and Streamer and when the Player is within range, the Streamer will annotate those _Player_s with a (nearby) tag.

Similarly, the Player can watch any local Streamer using the Watch Streamer command.

Getting prebuilt binaries

Prebuilt binaries are available as zip archives in the Downloads section We require DemoForge mirror driver (available at, Bonjour (available at - either the Bonjour SDK for Windows or Bonjour Print Services for Windows will work) and .NET 4.0. The installer will attempt to verify that the prerequisites are properly installed. The Streamer also requires administrative privileges. Every time you start the Streamer, “User Access Control” will prompt you for reconfirmation. To disable this prompt: Type ‘secpol.msc’ in the run dialog (of the Start menu). Change “Local Policies”->”User Access Control: Behavior of the elevation prompt for administrators in Admin Approval mode” to “Elevate without prompting”. Unfortunately, this behavior change is global and will affect all your applications.

The Controller provides an synchronous control service for DisplayCast and is useful for developers. The service needs to run on a machine that is on the same link-local subnet as the DisplayCast deployment (it uses Bonjour for locating _Streamer_s, _Player_s and _Archiver_s).

Building from sources


  1. DisplayCast uses Microsoft Visual Studio 2010 Professional. Microsoft offers a free [Express (] edition. Though the free version can be used to compile the system, it does not support the distribution installer.
  2. We require the DemoForge mirror driver.
  3. Apple Bonjour SDK
  4. 32feet.NET provides the wrapper for Bluetooth support.

##Build instructions The DisplayCast Visual studio solution defines 8 projects:

  1. Streamer - creates the Streamer program
  2. Player - creates the Player program
  3. ControllerService create the Controller service
  4. Shared - an internal library that compiles configuration parameters that are shared by Streamer, Player and ControllerService.
  5. Location - an internal library that uses the Cisco WiFi localization services. This component will only work if you have a properly configured and deployed Cisco WiFi localization system.
  6. ZeroconfService - a fully patched replica of the C# Zeroconf wrapper that is available in Google code.
  7. DisplayCast Installer - creates a Windows installer in \Installers folder.
  8. ControllerService Installer - creates a Windows installer in \Installers folder.

Building the solution (using the "Build->Build Solution" menu) compiles everything except the installer. Installers are built manually using the "Build->Build DisplayCast Installer" menu option in Visual Studio 2010.

Frequently asked questions

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.