LSENext

KO | EN

gitlite — search

#csharp #php #automation #html #tailwindcss #monitoring #editor #openai #computer-vision #ui

(★ 9)

LSENext (Link Shell Extension Next) — Windows 11 Explorer shell extension. Add symlink/junction/hardlink shortcuts to the context menu.

File Explorer

ZIP Download

- dotnet-tools.json
- - alpha.yml
  - ci.yml
  - release.yml
- icon.png
- zh_cn-demo.png
- - Cargo.toml
- - Cargo.toml
- - Cargo.toml
- AppxManifest.xml
- install.ps1
- LSENext.wxs
- uninstall.ps1
- - en-US.json
  - zh-CN.json
- package.ps1
.gitignore
AGENTS.md
Cargo.lock
Cargo.toml
CLAUDE.md
README.md
REQUIREMENTS.md

# Use via CDN

jsDelivr

jsDelivr serves any public GitHub repository as a CDN with zero setup. Pick a version and a file to get a ready-to-paste link and snippet.

Version

File

Link

Example

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

LSENext is a modern **Windows 11 Explorer shell extension** — a **Link Shell Extension successor** — focused on fast right-click **context menu** creation of:

- **Symbolic links** (symlink)
- **Directory junctions** (junction)
- **Hard links** (hardlink)

> Keywords: Link Shell Extension, Link Shell Extension Next, LSE, Windows 11 context menu, Explorer shell extension, symlink, junction, hardlink.

## Demo

![LSENext demo (zh-CN)](https://raw.githubusercontent.com/SunnyYYLin/LSENext/main/assets/zh_cn-demo.png)

## v0.2.3 Scope

- Pick one or more link sources from Explorer.
- Drop file/directory symbolic links into a target directory.
- Drop file hard links for file sources.
- Drop directory junctions for directory sources.
- Register LSENext as a Windows 11 native Explorer context menu through package identity when setup finishes in the signed-in user's session.
- Unregister the per-user package identity when uninstall finishes in the signed-in user's session.
- Preserve picked state per user at `%LOCALAPPDATA%\LSENext\state.json`.
- Build x64 and arm64 Windows artifacts from GitHub Actions.

## Build

```powershell
cargo test --workspace
```

Packaging is done in GitHub Actions:

- `.github/workflows/alpha.yml` for alpha pre-releases
- `.github/workflows/release.yml` for manual pre-releases

Artifacts are published from the workflow run and written to `artifacts\` during the job.

LSENext

File Explorer

# Use via CDN

Was this content helpful?

Recent Feedback

Download README