General suggestion

Aspose.Total Product Family
, , ,
1

Hello, many aspose products have a .net 4.0/4.5 dll but not a .net 4.8 dll.

To get started, even with the same source code it’s vital to have a .net 4.8 dll build, and has many benefits, specially for email, imaging and zip, can be useful for words/cells too.

In .net 4.0/4.5 many ssl/tls operations will fail by default unless you set the not recommended security protocols, and still not as stable as .net 4.8 compiled assembly.

There are some bugs in xml parsers in .net 4.0/4.5 compiled assemblies, updating to .net 4.6+ will immediately fix them, and 4.7.2+ up to 4.8 will bring many improvements!

The same for IO.Compression, I did have some files which .net 4.5 code could not extract, the same code upgraded to .net 4.6 fixed the issue!

Some improvements gained when building a .net 4.8 dll:

  • Hardened cryptography (CNG, RNG, hashing)
  • Better certificate validation
  • Safer XML, WCF, and serialization behaviors

Even legacy code runs more securely.

Same IL, but a much better runtime engine.

  • Faster JIT compilation

  • Improved garbage collection (server & workstation GC)

  • Better memory management

  • Reduced lock contention

  • More efficient threading and async infrastructure

  • Thousands of bug fixes since 4.0/4.5

  • More predictable exception handling

  • Fewer runtime issues

  • Improved thread pool stability

This alone is often enough justification for an upgrade.

For Aspose email, zip, imaging that don’t have a dll higher than 4.0/4.5 this is serious! Even with the same source…

Specially when working with x509certificates, some explicit disposal were added after 4.5/4.6 and a 4.8 build improves a lot.

Thanks.

2

@australian.dev.nerds

You are suggesting that Aspose products should target .NET Framework 4.8 instead of 4.0/4.5, citing benefits like improved security, TLS support, XML parsing, and runtime performance . You’ve also noted that some Aspose products, like Aspose.PDF, have recently returned to supporting .NET Framework 4.8 .

Aspose is aware of the demand for updated framework support. For example, Aspose.PDF now supports .NET Framework 4.8 again, addressing compatibility with older Windows versions . We recommend checking the official documentation or release notes for the latest updates on .NET Framework compatibility for your specific Aspose product. A support engineer will follow up in this thread if needed.

3

Nope, not to replace but to have an extra 4.8 build :blush:

4

@australian.dev.nerds

You are suggesting that Aspose products should offer an additional .NET Framework 4.8 build, alongside existing 4.0/4.5 builds, to take advantage of improved security, TLS support, XML parsing, and runtime performance . Aspose is aware of the demand for updated .NET Framework support, and some products like Aspose.PDF have returned to supporting .NET Framework 4.8, addressing compatibility with older Windows versions [2, 3].

Aspose is aware of the demand for updated .NET Framework support, and some products like Aspose.PDF have returned to supporting .NET Framework 4.8, addressing compatibility with older Windows versions [2, 3]. A user has suggested that Aspose products should offer an additional .NET Framework 4.8 build to benefit from improved security, TLS support, XML parsing, and runtime performance . This would allow better compatibility with modern security standards and runtime improvements, especially for applications dealing with certificates, encryption, and file I/O .

While Aspose.PDF now supports .NET Framework 4.8 again starting with version 25.6.0 , it’s unclear whether other Aspose products will follow suit. You may want to check the official documentation or release notes for the latest updates on .NET Framework compatibility for your specific Aspose product. A support engineer will follow up in this thread if needed.

5

Thanks, just to note that it will take zero time, for initial release, just upgrading a copy of project to 4.8 and compiling is enough! Even if they donot have time for new version tweaks/improvements, the same source compiled as 4.8 will instantly get all the improvements and fixes!

6

@australian.dev.nerds
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-29016

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

1 Like
7

@australian.dev.nerds,

Thank you for your suggestion.

It seems this addition could significantly enhance compatibility and support for you as you rely on this framework version as well. For Aspose.Cells, we will evaluate the feasibility of incorporating a .NET 4.8 (DLL) build into the release archive. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-59756

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

