One of our customers report some performance issues at loading time with our web site (using .net framework 3.5 and ASPOSE TOTAL .Net)
And we found that it was due to authenticode signing in Aspose assemblies (and the fact there were no internet connection on the server). Eventually, we workaround this with the "generatePublisherEvidence" parameter in aspnet.config, as already mention in this thread.
But, I noticed that you provide 1 of your assemblies without authenticode signing : Aspose.Words.dll. All the rest is signed with authenticode.
Is it possible to provide a version without authenticode signing for all of you assemblies ? Now and in the future ?