Skip to content

Instantly share code, notes, and snippets.

@otakusid

otakusid/vNext.md

Last active August 29, 2015 14:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save otakusid/1c08939e14edb90feec5 to your computer and use it in GitHub Desktop.
Save otakusid/1c08939e14edb90feec5 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
vNext.md

vNext

.NET

  • .NET Native

  • .NET Compiler Platform ("Roslyn")

    • Provide API to get information from compiler 'black box'. This API will be used in the MSVS vNext (some features available in MSVS 2013) and third-party tools.
    • Can work with some features of C# 6.0
    • Scripting API

  • Nextgen JIT (RyuJIT)

    • Faster code jeneration, faster code execution
    • Now focused on x64 (will be the basis of all JIT compilers in the future: x86, ARM, etc.)
      • SIMD
        • SIMD is a technology that employs data parallelization at the CPU level. Multi-threading and SIMD complement each other: multi-threading allows parallelizing work over multiple cores while SIMD allows parallelizing work within a single core.
        • Useful for numerical computing, gaming and image processing applications.

  • Project “Orleans”

    • Its design borrows heavily from Erlang and distributed objects systems.

ASP.NET

  • ASP.NET vNext will support true side-by-side deployment for all dependencies, including .NET for cloud.

    • ASP.NET vNext will let you deploy your own version of the .NET Framework on an app-by-app-basis.

  • ASP.NET vNext is host agnostic. You can host your app in IIS, or self-host in a custom process.

  • Dependency injection is built into the framework.

  • Web Forms, MVC 5, Web API 2, Web Pages 3, SignalR 2, EF 6 will be fully supported on ASP.NET vNext

  • MVC 6

    • MVC, Web API, and Web Pages will be merged into one framework, called MVC 6. MVC 6 has no dependency on System.Web.
    • MVC 6, SignalR 3, EF 7 will have some breaking changes:
      • New project system
      • New configuration system
      • MVC / Web API / Web Pages merge, using a common set of abstractions for HTTP, routing, action selection, filters, model binding, and so on
      • No System.Web, new lightweight HttpContext

  • Cloud-Optimized

    • ASP.NET vNext includes new cloud-optimized versions of MVC 6, SignalR 3, and Entity Framework 7
    • .NET vNext (Cloud Optimized) will be a subset of the .NET vNext Framework, optimized for cloud and server workloads.
      • Low-memory and high-throughput.
      • The CLR and cloud-optimized libraries are NuGet packages

  • Roslyn

    • Enabling the .NET Compiler Platform (“Roslyn”) in ASP.NET applications
      • During development time you can just change your C# classes and hit Refresh in the browser. No DLL`s created in the 'bin' directory. All processed in memory.

  • cross devices

    • ASP.NET vNext (and Rosyln) runs on Mono.
    • Worked closely with Unity, Xamarin and Mono teams.

  • System.Web

    • Will be slised to independent modules.

  • New configuration standard

    • Based on JSON?

  • project.json

    JSON file that lists our dependencies, the configurations we want the application to run in, and the commands that we can use against the web application

    • Integrated packages.config, NuGet specifications (nuspec), and project files (csprojs) into a unified view of project dependencies expressed in a project.json file.
    • NuGet packages are the unit of reference (not assemblies).
    • If NuGet package 'Foo.Bar' has a bug, you can make a folder called Foo.Bar in our local project and put the source of this package in that folder. That local version overrides the NuGet, allowing you to easily patch bugs locally in libraries while you wait for a new release

MSVS 2013 upd. 2

Links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment