Release & Distribution Plan (Modern Windows + Web)

Last Updated: February 28, 2026 - Win10 compatibility COMPLETE, P1 sprint ABORTED, WiX ABORTED → VLX .bundle to Autodesk App Store

Note: This plan is a working draft. Some technical details (exact file provenance, build parity, vendor timelines, pricing, and Autodesk product capabilities) may need verification as we inventory the full legacy tree and validate behavior in modern environments.

Distribution objectives

  • ✅ Build artifacts captured and archived (v3.60 + v11 hotfix)

  • ✅ Legacy installer analyzed — works as Administrator on XP/Vista/Win7/Win10x32

  • ❌ WiX Toolset 4.x selected → ABORTED Feb 28 — pivoting to .bundle/Autodesk App Store

  • ✅ isDcc decompilation produced setup.rul (4,163 lines InstallScript)

  • ✅ Cost analysis complete — VLX .bundle to App Store eliminates installer cost entirely

  • ✅ AC2000 + CV3.60 validated on XP, Vista, Win7, Win10x32 (Feb 13) — 8 bugs documented, all bypassed

  • ✅ Complete v11 installer specification created from 3-tool monitoring data (152 files, 5.5 MB)

  • ✅ Win10 32-bit FULL STACK WORKING (Feb 13) — AC2000 + CV + COM automation

  • ✅ Auto-config script created: Configure-ConstructiVision.ps1

  • ✅ P1 InstallShield sprint ABORTED (low ROI) → WiX also ABORTED → .bundle/App Store

  • ⚠️ Win10 64-bit: AC2000 runs, CV works, but COM fails (needs 64-bit AutoCAD)

  • 🔧 nanoCAD testing ACTIVE (Feb 13+) — Free 64-bit LISP-compatible CAD platform

  • ⏳ 64-bit AutoCAD purchase planned for March

  • 🔜 Alpha testing with GSCI engineers (Feb 17 - Mar 14) — VMs 200-201, Tailscale access

  • Deploy to multiple test environments without custom laptop handoffs

  • Upgradable (versioned releases)

  • Supportable (diagnostics + rollback)

  • Legally clean (licenses, notices)

  • Primary distribution: Autodesk App Store (.bundle format) 🔧

  • Future-proof: Path to AutoCAD Web via .NET/JavaScript refactoring 🔧

Installer & Code Signing Costs (January 27, 2026)

Key Insight: Installer Tools ≠ Code Signing

Component

Purpose

Selected Option

Cost

Installer Tool

Build .msi package

WiX Toolset 4.x

$0 (FREE)

Code Signing

Windows/SmartScreen trust

OV Certificate (Sectigo)

$200/year

Total

$200/year

Why WiX Over Commercial Alternatives?

Tool

Cost

Format

Decision

WiX Toolset 4.x

FREE

MSI

⭐ SELECTED

Inno Setup

FREE

EXE only

❌ No MSI (enterprise needs MSI)

InstallShield 12

~$500

MSI

❌ Obsolete (2006), no support

Advanced Installer

~$500/yr

MSI

❌ Unnecessary cost

InstallShield 2024

~$2,000+/yr

MSI

❌ Way too expensive

Code Signing Options

Type

Cost/Year

SmartScreen Behavior

Recommendation

Unsigned

$0

⚠️ Warning, user clicks “Run anyway”

OK for beta

OV (Organization)

~$200

⚠️ Builds reputation over downloads

⭐ For GA

EV (Extended)

~$400

✅ Instant trust, no warnings

Optional upgrade

See: installer-modernization-decision.md for detailed analysis. (archived)

Immediate deployment phase (P1 - Q1 2026)

Phase 1A: Installer & Build Sprint (✅ COMPLETE - Feb 13)

Timeline: Jan 21 - Feb 13, 2026 (~4 weeks)

See installer-rebuild-sprint.md for detailed plan. (archived)

Week 1 (Jan 21-27): v3.60 Installer Rebuild ✅ COMPLETED

  • Setup InstallShield 5.x in Windows XP VM

  • Import setup.rul (4,163 lines decompiled via isDcc)

  • Compile, test, create pre/post install snapshots

Week 2 (Jan 27 - Feb 3): Gap Analysis ✅ COMPLETED

  • Inspect existing v7.0/v11 desktop installation

  • Compare v3.60 vs v7.0 files, registry, paths

  • Document target state specification

Week 3 (Feb 3-10): Nero Analysis + Multi-OS Testing ✅ COMPLETED

  • Analyzed Nero 1.0 installer to validate isDcc workflow

  • Critical: isDcc bytecode output won’t compile → wizard approach validated

  • ✅ CV3.60 + AC2000 installed on XP, Vista, Win7

Weeks 4-5 (Feb 10-13): Win10 Testing + Decision ✅ COMPLETED

  • ✅ Win10 32-bit FULL STACK WORKING (AC2000 + CV + COM automation)

  • ✅ Auto-config script created: Configure-ConstructiVision.ps1

  • ✅ Total Uninstall v11 inventory: 152 files, 5.5 MB

  • ⚠️ Win10 64-bit: COM automation fails (needs 64-bit AutoCAD)

  • ❌ P1 InstallShield sprint ABORTED (Feb 13) — low ROI

