A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

Does Twilio provide a strong-named assembly of the C# helper library?

Twilio does not distribute a strong-named assembly. If you are using the Twilio C# helper library source code and created your own strong-named assembly but are receiving errors, you have several options:

You can "un-sign" the code library project that uses the Twilio assembly. This should resolve any errors, but you will not have a strong-named assembly.
You can use a technique to sign Twilio's DLL without recompiling.
Since Twilio's C# library is open source, you can sign the assemblies yourself in VisualStudio.

Have more questions? Submit a request