MSHelper 1.0.1
dotnet add package MSHelper --version 1.0.1
NuGet\Install-Package MSHelper -Version 1.0.1
<PackageReference Include="MSHelper" Version="1.0.1" />
paket add MSHelper --version 1.0.1
#r "nuget: MSHelper, 1.0.1"
// Install MSHelper as a Cake Addin #addin nuget:?package=MSHelper&version=1.0.1 // Install MSHelper as a Cake Tool #tool nuget:?package=MSHelper&version=1.0.1
MSHelper : Introduction to MSHelper
⭐ Star us on GitHub � it motivates us a lot!
Welcome to MSHelper
MSHelper is a set of helper libraries that can be most of the time (with some exceptions) used independently of each other to help you to build your web applications and microservices. MSHelper is neither a framework nor a silver bullet.
Quite opposite, it�s mostly the set of extensions methods along with additional abstractions that will help you to deal with common infrastructural concerns such as routing, service discovery, load balancing, tracing, asynchronous messaging and so on.
Getting started
This document is for the latest MSHelper.CQRS.Commands 1.0.1 release and later. In order to get started with MSHelper, simply install the core package:
dotnet add package MSHelper
Usage
Its sole responsibility is to expose IMSHelperBuilder
being used by other packages, which provides fluent API experience, similar to built-in ASP.NET Core IServiceCollection and IApplicationBuilder abstractions.
public class Program
{
public static async Task Main(string[] args)
=> await WebHost.CreateDefaultBuilder(args)
.ConfigureServices(services => services.AddMSHelper().Build())
.Configure(app =>
{
//Configure the middleware
})
.Build()
.RunAsync();
}
Whether you�re using just a Program.cs
on its own (yes, you can build your web applications and microservices without a need of having Startup class and AddMvc()
along with full UseMvc()
middleware) or doing it with a Startup.cs
included, just invoke AddMSHelper() on IServiceCollection
instance within the ConfigureServices()
method and start using MSHelper packages.
The core MSHelper package also registers AppOptions
type which contains the application name (and it�s purely optional).
Options
-- name - an optional name of the application.
-- displayBanner
- display a banner (console output) with the application name during a startup, true by default.
appsettings.json
"app": {
"name": "some service",
"displayBanner": true
}
Important Note:
All the MSHelper packages are for self learning purposes inspired by Devmentors.io
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net7.0 is compatible. 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. |
-
net7.0
- Figgle (>= 0.4.1)
- Scrutor.AspNetCore (>= 3.3.0)
NuGet packages (24)
Showing the top 5 NuGet packages that depend on MSHelper:
Package | Downloads |
---|---|
MSHelper.MessageBrokers
MSHelper.MessageBrokers - Asynchronous messaging using RabbitMQ. |
|
MSHelper.CQRS.Queries
MSHelper.CQRS.Queries - a list of helper classes that will adds an ability to create and process queries in the sense of CQRS. |
|
MSHelper.HTTP
MSHelper.HTTP - Requests, service discovery, load balancing. |
|
MSHelper.CQRS.Events
MSHelper.CQRS.Events - a list of helper classes that will adds an ability to create and process events in the sense of CQRS. |
|
MSHelper.Discovery.Consul
MSHelper.Discovery.Consul - Service Discovery |
GitHub repositories
This package is not used by any popular GitHub repositories.