ProjectAnalyzer.Compile failed internally and return null in dotnet-sdk-2.1.300 about buildalyzer

[daveaglick]

Thanks - pretty sure this is related to #49 - hoping to figure out a resolution soon.

[daveaglick]

Actually, I added the two NuGet packages you suggested directly to Buildalyzer and it works now. Thanks!

That makes sense too - I think the underlying problem is that they stopped shipping NuGet packages alongside the SDK. I had suggested some other more complicated solutions in #49 (like overriding the assembly loader), but I'm very tempted to just add the package references and be done with it.

[daveaglick]

A new version 0.5.0 is hitting NuGet now - can you please take it for a spin and let me know if it resolves this issue for you?

[itn3000]

Buildalyzer-0.5.0 resolves my problem, thank you for updating.
Additional Info: I found another workaround which use System.Runtime.Loader.AssemblyContext.Default.LoadFromAssemblyPath before project compilation.
But this way still remains "what assemblies should I load?" problem.
AssemblyContext.Resolved event was not fired when required NuGet.Versioning.

[daveaglick]

Yeah, I think the best bet is to directly depend on the NuGet packages. Unfortunately this increases the dependency surface of Buildalyzer, but none of the alternatives seem as stable to me.