.NET 6 is released now. I cannot use Aspose PDF anymore, the “SetLicense()” method throws “Exception of type ‘System.Exception’ was thrown”. It works fine with .NET 5. Could you please release a bugfix urgently?
Attached is a simple solution with two projects that are exactly the same, but one is for .NET 5, the second one is for .NET 6. Just put a correct license file named “Aspose.Total.NET.lic” in the output directory and run. .NET 5 version works fine, .NET 6 version throws an exception.
Same problem here. .Net 6 is released and we can not upgrade because SetLicense doesn’t work in Aspose.PDF 21.2.0.0 or 21.11.0 (latest)…but it works in Aspose.Words however!
System.Exception
HResult=0x80131500
Message=Exception_WasThrown
Source=Aspose.PDF
StackTrace:
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=z4xDo39F9MdcGEm2wZYiF18a63TKRox9SPw==(Object #=zXu3sMwY=)
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=zvrbWkL8JkJ125VSOQHEEUIFQ_sEpILZ2yAqT2T8=()
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=z0KicvzDdXSMCQk00xw0yuIiP3vup1z6h0Io10CuZdbEL(Object #=zXu3sMwY=, UInt32 #=zmrllAUM=)
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=zTut2MhEvThnrairR$DqretA_oPYFbx5xyQghPjw=(Boolean #=zXu3sMwY=)
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=z2AD4woqtYDAch5HflGqcDThFjMyzr77Yfw==(Object[] #=zXu3sMwY=, Type[] #=zmrllAUM=, Type[] #=z9uLQscI=, Object[] #=zh6LUchc=)
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=zLKn_kJ8HhmpAHkw37y7EZ_mQASqZcn51Ag==(Stream #=zXu3sMwY=, String #=zmrllAUM=, Object[] #=z9uLQscI=)
at #=qxAsi07iSgr$IoHvuXjuqyXspkpaf$LkIaBoLjQxdm0k=.#=zXJkEJnx6nfALRFdrX0$KhrUbrSrscmp42Q==(Stream #=zXu3sMwY=, String #=zmrllAUM=, Object[] #=z9uLQscI=)
at Aspose.Pdf.License.SetLicense(Stream stream)
at Agile360.Logic.WordTemplates.Agile360WordLogic.Start(SchemaBuilder sb) in C:\Code\Agile360\Agile360.Logic\WordTemplates\Agile360WordLogic.cs:line 18
This really is unacceptable. You guys have had months to deal with this. The libraries are supposed to be .NET Standard compatible. The only reason they could be failing like this is if you were using reflection stupidly or something with the obfuscation (my guess).
It’s bad enough that the 20.0 series does this but now if I want a fix I have to re-up my license. Why should I when even the new releases have problems like this?
Very disappointing and the latest in a long line of bugs that we’ve seen in this very expensive platform.
PS - to all, the way I deal with most Aspose bugs is gonna be the way I deal with this one. Keep all your Aspose use in a separate command line process or windows service and invoke it as needed. Then you can use .net framework for that process and .net6 for your actual app.
This ETA for this issue is Aspose.PDF for .NET 21.11 which will be released soon. We request for your patience and will share the good news with you as soon as the issue will be fixed.
The release is under review phase at the moment and we plan to upload it during this week. Yes, you can say that it will probably be available by tomorrow.
System.Exception
Exception of type 'System.Exception' was thrown.
at .(Byte[] )
at ..( )
at .(String )
at .(String )
at ..(String )
at ..()
at .(Object , ResolveEventArgs )
at System.Runtime.Loader.AssemblyLoadContext.InvokeResolveEvent(ResolveEventHandler eventHandler, RuntimeAssembly assembly, String name)
at System.Runtime.Loader.AssemblyLoadContext.OnResourceResolve(RuntimeAssembly assembly, String resourceName)
at System.Reflection.RuntimeAssembly.GetResource(QCallAssembly assembly, String resourceName, UInt32& length)
at System.Reflection.RuntimeAssembly.GetManifestResourceStream(String name)
at .(Object )
at .(Object )
at .(MethodBase , Boolean )
at .()
at .()
at .(Object )
at .(Object )
at . ()
at .()
at .()
at .()
at .(Object )
at .(Object )
at . ()
at .()
at .(Object[] , Type[] , Type[] , Object[] )
at .(Int32 , Type[] , Type[] , Boolean )
at . ( )
at .()
at .()
at .(Object )
at .(Object )
at . ()
at .()
at .()
at .()
at .(Object )
at .(Object )
at . ()
at .()
at .(Object[] , Type[] , Type[] , Object[] )
at .(Stream , String , Object[] , Type[] , Type[] , Object[] )
at .(Stream , String , Object[] )
at .(Stream , String , Object[] )
at Aspose.Html.License.SetLicense(Stream stream)
We have already noticed this issue in Aspose.HTML as well as in Aspose.Page. The following tickets have already been logged in our issue tracking system for resolution:
PAGENET-309
HTMLNET-3386
Above both tickets are under the phase of investigation at the moment. PAGENET-309 is expected to be fixed in 21.11 version of the API which will be released soon. We will further keep you posted on the status of tickets resolution. Please spare us some time.
A ticket as FONTNET-288 has also been already logged in our issue tracking system in order to resolve the issue in Aspose.Font related to the license settings. We have linked it as well with this forum thread and will inform you as soon as it is resolved. Please spare us some time.
The issue related to Aspose.HTML for .NET has been resolved and its fix will be included in the upcoming release i.e. 21.12. We will let you know as soon as the fix is published.
The issues you have found earlier (filed as HTMLNET-3386) have been fixed in this update. This message was posted using Bugs notification tool by pavel.petrushechkin
