I am geting the following error when I go to set the license fo r Aspose.Pdf .Net 4 in my .Net 4 application. I am also usingAspose.Words 2.0 which is working fine. code and such below...
at ..(Int32 ) at (Int32 ) at Aspose.Pdf.License.SetLicense(String licenseName) at symB.SymB..ctor() in C:\SoftAwareServices\SymB.Print2010\SymB.cs:line 101 at symB.Program.Main() in C:\SoftAwareServices\SymB.Print2010\Program.cs:line 15 at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args) at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
I am geting the following error when I go to set the license fo r Aspose.Pdf .Net 4 in my .Net 4 application. I am also usingAspose.Words 2.0 which is working fine. code and such below...
File is Aspose.Pdf.dll ver 4.9.0.0 out of the .ntet4 subdir
at ..(Int32 ) at (Int32 ) at Aspose.Pdf.License.SetLicense(String licenseName) at symB.SymB..ctor() in C:\SoftAwareServices\SymB.Print2010\SymB.cs:line 101 at symB.Program.Main() in C:\SoftAwareServices\SymB.Print2010\Program.cs:line 15 at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args) at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
I have tested the scenario using Aspose.Pdf for .NET 4.9.0 (net4.0_ClientProfile\Aspose.Pdf.dll) over Windows 2008 R2 Enterprise and I am unable to notice any problem. Can you please share the license file that you are using so that we can test the scenario once again at our end. We apologize for your inconvenience.
I have tested the scenario and I am able to notice the problem that Aspose.Pdf for .NET 4.9.0 is cauisng problem when using your provided license file inside an application developed over .NET Framework 4.0. For the sake of correction, I have logged this problem as PDFNET-23910 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction.
We apologize for your inconvenience.
PS, The license file is working properly with .NET Framework 2.0 application.
We have made some progress towards its resolution of this problem and we expect to get it resolved shortly. Please be patient and spare us little time. We apologize for the delay and inconvenience.
We have been able to figure out the actual cause of this problem and hopefully its resolution will be included in upcoming release version. Please be patient and spare us little time. As soon as the solution becomes available, we would be pleased to update you with the status of correction. We are really sorry for this inconvenience.
We have observed that .NET Framework 4.0 ClientProfile works with latest release version but .NET Framework 4.0 is causing some issues. We are working hard to get this issue resolved. Our humble request is to please be patient and spare us little time. We will try our level best to share the HotFix ASAP. We are really sorry for your inconvenience.
OK guys it’s been a month now, any news on this fix? You do realize this makes your toolkit completely unusable for any .NET 4.0 application? If this has already been fixed in a newer release disregard with my thanks.
Shortly we are about to release a new version of Aspose.Pdf for .NET and we plan to include the hotfix for this problem in this release. I would again make a humble request to be a bit more patient and spare us little time. We are really sorry for this inconvenience.
I wish I could have visited this forum more often. Anyway, I am getting the same error right after I deployed it to production (without testing it first on staging, my bad).
My latest aspose.Total download was a day ago with my new Dev OEM order, of version 5.0.
The new release version is still under testing phase and I am afraid currently I am not entirely certain about the timelines when it will be published. This new version will be Aspose.Pdf for .NET 5.1.0 whereas the current latest version available is 5.0.0.
As soon as this new version becomes available, we would be pleased to update you within this forum thread. We are sorry for this delay and inconvenience.
Please provide us an update on this license issue. I am sure some of us can wait for the fix, but I may be the only one who will lose an $300K project if I cannot deploy it within this week (until 3/10). Please advised that I have used your products for a couple of years and very happy with previous releases; however, just spent over $5999 for a new version I cannot use is a bit worry some.
I am deploying to Server 2008 R2 64-bit. If you do have a hotfix, please let me test it for you.