Page 8 - MSDN Magazine, September 2017

Editor’s NotE MICHAEL DESMOND
Hard Core: Focus on .NET Core 2.0 and .NET Standard 2.0
Microsoft has been pushing hard with its cross-platform, open source vision of software development, promoting the .NET Core and ASP.NET Core frameworks, and presenting .NET Standard as a universal target for .NET-based development. In August, Microsoft released version 2.0 of .NET Core, ASP.NET Core and .NET Standard, enabling a more robust, inclusive and complete platform for development than ever before.
To help support that effort, MSDN Magazine is publishing a set of five feature articles focused on the new releases. Immo Landwerth kicks off the festivities with his feature, “Demystifying .NET Core and .NET Standard,” where he addresses some of the confusion about the differences between .NET Framework, .NET Core and .NET Standard, and shows how Microsoft has developed a strategic vision for coding across the various flavors of .NET. Andrew Hall and Joe Morris follow that up with a hands-on dive into writing .NET Core apps on Windows, macOS and Linux using tools like Visual Studio, Visual Studio for Mac and Visual Studio Code.
There’s a lot going on in this issue and it reflects the excitement that Microsoft sees among developers in the field.
Web development gets a lot of love in this issue. Mike Rousos introduces the new ASP.NET Core 2.0 framework, guiding readers through development of a simple ASP.NET Core Web site as he explains important ASP.NET Core concepts and technologies. Steve Smith follows with “Simpler ASP.NET MVC Apps with RazorPages,”whichshowshowthisnewfeatureofASP.NETCore reduces friction common to MVC development while preserving flexibility. Finally, Microsoft Program Manager Nikhil Joglekar’s
“Snapshot Debugging for Production Apps and Services in Azure” illustrates how developers can diagnose production code bugs using the new Snapshot Debugger with Visual Studio and App Insights.
There’s a lot going on in this issue and it reflects the excitement that Microsoft sees among developers in the field. Andrew Hall says that .NET Core is matching the quickened pace of mod- ern development, by decoupling framework updates from the Windows OS and providing the ability to deploy side-by-side and even per-application copies of the framework.
“We commonly hear of customers who are stuck on much older versions of the .NET Framework, because a few applications on the server don’t work correctly with newer versions, which means that all their applications are pinned to the lowest common denom- inator,” Hall says. “.NET Core removes the problem of a single machine-wide installation of the framework, freeing developers to use the latest features for their new apps, without fear of impacting older apps running on the server.”
Microsoft has made a concerted effort to increase the utility and clarity of its framework offerings. Steve Smith notes that both .NET Core 2.0 and ASP.NET Core 2.0 eliminate rough edges in the cross-platform savvy frameworks and strongly boost productivity.
“There is more of an emphasis on convention over configuration, especially in areas like Startup, so that developers don’t have to deal with quite as much plumbing code in the basic project templates. All of the functionality is still available, but the expected path is now set up by default with much less code,” says Smith.
Sitting atop all this is the .NET Standard specification of APIs, which Immo Landwerth says brings consistency to .NET-based development across .NET Framework, .NET Core and Xamarin. Developers who target .NET Standard 2.0 can build libraries that can be used from any .NET implementation or supported OS, including Windows, Linux, Android, macOS and iOS. If you want to maximize the reach of your code in the most consistent and reliable way, .NET Standard is
the way to do it.
Visit us at msdn.microsoft.com/magazine. Questions, comments or suggestions for MSDN Magazine? Send them to the editor: mmeditor@microsoft.com.
© 2017 Microsoft Corporation. All rights reserved.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, you are not permitted to reproduce, store, or introduce into a retrieval system MSDN Magazine or any part of MSDN Magazine. If you have purchased or have otherwise properly acquired a copy of MSDN Magazine in paper format, you are permitted to physically transfer this paper copy in unmodified form. Otherwise, you are not permitted to transmit copies of MSDN Magazine (or any part of MSDN Magazine) in any form or by any means without the express written permission of Microsoft Corporation.
A listing of Microsoft Corporation trademarks can be found at microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx. Other trademarks or trade names mentioned herein are the property of their respective owners.
MSDN Magazine is published by 1105 Media, Inc. 1105 Media, Inc. is an independent company not affiliated with Microsoft Corporation. Microsoft Corporation is solely responsible for the editorial contents of this magazine. The recommendations and technical guidelines in MSDN Magazine are based on specific environments and configurations. These recommendations or guidelines may not apply to dissimilar configurations. Microsoft Corporation does not make any representation or warranty, express or implied, with respect to any code or other information herein and disclaims any liability whatsoever for any use of such code or other information. MSDN Magazine, MSDN and Microsoft logos are used by 1105 Media, Inc. under license from owner.
4 msdn magazine