Why it's time to migrate from SeleniumBasic to SeleniumVBA

[hanamichi77777]

As Microsoft recently announced, .NET Framework 3.5 (which SeleniumBasic relies on) is moving to a standalone deployment model starting with Windows 11 Insider Preview Build 27965. It will no longer be included as an optional component in future Windows versions. This change, combined with the fact that SeleniumBasic is no longer maintained, makes migration a priority for stable automation.
https://devblogs.microsoft.com/dotnet/dotnet-framework-3-5-moves-to-standalone-deployment-in-new-versions-of-windows/
In my opinion, switching to SeleniumVBA is the optimal path forward. What are your thoughts?

Why SeleniumVBA?
SeleniumVBA is a modern, pure-VBA alternative that offers several critical advantages:

Zero Dependencies: It does not require .NET Framework 3.5 or any external installers. It consists of pure VBA class modules you can simply import into your project.

High Code Affinity & Low Migration Cost: The syntax and object model are designed to be highly compatible with SeleniumBasic. You can migrate your existing scripts with minimal effort—often just by updating object declarations and a few method names.

Portability: Since there is no registry registration required, you can deploy your Excel tools to other users without needing administrative rights for installation.

Active Maintenance: It is compatible with the latest versions of Chrome and Edge and is frequently updated to handle modern web driver requirements.

[dornech]

I wonder if I mentioned before but I migrated I think in autumn 2024. I can confirm it is pretty straight forward and easy.

[dornech]

BTW: I took the liberty to recommend SeleniumVBA to the SeleniumBasic community in October 2024. For the reasons mentioned above.
florentbr/SeleniumBasic#288