Closed ghuntley closed 7 years ago
Thanks - looks like the root cause is because it's having trouble reading the csproj files (which cascades to failures in some of the Razor files because they're expecting the source to have been processed and symbols to be available).
I had some trouble a while back with the Roslyn MSBuildWorkspace finding the matching version of the MSBuild libraries. Wondering if that's what's happening here. The challenge is that it's very environment specific.
Do you mind running with the --verbose
CLI argument and pasting in the error you see (if any) when it tries to load the csproj in the API pipeline? It'll be on that last time through - all the earlier Wyam runs from the build script are to generate samples for the various themes and they seemed to run okay. The verbose flag generates a lot of output, so may need to pipe to a file if your console doesn't have a large buffer.
Thanks!
I think this is fixed for legacy csproj files. We still can't read new SDK-style projects, but that should be coming very soon now that Buildalyzer is done.