-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency Issue Creating Plugin A #95
Comments
Thanks for letting us know, @beerygaz. I'll try to get this taken care of soon. |
Is there a workaround in the short term? Can I just check out the HSPI repo and stick it in my project directory? |
If VS still creates the project, you can re-target the project to your desired .NET version and install the HSPI nuget package after the fact. You could pull the repo and try that. Use the Lemme know how it works out. |
The first option won't work. If I try to install the nuget package it fails dependency checks (HSPI has a dependency on the homeseer package, and that won't install). The second option is proving harder than expected in getting all the files in the right place and then adding them to the project. |
Long story short, try uninstalling the extension and reinstall it. I apologize for the inconvenience, but you shouldn't have to do that again. I goofed a couple weeks ago and messed some things up. Let me know if the new version of the extension works. https://marketplace.visualstudio.com/items?itemName=thealexdresko.HomeSeerTemplates2 |
Summary
Visual Studio 2017 throws an error when trying to create PluginA
Homeseer 1.0.0 can only target .NET 4.5
Many of the packages required by HSPI require .NET 4.6
Screenshots (if appropriate)
The text was updated successfully, but these errors were encountered: