XPS documents in .NET Core can't be opened

[wstaelens]

Besides the impersonation limitation I reported earlier we have also found that XPS documents coming from a virtual printer can't be opened in .NET Core.

We first have to extract the XPS files, combine all part files to a single file and then create the XPS file again. Then we can open an XPS file in .NET Core.

Is this by design or a bug?

Because we don't have to do this in .NET Full Framework.

[GrabYourPitchforks]

Please clarify the problem you're experiencing so that we can route the issue appropriately. Are you receiving a runtime exception? (If so, please provide the exception message and repro code.) Are you receiving no exception at runtime but still seeing incorrect behavior?

[no-response]

This issue has been automatically closed due to no response from the original author. Please feel free to reopen it if you have more information that can help us investigate the issue further.

[olowk]

When opening an XPS file which is created from a V4 XPS printer driver we can't access the 'FixedDocumentSequenceReader' because it's null. Code below works perfect in full framework but doesn't in .net Core 3.1

 using(var strm = File.OpenRead("path to xps file"))
{
      var package = Package.Open(strm, FileMode.Open, FileAccess.Read);
      var inMemoryPackageName = string.Format("memorystream://{0}.xps", Guid.NewGuid());
      PackageStore.AddPackage(new Uri(inMemoryPackageName), package);
      var xpsDoc = new System.Windows.Xps.Packaging.XpsDocument(package, CompressionOption.Fast, inMemoryPackageName);
      var fixedDocSeqReader = xpsDoc.FixedDocumentSequenceReader;
      var printTicket = fixedDocSeqReader.PrintTicket; //<- nullreferenceexception here because fixeddocumentsequencereader is null
}

[svick]

@olowk I think you should open a new issue about that, instead of commenting on a closed one.

[wstaelens]

@svick it is reopened, as @olowk and I tested the same.

Due to covid we could not respond earlier and the bot closed the issue... 🥱

[GrabYourPitchforks]

Thanks for the repro code! I'll get someone to transfer this to the WPF repo so that the appropriate area owners will get notification of the issue.

[ryalanms]

Thank you for the report, @olowk. Which versions of .NET Core and Windows are you using?

[olowk]

I am using .net core 3.1 and Windows 10 updated to latest version.

[wstaelens]

@GrabYourPitchforks @terrajobst did you ever test this?
We are still having these issues after all these months.

.NET SDK 5.0.202
.NET runtime 5.0.5
Windows 10 20H2 (19042.928)
Windows Server 2019 1809 (17763.1879)