Got tired of talking about it and did it.
First, I created https://github.com/alexdresko/HomeSeerNuget. This repo creates a nuget package (https://www.nuget.org/packages/Homeseer/) which is used by the next repo. It's basically just HomeSeerAPI.DLL, HSCF.dll, and Scheduler.dll. Prevents from having to install HomeSeer just to do HomeSeer development. It is the latest version of those assemblies as of this writing.
https://github.com/alexdresko/HSPI basically contains the original code that was posted in this thread. From here, we can work it however we want. Personally, I think we should break out the tester into its own nuget package, and then create a base, abstract plugin from the HSPI.cs class.
Please make your way to the two repos and let's begin some conversation about it all.
First, I created https://github.com/alexdresko/HomeSeerNuget. This repo creates a nuget package (https://www.nuget.org/packages/Homeseer/) which is used by the next repo. It's basically just HomeSeerAPI.DLL, HSCF.dll, and Scheduler.dll. Prevents from having to install HomeSeer just to do HomeSeer development. It is the latest version of those assemblies as of this writing.
https://github.com/alexdresko/HSPI basically contains the original code that was posted in this thread. From here, we can work it however we want. Personally, I think we should break out the tester into its own nuget package, and then create a base, abstract plugin from the HSPI.cs class.
Please make your way to the two repos and let's begin some conversation about it all.
Comment