Suggestion: Allow solution (project) global properties to be controlled via AnalyzerManager about buildalyzer HOT 4 CLOSED

Gotcha, makes sense. I'll add the ability to specify additional environment variables and MSBuild properties in the next release (not sure when that'll be though).

from buildalyzer.

This is a great idea for the general case.

I wonder if in this specific case we should be setting VSToolsPath for everyone though?

from buildalyzer.

I thought about that, but this is a very special edge case (loading a Framework project in Core) - I feel that setting any property to reference the Visual Studio directory for a Core run is likely going to trip someone else up at a later stage. Hence, the more general request.

from buildalyzer.

@IanKemp Note that ProjectAnalyzer does already have a SetGlobalProperty method you can call before calling Load or Compile. Does that help?

I still think it may be worthwhile to have this at the AnalyzerManager level as well though. IE, use AnalyzerManager.SetGlobalProperty to set it for all future projects, and use ProjectAnalyzer.SetGlobalProperty to set it for one specific project.

from buildalyzer.