PDFsharp & MigraDoc Foundation

Hello,

as I am working in a company, it is always preferred when a stable version is used.

I understand, after reading several other topics, that I'd rather user the latest pre-release version as your team consider it is more stable than the latest stable release available (i.e. 1.32 in NuGet). Would you tell your 'beta' is very close to a 'stable' ?

But still, I am wondering when you are planning to release the next stable version? Seems it appers to me, through this forum, that it was already planned in 2016 but here we are, close to 2018

By the way, I had another question : what are the differences between the GDI, WPF and core packages? I am devising a wpf app and the core happened to do just enough. So why is there a WPF package?

Thanks by advance for your answers.
And thanks a lot for your work on the Migradoc/PdfSharp project, amazing features

Hi!

There was a long time between beta 3 and beta 4.
One of the changes introduced with beta 4 led to problems, so in retrospect it was wise to call it "beta 4" (I was considering calling it "RC 1" or "RTM" (i.e. "stable")).
There were some updates of beta 4 with unpublished changes in the queue.

I don't want to publish several "stable" versions in short time. I'm afraid many folks avoid the beta versions and will only start testing 1.50 when it comes with the "stable" tag - and who knows how many bugs will be discovered then.

The WPF build does not use GDI+.
The Core build should not use GDI+, but still does.
The GDI build uses GDI+ by design.

GDI+ may not be available on some cloud servers.
empira use the WPF build in their applications, so a lot testing is done with that one.
In the beginning there was the GDI build only, so it is very mature.

No ETA for a stable version. Vague idea is it will come when a new beta didn't lead to new bug reports within some time. Also have to find spare time to do it.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

I see, thanks for the quick answer!

So I guess I can go with the latest beta pretty safely, right?
I might be a bit suspicious here but the term beta, depending on the software, is not always trustful.
But listening to you it seems that using it is safe.

Concerning my other question : as I am planning on devising a web app (using ASP.NET) based on my current WPF app, is it ok if I continue using the core package or would you advise otherwise?
(Since this matter doesn't refers to the subject I posted, I would understand if you'd prefer that I open another topic.)

Thanks.

You may have to switch to the WPF build if GDI+ is not available on the server.
I think there won't be compilation errors when switch from Core to WPF (small changes may be required when switching from GDI to WPF).


A beta version that receives bug fixes is better than a frozen "stable" version that didn't get bug fixes in four years.
There is a small risk of regressions with every new version, but you always can go back to a specific version from NuGet or SourceForge.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

Hi,

thanks for your quick and precise answer.

I tried to switch to the WPF build and I got the following error (points to the call of the RenderDoucment() method) :

An exception of type 'System.InvalidOperationException' occurred in PdfSharp-wpf.dll but was not handled in user code
Additional information: Cannot get a matching glyph typeface for font 'Trebuchet'.

I never encountered this error before so I guess it is due to my switch to the WPF build but I don't understand.
(I'm working with Visual Studio Pro 2013, and using the last pre-release version of the library.)

Thanks by advance.

EDIT : My bad, i changed style.Font.Name = "Trebuchet"; to style.Font.Name = "Trebuchet MS"; and it is working again. But still, I'd enjoy a quick explanation (I must admit I'm still pretty new to software development so all explanations are good to take!)

GDI returns a default font if the font you want is not available (outside the PDFsharp code) without telling about the substitution. WPF leads to an error if the font does not exist.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

Great thanks for the explanation.

That was all for me! I might come back in another topic if I encounter any issues while trying to run my app on a server, since I've never done that before

Regards.

Hi

Can you please let me know what is the expected release date of PDFsharp 1.50 ?

Nobody knows.
There will be another beta version that incorporates bug fixes from the past few weeks.

The "stable" tag won't make the version any better.

Please read second post in this thread.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)