Sprint Deliverables:

  • ✅ Platform compatibility matrix (XP/Vista/Win7/Win10x32/Win10x64)

  • ✅ 8 installer bugs documented with root cause analysis

  • ✅ 41 file v3.60 payload validated across all platforms

  • ✅ 152 file v11 payload captured via Total Uninstall

  • ✅ Auto-configuration script for AutoCAD support path + Startup Suite

Phase 1B: VM-Based Beta Deployment (✅ Active)

Purpose: Interim solution while modern installer under development

Implementation:

  • Deploy v3.60 + v11 on Windows XP VMs (legacy environment)

  • Enable remote access for Great Seattle Concrete + 4-9 additional beta customers

  • RDP/VPN secure tunnels with encrypted connections

  • NDA agreements and audit trail

Limitations:

  • Max 5-10 concurrent beta customers

  • Network latency affects CAD performance

  • Operational cost: $100-200/VM/month ($500-2000/month total)

  • Customer drawings hosted on our infrastructure (security consideration)

Sunset Date: Q3 2026 (replace with App Store .bundle distribution)

Phase 1C: WiX Installer Development (❌ ABORTED - Feb 28)

Original Timeline: Feb 13 - Mar 31, 2026 (7 weeks)

Decision (Feb 28): WiX MSI installer development ABORTED. Since the existing VLX works as validated (Feb 13) and the Autodesk App Store uses .bundle format (not MSI), building a WiX installer adds complexity with no clear payoff. Pivoting to .bundle packaging for direct App Store submission.

What We Keep:

  • ✅ Configure-ConstructiVision.ps1 auto-config script (works standalone)

  • ✅ File inventory from Total Uninstall (152 files, informs .bundle manifest)

  • ✅ Registry config knowledge (Startup Suite, support paths, COM)

  • ✅ Platform compatibility matrix (XP through Win10x64)

New Plan → Phase 1F: .bundle format packaging for Autodesk App Store (see Phase 3 below, now accelerated)

See: Installer Modernization Decision (archived) | 16-wix-bridge-analysis.md (archived) (historical reference)

Phase 1E: Alpha Testing with GSCI Engineers (🚧 ACTIVE - Feb 17 - Mar 14)

Timeline: February 17 - March 14, 2026 (3 weeks + 1 week wrap-up)

Objective: External alpha testing with GSCI engineers to validate v11 on Win10x32 before App Store submission.

Infrastructure:

  • VM 200: Terry (GSCI) on Win10x32 + AC2000 + CV v11

  • VM 201: Leon (GSCI) on Win10x32 + AC2000 + CV v11

  • Access: Tailscale PVE authentication + Remote Desktop

  • Isolated: Separate from internal VMs (100-109) for security

Timeline:

  • Prep Week (Feb 13-16): VM cloning, Tailscale config, user account setup

  • Week 1 (Feb 17-21): Installation validation, basic functionality testing

  • Week 2 (Feb 24-28): Real-world GSCI workflows, stress testing

  • Week 3 (Mar 3-7): Edge cases, bug reproduction, enhancement requests

  • Wrap-up (Mar 10-14): Debrief, bug triage, App Store requirements update

Deliverables:

  • Installation success/failure reports

  • Bug list with reproduction steps

  • Workflow feedback (usability, performance)

  • Enhancement requests

  • Alpha test summary for .bundle/App Store packaging

Success Criteria:

  • Remote access >99% uptime

  • CV menu loads on first launch (>95%)

  • Core functionality works without workarounds

  • <1 crash per day per user

  • User satisfaction >4/5

See: alpha-testing-gsci-plan.md (sensitive) | alpha-testing-gsci-checklist.md (sensitive)

Phase 1D: Windows Compatibility Validation ✅ COMPLETE (Feb 13)

Platform Compatibility Matrix (Validated):

Platform

AutoCAD 2000

CV Install

CV VLX Load

COM Automation

Status

Windows XP SP3

✅ Works

✅ Works

✅ Works

✅ Works

Fully Supported

Windows Vista

✅ Works

✅ Works

✅ Works

✅ Works

Fully Supported

Windows 7

✅ Works

✅ Works

⚠️ BHF bug

✅ Works

Limited (non-blocking)

Win10 32-bit

✅ Works

✅ Works

✅ Works

✅ Works

Fully Supported

Win10 64-bit

✅ Runs

✅ Works

✅ Works

❌ Fails

Needs 64-bit AutoCAD

nanoCAD 24.x (64-bit)

N/A

🔧 Testing

🔧 Testing

🔧 Testing

In Progress

Test Coverage (Actual Results):

Test

XP + ACAD 2000

Win7 + ACAD 2000

Win10x32 + ACAD 2000

Win10x64 + ACAD 2000

Installer runs

✅ Pass

✅ Pass

N/A (manual)

N/A (manual)

Files deployed

✅ 41 files

✅ 41 files

✅ 152 files (v11)

✅ 152 files (v11)

VLX loads

✅ Pass

✅ Pass

✅ Pass

✅ Pass

Menu appears

✅ Pass

✅ Pass

✅ Pass

✅ Pass

Basic command works

✅ Pass

✅ Pass

✅ Pass

✅ Pass

Dialog opens (DCL)

✅ Pass

✅ Pass

✅ Pass

✅ Pass

COM automation

✅ Pass

