1. Future of .NET Development
// Danilo Bordini, Microsoft Brasil
// @dbordini

3. Microsoft development platform
Innovation Agility Openness

4. Mobile Development Cloud Development DevOps

5. Mobile Development

7. Nascimento & Evolução .NET - Fragmentação
Unified View
PCL (Portable Class Libraries
Windows 8 Contracts
Unified Implementation

8. Machine-wide frameworks x Application-local frameworks
Pros
1.It allows centralized servicing
2.It reduces the disk space
3.Allows sharing native images between
applications
Cons
1.Dependency (OS, last version)
2.Break apps with newer frameworks
3.Hard to take advantage of new features
NUGet (out of band)

9. .NET Core is a modular implementation that can be used in a wide variety of verticals, scaling from the data center
to touch based devices, is available as open source, and is supported by Microsoft on Windows, Linux and Mac OSX.

10. .NET Native (touch based devices) and ASP.NET 5 (server side
web development)
Agile
App-local framework
Smart Sharing
Compatibility
Easier fix broken
situation

11. .NET Native (touch based devices) and ASP.NET 5 (server side
web development)
ENTERPRISE READY
Single Nuget package
for .NET Core as an
option (snapshot, 4x
year)
Offline installer for
development
environments
Centralized security
patches

12. Announcing
Open sourcing
.NET Core Runtime
and Framework

13. Announcing
A cross-platform .NET
for Linux and Mac

14. .NET Core goes Open Source
1.Open Source offers quasi real-time communication for the implementation and overall direction
2.Releasing packages to NuGet.org offers agility at the component level
3.Distributions offer agility at the platform level

15. ASP.NET 5 vNext
Vinícius Souza
Especialista Técnico – Microsoft Brasil
@vbs_br

16. “Our role is more important than ever before”
“We are required to innovate and deliver much faster”
“I need a cross-device development strategy”
“Open Source enriches the platform and the community
“…but I have existing applications to run and evolve”

17. Productivity of Visual Studio + Flexibility of Web
Interactive HTML / CSS tools for web apps that look and behave the
same across any browser
Powerful tools and technologies for interactive apps
Develop JavaScript/TypeScript complex logic with powerful editing,
debugging and diagnostics.
Supports demanding needs of LOB apps
Hybrid cloud requirements, flexibility, productivity,
Tools to develop and test complex web applications that scale.

19. .NET API for Hadoop WebClient
.NET Compiler Platform ("Roslyn")
.NET Map Reduce API for Hadoop
.NET Micro Framework
ASP.NET Web Pages
ASP.NET MVC
ASP.NET Web API
ASP.NET SignalR
Composition (MEF2)
Windows Phone Toolkit
Entity Framework
Linq to Hive
MEF (Managed Extensibility Framework)
Rx (Reactive Extensions)
Xamarin.Mobile
Couchbase for .NET
OWIN Authentication Middleware
Web Protection Library
Windows Azure .NET SDK
WnsRecipe
Mimekit Xamarin.Auth
http://www.dotnetfoundation.org
@dotnetfdn // #dotnetfdn
Mailkit
System.Drawing

20. Totally Modular Faster Development Cycle
Choose your Editors
and Tools
Seamless transition
from on-premises to cloud
Open Source
with Contributions
OSS Cross-Platform
Fast

21. Extending Application Types
Common Improvements
Familiar frameworks

22. Faster Development Cycle
More Control

23. Runtime Performance
Development productivity and low friction

24. Seamless transition from on-premises to cloud
Cloud ready
Diagnostics

25. Runtime
Editors
Open Source with Contributions
OSS

26. MVC, Web API, Web Pages 6, SignalR 3, EF 7
Feature .NET vNext .NET vNext (Cloud Optimized)
Cloud Ready * *
Modular Design * *
Dependency Injection * *
Consistent Tracing / Debugging * *
Faster Development (No Build Step) * *
Open Source * *
Full Side by Side (framework deployed inside application) *
Fast startup, Low memory / High throughput (best of class) *

28. Runtime Compilers
Next gen JIT (“RyuJIT”)
SIMD (Data Parallelization)
.NET Compiler Platform (“Roslyn”)
Languages innovation
Libraries
BCL and PCL
Entity Framework

29. Platform Framework Tools
…or bring your own …or bring your own …or bring your own

33. What about backwards compatibility???
• .NET Framework 4.6
• Visual Studio 2015 timeline: no feature gap
• .NET Core will be updated faster, then, in the future, innovation come first to .NET
Core
• Cadence (once per year) of .NET Framework update (incorporating .NET Core
features)
• Mono
• Today:
• open source implementation of .NET Framework (same factoring problems)
• .NET Framework Reference Source under an open source friendly license on
GitHub.
• Summary: NET Framework has two forks: One fork is provided by Microsoft and
is Windows only; the other is Mono which you can use on Linux and Mac.
• Future: having to maintain separate forks will no longer be necessary: together with
the Mono community we’ll make .NET Core great for Windows, Linux and Mac OSX

34. Start Today 
•You clone our repo (git clone https://github.com/dotnet/corefx)
•You invoke build.cmd

35. Announcing
A new free Visual Studio:
Visual Studio Community

36. Resources
www.asp.net/vnext
http://bit.ly/Download_VS15_Preview
http://bit.ly/VS2013_Community
www.azure.com
http://lab27.azurewebsites.net/