Add runtime strategy 'IgnoresAccessChecksTo' #28
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the concept of runtime strategies to Publicizer - ways to make sure the runtime doesn't throw a
MemberAccessException
when accessing a member in an assembly that was publicized at compile time.There are two strategies:
Unsafe
This is what we have had all along. Publicizer has been setting
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
, which causes some runtimes (mainly Mono) to suppress access checks at runtime.IgnoresAccessChecksTo
This emits an
IgnoresAccessChecksToAttribute
to the user's assembly, which causes some runtimes (most non-Mono) to suppress access checks.The runtime strategy can be chosen in the project file by specifying it in the
PublicizerRuntimeStrategies
property.By default, both of these strategies are used:
Users should generally not have to do anything for their assemblies to work in the runtime by default. Picking a specific runtime strategy should only be for people who needs more control of how their assemblies are compiled, e.g. omitting the
IgnoresAccessChecksToAttribute
.