Skip to content

feat: Linux & macOS support via Wine (+ artifacts output layout, fixes #1) - #2

Merged
aelmen merged 5 commits into
mainfrom
feat/linux-macos-wine-support
Jul 17, 2026
Merged

aelmen merged 5 commits into
mainfrom
feat/linux-macos-wine-support

Conversation

@aelmen

@aelmen aelmen commented Jul 15, 2026

Copy link
Copy Markdown
Member

Linux & macOS support (via Wine) + .NET 8 artifacts output layout

Runs the DevExpress XAF Model Editor on Linux and macOS by launching the Windows
.NET WinForms .exe through Wine, and adds support for the artifacts output layout.

Launch (non-Windows)

  • Spawn the .exe via wine (xafModelEditor.wineCommand) with a dedicated prefix
    (xafModelEditor.winePrefix, default ~/.wine-modeleditor).
  • Translate absolute path args to Windows form (Z:\…).
  • Set .NET-under-Wine stability env (pure JIT + workstation GC) — loading a large XAF model
    otherwise crashes the CLR with 0x80131506 at the end of model build.

Discovery

  • Auto-detect the editor from a version-scoped XDG dir
    ~/.local/share/xaf-modeleditor/<version>/ (mirrors the Windows layout).
  • Resolve the real home when VS Code runs as a Snap (SNAP_REAL_HOME).

Fixes #1 — artifacts output layout

Also locate the output DLL at <repoRoot>/artifacts/bin/<Project>/<pivot>/<Project>.dll.

Docs

README platform sections, docs/linux-wine-setup.md, and scripts/setup-wine.sh
(installs Wine + the Windows .NET 10 runtimes into the prefix).

Verified end-to-end on Ubuntu (Wine 10.0, .NET 10 runtimes): the full Pineapple model
loads in the editor under Wine.

aelmen and others added 5 commits July 15, 2026 15:22
Run the DevExpress XAF Model Editor (a Windows .NET WinForms app) on Linux and
macOS by launching it through Wine, and support the artifacts output layout.

Launch: spawn the .exe through `wine` on non-Windows (configurable wineCommand/winePrefix),
translate path args to Windows form (Z:\…), and set .NET-under-Wine stability env
(pure JIT + workstation GC) — a large XAF model otherwise crashes the CLR (0x80131506).

Discovery: auto-detect from a version-scoped XDG dir (~/.local/share/xaf-modeleditor/<version>/);
resolve the real home when VS Code runs as a Snap (SNAP_REAL_HOME).

Fixes #1: locate the output DLL in the .NET 8+ artifacts output layout.

Docs: README + docs/linux-wine-setup.md + scripts/setup-wine.sh.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…026)

- Fix the mangled project-structure tree (now a fenced code block).
- Expand installation & setup: per-platform Model Editor prep (Windows + Linux/macOS Wine),
  the new winePrefix/wineCommand settings, and a settings table.
- Refresh examples to 25.2, document the artifacts-layout + CI/CD publish flow.
- Bump copyright year to 2026 (README + LICENSE).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The setup-wine.sh script ships inside the .vsix, but a Marketplace user isn't in the repo,
so './scripts/setup-wine.sh' didn't apply to them. Add a Command Palette command
('XAF Model Editor: Set up Wine (Linux/macOS)') that locates and runs the bundled script,
and document the real bundled path in the README.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
docs/context-menu.png was a 0-byte placeholder, rendering as a broken image (and would
not render on the Marketplace anyway — relative image paths require absolute URLs there).
Drop the reference and the empty file; the numbered Usage steps stand on their own until a
real screenshot is added.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ut (#1)

The standalone Model Editor loads the target project's DLL and resolves its
references from that DLL's folder. A module (class library) doesn't copy its
NuGet dependencies to its own output by default (CopyLocalLockFileAssemblies
defaults to false for libraries), so opening the Model Editor against a module
project in the .NET 8+ artifacts output layout failed with:

  Could not load file or assembly 'DevExpress.Persistent.BaseImpl.EFCore.vXX,
  Culture=neutral, ...'. The system cannot find the file specified.

Extract the artifacts-layout lookup into a testable, vscode-free module and add
a fallback: when the module's own output lacks its dependency closure, load the
same module DLL from a project output that has it (typically the startup
.Blazor/.Win app, whose executable output carries the full closure). Falls back
to the bare module DLL with a clear warning if nothing complete is found.

Validated end-to-end on Linux/Wine against the issue's XafAppSimple sample
(retargeted 26.1 -> 25.2): the Culture=neutral error is reproduced with the bare
module output and resolved via the fallback. A separate Wine text-rendering
crash (GDI GetCharacterPlacement) is tracked independently.

See docs/specs/artifacts-output-layout.md for the full rationale and validation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aelmen
aelmen merged commit 4f0db78 into main Jul 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for solutions using .NET 8 "artifacts output layout"

1 participant