19.4460.0.48 fails during build due to missing dependency

The new 19.4460.0.48 Syncfusion.Pdf.Base causes a build error due to a missing dependency which is impossible to find even with output set to detailed. This only happens during the publish phase. It will build with a simple compile.


5 Replies

GK Gowthamraj Kumar Syncfusion Team February 1, 2022 02:12 PM UTC

Hi Matthew, 

We have created a simple sample to generate a PDF document in ASP NET Web Forms. We have attached the runnable sample with (19.4.0.48) version for your reference, please try the sample on your end and let us know the result.

 

Please refer the below documentation link for more information, 
Please let us know if you need any further assistance with this. 

Regards, 
Gowthamraj K 



MS Matthew Smith February 1, 2022 02:31 PM UTC

I have been using the for over 10+ years, so this is existing and working code. This failed during the publish of the project after a NuGet update to .48. Since version .47, new entries have been added to the web.config file in the assemblyBinding area which means something has changed on your end to have to use this. The settings in the assemblyBinding are not being updated, meaning .47 was not updated to .48 even though I received numerous dialogs regarding updating and saving the web.config file.

In short, I did a NuGet update and did a publish. I got the error message that a dependency was not found within the publish. I was dead in the water.

It appears that your mechanism in the NuGet is not operating properly in removing, adding or updating the components. It took me a couple of hours to try to fix this mess that was not of my own making.

And next time, please read the post. It is clear you did not and were just providing a stock 



KG Kalirajan Ganesan Syncfusion Team February 2, 2022 09:46 AM UTC

Hi Matthew,


We checked the reported problem by upgrading the Syncfusion.Pdf.Aspnet package to the 19.4.0.48 version from 19.4.0.47 and then publishing the application. The version has been updated properly to the assemblybindingredirect section in web.config file and we didn’t face any problems in the publishing phase. If you again face this kind of issues while updating the NuGet package in upcoming version, kindly let us know along with the screenshot of the output window. We will check this issue in your machine.


Thanks,

Kalirajan Ganesan



MS Matthew Smith February 2, 2022 02:05 PM UTC

Kalirajan, thanks for the update.


I just performed a NuGet update on another project. Below is the screen grab before the update:

Screenshot 2022-02-02 085845.jpg

After the update no change. This was being updated 19.4.0.48. The file had been opened because it had been checked out from the Team Explorer.



KG Kalirajan Ganesan Syncfusion Team February 3, 2022 12:32 PM UTC

Hi Mathew Smith,

We can reproduce the reported problem. While downgrading the Syncfusion.Pdf.Aspnet package, its dependency packages were not downgraded, and binding redirection added. After upgrading the Syncfusion.Pdf.Aspnet package, its dependency package has updated but the selected version is not updated in the binding redirection. We'll investigate this issue and get back to you as soon as possible.

Thanks,
Kalirajan Ganesan


Loader.
Up arrow icon