You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft has stopped supporting the individual ASP.NET Core libraries, now requiring web projects to depend on the full ASP.NET Core SDK.
The current implementation of the Webhook Receivers (e.g.. SendGrid, Twilio, Facebook) libraries that are reading from HTTP requests depend on some of the discontinued ASP.NET Core libraries: although this is not an immediate issue, it might become a demand to transition to the new pattern.
Expected Benefits
The Webhook Receiver libraries will be future-proof (at least for a while: until Microsoft won't change the dependency strategy again), and will not cause incompatibility issues with the new versions of the SDKs.
Possible Side Effects
Applications using the older versions of the SDKs might be forbidden from using the new Deveel Webhooks Receiver libraries
Microsoft has stopped supporting the individual ASP.NET Core libraries, now requiring web projects to depend on the full ASP.NET Core SDK.
The current implementation of the Webhook Receivers (e.g.. SendGrid, Twilio, Facebook) libraries that are reading from HTTP requests depend on some of the discontinued ASP.NET Core libraries: although this is not an immediate issue, it might become a demand to transition to the new pattern.
Expected Benefits
The Webhook Receiver libraries will be future-proof (at least for a while: until Microsoft won't change the dependency strategy again), and will not cause incompatibility issues with the new versions of the SDKs.
Possible Side Effects
Applications using the older versions of the SDKs might be forbidden from using the new Deveel Webhooks Receiver libraries
Further Reading
The text was updated successfully, but these errors were encountered: