The Silverlight Client

In addition to the native Windows Client, WhosOn includes a version of the Client that runs in a web browser using the Silverlight plugin. Silverlight is a web application framework similar to Adobe Flash. It is compatible with multiple web browsers on Windows, Mac or Linux operating systems. For more information about Silverlight, click here.

The advantage of the Silverlight Client is that it can be run in any browser without having to install an application, making deployment to a large number of users easy. The Silverlight Client also supports 'auto update', so any new versions of the Client that are installed on the WhosOn Server will automatically rollout to Client users.

Users start the Silverlight Client by launching a URL to the WhosOn Server in their browser. If the user doesn't have the Silverlight plugin installed they will be prompted to install it.

The Silverlight Client in action

Users also have the option of running the Silverlight Client 'Out Of Browser'. This allows the user to create a shortcut to the Client on their desktop and run it as a regular application. To do this, click the Run Out Of Browser button on the File menu:

The user then confirms:

When running out of browser, the Silverlight Client saves its application files to the users local machine, making launching of the application faster. Each time the Silverlight Client is launched it will check and download any new updates from the server.

Setting Up The Silverlight Client - Server Side

Before your users can use the Silverlight Client, you must configure it on the WhosOn Server. The Silverlight Client server-side component requires the .NET Framework 3.5 installed on your WhosOn Server. (The users of the Client do not need anything installed other than the Silverlight Plugin).

During the WhosOn Server installation the Silverlight Client server files are copied to C:\Program Files\WhosOnV5\Silverlight\ and a new IIS Application Virtual Directory is creating called 'whosonclient' under your Default Web Site. A new Application Pool is created called 'WhosOnSilverlight'. The whosonclient IIS Application is set to use the WhosOnSilverlight application pool.

Important: The WhosOnSilverlight Application Pool must be set to use the NetworkService Identity in IIS:

Select the WhosOnSilverlight Application Pool and choose Advanced Settings:

Select the Identity option and choose NetworkService.

Once the IIS Application is created, your users simply launch the URL in their browser (eg:"http://www.mysite.com/whosonclient/")

Configuring The Silverlight Client To Use HTTPS Transport

If you want your Silverlight Client users to connect over an SSL connection you need to edit the web.config file in the C:\Program Files\WhosOnV5\Silverlight\ folder.

In the <SERVICES> Section:

</service>

</services>

Change the BindingConfiguration option to "PubSubSecure":

</service>

</services>

Connecting To A WhosOn Server On A Separate Machine

By default the WhosOn Silverlight Client connects to the WhosOn Server on the same physical machine as the Silverlight Client IIS Application.

You can change this by editing the woserver entry in the web.config. Set the Value to the IP address or DNS name of the WhosOn Server to use.

Technical Notes

The Silverlight Client uses the Windows Communication Foundation (WCF) on the IIS server to communicate with the WhosOn Server. WCF is installed as part of .NET Framework 3. If IIS is configured after .NET 3 is installed then you will need to re-register WCF in IIS. To do this use a command prompt and enter:

"%WINDIR%\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" -r

IIS6 Notes

For IIS6 you need to add the XAP mime types so that the Silverlight file is served. In IIS, right click 'Web Sites' and choose Properties - HTTP Headers tab - MIME Types button.

Click New to add the following mime types:

.xap - application/x-silverlight-app

.xaml - application/xaml+xml

.xbap - application/x-ms-xbap