✅ Pass

✅ Pass

❌ Fail

Uninstaller works

✅ Pass

✅ Pass

N/A

N/A

Success Criteria (Updated):

  • ✅ >95% installation success rate on Windows 10 32-bit — ACHIEVED

  • ✅ >98% menu registration success — ACHIEVED via Startup Suite

  • 🔧 CV VLX loads in nanoCAD 64-bit (free LISP platform) — TESTING IN PROGRESS

  • ⏳ <5% support calls per installation — TBD (alpha/beta testing)

  • ⏳ Clean uninstall (no registry residue) — TBD (App Store .bundle)

Modern installer strategy (DEFERRED)

Note

WiX MSI installer development was ABORTED Feb 28, 2026 in favor of VLX .bundle distribution via the Autodesk App Store. The technical analysis below is retained for reference if MSI distribution is ever needed (e.g., enterprise customers requiring Group Policy deployment).

WiX Toolset 4.x Installer (DEFERRED)

Format: Windows Installer (MSI)

Key Features:

  1. AutoCAD Detection

    • Registry-based (not file search)

    • Reads from HKLM\Software\Autodesk\AutoCAD\R15.0\AcadLocation

    • Fast, reliable, no false positives

  2. Process Detection

    • Windows Restart Manager API

    • No file rename hacks (fixes Vista+ compatibility)

    • Can offer to close AutoCAD automatically

  3. Menu Registration

    • Active profile detection from HKCU\...\CurProfile

    • Dynamic (not hardcoded to <<Unnamed Profile>>)

    • Fixes 30-40% failure rate from legacy installer

  4. Installation Types

    • Typical: Core files + sample files

    • Custom: User selects components

    • Compact: Core files only (minimal footprint)

  5. Enterprise Features

    • Group Policy deployment (MSI standard)

    • SCCM/Intune compatible

    • Silent install mode

    • Repair and uninstall support

  6. Security & Trust

    • Code signed with valid certificate

    • UAC elevation prompt (legitimate)

    • No SmartScreen warnings

    • Windows 11 compatible

