30 — AutoCAD Evolution Analysis: Version-by-Version Impact on ConstructiVision

Note

This document maps every major AutoCAD release from R14 (1997) through AutoCAD 2026 against ConstructiVision’s codebase, identifying exactly what changed, what breaks, what needs adaptation, and in what order to address it. This is the master roadmap for modernization sequencing.

Executive Summary

ConstructiVision was built for AutoCAD 2000 (R15.0) — a platform released in 1999. Since then, Autodesk has shipped 25+ major releases with six architectural breaking points that directly affect CV:

#

Version

Year

Breaking Change

CV Impact

1

2004

2003

.NET API, DWG format change

Low — AutoLISP unaffected

2

2006

2005

CUI replaces MNU

Menu system must support both

3

2010

2009

Ribbon UI, first 64-bit

UI modernization, architecture shift

4

2013

2012

App Store + .bundle format

New distribution channel

5

2021

2020

32-bit dropped, VS Code debugger

Must recompile VLX for 64-bit

6

2025+

2024+

Cloud/AI features, subscription-only

Licensing model, not code changes

The good news: AutoLISP itself has remained remarkably stable. The core language, DCL dialogs, and VLX compilation have barely changed in 25 years. The adaptations are almost entirely about packaging, menus, and architecture — not rewriting application logic.

Baseline: Where We Are

Current Target: AutoCAD 2000 (R15.0), 32-bit, Windows XP through Windows 10 x32

Current Stack:

  • Menu system: .mnu / .mns (pre-CUI)

  • Loading: .vlx via Startup Suite + csvmenu.lsp

  • Dialogs: .dcl (Dialog Control Language)

  • Extensions: pcms.arx (cost module, 32-bit only)

  • Distribution: Legacy InstallShield installer (~2003 era)

What works today:

  • ✅ AutoCAD 2000 on Win10 x32 — fully validated

  • ✅ AutoCAD 2000 on Win10 x64 — works after COM registry fix (Wow6432Node)

  • ✅ VLX loads and runs without recompilation on 32-bit platforms

  • ❌ No modern AutoCAD support (2010+)

  • ❌ No 64-bit native VLX

  • ❌ No App Store presence

  • ❌ No .bundle packaging

Version-by-Version Analysis

AutoCAD R14 (1997) — The ARX Era

Internal Version: R14.0 Architecture: 32-bit only

Key Features:

  • ObjectARX (AutoCAD Runtime Extension) — C++ API for plugins

  • Visual LISP introduced as a separate add-on (not built into AutoCAD)

  • First version to support compiled .vlx format (via separate VLISP product)

CV Relevance: R14 is the birth era of the ARX/VLISP approach that CV uses. The pcms.arx cost module was likely first built for this platform. CV does not officially target R14.

Adaptation Required: None — R14 is legacy/historical only.

