Deprecated features for Windows client / VBScript

[Klaus Lichte]

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

[Jeremy Stent]

It does not help much with any vbScript source code you have developed, but we can replace the TabStrip, Calendar, etc. either with C++/C# source code using the MFC classes (CImageList, etc) or we can use COM import to replace them.  Both are rather tedious, but can be done in your standards layer.

[Arun Painuly]

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.

[mariozop]

Hi Arun,

we too have a lot of VBScript to manage ActiveX (Excel, CrystalReport, ecc.) and string/text file operations.

Let us know the implementations in the tool and the suggestions to follow.

Thanks

Mario

[Santiago Ayala]

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

[Arun Painuly]

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.