.NET Standard 2.0
dotnet add package WinDivertSharp --version
NuGet\Install-Package WinDivertSharp -Version
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="WinDivertSharp" Version="" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add WinDivertSharp --version
#r "nuget: WinDivertSharp,"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install WinDivertSharp as a Cake Addin
#addin nuget:?package=WinDivertSharp&version=

// Install WinDivertSharp as a Cake Tool
#tool nuget:?package=WinDivertSharp&version=

A safe, minimal .NET binding over WinDivert

Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows net7.0 net7.0-android net7.0-ios net7.0-maccatalyst net7.0-macos net7.0-tvos net7.0-windows
.NET Core netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.0 netstandard2.1
.NET Framework net461 net462 net463 net47 net471 net472 net48 net481
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen40 tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.
  • .NETStandard 2.0

    • No dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on WinDivertSharp:

Package Downloads

Transparent filtering proxy engine for Windows.

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on WinDivertSharp:

Repository Stars
Tool that limits bandwidth of devices on the same network without access.
Version Downloads Last updated 5,582 9/7/2018 1,200 7/26/2018
1.4.3 686 7/22/2018

Changes this to an unsafe library. Users must now enable unsafe code and perform raw pointer access, just like using the real native library. The reason for this is that we're getting mysterious errors that I can't even be bothered to attempt to fully understand by holding the user's hand like a baby and trying to hide pointer access away from them. If a user doesn't know to perform null checks, or thinks that there's such a thing as "safe" code, then they simply need to go away and hush now.