The ACME Protocol is an IETF Standard 

ServiceStack is an open source framework designed to be an alternative to the WCF, ASP.NET MVC, and ASP.NET Web API frameworks. 

jobs:
  build:

    runs-on: windows-latest
    
    steps:
    - name: Checkout
      uses: actions/checkout@v2
        
    - name: Setup MSBuild
      uses: microsoft/setup-msbuild@v1.0.0  
       
    - name: Setup NuGet
      uses: nuget/setup-nuget@v1.0.2
     
    - name: Restore NuGet Packages
      run: nuget restore src/WebApplication1.sln
 
    - name: Build (Release)
      run: msbuild src/WebApplication1.sln /p:Configuration=Release

• دستور runs-on: windows-latest این workflow را بر روی ویندوز اجرا میکنه (بدیهیه که پروژه‌های دات نت Full بر روی غیر از ویندوز قابل build شدن نیست)
• در step دوم MSBuild رو توسط اکشن microsoft/setup-msbuild نصب میکنیم.
• در step سوم Nuget رو توسطاکشن nuget/setup-nuget نصب میکنیم.
• در step چهارم وابستگی (پکیج)‌های پروژه رو restore میکنیم. 
• در step چهارم پروژه رو توسط msbuild و در مود Release بیلد میکنیم.
• عبارت src/WebApplication1.sln به پوشه و نام فایل سلوشن شما اشاره میکنه.

    - name: Setup VSTest
      uses: Malcolmnixon/Setup-VSTest@v2

    - name: VSTest
      run: vstest.console ClassLibrary.Test\bin\Debug\ClassLibrary.Test.dll

Entity Framework (EF) Core is the rearchitected and rewritten version of the Entity Framework object relational mapping engine for .NET Core applications. It is very light-weight, extensible, and cross platform.

However, high transaction .NET Core applications using EF Core face performance and scalability bottlenecks in the database-tier under peak loads. This is because, although you can linearly scale the application tier by adding more application servers, you cannot add more database servers to scale it.

But, if you use a distributed cache like NCache in your .NET Core applications, you can quickly remove these performance and scalability bottlenecks and handle extreme transaction loads. 

An independent group of volunteers within Microsoft has successfully open sourced and forked Windows Live Writer. The fork is called Open Live Writer (also known as OLW) and it is part of the .NET Foundation and managed by this group of volunteers.  

Welcome to the newest newsletter from JetBrains, .NET Annotated Monthly! This newsletter is hosted by Rachel Appel, a Developer Advocate at JetBrains, with occasional updates from other JetBrains Developer Advocates. 

This is a list of common LINQ mistakes, which has grown out from reading code of others (and myself) - and using the results for training people new to .NET. 

Before we dive into the technical details, let’s start with a quick history lesson, courtesy of Don Syme who worked on adding generics to .NET and then went on to design and implement F#, which is a pretty impressive set of achievements!!

Background and History

• 1999 Initial research, design and planning
  • .NET/C# Generics History: Some Photos From Feb 1999
• 1999 First ‘white paper’ published
  • More C#/.NET Generics Research Project History – The MSR white paper
  • MSR White Paper: Proposed Extensions to COM+ VOS (Draft) (pdf)
• 2001 C# Language Design Specification created
  • Some History: 2001 “GC#” (Generic C#) research project draft
  • MSR - .NET Generics Research Project - Generic C# Specification (pdf)
• 2001 Research paper published
  • Design and Implementation of Generics for the .NET CLR (pdf)
• 2004 Work completed and all bugs fixed
  • Some more .NET/C# Generics Research Project History