Properties like MSBuildThisFileDirectory don't work about buildalyzer

[daveaglick]

I’m not sure that’s possible - at least not without dumping the XML to disk as a temporary project file and loading from that. Even without a tweaker, we still manipulate the XML in some cases before loading and I’d like to reserve the option of doing other transformations before load in the future if needed.

IIRC, Buildalyzer does try and tell MSBuild about the filename and location. Perhaps there’s a way (even if means using reflection or other dark magic) to populate whatever MSBuild needs to populate those properties. Or could we just set all of them ourself?

[dfederm]

@daveaglick You're right that Buildalyzer attempts to set the FullFilePath, and I suspect a re-evaluate after setting that may populate these properties, but that happens after the initial load. If the initial load requires these properties (ie. used in Imports), loading may fail.

[daveaglick]

Ah, think I got it - so we’ve got to get those set during initial load and not via evaluation sometime later. I’d still like to find a way to do this via a stream instead of the file system - hopefully there’s way.

[jirikopecky]

@daveaglick I have created a pull request that should address this issue: #45, could you please take a look? The solution is taken from Roslyn MSBuildWorkspace and related classes and utilizes project creation through ProjectRootElement class.

[daveaglick]

@jirikopecky Thanks! I took a quick glance at the PR the other day and it looked good. I'll take a closer look and merge it in hopefully next week. Also have a couple other things to get in (plus a new MSBuild API) so I'll probably do a release with these changes next week too.