As mentioned the web-app is running on an IIS hosted by a Windows 2012 server.
Please comment on this:
“I noticed that moving from local aspose dll to nuget packages fetch quite a few other dependencies/references like SkiaSharp and System.Text.Encoding.CodePages and a lot of what appeared to be .netstandard 2 assemblies.”
Do I need to install .netstandard on the web-server?
Thank you for details. We have further investigated the issue. In case of Aspose.BarCode, we are able to reproduce the issue. The issue has been logged into our system with ID BARCODENET-36898. We will update you here once there is some information or a fix version available in this regard.
OK. Thanks.
I will rollback the move to nuget for the barcode dll. I will let you know how it works out
what whould my "nuget un-install options be?
The aspose.barcode depends on .NETStandard v2.0 and SkiaSharp>=1.6
I also have cells, words, email and pdf installed (via nuget) which also dependens on .NETStandard 2.
Is the error related to aspose.barcode og SkiaSharp?
There are two ways to resolve this issue (as a workaround).
Set exact targetFramework in packages.config. Update the packages XML with the following. It will resolve the issue.
< packages>
< package id=“Aspose.BarCode” version=“18.5.0” targetFramework=“net45” />
< /packages>
You may manually download Aspose.BarCode.nupkg, unzip it and add reference to assembly from folder ~/lib/net45 into your project.
For other APIs, we are working and will update you accordingly.
Hi Ikram, I really appreciate your hep.
In my “packages.config” I changed this:
package id=“Aspose.BarCode” version=“18.5.0” targetFramework=“net461”
To this:
package id=“Aspose.BarCode” version=“18.5.0” targetFramework=“net45”
screen shot: 2018-06-01_11-19-02.png (23.6 KB)
Then I re-build the project and rolled into test. I’m still getting the same error.
Also: What do you mean with “For other APIs, we are working and will update you accordingly.”?
/Morten
This means that we are investigating this issue for other APIs like we need for Aspose.BarCode. A ticket with ID CELLSNET-46154 for investigation of this issue has also been logged regarding Aspose.Cells.
since the issue persists (see my previous post), would you recommend me to remove all aspose nuget packages and revert to locally referenced files?
Yes, please try the second workaround method of manually download and update us with your feedback.
I have removed aspose nuget packages and reverted back to the same locally referenced aspose assemblies.
The problem persists.
As mentioned the aspose barcode nuget package appear to have also pulled down the following packages:
SkiaSharp
System.Text.Encoding.Codepages
.NETStandard 2.0
What to do with these packages?
removed the SkiaSharp package > problem persists
Removed System.Text.Encoding.CodePages v4.4.0 and now problem is gone.
Removing System.Text.Encoding.CodePages v4.4.0 appear to also have removed .NETStandard assemblies (see screen shots):
assemblies-removed-2.png (15.8 KB)
assemblies-removed-3.png (17.4 KB)
assemblies-removed-1.png (66.0 KB)
I noticed there was an update System.Text.Encoding.CodePages v4.5.0.
I didn’t upgrade and test.
Thank you for update. We have noted the comments. We will consider it during investigation.
thanks ikram. one question:
When referencing assemblies with dependencies (i.e. BarCode) using download of nuget package, un-zip and copy to local folder must I then also copy and reference all the other assemblies?
Thank you for writing us back. Un-zip the NuGet package, only copy the desired assembly/DLL to local folder and reference it. There is no need for all other assemblies to be copied and referenced.
why then all the dependencies in the nuget packages?
In case of Aspose.BarCode, NuGet package contains ‘lib’ which further contains sub-folders having DLL in them according to .NET versions. Aspose.BarCode has SkiaSharp dependency only for .NET Standard. For details you may visit the Aspose.BarCode NuGet page dependencies section. For regular .NET Framework for Aspose.BarCode, there is no additional dependency.
Similarly you may check NuGet pages for other Aspose components. Furthermore we had shared in previous post that for .NET 4.6 applications, get assemblies from folder /lib/netstandard2.0, instead of /lib/net45 for now. This issue will be fixed in the upcoming release of Aspose.BarCode.
The issue (BARCODENET-36898) has been fixed. Please get the latest version of API i.e. Aspose.BarCode for .NET 18.6 and try it at your end.
We have investigated the issue w.r.t Aspose.Slides and have failed to reproduce this using latest Aspose.Slides for .NET 18.9. Can you please confirm if the issue is still incurring on your end. In case there is still an issue then we need an example project that reproduces error.
This is to inform you that we have fixed your issue (logged earlier as “CELLSNET-46154”) now. We will soon provide you the fixed version after performing QA and incorporating other enhancements and fixes.