@AArnott are the XamlPropertyRule items required to be compiled? I just noticed when you moved .xaml files to shared project, you changed XamlPropertyRule items to None, but it did not seem to have any adverse effect.
The change to the item type was probably an oversight on my part. IIRC XamlPropertyRule causes code generation to run for each rule. If I got away with the mistake, I guess we didn't depend on the code generation -- although we should, in order to avoid magic strings in our code.
my thought process here: I want to deprecate support for 2013/2015 and only release for 2017
get rid of the MSI, keep only 2017 .vsix, update refences to MSBuild 15.0
I'm OK with that. We can keep a vs5015 branch in case we need to service it.
which is significant breaking change, so making NuProj.2017, NuProj.Common.2017 would make a sense
but I didn't realize you were waiting for me to finish #286
so, how about this:
could you release current master, that should at least have that Project reference error that we have like 10 different bugs for
then merge #286, I'll remove support for old VS, and then release .vsix and and updated packages for MSBuild 15.0