[Forums] Asynchronous programming in .net Extensions

Mikko Nieminen wrote:

After my first post, I had refactored the code, pretty much as you suggested:

namespace OutSystems.NssSendGridExt {
public class CssSendGridExt: IssSendGridExt {
public void MssSendTestEmail(out string ssResult) {
            TaskSendTestEmail().Wait();
            ssResult = "";
// TODO: Write implementation for action
} // MssSendTestEmail
        static async Task  TaskSendTestEmail()
        {
            var apiKey = "---------redacted-----------";
            var client = new SendGridClient(apiKey);
            var from = new EmailAddress("tmay@inscico.com", "Example User tmay");
            var subject = "Test02: Sending with SendGrid is Fun";
            var to = new EmailAddress("tmay@inscico.com", "Example User tmay");
            var plainTextContent = "and easy to do anywhere, even with C#";
            var htmlContent = "<strong>and easy to do anywhere, even with C#</strong>";
            var msg = MailHelper.CreateSingleEmail(from, to, subject, plainTextContent, htmlContent);
            var response = await client.SendEmailAsync(msg);
        }
    } // CssSendGridExt
} // OutSystems.NssSendGridExt

The code does send an email but it never returns to the caller. I don't see anything strange in this simple code but I'm not familiar with the innards of C# async. My next step would be to write a little standalone scaffolding program to test all of this without the OutSystems overhead. I'm curious as to why this never returns and would want to make sure it is something in my code and not an unwelcome side-effect of using async in an Outsystems Extension.

Also, after reading your post I think I will try using the SendGrid REST API to send emails and WebHooks to get notifications of delivery status etc. That would avoid having to use an Extension. I'll let you guys know how that turns out.

Thanks!