I am writing a bot for a discord. Took libu Discord.Net. I have win7, in which .Net's sockets are not supported (Something is written when trying to run)

I try to use a third-party socket provider, namely WebSocket4Net. When loading this data from nuget along with the discord, an error occurs: As I understood it, the discord could not find a designer with the required signature in WebSocket4Net.

Okay. I'm stubborn. I downloaded the source for WebSocket4Net and indeed, the designer added the required Buffer size parameter. Made it optional by specifying 4048bits.

I collected and tried to replace the library with my own. But Caught the error:

Failed to download file or assembly "WebSocket4Net, Version = 0.15.2.11, Culture = neutral, PublicKeyToken = eb4e154b696bf72a" or one of their dependencies. The found assembly manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

How to get rid of this shit?)

  • one
    Well, the seven are not XP, but you do not want to “persistently” change your development platform for something more modern? Windows 7 stopped receiving basic support on January 13, 2015, and in 2020, extended support will also cease. - AK ♦
  • I read, I smiled, I read it a second time (I thought I missed something) I didn’t miss it, the question was born - what is the difference between wn7 - winserver 2008 (r2) win 8.1, winserver 2012, with the last service pack 4. Graphical interface? I think it's just a curved system. And the missing files are dated 2010. - Digital Core
  • Maybe I'm confusing something, but PublicKeyToken is used if the .dll is configured using a strong name, that is, it must be signed. In this case, it turns out that the manifest of the original assembly does not coincide with what was obtained as a result of the changes. - UserName
  • to replace the library with your own - How was it replaced? - UserName
  • @UserName Yes, I simply deleted the link to my native library and indicated the link to my own. - Alexander Lee

0