-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProjectAnalyzer.Compile failed internally and return null in dotnet-sdk-2.1.300 #54
Comments
Thanks - pretty sure this is related to #49 - hoping to figure out a resolution soon. |
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. |
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? |
Buildalyzer-0.5.0 resolves my problem, thank you for updating. |
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. |
Environment
my
dotnet --info
output;Steps to reproduce
buildalyzertest
dotnet run -- ../sampleclass/sampleclass.csproj
Expected result
output compilation results(success) and project items and exit.
Actual result
with dotnet-core-sdk 2.1(2.1.300), output compilation results(failed) and output
project instance is null
then exit.but dotnet-core-sdk 2.0(2.1.4), expected results were output.
Workaround
add following packages into project that using Buildalyzer.
The text was updated successfully, but these errors were encountered: