From 91ff0d8c83b627e3724fd6dd73d947a7ecd412f5 Mon Sep 17 00:00:00 2001 From: Jason Alborough Date: Fri, 15 Jul 2022 14:06:00 -0400 Subject: [PATCH] nuspec-TEMPLATE fix: #17 changes nuspec to nuspec-TEMPALTE feature: adds brief configuration instructions for nuspec file to readme --- ... => PDT.EssentialsPluginTemplate.nuspec-TEMPLATE} | 0 README.md | 12 ++++++++++++ 2 files changed, 12 insertions(+) rename PDT.EssentialsPluginTemplate.EPI/{PDT.EssentialsPluginTemplate.nuspec => PDT.EssentialsPluginTemplate.nuspec-TEMPLATE} (100%) diff --git a/PDT.EssentialsPluginTemplate.EPI/PDT.EssentialsPluginTemplate.nuspec b/PDT.EssentialsPluginTemplate.EPI/PDT.EssentialsPluginTemplate.nuspec-TEMPLATE similarity index 100% rename from PDT.EssentialsPluginTemplate.EPI/PDT.EssentialsPluginTemplate.nuspec rename to PDT.EssentialsPluginTemplate.EPI/PDT.EssentialsPluginTemplate.nuspec-TEMPLATE diff --git a/README.md b/README.md index 67a4614..8dfb905 100644 --- a/README.md +++ b/README.md @@ -40,3 +40,15 @@ If you need a different version of PepperDash Core, use the command `nuget insta 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 + +## Build Instructions (PepperDash Internal) + +## Generating Nuget Package + +In the solution folder is a file named "PDT.EssentialsPluginTemplate.nuspec-TEMPLATE" + +1. Remove the -TEMPLATE so that the extention is .nuspec. +2. Rename the file to match your plugin solution name +3. Edit the file to include your project specifics including + 1. PepperDash.Essentials.Plugin.MakeModel Convention is to use the prefix "PepperDash.Essentials.Plugin" and include the MakeModel of the device. + 2. https://github.com/PepperDash/EssentialsPluginTemplate Change to your url to the project repo \ No newline at end of file