azlivestreaming Wiki Rss Feed

New Comment on "Documentation"

meemee — Tue, 04 Dec 2012 12:40:45 GMT

Thanks for a good post. When will Azure Media encoder provide encoding to LIVE smooth streaming?

Updated Wiki: Home

DmitriMartynov — Mon, 18 Jul 2011 18:32:59 GMT

Project Description
Windows Azure Live Smooth Streaming Project is self-contained package for quickly deploying Live Smooth Streaming solution to Windows Azure. Project contains:
- VS 2010 solution ready to be published
- Web portal with Silverlight player
- Auto-configuration for Media Services

UPDATED!
Release 0.2.2 updated with minor fixes - read release notes
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

New Comment on "Documentation"

Gorzsi — Mon, 18 Jul 2011 18:20:56 GMT

Nice work! I measured 1 minute latency. Is it normal? Can be reduced?

Updated Wiki: Documentation

DmitriMartynov — Mon, 18 Jul 2011 17:53:38 GMT

Overview

Windows Azure Live Streaming solution allows quickly deploy scalable service to perform live video broadcasting through Windows Azure Web Roles.

Solution source code is available for download from http://azlivestreaming.codeplex.com/

High level architecture presented in the following diagram:

Upstream Server (upstream.cloudapp.net)

Single instance Web role with Push publishing point (aka “ingest” server). URL of this publishing point used by Encoder to push video stream during Live event.

Important: to achieve redundancy for Push point it’s possible to deploy additional single Web role at different DNS. Azure staging deployment will work as well.

Upstream Server could be used as streaming server in small scale deployments. In this case player URL would be http://upstream.cloudapp.net/push.isml/manifest.

Downstream Server (downstream.cloudapp.net)

