microsoft / microsoft/WSL

Detect missing components on windows that does not support WSLC (Reduce requirement on Microsoft.WSL.Containers)

Open
#41,382 4 comments 0 reactions 1 assignee Claimed by @florelis View on GitHub
feature wslc
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

**Is your feature request related to a problem? Please describe.**

I would like to bundle the NuGet package `Microsoft.WSL.Containers` in my program that may run on older Windows that does not support WSLC.
The purpose is to offer container functionality if available and if not the program will still work as today.
I would like to detect WSL compatibility even on unsupported versions of Windows.

**Describe the solution you'd like**

- Reduce requirement to net8.0 (without -windows...) (or net10.0)
- Add a new `ComponentFlag.Windows10` or use an existing flag to indicate WSL is missing.

//Running on unsupported Windows
var missing = WslcService.GetMissingComponents();
missing == ComponentFlag.Windows10

**Describe alternatives you've considered**

Build a secondary exe with the target framework net10.0-windows10.0.26100.0 called from the main exe with target framework net10.0.
Any operation will then require communication between the two processes.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.