Net.RunMethodsSequentially 2.0.1

dotnet add package Net.RunMethodsSequentially --version 2.0.1
NuGet\Install-Package Net.RunMethodsSequentially -Version 2.0.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Net.RunMethodsSequentially" Version="2.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Net.RunMethodsSequentially --version 2.0.1
#r "nuget: Net.RunMethodsSequentially, 2.0.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Net.RunMethodsSequentially as a Cake Addin
#addin nuget:?package=Net.RunMethodsSequentially&version=2.0.1

// Install Net.RunMethodsSequentially as a Cake Tool
#tool nuget:?package=Net.RunMethodsSequentially&version=2.0.1


This RunStartupMethodsSequentially .NET library (shortened to RunSequentially) to as is designed to updates to single resources, e.g. a database, on startup of an application that has multiple instances running (e.g. a ASP.NET Core web site with Azure Scale Out is turned on). This library runs when the application starts up and run your startup services. Typical startup services are: migrating to a database, seeding a database and/or ensuring that an admin user has been added. It can also be used with non-database resources as Azure blob, common files, etc.

Scale Out: A scale out operation is the equivalent of creating multiple copies of your web site and adding a load balancer to distribute the demand between them (taken from Microsoft Azure docs).

This open-source library available on NuGet as Net.RunMethodsSequentially. The documentation can be found in the README file, and the article How to safely apply an EF Core migrate on ASP.NET Core startup and see the Release notes for details of changes.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.1 is compatible. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Net.RunMethodsSequentially:

Package Downloads

Provides extra authorization and multi-tenant features to an ASP.NET Core application.


AppText.Storage.EfCore is a storage implementation for the AppText CMS that uses EntityFramework Core. Currently, only MS SQL Server is supported.

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on Net.RunMethodsSequentially:

Repository Stars
This library provides extra authorization and multi-tenant features to an ASP.NET Core application.
Version Downloads Last updated
2.0.1 7,783 2/9/2024
2.0.0 65,165 11/15/2022
1.3.1 5,899 8/17/2022
1.3.0 20,408 12/1/2021
1.2.0 2,652 11/25/2021
1.1.0 278 11/23/2021
1.0.0 292 11/22/2021

- Microsoft.Data.SqlClient updated to because of vulnerable in current version
- Updated DistributedLock parts to fix the .NET 8 Postgres bug - see