GetReferences returns null although the project does reference other assemblies

[phmonte]

GetReferences returns null although the project does reference other assemblies

[bobuva]

@daveaglick I ran it again using Buildalyzer 1.0.0 and it worked! My only code change was from

IEnumerable<string> references = analyzer.GetReferences();

to

IEnumerable<string> references = analyzer.Build().GetReferences();

Note that I also tried

IEnumerable<string> references = analyzer.Build().GetProjectReferences();

but that returned an empty collection.

[daveaglick]

Thanks for the report. Buildalyzer should be working under all .NET Core 2.x scenarios except preview SDKs. I'm working on the problem with previews, but as far as I can tell it should only appear on systems at runtime when a preview SDK is installed. Does this describe your situation? Typically this failure exhibits itself as compilation failures which can be seen in the Buildalyzer log output - are you able to confirm if you see any errors in the log (you can pass in a logger to Buildalyzer or grab the string log)?

[bobuva]

I am using .NET Core 2.1 preview with the SDKs that come with it. For some reason, when I try to see the log output in a StringWriter (see below) I don't get anything. Even when I write it out in a finally clause.

            StringBuilder sb = new StringBuilder();
            StringWriter writer = new StringWriter(sb);
            AnalyzerManagerOptions options = new AnalyzerManagerOptions();
            options.LogWriter = writer;

[daveaglick]

Buildalyzer 1.0.0 was released to NuGet last night. Can you please try it out when you get the chance and let me know the status of this issue?

FYI - the Buildalyzer 1.0.0 API has changed significantly. Revised documentation is forthcoming, but I wanted to get the release out there ASAP. Hopefully you'll be able to figure out the differences, but if not the source code of the tests is a good place to look or wait until better docs are out next week.

[daveaglick]

Great! I'll go ahead and close this then - feel free to open a new issue if you have any other problems.