This document now exists on the official ASP.NET core docs page.
- Application
- Request Handling
Wonder Boy: The Dragon's Trap | |
----------------------------- | |
Quick Guide for programmers | |
Last updated October 2018 | |
Contact: Omar Cornut <XXXXXX | |
=============================================== | |
INDEX | |
=============================================== |
This document now exists on the official ASP.NET core docs page.
This workflow explores the 3.0
manifest-based tag in the mcr.microsoft.com/v2/dotnet/core/runtime repo on MCR as an example. It uses curl
to call a set of container registry APIs to find image digests, layer digests, and layer location. This example is intended to show the separation between MCR as a image manifest service and Azure CDN as an image layer service.
This pattern can be used on any operating system, but the specific commands are OS-specific. curl
is included in the latest versions of Windows and is also in most Linux and macOS distributions. findstr
is part of Windows, however, grep
can be used on Linux or macOS instead.
The 3.0
tag is a manifest tag. It represents a set of potential candidate images, for various operating systems and operating systems versions. When a manifest tag is pulled by a docker client, the client picks the best image for the host op
namespace Analogy | |
{ | |
/// <summary> | |
/// This example shows that a library that needs access to target .NET Standard 1.3 | |
/// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET | |
/// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library. | |
/// </summary>INetCoreApp10 | |
class Example1 | |
{ | |
public void Net45Application(INetFramework45 platform) |