Multiple instances Web role with Pull publishing point. URL for this publishing point (e.g. http://downstream.cloudapp.net/pull.isml/manifest).

IIS Media Services 4

IIS Media Services 4 is automatically installed and configured via Web role startup tasks and Web Administration API.

Publishing Points

Solution contains two predefined publishing points:

· Push.isml – to receive video stream from encoder

· Pull.isml – to pull video stream from Upstream Server

Each isml file deployed as part of normal Windows Azure deployment procedure either via management portal or from Visual Studio IDE.

Important: Push/Pull points configuration can be performed by simply editing isml (XML) files in Visual Studio or any other text editor.

Silverlight Player

Solution makes use of sample Silverlight player from iis.net/media site http://learn.iis.net/page.aspx/620/getting-started-with-iis-live-smooth-streaming/

Below we provide detailed deployment steps.

Pre-deployment steps

Install Visual Studio 2010 Service Pack 1

Solution uses newest ASP.NET MVC3 and Razor technology so SP1 is recommended.

Install Windows Azure Visual Studio Tools

Windows Azure SDK must be installed on local PC to enable creating deployment packages. We recommend installing Visual Studio Tools as well to support direct publishing and debugging from Visual Studio IDE.

Download link: http://www.microsoft.com/windowsazure/sdk/

Important: Check Windows Azure SDK system requirements http://msdn.microsoft.com/en-us/library/gg680300.aspx if you won’t use Web Platform installer

Install Expression Encoder 4 Pro SP1

Expression Encoder 4 Pro SP1 required to deliver Live Smooth Streaming broadcasts. Encoder must be installed on PC with video source connected. (e.g. video capture device, USB camera, etc).

Encoder link: http://www.microsoft.com/expression/products/EncoderPro_Overview.aspx

Important: Pro version required for Live Smooth Streaming and Apple devices support

Download solution source code

Download Visual Studio 2010 solution source code from http://azlivestreaming.codeplex.com/

Deployment Walkthrough

Load Visual Studio solution

1. Extract downloaded zip file to some location

2. Start Visual Studio in elevated mode (Ctrl+Shift+Click)

3. Open MediaServices.sln from save location

4. Cancel prompt to connect to source control server and then press OK to go offline

5. In next dialog answer No to question to remap Web project URL

6. If project can’t be opened and appears as grey in VS and you plan to run project locally against local IIS with Media Services installed then you must map MediaPortal folder to http://localhost:8080 in IIS Manager

7. If project can’t be opened and appears as grey in VS and you won’t plan to use local IIS Media Services or will change a local IIS url then do the following:

a. Right-Click MediaPortal in Solution Explorer and choose Edit MediaPortal.csproj

b. Find <UseIIS> and change to <UseIIS>False</UseIIS>

c. Find <IISUrl> and change to <IISUrl></IISUrl>

d. Right-Click MediaPortal in Solution Explorer and Reload

8. You should have the following solution loaded in Visual Studio:

Test run project locally

The following steps are optional – it’s just to make sure the solution can run on your PC:

1. Make sure MediaPortal is a startup project (Right-Click and choose Set as Startup Project)

2. Open MediaPortal properties page (Double-Click Properties under MediaPortal name)

3. Choose Web from left-side tabs

4. Use IIS Express as shown below:

5. Create Virtual Directory if asked so (change port number if necessary)

6. Hit F5 – default browser should open with portal loaded similar to below:

Configure Publishing Points

Solution contains two predefined publishing points as shown below:

Push.isml file doesn’t contain any external references and can be left as is.

Pull.isml must be edited to include reference to Upstream Server. Double-click to pull.isml and edit smil/body/switch/ref element as shown below:

Attribute src must contain URL of Push publishing point at Upstream Server such as http://upstream.cloudapp.net/push.isml

Optional Downstream Server configuration

Project web.config file has optional application configuration setting:

</appSettings>

This setting is optional and used in Web portal to identify downstream server. It only defines which URL is shown as a Player URL when user connects to Upstream server Web portal.

Windows Azure Project configuration

Number of Web role instances

Number of instances configured via UI (Double-Click to WindowsAzureProject1-Roles-MediaPortal) or in ServiceConfiguration.cscfg file:

<?xml version="1.0" encoding="utf-8"?>

</ConfigurationSettings>

</Role>

</ServiceConfiguration>

Important: Configure only 1 instance of Upstream server. Configure more than 1 instance of Downstream server.

ServiceDefinition.csdef

Make sure Web role runs in elevated security context (required to properly configure IIS Media Services):

<?xml version="1.0" encoding="utf-8"?>

<Sites>

</Bindings>

</Site>

</Sites>

</Endpoints>

</Imports>

</WebRole>

</ServiceDefinition>

Creating Hosted Services

Go to https://windows.azure.com management portal and create two separate deployments. It’s important to have separate DNS for Upstream and Downstream servers. Deployments could be in the same hosted service but be staging and production. Read more about Windows Azure deployments: http://msdn.microsoft.com/en-us/library/gg433108.aspx

For example one could create the following deployments:

· http://upstream.cloudapp.net – for Upstream server

· http://downstream.cloudapp.net – for Downstream servers

Important: make sure to put hosted services in the same datacenter to avoid unnecessary traffic between Upstream and Downstream servers.

Publishing Solution to Windows Azure

Normal procedure is used to publish solution to Windows Azure. As already mentioned Upstream server must have only 1 Web role instance so change number of instances to 1 for Upstream deployment. After deploying Upstream server change number of instances to >1 and deploy the same solution as downstream server.

Important: Upstream and Downstream solutions are the same. The only difference is number of instances and which publishing point used.

Encoding Live Stream

After solution was successfully published to Windows Azure one can set Encoder to push Live video stream to publishing point. The following is a basic steps required to start encoding session. For more information refer to complete guide at http://learn.iis.net/page.aspx/620/getting-started-with-iis-live-smooth-streaming/

1. Start Expression Encoder 4 Pro SP1 and choose Live Broadcasting Project

2. Add Live Source, choose one of the IIS Smooth Streaming Presets, check “Publishing Point” for output and use http://upstream.cloudapp.net/push.isml as configured before.

3. Hit Start and start encoding session

Watching Live Stream

Web portal in the solution includes Live Smooth Streaming player which uses the following <object> tag:

</a>

</object><iframe id="_sl_historyFrame" style="visibility:hidden;height:0px;width:0px;border:0px"></iframe>

InitParams must have mediaurl part pointing to either push point at Upstream server (single server deployment) or pull point at Downstream server.

· For Upstream: http://upstream.cloudapp.net/push.isml/manifest

· For Downstream: http://downstream.cloudapp.net/push.isml/manifest

This HTML snippet above could be inserted inside <iframe> at any Web site.

Watch Live Stream from portal

Open one of the deployments (e.g. http://downstream.cloudapp.net) in browser and:

· If you at Upstream server as defined by Pull.isml point configuration (that is Upstream server referred in Pull.isml) click on one of the URL under right pointing arrow

· If you at Downstream server (that is server you’re accessing isn’t referred in Pull.isml) click on one of the URL under left pointing arrow

Portal currently provided readonly configuration experience.

Updated Wiki: Home

DmitriMartynov — Fri, 15 Jul 2011 20:34:56 GMT

UPDATED!
Release 0.2.2 updated with minor fixes - read release notes
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Fri, 15 Jul 2011 20:16:00 GMT

UPDATED!
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Fri, 15 Jul 2011 20:14:36 GMT

UPDATED!
Cannot resolve file macro, invalid file name or id. or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Fri, 15 Jul 2011 19:49:23 GMT

UPDATED!
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Documentation

DmitriMartynov — Fri, 15 Jul 2011 19:48:05 GMT

Overview

Windows Azure Live Streaming solution allows quickly deploy scalable service to perform live video broadcasting through Windows Azure Web Roles.

Solution source code is available for download from http://azlivestreaming.codeplex.com/

High level architecture presented in the following diagram:

Upstream Server (upstream.cloudapp.net)

Single instance Web role with Push publishing point (aka “ingest” server). URL of this publishing point used by Encoder to push video stream during Live event.

Important: to achieve redundancy for Push point it’s possible to deploy additional single Web role at different DNS. Azure staging deployment will work as well.

Upstream Server could be used as streaming server in small scale deployments. In this case player URL would be http://upstream.cloudapp.net/push.isml/manifest.

Downstream Server (downstream.cloudapp.net)

Multiple instances Web role with Pull publishing point. URL for this publishing point (e.g. http://downstream.cloudapp.net/pull.isml/manifest).

IIS Media Services 4

IIS Media Services 4 is automatically installed and configured via Web role startup tasks and Web Administration API.

Publishing Points

Solution contains two predefined publishing points:

· Push.isml – to receive video stream from encoder

· Pull.isml – to pull video stream from Upstream Server

Each isml file deployed as part of normal Windows Azure deployment procedure either via management portal or from Visual Studio IDE.

Important: Push/Pull points configuration can be performed by simply editing isml (XML) files in Visual Studio or any other text editor.

Silverlight Player

Solution makes use of sample Silverlight player from iis.net/media site http://learn.iis.net/page.aspx/620/getting-started-with-iis-live-smooth-streaming/

Below we provide detailed deployment steps.

Pre-deployment steps

Install Visual Studio 2010 Service Pack 1

Solution uses newest ASP.NET MVC3 and Razor technology so SP1 is recommended.

Install Windows Azure Visual Studio Tools

Download link: http://www.microsoft.com/windowsazure/sdk/

Important: Check Windows Azure SDK system requirements http://msdn.microsoft.com/en-us/library/gg680300.aspx if you won’t use Web Platform installer

Install Expression Encoder 4 Pro SP1

Expression Encoder 4 Pro SP1 required to deliver Live Smooth Streaming broadcasts. Encoder must be installed on PC with video source connected. (e.g. video capture device, USB camera, etc).

Encoder link: http://www.microsoft.com/expression/products/EncoderPro_Overview.aspx

Important: Pro version required for Live Smooth Streaming and Apple devices support

Download solution source code

Download Visual Studio 2010 solution source code from http://azlivestreaming.codeplex.com/

Deployment Walkthrough

Load Visual Studio solution

1. Extract downloaded zip file to some location

2. Start Visual Studio in elevated mode (Ctrl+Shift+Click)

3. Open MediaServices.sln from save location

4. Cancel prompt to connect to source control server and then press OK to go offline

5. In next dialog answer No to question to remap Web project URL

7. If project can’t be opened and appears as grey in VS and you won’t plan to use local IIS Media Services or will change a local IIS url then do the following:

a. Right-Click MediaPortal in Solution Explorer and choose Edit MediaPortal.csproj

b. Find <UseIIS> and change to <UseIIS>False</UseIIS>

c. Find <IISUrl> and change to <IISUrl></IISUrl>

d. Right-Click MediaPortal in Solution Explorer and Reload

8. You should have the following solution loaded in Visual Studio:

Test run project locally

The following steps are optional – it’s just to make sure the solution can run on your PC:

1. Make sure MediaPortal is a startup project (Right-Click and choose Set as Startup Project)

2. Open MediaPortal properties page (Double-Click Properties under MediaPortal name)

3. Choose Web from left-side tabs

4. Use IIS Express as shown below:

5. Create Virtual Directory if asked so (change port number if necessary)

6. Hit F5 – default browser should open with portal loaded similar to below:

Configure Publishing Points

Solution contains two predefined publishing points as shown below:

Push.isml file doesn’t contain any external references and can be left as is.

Pull.isml must be edited to include reference to Upstream Server. Double-click to push.isml and edit smil/body/switch/ref element as shown below:

Attribute src must contain URL of Push publishing point at Upstream Server such as http://upstream.cloudapp.net/push.isml

Optional Downstream Server configuration

Project web.config file has optional application configuration setting:

</appSettings>

This setting is optional and used in Web portal to identify downstream server. It only defines which URL is shown as a Player URL when user connects to Upstream server Web portal.

Windows Azure Project configuration

Number of Web role instances

Number of instances configured via UI (Double-Click to WindowsAzureProject1-Roles-MediaPortal) or in ServiceConfiguration.cscfg file:

<?xml version="1.0" encoding="utf-8"?>

</ConfigurationSettings>

</Role>

</ServiceConfiguration>

Important: Configure only 1 instance of Upstream server. Configure more than 1 instance of Downstream server.

ServiceDefinition.csdef

Make sure Web role runs in elevated security context (required to properly configure IIS Media Services):

<?xml version="1.0" encoding="utf-8"?>

<Sites>

</Bindings>

</Site>

</Sites>

</Endpoints>

</Imports>

</WebRole>

</ServiceDefinition>

Creating Hosted Services

For example one could create the following deployments:

· http://upstream.cloudapp.net – for Upstream server

· http://downstream.cloudapp.net – for Downstream servers

Important: make sure to put hosted services in the same datacenter to avoid unnecessary traffic between Upstream and Downstream servers.

Publishing Solution to Windows Azure

Important: Upstream and Downstream solutions are the same. The only difference is number of instances and which publishing point used.

Encoding Live Stream

1. Start Expression Encoder 4 Pro SP1 and choose Live Broadcasting Project

2. Add Live Source, choose one of the IIS Smooth Streaming Presets, check “Publishing Point” for output and use http://upstream.cloudapp.net/push.isml as configured before.

3. Hit Start and start encoding session

Watching Live Stream

Web portal in the solution includes Live Smooth Streaming player which uses the following <object> tag:

</a>

</object><iframe id="_sl_historyFrame" style="visibility:hidden;height:0px;width:0px;border:0px"></iframe>

InitParams must have mediaurl part pointing to either push point at Upstream server (single server deployment) or pull point at Downstream server.

· For Upstream: http://upstream.cloudapp.net/push.isml/manifest

· For Downstream: http://downstream.cloudapp.net/push.isml/manifest

This HTML snippet above could be inserted inside <iframe> at any Web site.

Watch Live Stream from portal

Open one of the deployments (e.g. http://downstream.cloudapp.net) in browser and:

· If you at Upstream server as defined by Pull.isml point configuration (that is Upstream server referred in Pull.isml) click on one of the URL under right pointing arrow

· If you at Downstream server (that is server you’re accessing isn’t referred in Pull.isml) click on one of the URL under left pointing arrow

Portal currently provided readonly configuration experience.

Updated Wiki: Home

DmitriMartynov — Tue, 10 May 2011 14:21:01 GMT

NEW!
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Tue, 10 May 2011 14:20:37 GMT

NEW!
Download Deployment Guide or read online documentation

Important!
Release prior 0.2.2 fixed bug when no Media Service is installed during deployment procedure.
Please use latest release.

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Tue, 03 May 2011 14:04:30 GMT

NEW!
Download Deployment Guide or read online documentation

Web portal for easy configuration included:

Updated Wiki: Documentation

DmitriMartynov — Tue, 03 May 2011 14:03:17 GMT

Overview

Windows Azure Live Streaming solution allows quickly deploy scalable service to perform live video broadcasting through Windows Azure Web Roles.

Solution source code is available for download from http://azlivestreaming.codeplex.com/

High level architecture presented in the following diagram:

Upstream Server (upstream.cloudapp.net)

Single instance Web role with Push publishing point (aka “ingest” server). URL of this publishing point used by Encoder to push video stream during Live event.

Important: to achieve redundancy for Push point it’s possible to deploy additional single Web role at different DNS. Azure staging deployment will work as well.

Upstream Server could be used as streaming server in small scale deployments. In this case player URL would be http://upstream.cloudapp.net/push.isml/manifest.

Downstream Server (downstream.cloudapp.net)

Multiple instances Web role with Pull publishing point. URL for this publishing point (e.g. http://downstream.cloudapp.net/pull.isml/manifest).

IIS Media Services 4

IIS Media Services 4 is automatically installed and configured via Web role startup tasks and Web Administration API.

Publishing Points

Solution contains two predefined publishing points:

· Push.isml – to receive video stream from encoder

· Pull.isml – to pull video stream from Upstream Server

Each isml file deployed as part of normal Windows Azure deployment procedure either via management portal or from Visual Studio IDE.

Important: Push/Pull points configuration can be performed by simply editing isml (XML) files in Visual Studio or any other text editor.

Silverlight Player

Solution makes use of sample Silverlight player from iis.net/media site http://learn.iis.net/page.aspx/620/getting-started-with-iis-live-smooth-streaming/

Below we provide detailed deployment steps.

Pre-deployment steps

Install Visual Studio 2010 Service Pack 1

Solution uses newest ASP.NET MVC3 and Razor technology so SP1 is recommended.

Install Windows Azure Visual Studio Tools

Download link: http://www.microsoft.com/windowsazure/sdk/

Important: Check Windows Azure SDK system requirements http://msdn.microsoft.com/en-us/library/gg680300.aspx if you won’t use Web Platform installer

Install Expression Encoder 4 Pro SP1

Expression Encoder 4 Pro SP1 required to deliver Live Smooth Streaming broadcasts. Encoder must be installed on PC with video source connected. (e.g. video capture device, USB camera, etc).

Encoder link: http://www.microsoft.com/expression/products/EncoderPro_Overview.aspx

Important: Pro version required for Live Smooth Streaming and Apple devices support

Download solution source code

Download Visual Studio 2010 solution source code from http://azlivestreaming.codeplex.com/

Deployment Walkthrough

Load Visual Studio solution

1. Extract downloaded zip file to some location

2. Start Visual Studio in elevated mode (Ctrl+Shift+Click)

3. Open MediaServices.sln from save location

4. Cancel prompt to connect to source control server and then press OK to go offline

5. In next dialog answer No to question to remap Web project URL

6. You should have the following solution loaded in Visual Studio:

Test run project locally

The following steps are optional – it’s just to make sure the solution can run on your PC:

1. Make sure MediaPortal is a startup project (Right-Click and choose Set as Startup Project)

2. Open MediaPortal properties page (Double-Click Properties under MediaPortal name)

3. Choose Web from left-side tabs

4. Use IIS Express as shown below:

5. Create Virtual Directory if asked so (change port number if necessary)

6. Hit F5 – default browser should open with portal loaded similar to below:

Configure Publishing Points

Solution contains two predefined publishing points as shown below:

Push.isml file doesn’t contain any external references and can be left as is.

Pull.isml must be edited to include reference to Upstream Server. Double-click to push.isml and edit smil/body/switch/ref element as shown below:

Attribute src must contain URL of Push publishing point at Upstream Server such as http://upstream.cloudapp.net/push.isml

Optional Downstream Server configuration

Project web.config file has optional application configuration setting:

</appSettings>

This setting is optional and used in Web portal to identify downstream server. It only defines which URL is shown as a Player URL when user connects to Upstream server Web portal.

Windows Azure Project configuration

Number of Web role instances

Number of instances configured via UI (Double-Click to WindowsAzureProject1-Roles-MediaPortal) or in ServiceConfiguration.cscfg file:

<?xml version="1.0" encoding="utf-8"?>

</ConfigurationSettings>

</Role>

</ServiceConfiguration>

Important: Configure only 1 instance of Upstream server. Configure more than 1 instance of Downstream server.

ServiceDefinition.csdef

Make sure Web role runs in elevated security context (required to properly configure IIS Media Services):

<?xml version="1.0" encoding="utf-8"?>

<Sites>

</Bindings>

</Site>

</Sites>

</Endpoints>

</Imports>

</WebRole>

</ServiceDefinition>

Creating Hosted Services

For example one could create the following deployments:

· http://upstream.cloudapp.net – for Upstream server

· http://downstream.cloudapp.net – for Downstream servers

Important: make sure to put hosted services in the same datacenter to avoid unnecessary traffic between Upstream and Downstream servers.

Publishing Solution to Windows Azure

Important: Upstream and Downstream solutions are the same. The only difference is number of instances and which publishing point used.

Encoding Live Stream

1. Start Expression Encoder 4 Pro SP1 and choose Live Broadcasting Project

2. Add Live Source, choose one of the IIS Smooth Streaming Presets, check “Publishing Point” for output and use http://upstream.cloudapp.net/push.isml as configured before.

3. Hit Start and start encoding session

Watching Live Stream

Web portal in the solution includes Live Smooth Streaming player which uses the following <object> tag:

</a>

</object><iframe id="_sl_historyFrame" style="visibility:hidden;height:0px;width:0px;border:0px"></iframe>

InitParams must have mediaurl part pointing to either push point at Upstream server (single server deployment) or pull point at Downstream server.

· For Upstream: http://upstream.cloudapp.net/push.isml/manifest

· For Downstream: http://downstream.cloudapp.net/push.isml/manifest

This HTML snippet above could be inserted inside <iframe> at any Web site.

Watch Live Stream from portal

Open one of the deployments (e.g. http://downstream.cloudapp.net) in browser and:

· If you at Upstream server as defined by Pull.isml point configuration (that is Upstream server referred in Pull.isml) click on one of the URL under right pointing arrow

· If you at Downstream server (that is server you’re accessing isn’t referred in Pull.isml) click on one of the URL under left pointing arrow

Portal currently provided readonly configuration experience.

Updated Wiki: Home

DmitriMartynov — Tue, 03 May 2011 13:52:36 GMT

NEW!
Deployment Guide

Web portal for easy configuration included:

Updated Wiki: Home

DmitriMartynov — Tue, 03 May 2011 13:51:41 GMT

Updated Wiki: Temporary Post Used For Theme Detection (571220ff-70ea-450e-a864-352685a50760 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

DmitriMartynov — Tue, 03 May 2011 13:31:37 GMT

This is a temporary post that was not deleted. Please delete this manually. (5abb43c5-ea25-4a1b-9824-fe29efab3732 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

Updated Wiki: Documentation

DmitriMartynov — Wed, 27 Apr 2011 19:00:48 GMT

tl;dr; Load project to VS 2010 with Azure Tools for Visual Studio. Publish to Azure. Access instance. Check links.

Basic setup steps:
- Normal procedure to prepare PC for Azure development
- Prepare to publish to Azure
- Load VS 2010 project
- Hit F5. I actually recommend to run project outside Azure simulation environment - it's just a little faster.
- Publish 1 instance of upstream
- Publish >1 instance of downstream
- Check portal (root of instance <upstreamordownstream>.cloudapp,net)
- Use links on the portal for Expression Encoder
- Portal supports Smooth Streaming Players

I will update docs as soon as I have time