Windows local files and legacy WSL projects
Open a Windows project folder and preserve an older WSL project when moving its saved files.
In Digital Design Studio for Windows 2.1.2.3, open a folder stored on this PC from Local → Projects on this PC → Open project folder. The legacy WSL sections below describe recovery in an older installation. Keep the original distribution and saved files while preparing a verified copy.
Preserve and migrate an existing project
Keep the original distribution, files, Git data and unsaved work until recovery and a verified export/copy are complete. Check hashes, case-sensitive names, collisions, links and destination ownership. Unresolved transactions must be recovered by their original owner. Linux inode/UID identity, licence/device trust, signed execution qualifications and transaction journals are not Windows or Cloud authority. Do not delete a distribution or silently open a WSL path as a Windows root.
Legacy: Choose the right project location
A WSL project keeps source and Linux engine work in the selected distribution’s Linux filesystem. The Windows app supplies the window, editor and connection. A Windows-local project uses a different adapter; choose the host deliberately before editing.
Use an existing x86-64 Ubuntu 24.04 WSL2 distribution with a non-root default user. Keep the project under the Linux user’s directory, such as /home/your-user/projects/demo. /mnt/c and network shares do not satisfy this Linux workspace contract.
Legacy: Check and connect
Powershell
wsl --list --verbose
Confirm that the intended distribution is listed as WSL version 2. The app’s project connection does not install a distribution.
Select the Linux project from the Windows app using its WSL project path, for example
\\wsl.localhost\Ubuntu-24.04\home\your-user\projects\demo.If the installed app offers backend preparation, review it and use the matching bundled backend. A manually substituted helper can be incompatible.
Confirm the distribution, user, project root and connection status. Open and save one small text file before performing a transaction or running an engine.
Legacy: Files, Git and engines
Saved text, project settings and supported Source Control operations run through the Linux workspace. File writes check the saved revision. WSL-backed Git reads and edits use Linux Git for that project. A connected workspace does not enable every engine, binary viewer or remote Git transfer; check the action shown by your installed host.
Legacy: Reconnect after changes
Change or message | Recovery |
|---|---|
WSL restarted | Preserve unsaved text, explicitly reconnect, and reread files before saving. |
Project directory was moved or replaced | Reopen the intended directory; do not reuse an old connection for a new folder identity. |
Root user, shared permissions or Windows mount rejected | Select a user-owned Linux folder with the intended non-root user. |
Save outcome is uncertain | Reload and inspect the current saved content before repeating the write. |
See Windows installation, Local workspaces and Diagnostics for package, backup and error-reporting steps.
Use a Windows folder
Choose Local → Projects on this PC → Open project folder. Select a normal Windows folder for the project. WSL paths are not opened by this host.
Check the project root, save a harmless source edit and reopen it. Free local tools, including local Git, work without sign-in; sign in for AI, Cloud, remote Git and account services. No device licence is needed for My PC.
The WSL steps above are for an older app that exposes that connection. Recover and verify the original project there before copying files; keep the original distribution and do not copy credentials or transaction journals as authority.