...Which is common in large monorepos, because lots of reusable config is hidden away in Directory.Build.props (etc.) files. It errors with "Error: Failed to parse pre VS2017 project properties".
It does not support nuget's new "Central Package Management" feature. So when versions are kept in a Directory.Package.props file instead of the Foo.csproj file, then the ProjectParserResult.References has null for the versions.
I'm using it on a monorepo with a few dozen projects, and so far (other than the above) it works quite well. Thanks!
Moved here from https://github.com/cake-build/cake/issues/1662
I'm using the "incubator" version of
ParseProject. Some feedback:It supports this traditional style:
But not this form:
...Which is common in large monorepos, because lots of reusable config is hidden away in
Directory.Build.props(etc.) files. It errors with "Error: Failed to parse pre VS2017 project properties".It does not support nuget's new "Central Package Management" feature. So when versions are kept in a
Directory.Package.propsfile instead of theFoo.csprojfile, then theProjectParserResult.Referenceshasnullfor the versions.I'm using it on a monorepo with a few dozen projects, and so far (other than the above) it works quite well. Thanks!