David Tesar

Sorry folks!  This was correct, then went to Part 1(honestly not sure who updated the video incorrectly), but now is the correct one.

@bsubra: Thanks glad you liked it

@aar0nse - thanks for creating a "key takeaway" transcript!  @Gloery - We will definitely consider this for future interviews.  The reality is there is a TON of takeaways in the interview and really depending on your perspective you might get something different.  At a certain point, you'd be providing an entire transcript...

Glad you both found the chat useful/interesting. :)

@Steve: Sandboxing is focused on just security with code isolation.  Containers have some security code isolation, but this is not the only or primary purpose.  One way to think about containers is as a layered/quarantined filesystem which makes it quick/easy/lightweight to run an application and also makes the application (in the container) very portable.

@JanKratochvil: Rahul should have an answer soon for us.

@Paul Thomsen: I understand the desire ;) Send a post card addressed to me @ One Microsoft Way, Redmond, WA 98052.

@Ryan Graham: Sorry, no timeline specifically. I know the teams are trying hard to get all of the resources under this new management model!

@xied75: You can develop for ASP.NET on Docker using the open source Mono framework. More info here: http://www.mono-project.com/.  As far as Windows Service, WCF, etc development, this is restricted to Windows as they are proprietary technologies that simply don't exist on Linux.

As for your second question - Microsoft is aware of this idea, but we have nothing to discuss at this time.

Thanks BearlyAlive!  Glad you liked this episode.

Thanks for the feedback Julian.  Stay tuned for more on this in the future!

@Antonio Pinheiro: You would specify whatever the RD gateway server IP address or DNS name is at your company.  More on what RD Gateway servers: https://windows.microsoft.com/en-us/windows7/what-is-a-remote-desktop-gateway-server

@clegg: You still have to pay for the licenses of SharePoint separately.  Per http://www.windowsazure.com/en-us/pricing/licensing-faq/#header-4

"SharePoint Servers can be deployed to Windows Azure either through a customer's volume license agreement using License Mobility for Software Assurance, or as part of a hosted solution licensed via SPLA."

Sorry for the delay - here are the links to the relevant resources:

• SharePoint Cost Calculator http://bitly.com/SharePointCostCalculator 
• SharePoint 2013 on Windows Azure Infrastructure Services Whitepaper 
• TechEd: Paul Stubbs - Deploying SharePoint Farms on Windows Azure Virtual Machines