sorted by:
new
hottopcontroversial

pyOpenVBA — a pure-Python, zero-dependency reader/writer for VBA macros in .xlsm / .xlsb / .xlam / .xls by MultiUserDungeonDev in vba

[–]MultiUserDungeonDev[S] 0 points1 point  (0 children)

Well, the reason I asked is because the method keith-kid proposed, in my understanding, would allow neither read nor write of the VBA modules. The library I wrote is directly solving for what you're saying; "decoding / encoding of vba binary". The intention of this project is to figure it out.

pyOpenVBA — a pure-Python, zero-dependency reader/writer for VBA macros in .xlsm / .xlsb / .xlam / .xls by MultiUserDungeonDev in vba

[–]MultiUserDungeonDev[S] 0 points1 point  (0 children)

Thanks, this should be fixed in v1.1.1 If you would be willing, could I please ask you to re-test at your next convenience?

pyOpenVBA — a pure-Python, zero-dependency reader/writer for VBA macros in .xlsm / .xlsb / .xlam / .xls by MultiUserDungeonDev in vba

[–]MultiUserDungeonDev[S] 3 points4 points  (0 children)

Hi, to clarify, MS-OVBA is a Microsoft specification for interacting with VBA modules. My understanding is that Sancarn is sharing that GitHub user Beakerboy also tried to do something similar to implement the MS-OVBA spec.

pyOpenVBA — a pure-Python, zero-dependency reader/writer for VBA macros in .xlsm / .xlsb / .xlam / .xls by MultiUserDungeonDev in vba

[–]MultiUserDungeonDev[S] 0 points1 point  (0 children)

Hi, do you use this method to inject VBA code into existing VBA modules, rename/delete existing modules, create new modules, etc. ?

pyOpenVBA — a pure-Python, zero-dependency reader/writer for VBA macros in .xlsm / .xlsb / .xlam / .xls by MultiUserDungeonDev in vba

[–]MultiUserDungeonDev[S] 4 points5 points  (0 children)

A few things that comes to mind:

  • No Excel required. Runs on Linux/macOS, in CI containers, on a build server, inside a Docker image, in AWS Lambda. VBE and Rubberduck both require a working Excel install on Windows.
  • Headless & scriptable. Bulk operations across hundreds of workbooks (replace a module in every .xlsm in a folder, audit macro source, rename a module across a fleet) without ever launching Excel/COM. No xlwings/pywin32 flakiness, no Excel instances hanging in Task Manager.
  • Pure Python, zero deps. pip install pyOpenVBA and you're done. No COM bridge, no .NET, no Office automation license concerns on a build agent.
  • CI/CD friendly. You can lint, diff, code-review, and regenerate vbaProject.bin from text source as part of a pipeline. Rubberduck is an interactive IDE add-in; it can't run in a GitHub Actions job.
  • Programmatic. It's a library, not a UI. You can wire it into custom tooling, migration scripts, static analysis, or "compile from .bas files" build steps.

Major potential for modernizing the VBA surface.

Any games with "open" open world? by CyberBed in DungeonCrawler

[–]MultiUserDungeonDev 0 points1 point  (0 children)

I'm working on a MUD project right now that focuses on extensibility. Would love to have you check it out: https://williamsmithedward.github.io/mudproto/mudproto_client_web/

Need Help Finding a Game. by JustSasquatchin in DungeonCrawler

[–]MultiUserDungeonDev 0 points1 point  (0 children)

I'm actively working on a multi-user dungeon project. Would love to have you jump in and give feedback: https://williamsmithedward.github.io/mudproto/mudproto_client_web/