-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
PolySharp with InternalsVisibleTo produces CS0433 #103
Comments
After adding However that didn't solve the problem, but was in fact a result of me trying to produce a minimal repro. After adding
This build error could then be fixed by adding a condition on the package reference: Removing the multi-targetting, but keeping PolySharp as a dependency, the error can be reproduced like this:
Is this something PolySharp would be able to support: consuming a library targeting |
Duplicate of #50? |
Description (optional)
Using PolySharp in a
netstandard2.0
project that usesInternalsVisibleToAttribute
to expose internals to anothernet80
project, will cause that other project to fail to compile. This is because the types generated by PolySharp have internal visibility and collide with the typesnet80
provides.Reproduction Steps
I have a library project that targets
netstandard2.0
and I need to consume it from bothnet48
andnet80
targets:There are classes internal to the library that the test project needs to know about:
There is a test project that multi-target
net48
andnet80
. For simplicity we'll ignore the multi-targeting and only look at thenet80
consumer:Expected Behavior
Compiles.
Actual Behavior
System info
This section should contain useful info such as:
Additional context (optional)
N/A
The text was updated successfully, but these errors were encountered: