In an effort to dramatically reduce confusion, ASP.NET 5.0 and Entity Framework 7.0 have been renamed to ASP.NET Core 1.0 and Entity Framework Core 1.0.
On December 24th, Microsoft released its latest Integration Roadmap. This is the first insight, customers and partners have had, into the collective roadmap of Microsoft integration technologies in several years.
Microsoft recently released .NET Core and ASP.NET 5 Release Candidate, supported on Windows, OS X and Linux. Microsoft states this release is ready for production and will support it. Both release candidates are considered feature complete on Windows, OS X and Linux, although minor features may still be added until the final release.
Microsoft recently released ASP.NET WebHooks preview, a library to create and consume webhooks. WebHooks supports MVC 5 and WebApi 2.
Microsoft has released an SDK for its monitoring platform Visual Studio Application Insights that brings support for ASP.NET 5. Application Insights is divided into two main components; the Azure portal is where the data is displayed and the SDK provides the API to send telemetry events.
The roadmap for ASP.NET 5 includes three more betas between now and November’s release candidate. And that’s after dropping Visual Basic, SingalR 3, and Web Pages 4 from the list.
While most of the buzz has been about ASP.NET 5 and the cross-platform execution engine, MVC, Microsoft’s preferred UI and web service framework, is also seeing many changes. The most important being the unification of MVC, Web API, and Web Pages.
Microsoft has announced the release of a native Visual Studio application for Windows, Mac OS X, and Linux.
The latest preview of Visual Studio 2015 demonstrates new diagnostic and debugging tools along with a new release of TypeScript. An updated build of ASP.NET 5 is also included, broadening its developer tools.
Version 7 of Entity Framework represents a major redesign of the 6-year-old ORM. As such, Microsoft will not be recommending the initial release of EF 7 for existing projects. Rather, it is only meant for projects that are using ASP.NET 5 and .NET Core.
The ASP.NET vNext runtime uses the Rosylyn compiler to compile and load the C# sources before running them. David Fowler shows how you can leverage the DI-by-design approach of KRuntime to inject support for your own language.
Katana is Microsoft’s stand-alone implementation of the OWIN (Open Interface for .NET) standard. With the release of version 3, Kanata is wholly to the asynchronous model offered by .NET 4.5.
ASP.NET vNext alpha3 was released along with the Visual Studio "14" CTP3. Several interesting changes are around ASP.NET projects - simpler project files, ability to specify build event handlers, cleaner source folders and more.
Visual Studio Update 3 was released last week and includes some framework and tooling improvements relevant to web and mobile developers. We go through some of these, including the ASP.NET identity update supporting two-factor authentication, new Visual Studio-Azure integrations as well as several updates to the Apache Cordova Tooling preview.