Description

Come see an end-to-end view of the .NET platform in the new world of devices powered by cloud services. In this session you will see the present and the future of .NET in key areas such as the runtime, compiler and language foundation as well as the latest innovations for creating native applications in Windows, Azure services and cross-device experiences.

Why not an official Microsoft implementation of .NET on Unix (Linux, etc)?

The success of Java is just its presence in multitude of platforms, but .NET is much more rich for the front-end side.

With cloud computing, in the future the Operating System will be only a commodity (also the Data Base Management System). OS & DBMS will be less important because they will be managed by the cloud provider... for the future, we need platform independence for interoperate into a multi-cloud ecosystem.

There are rumors that MS is going to buy Xamarin. This is a MUST for the .Net community.This is why I am following build so closely this year. If they are not going to buy Xamarin. I will be disappointed. I really want Xamarin to just be apart of the studio as a default.

I don't know, the state of cross-platform desktop app development in .NET looks pretty sad if you ask me. Right now the only viable option that isn't tied to the browser is GTK#, and I don't see that changing any time soon. WPF is not very interesting to anybody that isn't focused exclusively on Windows.

Personally I don't care about MS buying Xamarin. What I would like to see is .Net support on other platforms and you don't need Xamarin or Mono to do that. There have been at least 2 'shared' source releases of the dot net clr for academic use that ran on an impressive list of non MS operating systems. We know you can do it already so just release your own versions. One thing you can learn from Xamarin is that you should not waste your time trying to reinvent the wheel on the UI side. Just wrap the native UI on the platform in as thin a layer as possible to surface it. With some more work the new Dot Net Native looks to be the perfect replacement for Mono:AOT so I don't see the need on a technical level to get Xamarin involved. The only reason to get Xamarin involved would be if you are so behind where your customers want you to be that you need to get a push up the ladder. If that is the case shame on you as your customers have been asking this since the very first day of the very first dot net beta...