A running list of cleanup, modernization, and improvement items for the VisioAutomation solution. Items are grouped by theme into separate files (linked below). Each entry includes a one-line What, a Why (cost of leaving it), and a rough Effort (S / M / L). This is a backlog — items are not committed to or scheduled until pulled out into actual work.
Forward-looking only. Done items live in
COMPLETED.md. The phase-level "what shipped" headlines live inROADMAP.md. When an item lands, the body moves toCOMPLETED.mdand is removed from itsfutures/*.mdfile. SeeCONTRIBUTING.mdfor the convention.
ROADMAP.md— staged-plan overview (Phase 1 / 2 / 3 status, what shipped per phase, what's still pending). Read this first for orientation.MILESTONES.md— planning by semester (CY26Q2, CY26Q3, ...). Sits between this backlog index andROADMAP.md: items scheduled to a quarter, with themed-milestone tags (A, B, C, ...) for the what kind of work axis. GitHub issues for each scheduled item live under the matching GitHub milestone.futures/build-and-code.md— Build & tooling, Code & architecture. Items: Consolidate target frameworks, Run tests in CI, Move development to Visual Studio 2026, Consider migrating off Visio 2010 PIA, Move to C# 14 / .NET 10, MakeCustomPropertyCellsvalues not require manualEncodeValues(), Borrow ideas from VisioBot3000 for VisioPS ergonomics, Borrow ideas from PSVA for VisioPS bulk-operation cmdlets, Evaluate NetOffice / NetOfficeFw as a replacement for the Visio PIA, MoveLinqExtensionsout ofInternal/.futures/tests.md— Test-related items. Items: Tests require a live Visio (design decision), Test coverage gaps (audit output infutures/test-coverage-gaps.md), Evaluate modern testing-stack options.futures/releases.md— Release process and version policy. Items: Reconcile version numbers across artifacts, Switch module-release builds from Debug to Release, AddressVisio.psd1deprecation warnings on PSGallery publish, Automate releases via GitHub CI.futures/docs.md— Documentation items, in-repo and user-facing gitbook. Items: Decide where docs live long-term, Restructure the user-docs repos, Keep CHANGELOGs current, Add a troubleshooting page to the .NET gitbook, Revise user-facing documentation for accuracy. (Decide whether to documentVisioScriptingas a public API resolved 2026-05-09 (#156) and documented (#131); seeCOMPLETED.md.)futures/identity.md— Dev team identity. Items: Transition dev team identity from to user "SevenPens" (9 axes total; axes 1, 2, 3, 4, 6, 7, 8 done as of 2026-05-07. Axis 5 (hosting URLs) tracked in #146 + #147, scheduledCY26Q4milestone. Axis 9 (retire unused VisioAutomation legacy account) tracked in #148, unscheduled).