Unsync, is the keyword. An eco system of developer tools not in sync is bad. very bad. Hopefully I didn’t forget to point out that its bad.
This is bad. Due to hardware constraints I had to install VS on the metal (in addition to VM) and I can’t compile VS2015 projects in VS2017 (missing or invalid GrassHopper paths). Couldn’t even add the missing grssHopper (5) paths in the project created with the old VS2015.
I really think that the R5 templates and wizzards should be updated to install for VS2017.
Fig.1. The two R5 templates (screenshot from VS2015) are not available for install in VS2017 :
This is getting annoying. It is a simple matter of fact that R5 will be around for some time yet (due to some plugins running only for R5) even if developing for R6. Currently “everything” in the eco system around Rhino is going more and more into a state of “unsync”.
If you don’t fix the develoepr ecos system, why then not open source it so we can fix it ourselves? Development with tools that you cannot fix when the world moves on, is one of the critical factors when deciding whether to use or abandon certain tools chains.
Short version: Fix the templates and NuGet packages for VS2017.