The course branch is what I used throughout both courses as a single branch of all changes minus the above three one-off branches at the end of the second course.
Links
Troubleshooting Docker for Windows, the docs are wonderful:
I've always wondered why separate aspnetcore repositories were necessary so I welcome this change!
Historically, as mentioned in the course, we've had three repos:
microsoft/dotnet
General .NET Core development (non-aspnetcore apps, i.e. console apps)
Contains runtime/production images, i.e. microsoft/dotnet:2-runtime
Contains sdk/development images, i.e. microsoft/dotnet:2-sdk
microsoft/aspnetcore
Contains only runtime/production images for ASP.NET Core apps, i.e. microsoft/aspnetcore:2
microsoft/aspnetcore-build
Contains only sdk/development images for ASP.NET Core apps, i.e. microsoft/aspnetcore-build:2
Also contains some front end build tools like nodejs
This division was confusing because for a general dotnet app you use one repo regardless if you need sdk or runtime, and then if you're developing ASP.NET Core then you have to pick a repo based on needing sdk (build) or runtime! SHEESH! Don't we have better things to worry about :) (I kid, .NET Core is so awesome I don't mind this inconvenience)
2.1.300-preview1 is the last version of .NET Core in aspnetcore/aspnetcore-build repos
AFAIK - aspnetcore nightly repos are stopping at v2.0 too
All branches in this repository have been updated for 2.0.0 RTM. Issue #3
If you want to use a future release:
Update global.json to appropriate sdk version.
Update csproj files based on dotnet new webapi and dotnet new xunit templates.
Address changes to app code.
If a future release comes out and you don't want to update, change Dockerfile tags to explicitly reference 2.0.0, i.e.
microsoft/dotnet:2.0.0-sdk instead of microsoft/dotnet:2-sdk
microsoft/aspnetcore:2.0.0 instead of microsoft/aspnetcore:2
microsoft/aspnetcore-build:2.0.0 instead of microsoft/aspnetcore-build:2
If you want to use a pre-release version use the -nightly repos, i.e.
microsoft/dotnet-nightly instead of microsoft/dotnet
Announcements related to this course, since publishing:
During the previews of .NET Core 2.0, Debian Stretch was released. Both Stretch (v9) and Jessie (v8) images are available. As of .NET Core 2.0 RTM Stretch is now used in the multi-architecture tags. And, Stretch is now the default for the lifespan of .NET Core 2.x releases. dotnet/announcements#16
microsoft/dotnet & microsoft/dotnet-nightly image tags are now visually grouped by OS & CPU architecture dotnet/announcements#27
dotnet restore is now an implicit command, i.e. when you run dotnet build it will perform a restore if needed. That said, dotnet restore is still worthwhile to explicitly control when package restore occurs, for example to optimize the speed of building images as discussed in the courses. dotnet/announcements#23
Resources on Coming Changes
These are great resources for keeping up to date on what's coming next in .NET Core land:
请发表评论