Notes from the ASP.NET Community Standup –December 13, 2016

Maria Naggaga

This is the next in a series of blog posts that will cover the topics discussed in the ASP.NET Community Standup. The community standup is a short video-based discussion with some of the leaders of the ASP.NET development teams covering the accomplishments of the team on the new ASP.NET Core framework over the previous week. Join Scott HanselmanDamian EdwardsJon Galloway and an occasional guest or two discuss new features and ask for feedback on important decisions being made by the ASP.NET development teams.

Each week the standup is hosted live on Google Hangouts and the team publishes the recorded video of their discussion to YouTube for later reference. The guys answer your questions LIVE and unfiltered. This is your chance to ask about the why and what of ASP.NET! Join them each Tuesday on where the meeting’s schedule is posted and hosted.

ASP.NET Community Standup 12/14/2016

Rethinking email confirmation

Managing Cookie Lifetime with ASP.NET Core OAuth 2.0 providers

Build a REST API for your Mobile Apps with ASP.NET Core

IdentityServer4 and ASP.NET Core 1.1

Url culture provider using middleware as filters in ASP.NET Core 1.1.0

Making Application Insight Fast and Secure

Simple SQL Localization NuGet package

Building Application Insights Logging Provider for ASP.NET Core

Generic Repository Pattern In ASP.NET Core

Integration Testing with Entity Framework Core and SQL Server

Bare metal APIs with ASP.NET Core MVC

Accessing HttpContext outside of framework components in ASP.NET Core

Optimize expression compilation memory usage

ASP.NET Core Response Optimization

Angular 2 and ASP.NET Core MVC

Dockerizing a Real World ASP.NET Core Application

Convert ASP.NET Web Servers to Docker with Image2Docker

Sharing code across .NET platforms with .NET Standard

Multiple Versions of .NET Core Runtimes and SDK Tools SxS Survive Guide

Migration to ASP.NET Core: Considerations and Strategies

Updating Visual Studio 2017 RC – .NET Core Tooling improvement


On December 12th, we announced updates to the .NET Core tooling for Visual Studio 2017 RC. This update came with enhancements and bug fixes to the earlier release of VS 2017 .NET Core tooling. Some areas addressed include:

csproj file simplification: .NET Core project files now use an even more simplified syntax, making them easier to read.



CLI commands added: New commands added for adding and removing  project to project references.

Overall quality improved: Bug fixes in xproj to csproj migration, project to project references, NuGet, MSBuild and ASP.NET Core with Docker.

For more details on the .NET Core Tooling improvements please read the announcement here.

Questions and Answers

Question:  With the new VS 2017 .NET Core tooling updates  I get csproj file when I create a new application. Will I ever want to use project.json again?

— The logic is when you go into a new folder and type dotnet, it needs to find an SDK. It will by default use the latest version of the dotnet SDK available. However, by using global.json you can specify previous versions of the SDK you would like to use.

Question: Is global.json still the router for the dotnet SDK?  checkout this post for reference

— In the current build it is but, will be replaced. The intent is we will still support side-by-side SDKs with the ability to switch between them.

See you at our next community standup!




Discussion is closed.

Feedback usabilla icon