-
Michael Kaczmarczyk
- PowerBuilder
- Monday, 29 June 2026 02:21 PM UTC
Hey,
we recently upgraded our application from PB2022 to PB2025 R1 and then to R2.
And we have some .net libraries developed, that we are using in our PB2025 application.
One of this libraries ( a component for excel ) is having a related/linked library, which uses the System.IO.packaging.dll.
While the original version of this in .net10 has a file size of 156KB and ist signed by MS, the file from the PB runtime is having 316KB and is signed by Appeon.

Both files have in the details section the exact same version listed.

We now face the issue in 64bit:
- if we use our (original .net) dll (so change the one from PB) the application we have developed if crashing with an error like 'a window can't be opened'
- if we use the dll from the pb runtime, and load the dll, which is done in the beginning, the program is marked as being a virus by our symantek virus scanner
In 32 bit, the crash does not happen, though we haven't tested whether all functions work correctly in our excel-extension. There we used the System.IO.packaging.dll from the PB runtime.
For the time being we have deactivated the usage of our 64bit excel extension, so that we don't run in an exception, but I wonder why a standard .net library is changed here and so vastly!
In mind I have a workaround for this, like our .net dlls being in a subfolder, but nevertheless I want to know why :D
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.