-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove all .NET Framework dependencies #6
Comments
easy there... i'm still using .net framework 4.6.2. |
.NET Standard is the better choice than .NET Framework. (for libraries like this) |
Hi Nealculiner You’re absolutely right, .NET Framework is a thing of the past and it’s crucial to move forward with .NET Core, especially with .NET 9 around the corner. Unfortunately, we’re currently dependent on Brevo’s developers to update their SDK. However, wouldn’t it be more practical to consider using curl requests directly instead of relying on an SDK to avoid this kind of issue? Right now, we’re stuck because our Azure app doesn’t recognize FubarCoder, and it’s blocking us. |
I have reached out the brevo support about their plans with the C# SDK. I haven't heard back from them. Does anybody know if they plan to maintain and / or further develop it? |
I've also reached out to Brevo support and am waiting for their response. Despite the development time it might take, I believe it’s safer to create our own C# library by wrapping the CURL API. |
You can just generate your own client using a code generator. I personally use openapitools/openapi-generator. This will generate pretty much the same code as this repo but with much moire up to date references. |
In 2024 .NET Framework is a thing of the past. We are on .NET Core now with NET 9 coming out soon and it's cross platform so this package needs to be able to run on Linux, etc. and not have dependencies that use .NET Framework such as the FubarCoder packages in use. This is a blocker and is breaking integrations. We need an update ASAP please.
The text was updated successfully, but these errors were encountered: