Hi, Pawel -

I've not verified this, but I believe the restriction is that you cannot utilize these functions when running the application from the IDE when the app has been converted to Solution format. Once compiled/deployed, I think these functions will work normally. My guess is that in order for these functions to work, they require access to the intermediate object code that is kept in a PBL (or compiled into PBD/DLL's). Only source code is available in a Solution-based app.

The same restriction is in place for the LibraryDirectory and LibraryDirectoryEx PowerScript functions.

If this is a critical issue for you, you will need to keep your application in a Workspace and continue to use PBL's.

Best regards, John

Hi Pawel;

  I have these functions in my 2022R3 STD Framework version. When converted to PB 2025 workspace & then over to a Solution, they are all working just fine.

  I think that why my code is still working is that it does not reference a PBL (argument variation) just plain class names. That lets the PB runtime locate the class code in its own way vs forcing the specific library processing under your PowerScript control.  HTH 

Regards ... Chris 

Hi, Pawel，

Thank you for your time in trying the PB 2025 beta!
Solution no longer has the concept of pbl, and it does not work when running in PB IDE. Some functions work when compiled into exe and PBD.

Best Regards,
Peter