chore: strong name for System.Net.WebSockets.Client.Managed

[skip ci]

Author: doghappy

src/SocketIOClient.Windows7/SocketIOClient.Windows7.csproj

@@ -3,7 +3,7 @@
   <PropertyGroup>
     <TargetFramework>netstandard2.0</TargetFramework>
     <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
-    <Version>2.2.4</Version>
+    <Version>2.2.4.1</Version>
     <Description>socket.io-client implemention for .NET</Description>
     <PackageLicenseExpression>MIT</PackageLicenseExpression>
     <PackageProjectUrl>https://github.com/doghappy/socket.io-client-csharp</PackageProjectUrl>
@@ -67,8 +67,13 @@
   </ItemGroup>
 
   <ItemGroup>
-    <PackageReference Include="System.Net.WebSockets.Client.Managed" Version="1.0.22" />
     <PackageReference Include="System.Text.Json" Version="5.0.2" />
   </ItemGroup>
 
+  <ItemGroup>
+    <Reference Include="System.Net.WebSockets.Client.Managed">
+      <HintPath>lib\System.Net.WebSockets.Client.Managed.dll</HintPath>
+    </Reference>
+  </ItemGroup>
+
 </Project>

src/SocketIOClient.Windows7/lib/README.md

@@ -0,0 +1,7 @@
+## Why not add this dependency from NuGet?
+
+The System.Net.WebSockets.Client.Managed assembly in NuGet is not signed, it is a weakly named assembly.
+
+So, I generated the il file based on the assembly in NuGet, and finally signed it, and got this strong-named assembly.
+
+https://stackoverflow.com/a/331555/7771913