-
-
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
PackageReference assemblies not returned by GetReferences() for full framework projects #33
Comments
I suspect the problem here is that the NuGet targets that know how to handle
This also suggests there's some kind of connection to the VS project system. Are you able to submit your tests as a PR so I can bring them in? Once we've got the failing tests merged we can take it from there. |
Sure thing. Created #37. |
Looks like this got worse. I'm now completely unable to use this library to load up a full framework solution which has project to project references. Not sure what changed, but I think it has to do with a recent Visual Studio update. Any progress on this issue? |
Not with this issue specifically, but I'll be pushing a new release within the hour that addresses the broader problems you described. Recently, every time VS or the .NET Core SDK updates Buildalyzer breaks because the MSBuild APIs that it uses aren't compatible with the newest MSBuild stuff in the SDK. |
Been chasing this down and I'm pretty sure at this point that the .NET Core SDK can't build legacy project files that use I've verified this by running I'm going to attempt to identify this special case and revert to the framework build tools when it's encountered. |
Using the .NET Framework tools from .NET Core did resolve the |
Going to close this as "won't fix" due to a limitation with MSBuild: you simply can't build a legacy project file that uses |
It seems that GetReferences() on ProjectAnalyzer doesn't return assemblies from NuGet packages if PackageReference is being used instead of packages.config. This causes compilation errors in Roslyn workspaces.
Interestingly this only seems to be a problem when the host is .NET Core. It works just fine when the host is .NET Framework. I added some tests in this commit that show this behaviour. I also see errors in the test output which are very similar to #29.
The text was updated successfully, but these errors were encountered: