FaKleiser

AD-XX: <TOPIC - short, concise summary>

• Date: <DATE - when the decision was made>
• Driver: <DRIVER - list a single person driving consenus and decision making>
• Stakeholders: <STAKEHOLDERS - list all relevant stakeholders affected by this decision>
• Status: [PROPOSED | DECIDED | SUPERSEDED]
• Categories: <CATEGORIES - use a simple grouping to help organize the set of decisions (e.g. backend, payment, user management, ...)>
• Outcome: <OUTCOME - once decided, provide a short summary of the decision outcome here>

Context

Antaris

<Project>
  <!-- TARGET FRAMEWORKS -->
  <ItemGroup Condition="'$(TargetFramework)'=='netstandard1.6'">
    <PackageReference Include="NETStandard.Library" Version="1.6.1" />
  </ItemGroup>
  
  <ItemGroup Condition="'$(TargetFramework)'=='netcoreapp1.1'">
    <PackageReference Include="Microsoft.NETCore.App" Version="1.1.0" />
  </ItemGroup>
  <!-- /TARGET FRAMEWORKS -->

DamianEdwards

Recorded talks by Damian Edwards & David Fowler

1. Application Diagnositcs in .NET Core 3.1
2. SignalR Deep Dive: Building Servers
3. Hidden gems in .NET Core 3
4. What you need to know about ASP.NET Core 2.2
5. Why your ASP.NET Core Application won't scale
6. Diagnosing issues in ASP.NET Core Applications
7. Patterns for application development with ASP.NET Core
8. Channel 9 interview, NDC Oslo 2017
9. ASP.NET Core Kestrel: Adventures in building a fast web server 1. Damian Edwards, David Fowler

davidfowl

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)