-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
ProjectReference support #5
Comments
Looks like ProjectReference mostly just works in our case, at least for native<->native dependencies. I likely still need to write my own reference resolver to augment ResolveAssemblyReferences, because the built-in one expects .NET assemblies, which, well, won't work with native libraries 😛 |
MyApplication should have access to A, B and C, while MySubLibrary should have B and C. |
So as it turns out, as long as you manually specify |
This is an absolute must because it makes MSBuild in .NET Core so much nicer to work with.
https://github.com/microsoft/msbuild/blob/master/documentation/ProjectReference-Protocol.md
Assuming this is up to date, we could reference it while implementing ProjectReference support for our own projects. We should be careful to not trip up everything else though.
The text was updated successfully, but these errors were encountered: