as we just left February behind and now are in March, any news on how and when this will be delivered?
Original Message:
Sent: Dec 16, 2025 04:34 AM
From: Arun Painuly
Subject: Deprecated features for Windows client / VBScript
Hi Anette-Nicole,
Thank you for following up on the progress of the VBScript alternative development.
We have completed most of the development work on this project, including translating the existing VBScript to Python scripts, completely rewriting a few functionalities, and implementing the necessary generator and C++ runtime changes.
As these changes have been integrated into the Pattern library, our current focus is on determining the best delivery approach to ensure minimal impact on existing Plex deployments.
We anticipate delivering these changes in early next year (January–March). We will provide a more detailed update as we finalize the remaining steps.
Thank you for your support.
Best regards,
Plex2E Team
Broadcom Inc.
Original Message:
Sent: Dec 04, 2025 05:54 AM
From: AnetteNicole Jahn
Subject: Deprecated features for Windows client / VBScript
Hi Arun,
Just the question about your progress on developing the VBScript alternative and whether you could give us an update on whether the schedule you mentioned in your last post here in the community can be met?
Thank you for your reply in advance.
Best regards
Anette-Nicole
Original Message:
Sent: Feb 26, 2025 05:48 AM
From: Arun Painuly
Subject: Deprecated features for Windows client / VBScript
Hi All,
We would like to update the progress on this thread for VBScript alternative, and here it goes.
We have done the POC for VBScript alternative for ActiveX support in C++ variant, explored multiple scripting options as per our need. The one which worked promising is Python Script and validated the same for a couple of ActiveX controls. On top of existing VBScript code translation to Python script, the changes are required in WinC runtime and Plex IDE - for POC purposes we have manually adjusted the generated code.
Considering the POC outcome, Python script is most promising alternative for VBScript in our context.
As of today we don't have ETA to deliver this change. We will keep you posted as we progress on this.
Thank you.
Regards,
Plex 2E Team
Broadcom Inc.
Original Message:
Sent: Feb 21, 2024 12:22 AM
From: Arun Painuly
Subject: Deprecated features for Windows client / VBScript
Hi Santi,
Thank you for bringing up your concern here, and we do understand your concern.
Most of the Plex IDE part (~90%) is based on C/C++ programming languages and the UI interfaces e.g. as you mentioned 'Object Browser', 'Panel Palette' etc. comes from Microsoft MFC classes (no ActiveX controls). So no usage of ActiveX controls within Plex IDE.
As we discussed earlier in this thread, Plex has VBScript footprint to support C++ variant's ActiveX within pattern/class libraries, and custom source code objects created by the users as well. We are fully aware about the VBScript deprecation and exploring the path forward.
We will take corrective actions to address the need, and keep you posted.
Thank you for all your cooperation.
Hope this helps.
Regards,
Plex2E Team.
Broadcom Inc.
Original Message:
Sent: Feb 15, 2024 04:07 AM
From: Santiago Ayala
Subject: Deprecated features for Windows client / VBScript
Hi Arun,
I'm currently analysing which functions we have that would be affected by the removal of VBScript and have encountered another potential problem (at least I think it could be a problem).
I don't know which programming language Plex itself is programmed with (I suppose C or C++), nor do I know if the Plex tool makes use of OCX controls. For example, if Plex itself uses TreeView (COMCTL.TreeCtrl) for its own functionality (ObjectBrowser or VariablePalette or...), Plex will not work even if Microsoft eliminates VBScript.
My fear is probably completely unfounded, but I would be very grateful if you could briefly calm me down by confirming that the Plex tool itself is not affected.
Thank you in advance.
Kind regards,
Santi
Original Message:
Sent: Dec 27, 2023 02:23 AM
From: Arun Painuly
Subject: Deprecated features for Windows client / VBScript
Hi All,
We are aware about the situation of VBScript deprecation news, and understand your concerns.
We didn't hear the exact timeline of complete removal of VBScript, as per the deprecation statement - VBScript will be available as a "Feature on Demand" for next Windows release and then in a later release of Operating System, VBScript will be completely removed.
So ideally, VBScript will be there for a couple of years (3+) from now.
We have raised a question in MSDN forums on this concern, and got the similar response as mentioned above without any definite timeline for complete removal of VBScript.
Plex has VBScript footprint to support C++ variant's ActiveX within pattern/class libraries, and custom source code objects created by the users as well.
We are fully aware about the situation and exploring the path forward. We will take corrective actions to address the need, and keep you posted.
Thank you for all your cooperation.
Regards,
Arun Painuly
Broadcom Inc.
Original Message:
Sent: Nov 02, 2023 06:54 AM
From: Klaus Lichte
Subject: Deprecated features for Windows client / VBScript
Hello everyone,
We have the information that Microsoft VBScript has been classified as "deprecated". Here is the link to this information:
https://learn.microsoft.com/en-us/windows/whats-new/deprecated-features
In addition to the possibility of creating source code as a VB script in Plex in order to integrate ActiveX controls, the tab control in the foundation classes is also done via VB script. As long as VB Script is available as a feature in demand, no problems are expected initially. However, as soon as VB Script is no longer available, our application will no longer be able to run in many places, especially the functions with tab control. Is there already any information or possible solutions for a switch from Broadcom?
Best regards
Klaus