What it is
Microsoft's platform for Windows programs. A .NET Framework 4.8 app runs even on Windows 7 with nothing extra installed.
How we use it
The OshaVPN client for Windows 7 is built on .NET Framework 4.8 and WinForms with logic shared with the main client.
Where it helps a business
- Staff or customers need a desktop program rather than a website: with system features, autostart and background work.
- Part of the fleet (tills, warehouses, production lines) runs Windows 7, and nobody will replace hardware for the sake of one program.
How we use it
OshaVPN has three clients sharing their connection logic:
- Windows 10/11: C# and .NET 10 with WPF. The VPN engines run as separate processes, TUN goes through wintun, and WFP "leak protection" filters block traffic bypassing the tunnel during a drop or an engine restart.
- Windows 7: a separate build on .NET Framework 4.8 and WinForms, sharing logic from
OshaVpn.Core. Windows 7 has no TUN, so the client works through the system proxy on the sing-box engine. - Install and updates. An archive with a built-in installer; self-updates download only changed files and roll back the replacement if it fails.
Development is under Android and Windows apps.
Common problems
- New things do not run on old systems. Newer .NET versions and Xray built with a newer Go do not work on Windows 7, hence a separate client.
- Testing on the real system. The Windows 7 client was built and run on Windows 11; the leak protection is covered by a self-check and tests, while a live run on a clean machine with administrator rights is still ahead. This is honestly listed among the limitations.
When you do not need it
If a website or bot solves the task, a Windows program is superfluous: it has to be installed, updated and supported on every machine.