public static class ContentResolutionWhich resolver the current thread's deserialisation should use.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Ambient, and that is defensible here in a way it was not for asset scopes. Deserialising one chunk is synchronous from start to finish — there is no await anywhere inside it, so "the resolver in force" has exactly one meaning for the whole of it. The argument that ruled out ambient scopes was that a load can outlive the block it started in; a chunk read cannot.
The alternative would be threading a resolver through every generated serializer's signature, which would put an asset-loading concept into the wire format of types that have nothing to do with assets.
Fields and properties (1)
public static IContentResolver? CurrentThe resolver in force on this thread, if any.
Methods (1)
public static ContentResolution.Scope Push(IContentResolver resolver)Puts a resolver in force until the returned scope is disposed.
Used by (4)
- AssetManagerVixen.Assets
- ContentReferenceSerializerVixen.Core.Serialization
- ContentReferenceTestsVixen.Assets.Tests
- ScopeVixen.Core.Serialization