Custom Actions (C#):

  • Detect AutoCAD installation path

  • Read active AutoCAD profile

  • Modify acad.rx or use .bundle approach

  • Register menu in correct profile

  • Fallback to acaddoc.lsp if registry fails

Target Installation Paths:

C:\Program Files\AutoCAD 2000\Support\ConstructiVision\
  ├── csv.vlx (main program)
  ├── pcms.arx, pcms2.arx (cost modules)
  ├── csv.mnc (compiled menu)
  ├── csvmenu.lsp (menu loader)
  ├── csv.hlp (help file)
  ├── Manual.rtf (user manual)
  └── Wincss.exe (registration manager) — SEE MODERNIZATION NOTE BELOW

C:\Program Files\AutoCAD 2000\Project Files\CSV Sample Site\
  └── [Sample drawings and scripts - optional]

Registration Manager Modernization (wincss2000.exe)

Legacy Component: wincss2000.exe — “ConstructiVision Registration Manager 2.0”

  • Built: July 2001, CompanyName: ConstructiVision, 32-bit Win32 executable

  • Purpose: License key validation and product registration

  • Status: Must be replaced — 32-bit only, no modern crypto, no network capability

Modern Replacement Options (evaluate for PB11):

Approach

Example

Pros

Cons

Signed license file

Ed25519-signed JSON

Offline, simple, no server needed

Manual key distribution

Cloud license service

Keygen.sh, Cryptlex

Dashboard, analytics, subscription support

Requires internet, ongoing cost

Autodesk App Store

Built-in licensing

Handles payments and access control

Tied to Autodesk ecosystem

Remove licensing entirely

Open source (MIT)

Zero friction, community growth

No revenue protection

Recommended path: If distributing via Autodesk App Store (P5, 2027+), leverage their built-in licensing. For direct distribution, implement Ed25519-signed license files validated by a small helper utility callable from LISP.

VLX Compilation & Modernization Strategy

Current State: Legacy VLX ✅ VALIDATED (Feb 13)

v3.60/v11 VLX Binary:

  • Size: 1,103,600 bytes

  • Format: 109 FAS modules compiled into VLX container

  • Target: AutoCAD 2000 (32-bit only)

  • Status: ✅ WORKS ON WIN10x32 — no recompilation needed for 32-bit platforms

Source Availability:

  • ✅ LSP source files available in src/x86/v3_60/v3.60/ and src/x86/v7.0(patch)/

  • ✅ DCL dialog files available

  • ✅ Existing VLX validated on Win10x32 (Feb 13) — full functionality confirmed

Phase 1: VLX Recompilation ✅ BYPASSED

Original Goal: Prove we can rebuild VLX from LSP source.

Feb 13 Finding: Existing VLX works perfectly on Win10x32 with AutoCAD 2000. Recompilation is not required for 32-bit platforms.

Status: BYPASSED — existing VLX files will be used in .bundle for App Store.

Phase 2: 64-bit VLX for Modern AutoCAD (Feb-Mar 2026)

Challenge:

  • 32-bit VLX won’t load in 64-bit AutoCAD (2014+)

  • Win10x64 COM automation fails with 32-bit AutoCAD 2000

Solution Path:

Step 1: nanoCAD Testing (Feb 13 - ongoing) — 🔧 ACTIVE

Why nanoCAD:

  • ✅ FREE — No purchase required for 64-bit LISP testing

  • ✅ 64-bit native — Modern Windows 10/11 platform

  • ✅ LISP compatible — Supports AutoLISP/VisualLISP VLX files

  • ✅ 3D capable — Full 3D modeling environment

  • ✅ Only free option found — BricsCAD ($$$), ZWCAD ($$$), AutoCAD ($$$)

  • ✅ DWG compatible — Reads/writes AutoCAD DWG format

  • ✅ No license risk — Free for testing, validate before AutoCAD purchase

Test Plan:

  1. Install nanoCAD 24.x (latest free version) on Win10x64 VM

  2. Copy CV VLX files (csv.vlx, pcms.arx, pcms2.arx) to nanoCAD support path

  3. Test VLX loading via (load "csv.vlx")

  4. Validate DCL dialogs load and function correctly

  5. Test core CV commands (panel creation, calculations, exports)

  6. Test menu system integration

  7. Document any incompatibilities or required changes

Expected Outcomes:

  • ✅ Best case: VLX loads without modification → proves 64-bit compatibility

  • ⚠️ Likely case: Minor LISP tweaks needed → document for AutoCAD testing

  • ❌ Worst case: Major rewrite needed → informs AutoCAD purchase decision

Why This Matters:

  • Validates 64-bit VLX compatibility BEFORE spending $2,000+ on AutoCAD

  • If CV doesn’t work on nanoCAD, we know recompilation is required

  • If CV works on nanoCAD, high confidence it will work on 64-bit AutoCAD

  • Opens door to nanoCAD as a supported platform for cost-sensitive customers

Step 2: 64-bit AutoCAD Testing (March 2026) — ⏳ PLANNED

Process:

  1. Purchase 64-bit AutoCAD license (2010+ for 64-bit, ideally 2014+ for VLX compat)

  2. Install on Win10x64 test VM (VM 109)

  3. Test existing VLX loading — may work without recompilation

  4. If VLX doesn’t load, recompile using 64-bit VLIDE

  5. Verify COM automation works from 64-bit apps

  6. Compare behavior with nanoCAD test results

Timeline:

  • nanoCAD: Feb 13 - ongoing (Week 9+)

  • 64-bit AutoCAD: Week 12 (Mar 6-13, 2026)

Phase 3: .bundle Format for App Store (P3)

Requirement: Autodesk App Store requires .bundle format.

Bundle Structure:

ConstructiVision.bundle/
├── PackageContents.xml    (manifest)
├── Contents/
│   ├── Windows/
│   │   ├── csv.vlx        (main code)
│   │   ├── pcms.arx       (cost module - 32-bit)
│   │   ├── pcms64.arx     (cost module - 64-bit)
│   │   └── *.dcl          (dialogs)
│   └── Resources/
│       ├── csv.cui        (menu)
│       └── csv.hlp        (help)
└── README.md

PackageContents.xml Example:

<?xml version="1.0" encoding="utf-8"?>
<ApplicationPackage
  SchemaVersion="1.0"
  AppVersion="4.0.0"
  ProductCode="{GUID}"
  Name="ConstructiVision"
  Description="Concrete construction detailing for AutoCAD"
  Author="ConstructiVision, Inc.">
  <CompanyDetails Name="ConstructiVision" Url="https://constructivision.com" />
  <Components>
    <RuntimeRequirements OS="Win64" Platform="AutoCAD" SeriesMin="R24.0" />
    <ComponentEntry AppName="CSV" Version="4.0.0" ModuleName="./Contents/Windows/csv.vlx" />
  </Components>
</ApplicationPackage>

Timeline: Q3 2026 (before App Store submission)

Future Platform Support: If nanoCAD testing is successful (Feb-Mar 2026), consider adding nanoCAD as a supported platform alongside AutoCAD:

  • ✅ No licensing fees (nanoCAD is free)

  • ✅ Expands addressable market (cost-sensitive customers)

  • ✅ 64-bit native with LISP/VLX support

  • ⚠️ Requires documentation and support effort

  • ⚠️ May need platform-specific workarounds

Decision Point: Q2 2026 (after nanoCAD test results available)

Web Deployment Strategy (P5 - 2027+)

Warning

AutoLISP is NOT compatible with AutoCAD Web

AutoCAD Web (browser-based) uses JavaScript APIs only. To deploy ConstructiVision on AutoCAD Web, the entire codebase must be rewritten in JavaScript or use Autodesk Platform Services (APS) Design Automation.

Option A: JavaScript Rewrite for AutoCAD Web

Scope: Full rewrite of ~50,000 lines of AutoLISP to JavaScript.

AutoCAD Web API:

  • JavaScript-based API (not AutoLISP)

  • Limited compared to desktop (no ARX, no DCL)

  • HTML/CSS for UI (no DCL dialogs)

  • Uses Autodesk identity service for auth

Migration Path:

  1. Phase 1: Identify core algorithms (panel layout, calculations)

  2. Phase 2: Rewrite algorithms in JavaScript/TypeScript

  3. Phase 3: Build HTML/CSS UI to replace DCL dialogs

  4. Phase 4: Integrate with AutoCAD Web API

  5. Phase 5: Test and deploy

Estimated Effort: 12-18 months, $150-300K (contractor or 2 FTE)

Prerequisites:

  • ✅ Complete LSP source inventory

  • ✅ Menu tree documentation (Sprint Week 3)

  • ⏳ Algorithm documentation

  • ⏳ UI/UX redesign for web

Option B: APS Design Automation (Headless)

Scope: Run existing AutoLISP code on Autodesk cloud servers.

How It Works:

  1. User uploads DWG to your web app

  2. Web app calls APS Design Automation API

  3. APS spins up headless AutoCAD instance

  4. AutoLISP code runs on cloud (same code as desktop!)

  5. Modified DWG returned to user

Benefits:

  • ✅ Reuse existing AutoLISP code (no rewrite)

  • ✅ Runs on any device with browser

  • ✅ No local AutoCAD installation required

Limitations:

  • ❌ No real-time interactive editing

  • ❌ Batch processing only (not live CAD session)

  • ❌ Pay per compute minute (~$0.10-0.50/job)

  • ❌ No DCL dialogs (must build web UI)

Architecture:

┌─────────────┐     ┌─────────────┐     ┌─────────────────────┐
│  Web App    │────▶│  Your API   │────▶│  APS Design         │
│  (Browser)  │     │  (Node.js)  │     │  Automation         │
│             │◀────│             │◀────│  (Headless AutoCAD) │
└─────────────┘     └─────────────┘     └─────────────────────┘
      │                    │                      │
   HTML/JS             REST API              AutoLISP + DWG

Cost Model:

  • APS subscription: $500-2,000/month (usage-based)

  • Development: 3-6 months for web frontend

  • Ongoing: Compute costs per job

Timeline: P5 (2027+)

Option C: .NET Rewrite for Desktop + Web

Scope: Rewrite AutoLISP to C#/.NET for both desktop and web.

Benefits:

  • ✅ Single codebase for desktop (.NET API) and web (ASP.NET + APS)

  • ✅ Better performance than AutoLISP

  • ✅ Modern development tools (Visual Studio, NuGet)

  • ✅ Easier to hire developers

Desktop (.NET API):

// Example: AutoCAD .NET API
[CommandMethod("CSVPANEL")]
public void CreatePanel()
{
    Document doc = Application.DocumentManager.MdiActiveDocument;
    Database db = doc.Database;
    Editor ed = doc.Editor;
    // ... panel creation logic
}

Web (Blazor + APS):

// Same algorithms, different UI
@page "/panel-designer"
<PanelDesigner OnPanelCreated="HandlePanelCreated" />

@code {
    async Task HandlePanelCreated(PanelSpec spec)
    {
        // Call APS Design Automation with spec
        await _apsService.CreatePanel(spec);
    }
}

Estimated Effort: 18-24 months, $200-400K

Timeline: P5 (2027+)

Web Deployment Decision Matrix

Option

Effort

Cost

Code Reuse

Real-Time

Best For

A: JavaScript

High

$150-300K

None

Yes

Full web experience

B: APS Design Auto

Medium

$50-100K + usage

Full

No

Batch processing

C: .NET Rewrite

Very High

$200-400K

Partial

Desktop only

Long-term platform

Recommendation: Start with Option B (APS) as proof of concept in 2027, evaluate Option C for 2028+ based on market demand.

Security & Compliance Requirements

Code Signing Certificate (Required for All Distribution)

Purpose: Prevents SmartScreen warnings, proves publisher identity.

Options:

Provider

Type

Cost/Year

Trust Level

DigiCert

EV Code Signing

$699

Highest (immediate trust)

Sectigo

EV Code Signing

$499

High

Certum

Standard Code Signing

$199

Medium (needs reputation)

EV (Extended Validation) Recommended:

  • ✅ Immediate SmartScreen trust (no reputation building)

  • ✅ Hardware token required (more secure)

  • ✅ Better for enterprise customers

  • ❌ More expensive ($500-700/year)

  • ❌ Requires business verification (2-4 weeks)

Process:

  1. Purchase certificate from provider

  2. Complete business verification (D-U-N-S number, legal docs)

  3. Receive hardware token (USB)

  4. Configure build pipeline to sign MSI/EXE

  5. Renew annually

Build Integration (GitHub Actions):

- name: Sign MSI with EV Certificate
  run: |
    & 'C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe' sign \
      /tr http://timestamp.digicert.com \
      /td sha256 /fd sha256 \
      /sha1 ${{ secrets.CERT_THUMBPRINT }} \
      ConstructiVision.msi

Autodesk Developer Network (ADN) Membership

Purpose: Technical support, early API access, App Store publishing.

Tiers:

Tier

Cost/Year

Benefits

Standard

Free

Forums, basic docs

Developer

~$500

Technical support, early APIs, App Store publishing

Enterprise

~$2,000

Priority support, dedicated contact

Developer Tier Required For:

  • ✅ Publishing to Autodesk App Store

  • ✅ Early access to AutoCAD 2027 APIs

  • ✅ Technical support for API questions

  • ✅ Beta program participation

Registration Process:

  1. Create Autodesk account

  2. Register at https://aps.autodesk.com (Autodesk Platform Services)

  3. Apply for ADN Developer tier

  4. Pay annual fee

  5. Access App Store publisher portal

Timeline: Q3 2026 (before App Store submission)

Autodesk App Store Requirements

Technical Requirements:

  • ✅ .bundle format (PackageContents.xml manifest)

  • ✅ Works on AutoCAD 2020+ (minimum 3 recent versions)

  • ✅ Code signed with valid certificate

  • ✅ Clean install/uninstall (no registry residue)

  • ✅ 64-bit support (32-bit deprecated)

Documentation Requirements:

  • ✅ Product description (1000+ chars)

  • ✅ Screenshots (min 3, 1920x1080)

  • ✅ Video demo (recommended)

  • ✅ System requirements

  • ✅ Version history

  • ✅ Support contact info

Legal Requirements:

  • ✅ EULA (End User License Agreement)

  • ✅ Privacy Policy (if collecting data)

  • ✅ Terms of Service

  • ✅ No GPL/copyleft dependencies in commercial product

Review Process:

  1. Submit app package + metadata

  2. Autodesk reviews (1-2 weeks per cycle)

  3. Address feedback (if any)

  4. Resubmit and wait for re-review

  5. Approved → Published

Common Rejection Reasons:

  • Missing or invalid code signature

  • Installer leaves files after uninstall

  • Crashes on supported AutoCAD versions

  • Inadequate documentation

  • EULA/Privacy Policy issues

Timeline: Allow 4-6 weeks for review cycles (submit Nov 1 for Dec launch)

APS (Autodesk Platform Services) Registration

Purpose: Required for Design Automation (web deployment).

Process:

  1. Create APS account at https://aps.autodesk.com

  2. Create “App” to get Client ID and Secret

  3. Enable Design Automation API

  4. Upload AutoLISP bundle as “AppBundle”

  5. Create “Activity” defining inputs/outputs

  6. Call API from your web app

Costs:

  • Free tier: 100 cloud credits/month (~10-50 jobs)

  • Paid tier: $0.10-0.50 per compute minute (usage-based)

Security:

  • OAuth 2.0 for authentication

  • HTTPS only

  • Short-lived access tokens

  • Secrets stored in environment variables (never in code)

Timeline: P5 (2027+)

Distribution channels (P4 - Q4 2026)

Channel 1: Direct Download (DEFERRED)

Status: Deferred — requires WiX MSI build (currently not planned)

Implementation (if revived):

  • Download portal on constructivision.com

  • Hosted WiX MSI installer (code signed)

  • Version history and changelogs

  • IT deployment guide (Group Policy, SCCM)

Benefits:

  • Full control over updates

  • No revenue share

  • Direct customer relationship

  • Faster iteration cycles

Target Audience:

  • Existing customers

  • Referrals and word-of-mouth

  • Enterprise IT departments (direct contact)

Metrics:

  • Downloads per month

  • Installation success rate

  • Support ticket volume

  • Conversion rate (download → activation)

Channel 2: Autodesk App Store (⭐ PRIMARY) 🆕

Status: Target Q3-Q4 2026

Timeline:

  • Q3 2026: Join ADN Developer tier (~$500/year)

  • Q3 2026: Migrate to .bundle format (required for App Store)

  • Q3 2026: Prepare submission package (screenshots, docs, EULA)

  • Nov 1, 2026: Submit to Autodesk App Store

  • Nov-Dec 2026: Address review findings (allow 2 cycles = 4 weeks)

  • Dec 2026: App Store listing live (target)

Requirements:

  • ✅ Works on AutoCAD 2020-2026 (P3 deliverable)

  • ✅ .bundle format (modern plugin structure)

  • ✅ Code signed with valid certificate

  • ✅ Professional UI/UX and documentation

  • ✅ EULA, privacy policy, terms of service

  • ⏳ Security review passing (Autodesk process)

Revenue Model:

  • Autodesk takes 30% of sales

  • We receive 70% of revenue

  • Autodesk handles payment processing and licensing

Benefits:

  • Trusted marketplace (users trust Autodesk)

  • Wider reach (new customers discovering via search)

  • Enterprise-friendly (IT can deploy from trusted source)

  • Co-marketing opportunities (featured app listings)

Risks:

  • Probability: MEDIUM - Review rejection or delays

  • Mitigation: Don’t depend on App Store for 2026 launch; use as secondary channel

Target Audience:

  • New customers (discovery via search)

  • Enterprise customers (prefer marketplace)

  • International customers (Autodesk global reach)

Metrics:

  • App Store downloads per month

  • Conversion rate (download → purchase)

  • Customer rating and reviews

  • ROI (revenue - ADN fees)

Channel 3: VM Access (Legacy - Sunset Q3) ⏱️

Status: Active for alpha/beta, retired Q3 2026

Purpose: Interim solution during App Store preparation

Phase Out:

  • Q1-Q2 2026: Active for alpha (GSCI) + White Cap beta testing

  • Q3 2026: Transition customers to App Store / .bundle distribution

  • Q3 2026: Shut down VMs, end VM hosting costs

Distribution model comparison

Model

Scalability

Cost

Customer Control

IT Approval

Best For

VM Access

LOW (~10 users)

HIGH ($100-200/user/mo)

LOW

MEDIUM

Alpha/beta only

App Store (.bundle)

HIGH (unlimited)

MEDIUM (30% cut)

HIGH

HIGH

Primary channel

Direct Install (MSI)

HIGH (unlimited)

LOW ($0/user)

HIGH

MEDIUM

DEFERRED

Recommendation: Two-phase approach:

  1. Q1-Q2 2026: VM access for alpha (GSCI) + White Cap beta

  2. Q3-Q4 2026: Autodesk App Store as primary distribution channel

Versioning and release channels

Release Channels

  1. Internal / Nightly (engineers only)

    • Automated builds from main branch

    • Not code signed

    • May be unstable

    • For development testing only

  2. Beta (White Cap + GSCI select customers)

    • VM access (Q1-Q2) or direct install (Q2+)

    • Code signed but marked as beta

    • Rapid feedback cycle (weekly updates)

    • NDA required

  3. Release Candidate (demo-ready freeze)

    • Feature freeze, bug fixes only

    • Full QA testing

    • Code signed and production-ready

    • Used for White Cap demos and rehearsals

  4. GA Release (production, end of 2026 target)

    • Stable, fully tested

    • Code signed with production certificate

    • Distributed via direct download + App Store

    • Supported for 12+ months

Version Numbering

Format: MAJOR.MINOR.PATCH[-TAG]

Examples:

  • 4.0.0-beta1 - First beta release (Q1 2026)

  • 4.0.0-rc1 - First release candidate (Q3 2026)

  • 4.0.0 - GA release (Q4 2026)

  • 4.0.1 - Bug fix patch

  • 4.1.0 - Minor feature update

Semantic Versioning:

  • MAJOR: Breaking changes, incompatible with previous version

  • MINOR: New features, backward compatible

  • PATCH: Bug fixes, backward compatible

  • TAG: Pre-release identifier (beta, rc)

Licensing & entitlements (ties into P4)

Even before cloud, decide:

  • per-seat vs per-org

  • offline mode rules

  • how to map customers to entitlements

For 2026, keep licensing minimal but clean; P4 can harden it.

Support Plan (Updated Feb 13, 2026)

Support Toolkit

Component

Status

Description

Export Diagnostics

⏳ Planned

“Export diagnostics” button in CV → zips logs, registry state, AutoCAD version

Known Issues Doc

✅ Created

See Bug Log below

Rollback Procedure

✅ Documented

Restore from App Store uninstall or VM snapshot

Compatibility Matrix

✅ Validated

XP/Vista/Win7/Win10x32 fully supported

Auto-Config Script

✅ Created

Configure-ConstructiVision.ps1

Installation Guide

⏳ Planned

Step-by-step for IT departments

Support Escalation Path

Level

Responder

Response Time

Scope

L1

Self-service

Immediate

Known issues doc, FAQ, compatibility matrix

L2

Email support

24-48 hours

Installation issues, config problems

L3

Remote session

By appointment

Complex issues requiring screen sharing

L4

Engineering

As needed

Bug fixes, feature requests

Common Support Scenarios

Scenario

Solution

Documentation

CV menu doesn’t appear

Run Configure-ConstructiVision.ps1

See “Menu Not Loading” in FAQ

AutoCAD not detected

Verify AC installed, run AutoCAD once, re-run script

Check registry R15.0\ACAD-1:409

VLX fails to load

Check support path in AutoCAD Options

Add CV folder to support path

COM automation fails (x64)

Use 32-bit app or upgrade to 64-bit AutoCAD

Document in FAQ

csv.arx error on load

Ignore - CV works without it

Non-critical, documented in Bug 4

64-bit compatibility

Test with nanoCAD (free) or 64-bit AutoCAD 2010+

See nanoCAD testing results

Support Metrics to Track

  • Installation success rate (target: >95%)

  • Time to resolution (target: <24 hours for L2)

  • Support tickets per installation (target: <5%)

  • Customer satisfaction score

Bug Log (Frozen Feb 13, 2026 — See Doc 32)

Note

This bug log covers the original 9 installer/compatibility bugs from Phase 1A-1D (Feb 13). The authoritative bug tracker is now 32-tb11-bug-tracker.md which tracks all 21 bugs including source-mode bugs (1-18), deployment bugs (19-21), DFMEA cross-references, and detailed root cause analysis.

Original installer/compatibility bugs from CV360 analysis and Win10 testing:

Active Bugs

ID

Severity

Title

Status

Workaround

Owner

BUG-001

🔴 Critical

Profile detection writes to .DEFAULT instead of HKCU

✅ BYPASSED

Auto-config script writes to correct HKCU path

Deploy

BUG-002

🟡 Medium

acad.exe crash on Vista/Win7 during menu compilation

✅ BYPASSED

Pre-compiled menus; Startup Suite approach avoids crash

Deploy

BUG-003

🟡 Medium

Version registry key says 3.2, installer is 3.60

✅ N/A

None needed - cosmetic (legacy installer only)

N/A

BUG-004

🟡 Medium

csv.arx fails to load (ObjectARX incompatibility)

✅ BYPASSED

CV works without ARX - non-critical component

N/A

BUG-005

🟢 Low

LOADCTRLS downgrade from 13 to 4

✅ N/A

Legacy installer only - irrelevant for .bundle

N/A

BUG-006

🟢 Low

LocalServer32 path uses forward slashes

✅ N/A

None needed - Windows accepts forward slashes

N/A

BUG-007

🟢 Low

CLSID name case change (Visual LISP → Visual Lisp)

✅ N/A

None needed - cosmetic

N/A

BUG-008

🟡 Medium

ACAD path includes CD drive letter (E:)

✅ BYPASSED

Auto-config script uses local path only

Deploy

BUG-009

🔴 Critical

Win10x64 COM automation fails (32-bit CLSID)

⏳ PLANNED

Use 64-bit AutoCAD (purchase March)

@chadw

TEST-001

🔧 Testing

nanoCAD 64-bit VLX compatibility

🔧 IN PROGRESS

Free 64-bit LISP platform validation

@chadw

Bug Details

BUG-001: Profile Detection Failure

Root Cause: InstallShield script uses RegDBSetDefaultRoot(HKEY_USERS) and resolves “current user” SID incorrectly, falling back to .DEFAULT (S-1-5-18) — the Local System service account.

Impact: Startup apps (pcms2.arx, csv.vlx), search path additions, and menu configuration written to wrong profile. When a standard user logs in, AutoCAD won’t auto-load CV components.

Solution: Auto-config script (Configure-ConstructiVision.ps1) writes startup entries to correct path:

HKCU\Software\Autodesk\AutoCAD\R15.0\ACAD-1:409\Profiles\<<Unnamed Profile>>\Dialogs\Appload\Startup

BUG-002: AutoCAD Crash During Menu Compilation

Root Cause: CV3.60 installer launches AutoCAD to compile menus (csv.mnc/csv.mnr) on Vista/Win7. AutoCAD 2000 was not designed for Vista+ and crashes under UAC/WFP.

Impact: Windows Error Reporting captures AppCrash_acad.exe during installation.

Solution: Use Startup Suite approach (csvmenu.lsp + csv.vlx). Menu loads at AutoCAD startup, no compilation needed during install.

BUG-004: csv.arx Incompatibility

Root Cause: csv.arx compiled for AutoCAD 2000 ObjectARX SDK. ObjectARX has strict version binding.

Impact: Error message on load: “Unable to load csv.arx”

Solution: Ignore. CV works fully without ARX extension. All core functionality is in VLX.

BUG-009: Win10x64 COM Automation Failure

Root Cause: AutoCAD 2000 is 32-bit only. Installs COM CLSID under HKCR\CLSID\{...}. 64-bit Windows apps look in HKCR\Wow6432Node\CLSID\{...} for 32-bit COM servers, but AC2000 doesn’t register there.

Impact: Python/PowerShell running as 64-bit cannot connect to AutoCAD.Application COM object.

Attempted Fix (Failed): Manually created WOW6432Node registry entries — still fails. 32-bit AC2000 cannot service 64-bit COM clients.

Solution: Purchase 64-bit AutoCAD (2010+) which registers both 32-bit and 64-bit COM interfaces. Planned for March 2026.

Closed Bugs

ID

Title

Closed Date

Resolution

(none yet)

Bug Severity Definitions

Severity

Definition

Response Time

🔴 Critical

Blocks installation or core functionality

Immediate

🟡 Medium

Affects some users, workaround exists

1-2 weeks

🟢 Low

Cosmetic or edge case

Backlog

Support readiness

Minimum support toolkit:

  • ⏳ “Export diagnostics” button (planned for App Store release)

  • ✅ Known issues + workarounds (see Bug Log above + doc 32)

  • ✅ Rollback procedure (App Store uninstall or VM snapshot)

  • ✅ Compatibility matrix (XP, Vista, Win7, Win10x32, Win10x64)

Deliverables by end of Q1 (Feb 13 - Mar 31) 🆕

  • ✅ Platform compatibility validated (XP/Vista/Win7/Win10x32)

  • ✅ Auto-config script created (Configure-ConstructiVision.ps1)

  • ✅ Bug log established (21 bugs in doc 32, 17 fixed)

  • ✅ Support plan drafted

  • ✅ TB11 source-mode validation — 18 bugs found and fixed on VM 108

  • ✅ VLX deployment validation — deferred loading via acaddoc.lsp confirmed on VM 104

  • 🔧 GSCI alpha testing (Feb 17 - Mar 14, VMs 201-202)

    • Week 1: Installation validation reports

    • Week 2: Workflow feedback from real GSCI projects

    • Week 3: Bug reports with reproduction steps

    • Wrap-up: Alpha test summary, App Store requirements impact

  • ❌ WiX installer v1 → ABORTED, pivoting to .bundle/App Store

  • ⏳ 64-bit AutoCAD purchased (Target: March 2026)

Deliverables by end of Q3 (updated)

  • ⏳ .bundle format packaging complete (replaces WiX MSI)

  • ⏳ Transition from VM to App Store distribution

  • ⏳ ADN Developer membership active

  • ⏳ App Store submission package ready (screenshots, docs, EULA)

  • ⏳ Code signing certificate (OV or EV)

  • Release notes template

  • Support playbook draft

Deliverables by end of Q4 (required)

  • Autodesk App Store listing live (or in final review)

  • White Cap beta testing complete (potential beta customer)

  • Release candidate .bundle build

  • Final demo build

  • Customer onboarding guide

  • Partner pilot package

  • Distribution metrics dashboard

    • App Store downloads

    • Conversion rates

    • Support ticket volume