// the find
JeffreySu/WeiXinMPSDK
微信全平台 .NET SDK， Senparc.Weixin for C#，支持 .NET Framework 及 .NET Core、.NET 10.0。已支持微信公众号、小程序、小游戏、微信支付、企业微信/企业号、开放平台、JSSDK、微信周边等全平台。 WeChat SDK for C#.
WeiXinMPSDK is a C# SDK that wraps the entire WeChat platform API — public accounts, mini-programs, WeChat Pay, enterprise WeChat, and the open platform. It's the dominant WeChat .NET SDK in China, actively maintained for 12+ years. If you're building any WeChat integration in C#, this is the library you use; there's no real competitor in this space.
1. Coverage is genuinely complete: public accounts, mini-programs, WeChat Pay V2 and V3, enterprise WeChat, JSSDK, WebSocket — all under one roof with consistent patterns across modules. Once you learn one, the rest follow the same registration/middleware/API-call shape. 2. AccessToken lifecycle management is fully automatic — you just pass AppId and the SDK handles refresh, caching, and expiry. That alone saves a week of plumbing on any new integration. 3. Distributed cache support is pluggable: in-memory, Redis, Memcached, or Dapr, swappable at config time without touching application code. 4. .NET version breadth is real — .NET Framework 4.6+ through .NET 10, including MAUI and Blazor. The net10-mvc sample is kept current and builds against source, so you can see exactly what the latest idioms look like.
1. The repo is Chinese-first. Documentation, issue discussions, and community forums are almost entirely in Chinese. English-speaking developers will hit walls quickly beyond the basic Hello World. 2. The module split means a non-trivial dependency graph — there are 15+ NuGet packages, and the 'Senparc.Weixin.All' meta-package pulls in everything whether you need it or not. Trimming for a minimal footprint is manual work. 3. WeChat Pay V2 is still present and documented despite being officially deprecated. The codebase carries years of legacy surface area, and it's not always obvious which APIs are current vs. vestigial. 4. The MessageHandler pattern is clever but opinionated — it works well for the standard request/response flow, but if you need async streaming, custom middleware ordering, or non-standard webhook shapes, you'll be fighting the abstraction rather than working with it.