David Gardiner
David Gardiner
Would definitely like to see this fixed. Not allowing MSBuild to figure out that there's nothing to do means builds are much more inefficient.
If someone wanted to test this locally, find your local copy of SpecFlow.Tools.MsBuild.Generation.targets and revert the change made in the commit mentioned above and see if it behaves correctly. If...
I'm guessing this is because https://www.nuget.org/packages/Microsoft.VisualStudio.Threading/15.8.209 has a dependency on https://www.nuget.org/packages/Microsoft.VisualStudio.Threading.Analyzers/ Interestingly, for the 16.x release of Microsoft.VisualStudio.Threading, that dependency has been removed.
+1 for filters - now that I've just started using them and discovered I will lose them if I use the UI to edit the template.
Hmm.. that didn't seem to be my experience. I'll check again, and log a new issue if I can reproduce it
@reduckted Bingo! - yes I am. Removing that direct package reference seems to have resolved the warning
I think this might be the same problem as #324
Can you confirm if file://\\xxx\BoxShare/boxstarter.chocolatey/chocolatey/log4net.dll exists? If it doesn't, then I think this is #324. If not, then it probably is different.
Seems like each package is going one level deeper :-)
Still seeing this in 2.9.5 :-(