What's new for WPF Developers
Play ASP.NET Today and Tomorrow (Keynote)
Description
It's been an amazing decade for ASP.NET. Today in 2014, most all of ASP.NET is open source, developed in the open, and accepting community contributions. One ASP.NET and VS 2013 added some amazing new tooling enhancements for HTML5, CSS3 and JavaScript. VS2013.3 is coming soon with even more innovations as we march towards ASP.NET vNext. Join Scott Hunter as he shows you how it works together. What's available on ASP.NET today, and where is ASP.NET headed tomorrow, and what do you need to know to best support the code you've written and the code you will write. We'll also talk about the rise of the cloud and how it changes the way we write large systems. All this, plus a lot of open source, and deploying to Azure.
Day:
2Download
More episodes in this series
Dependency Injection and Testability in .NET
Related episodes
Unifying Windows desktop development with .NET Core 3.0
What’s Coming with .NET Core 3.0
.NET today and tomorrow
Keynote
The Future of .NET on the Desktop
Past, Present, and Future of .NET
.NET Overview & Roadmap
Modernizing Desktop Apps on Windows 10 with .NET Core 3.0 and much more
A day in the life of a modern .NET developer
Modern .NET: .NET Core, Cloud, Diagnostics, Visual Studio 2017
The Discussion
-
Shovon Kumar Pramanik Good.
-
robvettor What is link for the video feed for this session?
-
gduncan411 @robvettor: It's live right now on https://channel9.msdn.com/. It will be here for on-demand viewing in 24-48 hours
-
Stilgar Aren't you worried that breaking compatibility like this may result in problems with people not moving to the new platform? Python 3 broke backward compatibility and 6 years later Python 2 is still more widely used.
-
robertsundstrom Imagine enabling all .NET applications to be dynamic and modular.
What if you just could double-click a ".csx" source file (with directives to other files) and then the app (whether Console, WPF or Web app) automatically launched after "Roslyn" dynamically compiled the app using its own designated runtime (.NET or Mono) on the fly?
That is the future!