-
Michael Kaczmarczyk
- PowerBuilder
- Wednesday, 14 January 2026 01:18 PM UTC
Hi everyone,
I have a question regarding the general support of Powerbuilder when it comes to the .net assembly classes and their corresponding runtimes.
Our product relies more and more on .net assemblies, which are extending the functionality of our code and product. We have to do this as we need functionality that is not availabe in Powerbuilder or very hard to develop there.
Our customers have now the question, about how we handle the .net lifecycle, when it comes to new releases of .net as well as the EOL, which is more important. An example would be the EOL of .net8 by Nov this year.
My assumption is, that PB2025R3, which will be around some time next year might cope with .net10, but this will be too late by means of EOL of .net8. ( https://community.appeon.com/qna/q-a/powerbuilder-support-for-net-10-assemblies )
This question arises as their IT security wants to enforce a policy that 'no EOL-software' is used on their systems.
Would it be possible to have e.g. a .net10 runtime installed and by some means .net8 dlls used within our PB-code? So that the runtime would be up to date and the libraries that have been written in .net8 are working within the product?
Appeon knowledgebase ( shows a possible way for the IDE )
Kind regards,
Michael
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.