ASP.Net Core 1.0 compatibility

[davidetaddeucci]

Any news about the release of Sendgrid C# API libraries compatible with ASP.Net 5.0 (or ASP.Net Core 1.0)?
Just added the reference to the last version of this library on my ASP.Net Core 1.0 using NuGet manager project but there's an error in the dependencies saying that SendGrid API is not compatible with DNX 5.0.

[saluce65]

See issue #146.

[0xdeafcafe]

I wrote a small library for covering a limited usage of the v2 mail send endpoint as we needed coverage at my company. It supports DotNet Core, if you want to use it, it's over here. It would be nice if SendGrid supported DotNet Core on the v3beta branch however.

[davidetaddeucci]

Dear Alex,

thanks a lot for your support.

Unfortunatelt in these days I have opted for an other massive mailing service provider, SparkPost; but I would try also your interesting solution.

Best regards from Tuscany.

Davide

Da: Alex Forbes-Reed [mailto:notifications@github.com]
Inviato: giovedì 19 maggio 2016 15:26
A: sendgrid/sendgrid-csharp sendgrid-csharp@noreply.github.com
Cc: davidetaddeucci info@hybrid.it; Author author@noreply.github.com
Oggetto: Re: [sendgrid/sendgrid-csharp] ASP.Net Core 1.0 compatibility (#221)

I wrote a small library for covering a limited usage of the v2 mail send endpoint as we needed coverage at my company. It supports DotNet Core, if you want to use it, it's over here https://github.com/0xdeafcafe/sendgrid-dotnet . It would be nice if SendGrid supported DotNet Core on the v3beta branch however.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #221 (comment) https://github.com/notifications/beacon/AGRiDHXp7EAPr3r7ewuORYi5vGKOERREks5qDGThgaJpZM4Ib1fA.gif

[thinkingserious]

@davidetaddeucci this is definitely on our roadmap, see: sendgrid/csharp-http-client#1

@0xdeafcafe Awesome! Highest of Fives

I'm going to leave this ticket open to make sure we support .NET Core on the v3beta branch too.

Thanks everyone for your support!

[RyanONeill1970]

Can we have a list of action points and get these agreed by the project owners? I can then sign a CLA and work on some bits.

From what I understand, the SendGrid project that handles the API v3 calls only has 3 points that need addressing to turn it into a Portable Class Library that can be used by the different .Net variants.

The Mail project (in the same solution) however has that huge dependency on System.Net.Mail (which will be ported, but they only seem to have started it just a few days back, see https://github.com/dotnet/corefx/issues/1006 ). I suggest splitting the projects so that the API can go fully PCL and be used by .Net core.

If the project owners think this is OK and can split the solution then I can list the points required to convert the API to a PCL based class.

It would mean effectively stopping working on the older Mail project until .Net core catches up with a new implementation of System.Net.Mail.

[thinkingserious]

@RyanONeill1970,

Thank you for the feedback!

So far we have two pull requests that are attempting a solution: https://github.com/sendgrid/csharp-http-client/pulls. Have you checked those out? If so, what do you think?

[RyanONeill1970]

I was talking about the API3 beta3 branch at https://github.com/sendgrid/sendgrid-csharp/tree/v3beta , the branch you pointed to is a lower level one I think (not so strongly typed). However, those pull requests look good. They'll need to be re-done though as I'm sure you are aware, a new beta came out last week which overlapped them. Looks like you have plenty of help anyway, I'll stand back and watch. Thanks

[thinkingserious]

Yes, the pull requests refer to the HTTP client that the v3beta version of
this library depends upon. I'm thinking if we get it right there, making
the necessary changes in this project should be straight forward.

Thanks for your support!

http://www.sendgrid.com
Elmer Thomas
Developer Experience Engineer | Product

On Mon, May 23, 2016 at 9:03 AM, RyanONeill1970 notifications@github.com
wrote:

I was talking about the API3 beta3 branch at
https://github.com/sendgrid/sendgrid-csharp/tree/v3beta , the branch you
pointed to is a lower level one I think (not so strongly typed).
However, those pull requests look good.

They'll need to be re-done though as I'm sure you are aware, a new beta
came out last week which overlapped them.

Looks like you have plenty of help anyway, I'll stand back and watch.

Thanks

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#221 (comment)

[cleftheris]

Hi all any updates?

[thinkingserious]

@cleftheris

Thanks for checking in!

We have one signed CLA from @PaitoAnderson, but I was hoping to get one for this pull request from @Gekctek also: sendgrid/csharp-http-client#2 so that we could compare notes and possibly merge solutions.

That said, we just took this library out of beta yesterday (along with our 6 others) and we will likely be spending a few weeks ironing out bugs before we come back to enhancements such as this one.

[bdparrish]

@thinkingserious

I am following this update closely. Is there any update for this, so that it can be used with Azure Developer Services?

[yellowsix]

For anyone who just needs the basic functionality of sending email via the SendGrid API from a .NET Core application, it's actually pretty easy to use the REST API directly. The C# API in this library was definitely written by someone who is not a .NET developer... it is very disorienting to use with the weird dynamic type stuff and lack of typical naming for async methods and the such. To actually send an email you only need a few lines of code:

    // you can/should reuse the http client instance for multiple requests, 
    // then Dispose when done with it. I recommend making a singleton class
    // with this client as a member, and registering it in Startup.cs of your ASP.NET Core app, 
    // just as an example
    var client = new HttpClient();
    client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", "your api key");
    client.BaseAddress = new Uri("https://api.sendgrid.com/v3/");

    // sending JSON to the API is as easy as a single line of code:
    var response = await client.PostAsync("mail/send", new StringContent(json, Encoding.UTF8, "application/json"));

And to get the json string to send, you can make a little object model on the REST API here:
https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html

For example, 5 minutes of coding gets you this:

        public class SendGridMessage
        {
            public const string TYPE_TEXT = "text";
            public const string TYPE_HTML = "text/html";

            public List<SendGridPersonalization> personalizations { get; set; }
            public SendGridEmail from { get; set; }
            public List<SendGridContent> content { get; set; }

            public SendGridMessage() { }

            public SendGridMessage(SendGridEmail to, string subject, SendGridEmail from, string message, string type = TYPE_HTML)
            {
                personalizations = new List<SendGridPersonalization> { new SendGridPersonalization { to = new List<SendGridEmail> { to }, subject = subject } };
                this.from = from;
                content = new List<SendGridContent> { new SendGridContent(type, message) };
            }
        }

        public class SendGridPersonalization
        {
            public List<SendGridEmail> to { get; set; }
            public string subject { get; set; }
        }

        public class SendGridEmail
        {
            public string email { get; set; }
            public string name { get; set; }

            public SendGridEmail() { }

            public SendGridEmail(string email, string name = null)
            {
                this.email = email;
                this.name = name;
            }
        }

        public class SendGridContent
        {
            public string type { get; set; }
            public string value { get; set; }

            public SendGridContent() { }

            public SendGridContent(string type, string content)
            {
                this.type = type;
                value = content;
            }
        }

Then you can use JSON.NET to serialize your object as a string:

        public async Task SendEmailAsync(string to, string subject, string fromAddress, string fromName, string message)
        {
            var msg = new SendGridMessage(new SendGridEmail(to), subject, new SendGridEmail(fromAddress, fromName), message);
            try
            {
                string json = JsonConvert.SerializeObject(msg);
                var response = await _httpClient.PostAsync("mail/send", new StringContent(json, Encoding.UTF8, "application/json"));

                // this is just a rough example of handling errors
                if (!response.IsSuccessStatusCode)
                {
                    // see if we can read the response for more information, then log the error
                    string errorJson = await response.Content.ReadAsStringAsync();
                    throw new Exception($"SendGrid indicated failure, code: {response.StatusCode}, reason: {errorJson}");
                }

            }
            catch (Exception ex)
            {
                // example using a fictional object "_logger" that can log exceptions for you
                await _logger.LogExceptionAsync(ex);
            }
        }

In this example, the HttpClient created above is stored as _httpClient in a class that I have for sending emails. Included is some rough example of logging errors, but not failing on an email that can't be sent. Change as appropriate for your situation.

Hopefully that will help some people who don't want to include this library just to send some simple emails from a .NET Core application.