-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Multitarget O# external access projects to fix issues accessing prope… #67163
Conversation
Are you interested in the other option here? All we need to do is add a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to answer the question before proceeding
I'll send a PR for a concrete example here |
Submitted #67171 |
@sharwell I'm not necessarily opposed to another fix, but O# multi-targets netframework and .netcore already, so multi-targeting the external access project doesn't seem inappropriate to me. I can try out your change, but I don't think I'll be able to get to it until late this afternoon / Monday. |
Withdrawing by block on the basis that both binaries here will be used. If we were only building downstream for one target, this wouldn't be an appropriate resolution.
Going ahead with this change since O# multi-targets and I already tested this one (and CI already finished). |
…rties on records
The last PR - #67106 was slightly incorrect - it fixed the build, but caused a bunch of test failures trying to call methods on records
The root cause of that failure appeared to be a mismatch in the method signatures caused by the workspace version of IsExternalInit
vs the caller
Switching over to appropriately multi-target the external access project appears to have fixed the issue in build and in the tests (so far).