AutoCAD 2000 (1999) — CV’s Home Base {#acad-2000}

Internal Version: R15.0 Architecture: 32-bit only DWG Format: 2000 (also used by 2000i, 2002)

Key Features:

  • Visual LISP IDE built into AutoCAD — no longer a separate product

  • VLX compilation integrated (File → Make Application)

  • Separate namespace support for VLX applications

  • ActiveX/COM automation from AutoLISP (vlax-* functions)

  • MDE (Multiple Design Environment) — multiple drawings open simultaneously

  • .mnu / .mns / .mnc / .mnr menu system

  • Startup Suite for automatic application loading

CV Relevance: This is ConstructiVision v11’s target platform. Every design decision — menu structure, VLX compilation, COM automation, DCL dialogs, the progcont dispatch architecture — was built for R15.0.

What CV Uses from 2000:

Feature

CV Usage

Visual LISP IDE

VLX compilation (.lsp → .fas → .vlx)

vlax-* COM functions

Spreadsheet export, system integration

Startup Suite

csvmenu.lsp + csv.vlx auto-load

.mnu menus

csv.mnu with MENUGROUP=CSV

DCL dialogs

44 .dcl files for all user interfaces

Separate namespace

VLX runs in isolated namespace

(command) function

Drives AutoCAD drafting commands

System variables

~50 sysvars set by c:csv startup

Adaptation Required: None — this IS the baseline.

AutoCAD 2002 (2001)

Internal Version: R15.06 Architecture: 32-bit only DWG Format: 2000 (unchanged)

Key Features:

  • Incremental update to 2000

  • dbConnect improvements

  • Attribute extraction enhancements

  • No API changes affecting AutoLISP

CV Relevance: Fully compatible with 2000. No adaptations needed.

AutoCAD 2004 (2003) — First DWG Format Change {#acad-2004}

Internal Version: R16.0 Architecture: 32-bit only DWG Format: 2004 (NEW — first format change since 2000)

Key Features:

  • New DWG file format (2004 format, used through 2006)

  • Tool Palettes window

  • Sheet Set Manager (2005, R16.1)

  • .NET API introduced (2004) — first managed code support

  • Enhanced MTEXT editor

  • Password protection for DWG files

CV Impact:

Change

Impact

Severity

DWG 2004 format

CV drawings saved in 2000 format open fine; 2004-format drawings work with CV

None

.NET API

Not used by CV (pure AutoLISP)

None

Tool Palettes

CV uses DCL, not tool palettes

None

Adaptation Required: None for AutoLISP code. Drawings saved in 2004 format will not open in AutoCAD 2000 — but this is a user workflow issue, not a CV code issue.

AutoCAD 2006 (2005) — CUI Replaces MNU ⚠️ {#acad-2006}

Internal Version: R16.2 Architecture: 32-bit only DWG Format: 2004 (unchanged)

Key Features:

  • CUI (Customize User Interface) replaces MNU/MNS/MNC system

  • Dynamic Blocks (parametric block insertion)

  • DWS (Drawing Standards) enforcement

  • XREF relative paths

  • Hatch enhancements

CV Impact — CRITICAL:

Warning

This is the first major breaking change for ConstructiVision. The .mnu menu format that CV relies on was deprecated in favor of .cui (later .cuix). AutoCAD 2006+ can still import .mnu files but no longer uses them natively.

Change

Impact

Severity

CUI replaces MNU

csv.mnu must be imported into CUI format

HIGH

MNU import still works

AutoCAD 2006-2009 can import .mnu → .cui

Medium

Menu loading changes

(menucmd) and (menuload) behavior changes

Medium

Dynamic Blocks

Opportunity: CV block library could use parametric blocks

Low (future)

What CV Already Has:

  • csv.cui exists (38 MenuMacro elements, XML format, MajorVersion 16)

  • The CUI file mirrors the .mnu content — same 38 menu items

  • Both files reference the same progcont dispatch pattern

What Needs to Happen:

  1. Detect AutoCAD version at startup — branch menu loading logic in csvmenu.lsp

  2. Pre-2006: Load csv.mnu via (menuload) (current behavior)

  3. 2006+: Load csv.cui via (command "CUILOAD" ...) or registry-based auto-load

  4. Test menu loading on both paths to confirm all 38 items work

Effort Estimate: 1-2 days — the CUI file already exists; this is primarily a loader change.

Detection Method:

;; AutoCAD version detection
(setq acver (atoi (getvar "ACADVER")))
;; R15 = 2000, R16 = 2004/5/6, R17 = 2007/8/9, R18 = 2010/11/12

(if (>= acver 16)
  ;; Use CUI loading
  (command "CUILOAD" "csv.cui")
  ;; Use MNU loading (legacy)
  (menuload "csv")
)

AutoCAD 2007 (2006) — 3D Overhaul

Internal Version: R17.0 Architecture: 32-bit only DWG Format: 2007 (NEW)

Key Features:

  • Complete 3D modeling overhaul (conceptual/realistic visual styles)

  • New DWG format (2007, used through 2009)

  • Dashboard (precursor to Ribbon)

  • Multileader objects

CV Impact: Low. CV is a 2D panel-layout tool — 3D changes are irrelevant. DWG format change affects file interchange only.

Adaptation Required: None for code. Users saving in 2007 format need to “Save As” 2000 format for backward compatibility.

AutoCAD 2009 (2008) — Quick Access Toolbar Preview

Internal Version: R17.2 Architecture: 32-bit only DWG Format: 2007 (unchanged)

Key Features:

  • Action Recorder (macro recording)

  • Menu Browser (precursor to Application Menu)

  • Quick Access Toolbar (QAT) — early version

  • Quick View Drawings/Layouts

  • ViewCube and SteeringWheels

  • Last version before the Ribbon UI revolution

CV Impact: Minimal. The QAT and Menu Browser are additions, not replacements — traditional pull-down menus still work in their classic form.

Adaptation Required: None — but this is the last comfortable version for CV’s traditional menu approach.

AutoCAD 2010 (2009) — Ribbon UI + First 64-bit ⚠️ {#acad-2010}

Internal Version: R18.0 Architecture: 32-bit AND 64-bit (first dual-architecture release) DWG Format: 2010 (NEW)

Key Features:

  • Ribbon UI replaces pull-down menus as default interface

  • Parametric constraints (geometric + dimensional)

  • Mesh modeling

  • PDF output/underlay improvements

  • First native 64-bit AutoCAD build

  • New DWG format (2010, used through 2012)

  • .cuix format replaces .cui (binary XML)

CV Impact — SIGNIFICANT:

Warning

This is the second major breaking change. The Ribbon UI fundamentally changes how users interact with AutoCAD. Traditional pull-down menus are no longer the primary interface. They still exist but are hidden by default — users must manually enable the “Menu Bar” system variable.

Change

Impact

Severity

Ribbon as default UI

CV menus hidden; users must enable menu bar

HIGH (UX)

64-bit architecture

CV VLX (32-bit) won’t load in 64-bit AutoCAD

HIGH

.cuix replaces .cui

Another menu format migration

Medium

Parametric constraints

No CV impact (2D feature, but CV doesn’t use it)

None

PDF improvements

Could replace CV’s current print approach

Low (future)

The 64-bit Problem:

  • AutoCAD 2010 ships both 32-bit and 64-bit installers

  • A VLX compiled in 32-bit VLISP cannot load in 64-bit AutoCAD

  • The pcms.arx module is 32-bit only — needs 64-bit version

  • Users installing 64-bit AutoCAD cannot use CV at all

The Ribbon Problem:

  • Pull-down menus still work but must be enabled: (setvar "MENUBAR" 1)

  • Better approach: Create a Ribbon tab for ConstructiVision

  • Ribbon tabs are defined in .cuix files (binary CUI XML)

  • Creating a custom Ribbon tab is possible via CUI editor or XML manipulation

What Needs to Happen:

  1. Set MENUBAR=1 in c:csv startup to force pull-down menu visibility (quick fix)

  2. Create Ribbon tab for CV as an optional modern UI (longer-term)

  3. Recompile VLX in 64-bit VLISP (requires a modern AutoCAD license)

  4. Recompile or replace pcms.arx for 64-bit (may need ObjectARX SDK)

Effort Estimate:

  • MENUBAR quick fix: 15 minutes

  • Ribbon tab creation: 3-5 days (design + implementation + testing)

  • 64-bit VLX recompilation: 1 day (if VLX bytecode is compatible) to 1 week (if source changes needed)

  • 64-bit ARX module: 1-2 weeks (requires C++ development and ObjectARX SDK)

AutoCAD 2012 (2011) — Associative Arrays

Internal Version: R18.2 Architecture: 32-bit and 64-bit DWG Format: 2010 (unchanged)

Key Features:

  • Associative Arrays (path, polar, rectangular)

  • AutoCAD WS (web/mobile companion — precursor to AutoCAD Web)

  • Content Explorer

  • Reality Capture point clouds

CV Impact: None for core functionality. Associative arrays don’t affect CV’s panel layout algorithms.

AutoCAD 2013 (2012) — App Store + .bundle Format ⚠️ {#acad-2013}

Internal Version: R19.0 Architecture: 32-bit and 64-bit DWG Format: 2013 (NEW)

Key Features:

  • Autodesk Exchange App Store launched (apps.autodesk.com)

  • .bundle format for plugin distribution — standard packaging

  • ApplicationPlugins folder — AutoCAD auto-detects plugins on startup

  • Command line autocomplete (intelligent suggestions)

  • Autodesk 360 cloud integration

  • Support file search path improvements

  • New DWG format (2013, used through 2017)

CV Impact — STRATEGIC:

Note

This is not a breaking change but a major opportunity. The App Store opens a new distribution channel. The .bundle format provides standardized, zero-config plugin loading — no more manual Startup Suite setup, no more registry hacking, no more installer complexity.

Change

Impact

Severity

App Store

New distribution/sales channel for CV

HIGH (business)

.bundle format

Standardized packaging replaces manual install

HIGH (distribution)

Auto-detect plugins

%PROGRAMDATA%\Autodesk\ApplicationPlugins\

HIGH (UX)

Command autocomplete

CV commands appear in autocomplete

Positive

DWG 2013 format

No code impact

None

How .bundle Changes Everything:

Before (current CV):

1. Run InstallShield installer (or manual copy)
2. Configure Support Path in AutoCAD Options
3. Add csvmenu.lsp to Startup Suite
4. Restart AutoCAD
5. Pray it works

After (.bundle):

1. Copy ConstructiVision.bundle/ to ApplicationPlugins folder
2. Start AutoCAD
3. Done — CV loads automatically

What Needs to Happen:

  1. Create ConstructiVision.bundle/ folder structure with PackageContents.xml

  2. Test auto-loading — verify csvmenu.lsp entry point works from .bundle

  3. Sign up for Autodesk Publisher account ($0 — free for publishers)

  4. Ensure VLX works in AutoCAD 2013+ (recompile if needed)

  5. Submit to App Store with screenshots, description, pricing

Effort Estimate:

  • .bundle creation and testing: 2-3 days

  • App Store submission preparation: 1 week (screenshots, marketing copy, testing)

  • Approval process: 2-4 weeks (Autodesk review)

App Store Requirements (current):

  • Must support at least the 3 most recent AutoCAD versions

  • Must use .bundle format

  • Must pass Autodesk’s security and quality review

  • Pricing set by publisher (free, one-time, subscription)

  • Revenue share: Autodesk takes 25% (publisher keeps 75%)

AutoCAD 2014 (2013)

Internal Version: R19.1 Architecture: 32-bit and 64-bit DWG Format: 2013 (unchanged)

Key Features:

  • .NET 4.0 migration (from 3.5)

  • Design Feed (social collaboration in drawings)

  • File tabs (MDI tab bar)

  • Autodesk Live Maps

  • Geographic location

CV Impact: None for AutoLISP. The .NET migration only affects .NET plugins, not AutoLISP/VLX.

AutoCAD 2015-2017 — Incremental Improvements

Versions: R20.0 through R21.0 Architecture: 32-bit and 64-bit DWG Format: 2013 (unchanged through 2017)

Key Features (highlights):

  • 2015 (R20.0): Sysvar Monitor, Design Feed improvements, gallery views

  • 2016 (R20.1): Smart Dimensioning, Geometric Center osnap, PDF enhancements, revision clouds

  • 2017 (R21.0): PDF import (convert PDF geometry to AutoCAD objects), Center marks, migration improvements

CV Impact: Minimal. These are drafting workflow improvements that don’t break or require changes to CV code. PDF import (2017) is interesting for CV users but doesn’t affect the plugin itself.

Note on Architecture: These versions still ship both 32-bit and 64-bit installers. CV’s 32-bit VLX continues to work on the 32-bit install.

AutoCAD 2018 (2017) — DWG Format Change

Internal Version: R22.0 Architecture: 32-bit and 64-bit (last era of dual installers) DWG Format: 2018 (NEW)

Key Features:

  • New DWG format (2018, used through 2024)

  • External references (XREF) path improvements

  • High-resolution (4K) monitor support

  • SHX text recognition in PDFs

  • Off-screen selection

CV Impact: Low. DWG format change doesn’t affect CV code. The 4K support is relevant for DCL dialogs — they scale poorly on high-DPI monitors, but this is a cosmetic issue.

Note

DPI Scaling Issue: DCL dialogs (all 44 of CV’s .dcl files) render at fixed pixel sizes and do not scale on high-DPI displays. On 4K monitors, CV dialogs will appear very small. This is a known limitation of DCL with no AutoLISP-side fix — it’s a platform deficiency. Users must set Windows DPI scaling to 100% or reduce resolution when using CV.

AutoCAD 2019-2020 — Modern Refinements

Versions: R23.0 through R23.1 Architecture: 32-bit and 64-bit DWG Format: 2018 (unchanged)

Key Features:

  • 2019 (R23.0): Comparison tools (DWG Compare), shared views (web publishing)

  • 2020 (R23.1): Quick Measure, Blocks palette (insert from drawings), dark mode improvements, Performance improvements

CV Impact: None for code. DWG Compare could be useful for CV users comparing panel layouts between revisions, but requires no CV changes.

AutoCAD 2021 (2020) — 32-bit Dropped + VS Code Debugger ⚠️ {#acad-2021}

Internal Version: R24.0 Architecture: 64-bit ONLY (32-bit dropped permanently) DWG Format: 2018 (unchanged)

Key Features:

  • 32-bit version discontinued — 64-bit only from this point forward

  • AutoLISP Extension for VS Code with debugging support

  • Drawing History (DWG version history via cloud)

  • XREF Compare

  • Trim/Extend enhancements

  • AutoLISP improvements: Unicode strings, error handling enhancements

CV Impact — CRITICAL:

Warning

This is the third major breaking change and the most architecturally significant. With 32-bit dropped, a VLX compiled in 32-bit AutoCAD 2000 cannot run in AutoCAD 2021+. ConstructiVision must be recompiled in a 64-bit AutoCAD VLISP environment to support modern users.

Change

Impact

Severity

32-bit dropped

CV VLX must be recompiled for 64-bit

CRITICAL

pcms.arx 32-bit

Need 64-bit ARX or replacement

CRITICAL

VS Code debugger

Can debug CV code without VLISP IDE

HIGH (positive)

Unicode strings

May expose encoding issues in CV

Medium

Error handling

Improved (vl-catch-all-apply) behavior

Low

The 64-bit Compilation Challenge:

  • AutoCAD 2000’s VLISP IDE produces 32-bit .fas and .vlx files

  • 64-bit AutoCAD (2021+) cannot load 32-bit compiled bytecode

  • Must recompile all .lsp → .fas → .vlx on a 64-bit AutoCAD

  • This requires purchasing a modern AutoCAD license (planned: 2026, $1,865/year)

  • The VLISP IDE in modern AutoCAD can still compile .vlx files — the process is the same

The VS Code Debugger Opportunity:

  • The Autodesk AutoLISP Extension (autodesk.autolispext) supports:

    • Syntax highlighting (works with any AutoCAD version)

    • Bracket matching, code folding (works with any AutoCAD version)

    • Debugging: attach to running AutoCAD process (2021+ only)

    • Breakpoints, step-through, variable inspection

    • REPL (Read-Eval-Print Loop) via debug console

  • This transforms the development workflow — no more print-debugging with (alert) and (princ)

The pcms.arx Problem:

  • pcms.arx is a 32-bit C++ ARX module (cost estimation calculations)

  • Options for 64-bit:

    1. Recompile from source (if source exists) with 64-bit ObjectARX SDK

    2. Rewrite cost calculations in pure AutoLISP (eliminate ARX dependency)

    3. Wrap in a 64-bit .NET plugin that calls the 32-bit DLL via interop (fragile)

  • Option 2 is recommended if the ARX source is unavailable

What Needs to Happen:

  1. Acquire AutoCAD 2026 license (planned: May 2026, $1,865)

  2. Recompile CSV.VLX in 64-bit VLISP on AutoCAD 2026

  3. Test all 126 .lsp files compile cleanly in modern VLISP

  4. Resolve pcms.arx — find source or rewrite in AutoLISP

  5. Set up VS Code debugging against modern AutoCAD

  6. Test complete click-path matrix on 64-bit platform

Effort Estimate:

  • VLX recompilation: 1-3 days (if no code changes needed)

  • Code compatibility fixes: 1-2 weeks (if deprecated functions found)

  • pcms.arx resolution: 1-4 weeks depending on approach

  • VS Code debug setup: 1 day

  • Full testing: 1-2 weeks

AutoCAD 2022-2024 — Cloud & AI Era

Versions: R24.1 through R24.3 Architecture: 64-bit only DWG Format: 2018 (unchanged)

Key Features (highlights):

  • 2022 (R24.1): Trace (markup without modifying drawings), floating drawing windows

  • 2023 (R24.2): My Insights (usage analytics), drawing improvements, Markup Import

  • 2024 (R24.3): Activity Insights, Smart Blocks (ML-based placement), Markup Assist AI

CV Impact: None for code. These are Autodesk cloud features and AI enhancements that don’t affect the AutoLISP API or plugin loading.

AutoCAD 2025 (2024) — Current Release {#acad-2025}

Internal Version: R25.0 Architecture: 64-bit only DWG Format: 2025 (NEW — first format change since 2018)

Key Features:

  • New DWG format (2025)

  • Autodesk Assistant (AI chatbot integration)

  • Activity Insights improvements

  • Hatch enhancements

  • Smart Block replace

CV Impact: New DWG format — drawings saved in 2025 format won’t open in older AutoCAD. No API changes affecting AutoLISP.

AutoCAD 2026 (2025) — CV Target Platform {#acad-2026}

Internal Version: R25.1 (expected) Architecture: 64-bit only DWG Format: 2025 (expected, unchanged)

Planned:

  • License acquisition: May 2026 ($1,865/year)

  • ADN (Autodesk Developer Network) membership: $500 (for App Store access)

  • Primary development/compilation platform for 64-bit VLX

  • Target for App Store submission (Q4 2026)

AutoLISP Language Stability Analysis

One of the most remarkable aspects of AutoCAD’s evolution is how stable AutoLISP has remained. Here is what has and hasn’t changed:

Unchanged Since AutoCAD 2000 (25 years)

Feature

Status

Notes

Core AutoLISP functions

✅ Identical

defun, setq, if, cond, while, foreach, etc.

(command) function

✅ Identical

Still drives AutoCAD commands

System variable access

✅ Identical

(getvar) / (setvar) — same API

Entity access (DXF)

✅ Identical

(entget), (entmod), (entmake)

Selection sets

✅ Identical

(ssget), (sslength), (ssname)

File I/O

✅ Identical

(open), (read-line), (write-line)

DCL dialogs

✅ Identical

(load_dialog), (new_dialog), (start_dialog)

Visual LISP extensions

✅ Identical

vlax-*, vla-* COM automation functions

VLX compilation

✅ Identical

Same .fas/.vlx format and process

Error handling

✅ Identical

(*error*), (vl-catch-all-apply)

Reactor system

✅ Identical

(vlr-*) reactor functions

Changed or Added

Feature

Version

Change

CV Impact

Unicode strings

2021+

Full Unicode support (was partial before)

Low — test for encoding issues

(vlax-machine-product-key)

Varies

Registry path varies by architecture

Medium — if CV uses registry lookups

Namespace handling

R18+

Some namespace edge cases changed

Low — CV uses separate namespace

ARX API version

Every release

C++ API changes per version

HIGH for pcms.arx

Menu loading API

2006+

(menucmd) behavior differs with CUI

Medium

Bottom line: CV’s 126 .lsp files will almost certainly run without code changes in modern AutoCAD. The challenges are:

  1. Compilation (32-bit → 64-bit VLX)

  2. Menu loading (MNU → CUI)

  3. ARX module (pcms.arx 32-bit → 64-bit)

The Six Adaptation Layers

Based on the version analysis above, CV modernization breaks down into six distinct adaptation layers, ordered by dependency:

Layer 1: Version Detection (Foundation)

Prerequisite for everything else.

Add a version-detection utility to csv.lsp or a new csvcompat.lsp:

;;;------------------------------------------------------------
;;; csvcompat.lsp — AutoCAD version compatibility layer
;;;------------------------------------------------------------

(defun csv_get-acad-version ()
  ;; Returns integer: 15=2000, 16=2004-6, 17=2007-9,
  ;;   18=2010-12, 19=2013-14, 20=2015-16, 21=2017,
  ;;   22=2018, 23=2019-20, 24=2021-24, 25=2025+
  (atoi (getvar "ACADVER"))
) ; end defun csv_get-acad-version

(defun csv_is-64bit ()
  ;; Returns T if running on 64-bit AutoCAD
  (not (null (getenv "ProgramFiles(x86)")))
) ; end defun csv_is-64bit

(defun csv_is-ribbon-era ()
  ;; AutoCAD 2010+ has Ribbon UI
  (>= (csv_get-acad-version) 18)
) ; end defun csv_is-ribbon-era

(defun csv_is-cui-era ()
  ;; AutoCAD 2006+ uses CUI menus
  (>= (csv_get-acad-version) 16)
) ; end defun csv_is-cui-era

(defun csv_is-bundle-era ()
  ;; AutoCAD 2013+ supports .bundle format
  (>= (csv_get-acad-version) 19)
) ; end defun csv_is-bundle-era

Effort: 0.5 days Dependencies: None Priority: Do first

Layer 2: Menu System Adaptation

Handles the 2006 CUI transition and 2010 Ribbon visibility.

Modify csvmenu.lsp to branch on version:

(defun csv_load-menus ()
  (cond
    ;;----------------------------------------------------------
    ;; Pre-2006: Traditional MNU loading (current behavior)
    ;;----------------------------------------------------------
    ((< (csv_get-acad-version) 16)
      (menuload "csv")
    )
    ;;----------------------------------------------------------
    ;; 2006-2009: CUI loading
    ;;----------------------------------------------------------
    ((< (csv_get-acad-version) 18)
      (command "_.CUILOAD" "csv.cui")
    )
    ;;----------------------------------------------------------
    ;; 2010+: CUI loading + force menu bar visible
    ;;----------------------------------------------------------
    (T
      (command "_.CUILOAD" "csv.cui")
      (setvar "MENUBAR" 1)
    )
  ) ; end cond
) ; end defun csv_load-menus

Effort: 1-2 days Dependencies: Layer 1 (version detection) Priority: Second — enables UI on modern AutoCAD

Layer 3: 64-bit VLX Recompilation

The critical gate for AutoCAD 2021+ support.

Steps:

  1. Install AutoCAD 2026 (requires license — May 2026)

  2. Open VLISP IDE in AutoCAD 2026

  3. Create new project with all 126 .lsp + 44 .dcl files

  4. Compile to CSV.VLX (64-bit)

  5. Test on AutoCAD 2026

Known Risks:

  • Some vlax-* function behavior may differ between R15 and R25

  • String encoding (ANSI → Unicode) may cause display issues in DCL

  • System variable names may have changed (check all 50 sysvars set by c:csv)

Effort: 1-2 weeks (compile + fix + test) Dependencies: AutoCAD 2026 license Priority: Third — unlocks modern AutoCAD market

Layer 4: ARX Module Resolution

The pcms.arx problem.

pcms.arx is a 32-bit C++ ARX module for cost calculations. Options:

Option

Effort

Risk

Recommended

Recompile from C++ source

1-2 weeks

Low (if source exists)

If source available

Rewrite in AutoLISP

2-4 weeks

Medium

If source lost

Create .NET wrapper

1-2 weeks

High (fragile)

Not recommended

Drop cost module

0

HIGH (feature loss)

Last resort

Effort: 1-4 weeks depending on approach Dependencies: Layer 3 (need 64-bit AutoCAD environment) Priority: Fourth — required for full feature parity on 64-bit

Layer 5: .bundle Packaging

Standardized plugin deployment for AutoCAD 2013+.

Create ConstructiVision.bundle/ with:

  • PackageContents.xml manifest

  • Contents/ folder with VLX, CUI, help files, blocks

  • Support for both 32-bit (legacy) and 64-bit paths

<Components Description="ConstructiVision">
  <!-- 64-bit component (AutoCAD 2021+) -->
  <RuntimeRequirements OS="Win64" Platform="AutoCAD" SeriesMin="R24.0" />
  <ComponentEntry
    AppName="ConstructiVision"
    Version="11.0.1.64"
    ModuleName="./Contents/Win64/csvmenu.lsp"
    />

  <!-- 32-bit component (AutoCAD 2010-2020) -->
  <RuntimeRequirements OS="Win32" Platform="AutoCAD" SeriesMax="R23.1" />
  <ComponentEntry
    AppName="ConstructiVision"
    Version="11.0.1.32"
    ModuleName="./Contents/Win32/csvmenu.lsp"
    />
</Components>

Effort: 2-3 days Dependencies: Layer 3 (64-bit VLX) and Layer 4 (ARX resolution) Priority: Fifth — enables App Store submission

Layer 6: App Store Submission

The distribution endgame.

Requirements (current as of 2025):

Requirement

Status

Action

Autodesk Publisher account

⏳ Needed

Sign up (free)

ADN membership

⏳ Planned ($500)

Apply

Support 3 recent AutoCAD versions

⏳ Needed

Test on 2024, 2025, 2026

.bundle format

⏳ Layer 5

Create

App icon (400×400 PNG)

⏳ Needed

Design

Screenshots (5 minimum)

⏳ Needed

Capture

Description and documentation

⏳ Needed

Write

Security review passes

⏳ Needed

No malware, proper API use

Effort: 1-2 weeks (preparation + submission), 2-4 weeks (review) Dependencies: Layers 1-5 complete Priority: Sixth (final) — targeted Q4 2026

Ordered Modernization Sequence

Important

This is the recommended order of implementation, driven by dependencies and business value. Each layer builds on the previous one.

Phase 0: Foundation (NOW — no license needed)
├── Layer 1: Version detection utility (csvcompat.lsp)
├── Layer 2: Menu system adaptation (csvmenu.lsp branching)
└── Deliverable: CV works on AutoCAD 2000-2020 (32-bit)

Phase 1: 64-bit Gate (May 2026 — requires AutoCAD license)
├── Layer 3: 64-bit VLX recompilation
├── Layer 4: pcms.arx resolution
└── Deliverable: CV works on AutoCAD 2021-2026 (64-bit)

Phase 2: Distribution (Q3-Q4 2026)
├── Layer 5: .bundle packaging
├── Layer 6: App Store submission
└── Deliverable: CV available on Autodesk App Store

Timeline Mapped to Existing Phase Plan

Adaptation

Phase Plan Ref

Timeline

Cost

Layer 1: Version detection

P1 (Sprint)

Now

$0

Layer 2: Menu adaptation

P1 (Sprint)

Now

$0

Layer 3: 64-bit VLX

P3 (Modern)

May-Jun 2026

$1,865 (AutoCAD license)

Layer 4: ARX resolution

P3 (Modern)

Jun-Jul 2026

$0 (if rewrite in LISP)

Layer 5: .bundle packaging

P3 (Modern)

Jul-Aug 2026

$0

Layer 6: App Store

P3 (Modern)

Sep-Dec 2026

$500 (ADN membership)

Total estimated cost: $2,365 Total estimated effort: 4-8 weeks of development

AutoCAD Version Support Matrix (Complete)

This matrix shows which AutoCAD versions CV can support at each modernization layer:

AutoCAD

Year

Arch

Layer 0 (Current)

Layer 1-2 (Menus)

Layer 3-4 (64-bit)

Layer 5-6 (App Store)

2000

1999

32

✅ Working

✅ Working

✅ Working

N/A (too old)

2002

2001

32

✅ Expected

✅ Expected

✅ Expected

N/A

2004

2003

32

⚠️ Untested

✅ MNU path

✅ MNU path

N/A

2006

2005

32

❌ Menu fail

✅ CUI path

✅ CUI path

N/A

2007-2009

2006-08

32

❌ Menu fail

✅ CUI path

✅ CUI path

N/A

2010-2012

2009-11

32/64

❌ Menu hidden

✅ CUI + MENUBAR

✅ CUI + MENUBAR

N/A (pre-App Store)

2013-2020

2012-19

32/64

❌ Menu hidden

✅ CUI + MENUBAR

✅ Both arches

✅ .bundle

2021-2024

2020-23

64

❌ Won’t load

❌ 32-bit VLX

✅ 64-bit VLX

✅ .bundle + App Store

2025-2026

2024-25

64

❌ Won’t load

❌ 32-bit VLX

✅ 64-bit VLX

✅ .bundle + App Store

DWG Format History (Reference)

CV doesn’t control DWG formats, but users need to understand format interchange:

DWG Format

AutoCAD Versions

Years

R14

R14

1997

2000

2000, 2000i, 2002

1999-2003

2004

2004, 2005, 2006

2003-2006

2007

2007, 2008, 2009

2006-2009

2010

2010, 2011, 2012

2009-2012

2013

2013, 2014, 2015, 2016, 2017

2012-2017

2018

2018, 2019, 2020, 2021, 2022, 2023, 2024

2017-2024

2025

2025, 2026

2024-2025

Tip

CV sample drawings and block libraries should be saved in 2000 DWG format for maximum compatibility. Users working in modern AutoCAD can open 2000-format files without issue — AutoCAD is fully backward-compatible for reading older DWG formats. The reverse is not true.

Risk Assessment: What Could Go Wrong

High Risk

Risk

Likelihood

Impact

Mitigation

VLX bytecode incompatibility (32→64)

Medium

Critical

Test early; may need .lsp → .fas → .vlx rebuild from scratch

pcms.arx source code lost

High

High

Reverse-engineer cost calculations or rewrite in AutoLISP

AutoLISP deprecation by Autodesk

Low

Critical

Monitor Autodesk roadmap; they’ve committed to long-term AutoLISP support

DCL dialog rendering on 4K/HiDPI

Certain

Medium

Document limitation; no fix available in AutoLISP

COM automation differences (64-bit)

Medium

Medium

Test all vlax-* calls on 64-bit; fix as found

Low Risk

Risk

Likelihood

Impact

Mitigation

System variable removed

Low

Low

Wrap (setvar) calls in error handlers

(command) syntax changes

Very Low

High

AutoCAD maintains backward compatibility

DCL syntax changes

None

N/A

DCL has not changed since R14

Menu item limit changes

None

N/A

CUI supports unlimited items

Key Takeaways

  1. AutoLISP is immortal (for now). The language hasn’t meaningfully changed in 25 years. CV’s 126 .lsp files will almost certainly run without modification on modern AutoCAD.

  2. The three real challenges are: recompiling for 64-bit, adapting the menu system, and resolving the pcms.arx dependency. Everything else is packaging.

  3. Phase 0 costs nothing. Version detection and menu adaptation can be done now, on AutoCAD 2000, without any license purchase. This gets CV working on AutoCAD 2004-2020 immediately.

  4. The 64-bit gate opens in May 2026 when the AutoCAD license is purchased. Budget 4-6 weeks of development after that.

  5. App Store is the prize. Every adaptation layer builds toward the App Store goal. Once listed, CV gains: automatic updates, payment processing, global distribution, and credibility.

  6. Don’t fear the Ribbon. Setting MENUBAR=1 in c:csv is a one-line fix that makes pull-down menus visible in Ribbon-era AutoCAD. A custom Ribbon tab would be ideal but is not required.