1 Like
8

@australian.dev.nerds

From 25.10, Aspose.Cells provides specific version for .NET4.6.1. Would you please try the one in our latest version Downloads —New Releases-aspose.cells-for-.net-26.1 to check whether it can fit your requirement?

1 Like
9

Thanks, actually the highest prioprity belongs to Imaging and Email since their highest build is the highly unsafe and insecure .net 4.0 / 4.5, indeed anything below 4.6.2…

Important note is that if you upgrade a .net 4.5 project to .net 4.8 even with the same source, since it does not use newer apis than the ones in .net 4.5, users of .net 4.5~4.8 can use it in their projects!

But what is gained instantly I mentioned above! So this is a very basic .net thing…

It’s not my requirement at all; I just wanted to draw your attention to this issue :smiley:

10

@australian.dev.nerds,

Thank you for your feedback. We will thoroughly evaluate the feasibility of including the .NET 4.8 (DLL) build for Aspose.Cells, as we have already logged a ticket for this issue (“CELLSNET-59756”). Once we have an update, we will inform you here.

We apologize that the respective teams have not evaluated it yet. Rest assured, our members from the Aspose.Imaging and Aspose.Email teams will get back to you soon.

11

Hello,

We’ll consider your suggestion for Aspose.Email, thank you.

12

@australian.dev.nerds
NetFramework is considered a legacy platform, replaced by the .Net platform, which is actively developed by Microsoft. Microsoft recommends migrating to the modern .Net platform.
Therefore, we stopped supporting the stagnant .NetFramework at version 4.0.
We(Aspose.Imaging) now support the more modern cross-platform versions .Net 6.0 and Net 8.0.

Key advantages of .NET 6.0 and .NET 8.0

Long-term support (LTS)
Both .NET 6.0 and .NET 8.0 are Long-Term Support releases, providing predictable update cycles, security patches, and long-term stability for production systems.

Significantly improved performance
Modern .NET versions offer major runtime, JIT, and garbage collector optimizations, resulting in faster execution, lower memory usage, and better scalability compared to .NET Framework.

Cross-platform support
Applications can run natively on Windows, Linux, and macOS, enabling flexible deployment scenarios including cloud, containers, and on-premise environments.

Active development and security updates
The modern .NET platform is actively developed by Microsoft, with continuous improvements, new features, and regular security fixes.

Modern language and runtime features
Support for the latest C# language features, improved async/await performance, enhanced diagnostics, and modern APIs not available in .NET Framework.

Cloud-native and container-friendly
Designed with cloud workloads in mind, .NET 6.0 and 8.0 provide first-class support for Docker, Kubernetes, microservices, and scalable web APIs.

Unified development platform
A single platform for building web APIs, background services, desktop applications, and cloud services, reducing complexity and maintenance costs.

Better tooling and developer experience
Improved SDK-style projects, faster builds, Hot Reload, modern CLI tooling, and enhanced debugging and profiling support.

Based on the above, I would also recommend that you migrate to .Net 8.0.

1 Like
13

Thanks for the info,
While modern .NET is the future, calling it a direct upgrade for every scenario is misleading. For many Windows specific applications, moving from .NET Framework to .NET is more of a migration or a rebuild, and it comes with real tradeoffs. So, remove your .Net Framework builds to lose half of your users immediately :smiley:

.NET Framework 4.8 is finished but stable and supported as long as Windows is, the suggestion was just to have a latest .Net Framework build though :slight_smile:

14

@australian.dev.nerds Thank you for your advice.
We’re not eliminating support for NetFramework, but we’ve stopped development at version 4.0 in favor of more modern technologies.

Furthermore, you can easily connect this build to a project using .NetFramework 4.8. and your app will use CLR 4.8
I’d like to point out that we also support .NetStandard 2.0, which is more modern than .NetFramework 4.0 and works with NetFramework 4.8.

1 Like
15

Thanks, perhaps I was not able to describe it well, or you didn’t get my point :slight_smile: