Pepperdash.Essentials.Plugins.Display.NEC 1.1.0-feature-4-series.2

.NET Framework 4.7.2 This package targets .NET Framework 4.7.2. The package is compatible with this framework or higher.
This is a prerelease version of Pepperdash.Essentials.Plugins.Display.NEC.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package Pepperdash.Essentials.Plugins.Display.NEC --version 1.1.0-feature-4-series.2                

                    
                

            
NuGet\Install-Package Pepperdash.Essentials.Plugins.Display.NEC -Version 1.1.0-feature-4-series.2
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="Pepperdash.Essentials.Plugins.Display.NEC" Version="1.1.0-feature-4-series.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Pepperdash.Essentials.Plugins.Display.NEC --version 1.1.0-feature-4-series.2                

                    
                

            
#r "nuget: Pepperdash.Essentials.Plugins.Display.NEC, 1.1.0-feature-4-series.2"
#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 Pepperdash.Essentials.Plugins.Display.NEC as a Cake Addin
#addin nuget:?package=Pepperdash.Essentials.Plugins.Display.NEC&version=1.1.0-feature-4-series.2&prerelease

// Install Pepperdash.Essentials.Plugins.Display.NEC as a Cake Tool
#tool nuget:?package=Pepperdash.Essentials.Plugins.Display.NEC&version=1.1.0-feature-4-series.2&prerelease

Internal Essentials Plugin Template (c) 2020

License

Provided under MIT license

Overview

Use this repo as a template when creating a new plugin for Essentials. For more information about plugins, refer to the Essentials Wiki Plugins article.

Github Actions

This repo contains two Github Action workflows that will build this project automatically. Modify the SOLUTION_PATH and SOLUTION_FILE environment variables as needed. Any branches named feature/*, release/*, hotfix/* or development will automatically be built with the action and create a release in the repository with a version number based on the latest release on the master branch. If there are no releases yet, the version number will be 0.0.1. The version number will be modified based on what branch triggered the build:

  • feature branch builds will be tagged with an alpha descriptor, with the Action run appended: 0.0.1-alpha-1
  • development branch builds will be tagged with a beta descriptor, with the Action run appended: 0.0.1-beta-2
  • release branches will be tagged with an rc descriptor, with the Action run appended: 0.0.1-rc-3
  • hotfix branch builds will be tagged with a hotfix descriptor, with the Action run appended: 0.0.1-hotfix-4

Builds on the Master branch will ONLY be triggered by manually creating a release using the web interface in the repository. They will be versioned with the tag that is created when the release is created. The tags MUST take the form major.minor.revision to be compatible with the build process. A tag like v0.1.0-alpha is NOT compatabile and may result in the build process failing.

If you have any questions about the action, contact Andrew Welker or Neil Dorin.

Product Compatible and additional computed target framework versions.
.NET Framework net472 is compatible.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.