PepperDash.Essentials.Plugin.AvocorDisplay
1.0.0
dotnet add package PepperDash.Essentials.Plugin.AvocorDisplay --version 1.0.0
NuGet\Install-Package PepperDash.Essentials.Plugin.AvocorDisplay -Version 1.0.0
<PackageReference Include="PepperDash.Essentials.Plugin.AvocorDisplay" Version="1.0.0" />
paket add PepperDash.Essentials.Plugin.AvocorDisplay --version 1.0.0
#r "nuget: PepperDash.Essentials.Plugin.AvocorDisplay, 1.0.0"
// Install PepperDash.Essentials.Plugin.AvocorDisplay as a Cake Addin #addin nuget:?package=PepperDash.Essentials.Plugin.AvocorDisplay&version=1.0.0 // Install PepperDash.Essentials.Plugin.AvocorDisplay as a Cake Tool #tool nuget:?package=PepperDash.Essentials.Plugin.AvocorDisplay&version=1.0.0
Essentials Plugin Template (c) 2020
License
Provided under MIT license
Overview
Fork this repo when creating a new plugin for Essentials. For more information about plugins, refer to the Essentials Wiki Plugins article.
This repo contains example classes for the three main categories of devices:
EssentialsPluginTemplateDevice
: Used for most third party devices which require communication over a streaming mechanism such as a Com port, TCP/SSh/UDP socket, CEC, etcEssentialsPluginTemplateLogicDevice
: Used for devices that contain logic, but don't require any communication with third parties outside the programEssentialsPluginTemplateCrestronDevice
: Used for devices that represent a piece of Crestron hardware
There are matching factory classes for each of the three categories of devices. The EssentialsPluginTemplateConfigObject
should be used as a template and modified for any of the categories of device. Same goes for the EssentialsPluginTemplateBridgeJoinMap
.
This also illustrates how a plugin can contain multiple devices.
Cloning Instructions
After forking this repository into your own GitHub space, you can create a new repository using this one as the template. Then you must install the necessary dependencies as indicated below.
Dependencies
The Essentials libraries are required. They referenced via nuget. You must have nuget.exe installed and in the PATH
environment variable to use the following command. Nuget.exe is available at nuget.org.
Installing Dependencies
To install dependencies once nuget.exe is installed, run the following command from the root directory of your repository:
nuget install .\packages.config -OutputDirectory .\packages -excludeVersion
.
To verify that the packages installed correctly, open the plugin solution in your repo and make sure that all references are found, then try and build it.
Installing Different versions of PepperDash Core
If you need a different version of PepperDash Core, use the command nuget install .\packages.config -OutputDirectory .\packages -excludeVersion -Version {versionToGet}
. Omitting the -Version
option will pull the version indicated in the packages.config file.
Instructions for Renaming Solution and Files
See the Task List in Visual Studio for a guide on how to start using the templage. There is extensive inline documentation and examples as well.
For renaming instructions in particular, see the XML remarks
tags on class definitions
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net35 is compatible. net40 was computed. net403 was computed. net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 is compatible. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.0 | 350 | 7/19/2022 |