PDFsharp & MigraDoc Foundation

PDFsharp - A .NET library for processing PDF & MigraDoc Foundation - Creating documents on the fly
It is currently Sun Sep 01, 2024 4:17 am

All times are UTC


Forum rules


Please read this before posting on this forum: Forum Rules



Post new topic Reply to topic  [ 7 posts ] 
Author Message
PostPosted: Fri Aug 09, 2024 9:04 am 
Offline

Joined: Fri Aug 09, 2024 8:50 am
Posts: 4
Hi,

I'm trying to update PDFsharp-MigraDoc-gdi from version 1.50.5147 to PDFsharp-MigraDoc-GDI 6.1.1 in a .NET 4.8 environment. The NuGet upgrade works, but the process breaks my bindingRedirect, as seen in the web.config diff.

Could you relax the dependencies?


Attachments:
File comment: Screenshop of web.config upgrade
pdfsharp_upgrade.png
pdfsharp_upgrade.png [ 105.5 KiB | Viewed 5469 times ]
Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 9:12 am 
Offline
PDFsharp Expert
User avatar

Joined: Sat Mar 14, 2015 10:15 am
Posts: 971
Location: CCAA
Hi!
miikaol wrote:
Could you relax the dependencies?
I'm afraid I don't understand.
How could we do that?

You can download the source and remove .NET 6 and .NET 8 from the target framework list and/or replace the versions in the package dependencies.

And if you only have to change the package dependencies, please let us know what changes you made.

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


Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 9:23 am 
Offline

Joined: Fri Aug 09, 2024 8:50 am
Posts: 4
TH-Soft wrote:
Hi!
miikaol wrote:
Could you relax the dependencies?
I'm afraid I don't understand.
How could we do that?

You can download the source and remove .NET 6 and .NET 8 from the target framework list and/or replace the versions in the package dependencies.

And if you only have to change the package dependencies, please let us know what changes you made.


As you see I already have all needed dependencies installed. Upgrade try to downgrade redirects and break the project. PDFSharp should somehow link to new libraries.


Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 9:37 am 
Offline
PDFsharp Expert
User avatar

Joined: Sat Mar 14, 2015 10:15 am
Posts: 971
Location: CCAA
miikaol wrote:
PDFSharp should somehow link to new libraries.
I don't know what to do about it. Where would we make what changes?

Does it work when you keep the old (higher) values in web.config?

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


Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 10:40 am 
Offline

Joined: Fri Aug 09, 2024 8:50 am
Posts: 4
TH-Soft wrote:
miikaol wrote:
PDFSharp should somehow link to new libraries.
I don't know what to do about it. Where would we make what changes?

Does it work when you keep the old (higher) values in web.config?


Found the root problem:

PDFSharp try to replace my project libraries with bundled ones! So could you change PDFSharp nuget to use reference libraries not local ones?


Attachments:
File comment: upgraded libs
pdfsharp_libs.png
pdfsharp_libs.png [ 197.13 KiB | Viewed 5447 times ]
Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 12:04 pm 
Offline
PDFsharp Expert
User avatar

Joined: Sat Mar 14, 2015 10:15 am
Posts: 971
Location: CCAA
PDFsharp 6.1.1 accidentally includes some Microsoft assemblies in the NET472 folder of the NuGet package.
This was fixed for internal builds and PDFsharp 6.2.0 Preview 1 (coming soon) no longer includes Microsoft assemblies in the NuGet package.

If that's the cause of your problems, then they should be resolved with the next release.

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


Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 09, 2024 12:26 pm 
Offline

Joined: Fri Aug 09, 2024 8:50 am
Posts: 4
TH-Soft wrote:
PDFsharp 6.1.1 accidentally includes some Microsoft assemblies in the NET472 folder of the NuGet package.
This was fixed for internal builds and PDFsharp 6.2.0 Preview 1 (coming soon) no longer includes Microsoft assemblies in the NuGet package.

If that's the cause of your problems, then they should be resolved with the next release.


Ok, thanks for the info!


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 82 guests


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

Search for:
Jump to:  
cron
Privacy Policy, Data Protection Declaration, Impressum
Powered by phpBB® Forum Software © phpBB Group