You can find binaries (assemblies) on NuGet. Make sure to check "Include prerelease" in the NuGet Package Manager.

Note: New on NuGet are the Core, GDI, and WPF packages.The Silverlight package was not yet updated on NuGet.The Silverlight package will most likely be updated - ETA is before the ides of August, 2017.

The source on GitHub was also updated.

The ZIP files with the samples were not updated (yet). There were no changes since 1.50 beta 3b. The NuGet Package Manager will fetch the latest packages.

Please report all regressions versus 1.50 beta 3b.Several bugs have been fixed - and hopefully there are no new bugs.

_________________Best regardsThomas(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

Looks really good. After I'd merged in a load of the font bits from the pdfsharper fork it's working great. and fixes issues I was having with a number of PDFs.

However... there is always a however!

I'm having to fight hard to stop .net throwing out of memory exceptions if I build up a pdf from a series of huge full colour PNGs. Adding pages with one png per page.I have 9 pngs that are A4 (ish) at 600dpi. 5000+pixels by 8000+pixels. So yes when each goes through the bitmap bits I know I'm gonna be using 300MB or so. However it doesn't seem to let it go again, the memory usage goes 300>600>900>1200... Crash after 6 or 7 pages are added. I've tried lots of tweaking in the code, but the only thing I can do to get it to work is to run things in an apartment, save the pdf after each page, close everything, end the apartment thread, start a new one, open the pdf and then add page 2... etc etc. I have builds of this version which will work but it seems I'm performing a hack to get around some 300MB object reference somewhere not being released. You'd think that's be easy to find but .net likes to hide the magic!

1.50 beta 4 - Simplest WPF program instantly crashes but does not in beta3------------------------------------------------------------------------------------------The simplest WPF program creates a valid PDF but crashes after that without throwing an exception.

If the experts could have a look, Many Thanks!(+ Many thanks for sharing the project!)

The problem is caused by calling "_dc.Dispatcher.InvokeShutdown();"This call was introduced to prevent PDFsharp on Azure servers from running out of resources.Unwanted side effect: the WPF desktop application will be closed.See here:viewtopic.php?p=10149#p10149

The call to "_dc.Dispatcher.InvokeShutdown();" will be removed from the next version on NuGet.For use on a server, get the source code package and uncomment that line.

Thanks for the feedback. Sorry for the inconvenience.I have no idea how to help both usage cases with a single NuGet package.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum