Edward Neal

We're starting to see PRs for SqlClientX merged, so I'd definitely be interested to understand what the roadmap for this is and what design work's already been done.

I see your point, but think that it might mix concerns a little. I could see the buffer being allocated from a few different places: * Builtin `byte[]` allocator *...

When I wrote that particular PR my first intuition was to reach for `AsnDecoder` and `AsnEncoder` classes - I ideally wanted to avoid allocating anything other than the resultant byte...

@gewarren I'm not sure, but I think it's unlikely - I've created this issue towards the conclusion of the PR merge process, and chose Preview 3 because it was the...

The PR referenced has now been merged in commit [6cc6c66](https://github.com/dotnet/runtime/commit/6cc6c66acc3f187f30e0fc7541e1097999863ff5).

We've been looking at opening XPS documents in .NET Core over in dotnet/runtime#51929 and this point came up. For the sake of full disclosure: I've got next to no experience...

@wstaelens I agree - the idea behind XPS is good. An open, easily-parsable, declarative way to lay out a document is a great idea, and I've seen my fair share...

There are some performance improvements in progress in the runtime repo, but those improvements are on ZipArchive, rather than on XpsDocument directly. Once these are in place, I expect there'll...

I agree; this'll need a bit of work though. For approaches where the output isn't directly shown on a GUI, there's no need for the XpsDocument to construct and retain...

Sorry wstaelens, I don't have an update - this needs guidance/direction from the WPF team (and if XPS support is to be lifted into its own package, probably another group...