[Windows Azure] Building worker role B (email sender) for the Windows Azure Email Service application - 5 of 5.

Building worker role B (email sender) for the Windows Azure Email Service application - 5 of 5.

This is the fifth tutorial in a series of five that show how to build and deploy the Windows Azure Email Service sample application. For information about the application and the tutorial series, see the first tutorial in the series.

In this tutorial you'll learn:

• How to add a worker role to a cloud service project.
• How to poll a queue and process work items from the queue.
• How to send emails by using SendGrid.
• How to handle planned shut-downs by overriding the OnStop method.
• How to handle unplanned shut-downs by making sure that no duplicate emails are sent.

Add worker role BAdd worker role B project to the solution

1. In Solution Explorer, right-click the cloud service project, and choose New Worker Role Project.

   

2. In the Add New Role Project dialog box, select C#, select Worker Role, name the project WorkerRoleB, and click Add.

   

Add referenceAdd a reference to the web project

You need a reference to the web project because that is where the entity classes are defined. You'll use the entity classes in worker role B to read and write data in the Windows Azure tables that the application uses.

1. Right-click the WorkerRoleB project, and choose Add Reference.

   

2. In Reference Manager, add a reference to the MvcWebRole project (or to the web application project if you are running the web UI in a Windows Azure Web Site).

   

Add SCL 2.0 PackageAdd the Storage Client Library 2.0 NuGet package to the project

When you added the project, it didn't automatically get the updated version of the Storage Client Library NuGet package. Instead, it got the old 1.7 version of the package since that is what is included in the project template. Now the solution has two versions of the Windows Azure Storage NuGet package: the 2.0 version in the MvcWebRole and WorkerRoleA projects, and the 1.7 version in the WorkerRoleB project. You need to uninstall the 1.7 version and install the 2.0 version in the WorkerRoleB project.

1. From the Tools menu choose Library Package Manager and then Manage NuGet Packages for Solution.

2. With Installed Packages selected in the left pane, scroll down until you get to the Windows Azure Storage package.

   You'll see the package listed twice, once for the 1.7 version and once for the 2.0 version.

3. Select the 1.7 version of the package and click Manage.

   The check boxes for MvcWebRole and WorkerRoleB are cleared, and the check box for WorkerRoleB is selected.

4. Clear the check box for WorkerRoleB, and then click OK.

5. When you are asked if you want to uninstall dependent packages, click No.

   When the uninstall finishes you have only the 2.0 version of the package in the NuGet dialog box.

6. Click Manage for the 2.0 version of the package.

   The check boxes for MvcWebRole and WorkerRoleA are selected, and the check box for WorkerRoleA is cleared.

7. Select the check box for WorkerRoleA, and then click OK.

Add SCL 1.7 referenceAdd a reference to an SCL 1.7 assembly

Version 2.0 of the Storage Client Library (SCL) does not have everything needed for diagnostics, so you have to add a reference to one of the 1.7 assemblies, as you did earlier for the other two projects.

1. Right-click the WorkerRoleB project, and choose Add Reference.

2. Click the Browse... button at the bottom of the dialog box.

3. Navigate to the following folder:

   C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-10\ref

4. Select Microsoft.WindowsAzure.StorageClient.dll, and then click Add.

5. In the Reference Manager dialog box, click OK.

Add SendGrid packageAdd the SendGrid NuGet package to the project

To send email by using SendGrid, you need to install the SendGrid NuGet package.

1. In Solution Explorer, right-click the WorkerRoleB project and choose Manage NuGet Packages.

   

2. In the Manage NuGet Packages dialog box, select the Online tab, enter "sendgrid" in the search box, and press Enter.

3. Click Install on the Sendgrid package.

   

4. Close the dialog box.

Add project settingsAdd project settings

Like worker role A, worker role B needs storage account credentials to work with tables, queues, and blobs. In addition, in order to send email, the worker role needs to have credentials to embed in calls to the SendGrid service. And in order to construct an unsubscribe link to include in emails that it sends, the worker role needs to know the URL of the application. These values are stored in project settings.

For storage account credentials, the procedure is the same as what you saw in the third tutorial.

1. In Solution Explorer, under Roles in the cloud project, right-click WorkerRoleB and choose Properties.

2. Select the Settings tab.

3. Make sure that All Configurations is selected in the Service Configuration drop-down list.

4. Select the Settings tab and then click Add Setting.

5. Enter "StorageConnectionString" in the Name column.

6. Select Connection String in the Type drop-down list.

7. Click the ellipsis (...) button at the right end of the line to open the Storage Account Connection String dialog box.

8. In the Create Storage Connection String dialog, click the Your subscription radio button.

9. Choose the same Subscription and Account name that you chose for the web role and worker role A.

10. Follow the same procedure to configure settings for the Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString connection string.

Next, you create and configure the three new settings that are only used by worker role B.

1. In the Settings tab of the Properties window, Click Add Setting, and then add three new settings of type String:

   • Name: SendGridUserName, Value: the SendGrid user name that you established in the second tutorial.

   • Name: SendGridPassword, Value: the SendGrid password.

   • Name: AzureMailServiceURL, Value: the base URL that the application will have when you deploy it, for example: http://sampleurl.cloudapp.net.

   

Add code that runs when the worker role starts

1. In the WorkerRoleB project, delete WorkerRole.cs.

2. Right-click the WorkerRoleB project, and choose Add Existing Item.

   

3. Navigate to the folder where you downloaded the sample application, select the WorkerRoleB.cs file in the WorkerRoleB project, and click Add.

4. Open WorkerRoleB.cs and examine the code.

   As you already saw in worker role A, the OnStart method initializes the context classes that you need in order to work with Windows Azure storage entities. It also makes sure that all of the tables, queues, and blob containers you need in the Run method exist.

   The difference compared to worker role A is the addition of the blob container and the subscribe queue among the resources to create if they don't already exist. You'll use the blob container to get the files that contain the HTML and plain text for the email body. The subscribe queue is used for sending subscription confirmation emails.

   publicoverrideboolOnStart(){ServicePointManager.DefaultConnectionLimit=Environment.ProcessorCount;// Read storage account configuration settingsConfigureDiagnostics();Trace.TraceInformation("Initializing storage account in worker role B");var storageAccount =CloudStorageAccount.Parse(RoleEnvironment.GetConfigurationSettingValue("StorageConnectionString"));// Initialize queue storage Trace.TraceInformation("Creating queue client.");CloudQueueClient queueClient = storageAccount.CreateCloudQueueClient();this.sendEmailQueue = queueClient.GetQueueReference("azuremailqueue");this.subscribeQueue = queueClient.GetQueueReference("azuremailsubscribequeue");// Initialize blob storageCloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();this.blobContainer = blobClient.GetContainerReference("azuremailblobcontainer");// Initialize table storagevar tableClient = storageAccount.CreateCloudTableClient();
   tableServiceContext = tableClient.GetDataServiceContext();Trace.TraceInformation("WorkerB: Creating blob container, queue, tables, if they don't exist.");this.blobContainer.CreateIfNotExists();this.sendEmailQueue.CreateIfNotExists();this.subscribeQueue.CreateIfNotExists();var messageTable = tableClient.GetTableReference("Message");
   messageTable.CreateIfNotExists();var mailingListTable = tableClient.GetTableReference("MailingList");
   mailingListTable.CreateIfNotExists();returnbase.OnStart();}

   The Run method processes work items from two queues: the queue used for messages sent to email lists (work items created by worker role A), and the queue used for subscription confirmation emails (work items created by the subscribe API method in the MvcWebRole project).

   publicoverridevoidRun(){CloudQueueMessage msg =null;Trace.TraceInformation("WorkerRoleB start of Run()");while(true){try{bool messageFound =false;// If OnStop has been called, return to do a graceful shutdown.if(onStopCalled ==true){Trace.TraceInformation("onStopCalled WorkerRoleB");
               returnedFromRunMethod =true;return;}// Retrieve and process a new message from the send-email-to-list queue.
           msg = sendEmailQueue.GetMessage();if(msg !=null){ProcessQueueMessage(msg);
               messageFound =true;}// Retrieve and process a new message from the subscribe queue.
           msg = subscribeQueue.GetMessage();if(msg !=null){ProcessSubscribeQueueMessage(msg);
               messageFound =true;}if(messageFound ==false){System.Threading.Thread.Sleep(1000*60);}}catch(Exception ex){string err = ex.Message;if(ex.InnerException!=null){
               err +=" Inner Exception: "+ ex.InnerException.Message;}if(msg !=null){
               err +=" Last queue message retrieved: "+ msg.AsString;}Trace.TraceError(err);// Don't fill up Trace storage if we have a bug in either process loop.System.Threading.Thread.Sleep(1000*60);}}}

   This code runs in an infinite loop until the worker role is shut down. If a work item is found in the main queue, the code processes it and then checks the subscribe queue.

   // Retrieve and process a new message from the send-email-to-list queue.
               msg =this.sendEmailQueue.GetMessage();if(msg !=null){ProcessQueueMessage(msg);
                   messageFound =true;}// Retrieve and process a new message from the subscribe queue.
           msg =this.subscribeQueue.GetMessage();if(msg !=null){ProcessSubscribeQueueMessage(msg);
               messageFound =true;}

   If nothing is waiting in either queue, the code sleeps 60 seconds before continuing with the loop.

   if(messageFound ==false){System.Threading.Thread.Sleep(1000*60);}

   The purpose of the sleep time is to minimize Windows Azure Storage transaction costs, as explained in the previous tutorial.

   When a queue item is pulled from the queue by the GetMessage method, that queue item becomes invisible for 30 seconds to all other worker and web roles accessing the queue. This is what ensures that only one worker role instance will pick up any given queue message for processing. You can explicitly set this exclusive lease time (the time the queue item is invisible) by passing a visibility timeout parameter to the GetMessage method. If the worker role could take more than 30 seconds to process a queue message, you should increase the exclusive lease time to prevent other role instances from processing the same message.

   On the other hand, you don't want to set the exclusive lease time to an excessively large value. For example, if the exclusive lease time is set to 48 hours and your worker role unexpectedly shuts down after dequeuing a message, another worker role would not be able to process the message for 48 hours. The exclusive lease maximum is 7 days.

   The GetMessages method (notice the "s" at the end of the name) can be used to pull up to 32 messages from the queue in one call. Each queue access incurs a small transaction cost, and the transaction cost is the same whether 32 messages are returned or zero messages are returned. The following code fetches up to 32 messages in one call and then processes them.

   foreach(CloudQueueMessage msg in sendEmailQueue.GetMessages(32)){ProcessQueueMessage(msg);
       messageFound =true;}

   When using GetMessages to remove multiple messages, be sure the visibility timeout gives your application enough time to process all the messages. Once the visibility timeout expires, other role instances can access the message, and once they do, the first instance will not be able to delete the message when it finishes processing the work item.

   The Run method calls ProcessQueueMessage when it finds a work item in the main queue:

   privatevoidProcessQueueMessage(CloudQueueMessage msg){// Log and delete if this is a "poison" queue message (repeatedly processed// and always causes an error that prevents processing from completing).// Production applications should move the "poison" message to a "dead message"// queue for analysis rather than deleting the message.           if(msg.DequeueCount>5){Trace.TraceError("Deleting poison message:    message {0} Role Instance {1}.",
               msg.ToString(),GetRoleInstance());
           sendEmailQueue.DeleteMessage(msg);return;}// Parse message retrieved from queue.// Example:  2012-01-01,0123456789email@domain.com,0var messageParts = msg.AsString.Split(newchar[]{','});var partitionKey = messageParts[0];var rowKey = messageParts[1];var restartFlag = messageParts[2];Trace.TraceInformation("ProcessQueueMessage start:  partitionKey {0} rowKey {1} Role Instance {2}.",
           partitionKey, rowKey,GetRoleInstance());// If this is a restart, verify that the email hasn't already been sent.if(restartFlag =="1"){var retrieveOperationForRestart =TableOperation.Retrieve<SendEmail>(partitionKey, rowKey);var retrievedResultForRestart = messagearchiveTable.Execute(retrieveOperationForRestart);var messagearchiveRow = retrievedResultForRestart.ResultasSendEmail;if(messagearchiveRow !=null){// SendEmail row is in archive, so email is already sent. // If there's a SendEmail Row in message table, delete it,// and delete the queue message.Trace.TraceInformation("Email already sent: partitionKey="+ partitionKey +" rowKey= "+ rowKey);var deleteOperation =TableOperation.Delete(newSendEmail{PartitionKey= partitionKey,RowKey= rowKey,ETag="*"});try{
                   messageTable.Execute(deleteOperation);}catch{}
               sendEmailQueue.DeleteMessage(msg);return;}}// Get the row in the Message table that has data we need to send the email.var retrieveOperation =TableOperation.Retrieve<SendEmail>(partitionKey, rowKey);var retrievedResult = messageTable.Execute(retrieveOperation);var emailRowInMessageTable = retrievedResult.ResultasSendEmail;if(emailRowInMessageTable ==null){Trace.TraceError("SendEmail row not found:  partitionKey {0} rowKey {1} Role Instance {2}.",
               partitionKey, rowKey,GetRoleInstance());return;}// Derive blob names from the MessageRef.var htmlMessageBodyRef = emailRowInMessageTable.MessageRef+".htm";var textMessageBodyRef = emailRowInMessageTable.MessageRef+".txt";// If the email hasn't already been sent, send email and archive the table row.if(emailRowInMessageTable.EmailSent!=true){SendEmailToList(emailRowInMessageTable, htmlMessageBodyRef, textMessageBodyRef);var emailRowToDelete =newSendEmail{PartitionKey= partitionKey,RowKey= rowKey,ETag="*"};
       emailRowInMessageTable.EmailSent=true;var upsertOperation =TableOperation.InsertOrReplace(emailRowInMessageTable);
       messagearchiveTable.Execute(upsertOperation);var deleteOperation =TableOperation.Delete(emailRowToDelete);
       messageTable.Execute(deleteOperation);}// Delete the queue message.
   sendEmailQueue.DeleteMessage(msg);Trace.TraceInformation("ProcessQueueMessage complete:  partitionKey {0} rowKey {1} Role Instance {2}.",
      partitionKey, rowKey,GetRoleInstance());}

   Poison messages are those that cause the application to throw an exception when they are processed. If a message has been pulled from the queue more than five times, we assume that it cannot be processed and remove it from the queue so that we don't keep trying to process it. Production applications should consider moving the poison message to a "dead message" queue for analysis rather than deleting the message.

   The code parses the queue message into the partition key and row key needed to retrieve the SendEmail row, and a restart flag.

   var messageParts = msg.AsString.Split(newchar[]{','});var partitionKey = messageParts[0];var rowKey = messageParts[1];var restartFlag = messageParts[2];

   If processing for this message has been restarted after an unexpected shut down, the code checks the messagearchive table to determine if this email has already been sent. If it has already been sent, the code deletes the SendEmail row if it exists and deletes the queue message.

   if(restartFlag =="1"){var retrieveOperationForRestart =TableOperation.Retrieve<SendEmail>(partitionKey, rowKey);var retrievedResultForRestart = messagearchiveTable.Execute(retrieveOperationForRestart);var messagearchiveRow = retrievedResultForRestart.ResultasSendEmail;if(messagearchiveRow !=null){Trace.TraceInformation("Email already sent: partitionKey="+ partitionKey +" rowKey= "+ rowKey);var deleteOperation =TableOperation.Delete(newSendEmail{PartitionKey= partitionKey,RowKey= rowKey,ETag="*"});try{
                   messageTable.Execute(deleteOperation);}catch{}
               sendEmailQueue.DeleteMessage(msg);return;}}

   Next, we get the SendEmail row from the message table. This row has all of the information needed to send the email, except for the blobs that contain the HTML and plain text body of the email.

   var retrieveOperation =TableOperation.Retrieve<SendEmail>(partitionKey, rowKey);var retrievedResult = messageTable.Execute(retrieveOperation);var emailRowInMessageTable = retrievedResult.ResultasSendEmail;if(emailRowInMessageTable ==null){Trace.TraceError("SendEmail row not found:  partitionKey {0} rowKey {1} Role Instance {2}.",
               partitionKey, rowKey,GetRoleInstance());return;}

   Then the code sends the email and archives the SendEmail row.

   if(emailRowInMessageTable.EmailSent!=true){SendEmailToList(emailRowInMessageTable, htmlMessageBodyRef, textMessageBodyRef);var emailRowToDelete =newSendEmail{PartitionKey= partitionKey,RowKey= rowKey,ETag="*"};
       emailRowInMessageTable.EmailSent=true;var upsertOperation =TableOperation.InsertOrReplace(emailRowInMessageTable);
       messagearchiveTable.Execute(upsertOperation);var deleteOperation =TableOperation.Delete(emailRowToDelete);
       messageTable.Execute(deleteOperation);}

   Moving the row to the messagearchive table can't be done in a transaction because it affects multiple tables.

   Finally, if everything else is successful, the queue message is deleted.

   sendEmailQueue.DeleteMessage(msg);

   The actual work of sending the email by using SendGrid is done by the SendEmailToList method. If you want to use a different service than SendGrid, all you have to do is change the code in this method.

   Note: If you have invalid credentials in the project settings, the call to SendGrid will fail but the application will not get any indication of the failure. If you use SendGrid in a production application, consider setting up separate credentials for the web API in order to avoid causing silent failures when an administrator changes his or her SendGrid user account password. For more information, see SendGrid MultiAuth - Multiple Account Credentials. You can set up credentials at https://sendgrid.com/credentials.

   privatevoidSendEmailToList(string emailAddress,string fromEmailAddress,string subjectLine,string htmlMessageBodyRef,string textMessageBodyRef){var email =SendGrid.GenerateInstance();
       email.From=newMailAddress(fromEmailAddress);
       email.AddTo(emailAddress);
       email.Html=GetBlobText(htmlMessageBodyRef);
       email.Text=GetBlobText(textMessageBodyRef);
       email.Subject= subjectLine;var credentials =newNetworkCredential(RoleEnvironment.GetConfigurationSettingValue("SendGridUserName"),RoleEnvironment.GetConfigurationSettingValue("SendGridPassword"));var transportREST = REST.GetInstance(credentials);
       transportREST.Deliver(email);}privatestringGetBlobText(string blogRef){var blob = blobContainer.GetBlockBlobReference(blogRef);
       blob.FetchAttributes();var blobSize = blob.Properties.Length;using(var memoryStream =newMemoryStream((int)blobSize)){
           blob.DownloadToStream(memoryStream);returnSystem.Text.Encoding.UTF8.GetString(memoryStream.ToArray());}}

   In the GetBlobText method, the code gets the blob size and then uses that value to initialize the MemoryStream object for performance reasons. If you don't provide the size, what the MemoryStream does is allocate 256 bytes, then when the download exceeds that, it allocates 512 more bytes, and so on, doubling the amount allocated each time. For a large blob this process would be inefficient compared to allocating the correct amount at the start of the download.

   The Run method calls ProcessSubscribeQueueMessage when it finds a work item in the subscribe queue:

   privatevoidProcessSubscribeQueueMessage(CloudQueueMessage msg){// Log and delete if this is a "poison" queue message (repeatedly processed// and always causes an error that prevents processing from completing).// Production applications should move the "poison" message to a "dead message"// queue for analysis rather than deleting the message.  if(msg.DequeueCount>5){Trace.TraceError("Deleting poison subscribe message:    message {0}.",
               msg.AsString,GetRoleInstance());
           subscribeQueue.DeleteMessage(msg);return;}// Parse message retrieved from queue. Message consists of// subscriber GUID and list name.// Example:  57ab4c4b-d564-40e3-9a3f-81835b3e102e,contoso1var messageParts = msg.AsString.Split(newchar[]{','});var subscriberGUID = messageParts[0];var listName = messageParts[1];Trace.TraceInformation("ProcessSubscribeQueueMessage start:    subscriber GUID {0} listName {1} Role Instance {2}.",
           subscriberGUID, listName,GetRoleInstance());// Get subscriber info. string filter =TableQuery.CombineFilters(TableQuery.GenerateFilterCondition("PartitionKey",QueryComparisons.Equal, listName),TableOperators.And,TableQuery.GenerateFilterCondition("SubscriberGUID",QueryComparisons.Equal, subscriberGUID));var query =newTableQuery<Subscriber>().Where(filter);var subscriber = mailingListTable.ExecuteQuery(query).ToList().Single();// Get mailing list info.var retrieveOperation =TableOperation.Retrieve<MailingList>(subscriber.ListName,"mailinglist");var retrievedResult = mailingListTable.Execute(retrieveOperation);var mailingList = retrievedResult.ResultasMailingList;SendSubscribeEmail(subscriberGUID, subscriber, mailingList);
   
   subscribeQueue.DeleteMessage(msg);Trace.TraceInformation("ProcessSubscribeQueueMessage complete: subscriber GUID {0} Role Instance {1}.",
       subscriberGUID,GetRoleInstance());}

   This method performs the following tasks:

   • If the message is a "poison" message, logs and deletes it.
   • Gets the subscriber GUID from the queue message.
   • Uses the GUID to get subscriber information from the MailingList table.
   • Sends a confirmation email to the new subscriber.
   • Deletes the queue message.

   As with emails sent to lists, the actual sending of the email is in a separate method, making it easy for you to change to a different email service if you want to do that.

   privatestaticvoidSendSubscribeEmail(string subscriberGUID,Subscriber subscriber,MailingList mailingList){var email =SendGrid.GenerateInstance();
       email.From=newMailAddress(mailingList.FromEmailAddress);
       email.AddTo(subscriber.EmailAddress);string subscribeURL =RoleEnvironment.GetConfigurationSettingValue("AzureMailServiceURL")+"/subscribe?id="+ subscriberGUID +"&listName="+ subscriber.ListName;
       email.Html=String.Format("<p>Click the link below to subscribe to {0}. "+"If you don't confirm your subscription, you won't be subscribed to the list.</p>"+"<a href=\"{1}\">Confirm Subscription</a>", mailingList.Description, subscribeURL);
       email.Text=String.Format("Copy and paste the following URL into your browser in order to subscribe to {0}. "+"If you don't confirm your subscription, you won't be subscribed to the list.\n"+"{1}", mailingList.Description, subscribeURL);
       email.Subject="Subscribe to "+ mailingList.Description;var credentials =newNetworkCredential(RoleEnvironment.GetConfigurationSettingValue("SendGridUserName"),RoleEnvironment.GetConfigurationSettingValue("SendGridPassword"));var transportREST = REST.GetInstance(credentials);
       transportREST.Deliver(email);}

TestingTesting Worker Role B

1. Run the application by pressing F5.

2. Go to the Messages page to see the message you created to test worker role A. After a minute or so, refresh the web page and you will see that the row has disappeared from the list because it has been archived.

3. Check the email inbox where you expect to get the email. Note that there might be delays in the sending of emails by SendGrid or delivery to your email client, so you might have to wait a while to see the email. You might need to check your junk mail folder also.

Next stepsNext steps

You have now built the Windows Azure Email Service application from scratch, and what you have is the same as the completed project that you downloaded. To deploy to the cloud, test in the cloud, and promote to production, you can use the same procedures that you saw in the second tutorial. If you chose to build the alternative architecture, see the Windows Azure Web Sites getting started tutorial for information about how to deploy the MVC project to a Windows Azure Web Site.

To learn more about Windows Azure storage, see the following resource:

• Essential Knowledge for Windows Azure Storage (Bruno Terkaly's blog)

To learn more about the Windows Azure Table service, see the following resources:

• Essential Knowledge for Windows Azure Table Storage (Bruno Terkaly's blog)
• How to get the most out of Windows Azure Tables (Windows Azure Storage team blog)
• How to use the Table Storage Service in .NET
• Windows Azure Storage Client Library 2.0 Tables Deep Dive (Windows Azure Storage team blog)
• Real World: Designing a Scalable Partitioning Strategy for Windows Azure Table Storage

To learn more about the Windows Azure Queue service and Windows Azure Service Bus queues, see the following resources:

• Windows Azure Queues and Windows Azure Service Bus Queues - Compared and Contrasted
• How to use the Queue Storage Service in .NET

To learn more about the Windows Azure Blob service, see the following resource:

• How to use the Windows Azure Blob Storage Service in .NET

To learn more about autoscaling Windows Azure Cloud Service roles, see the following resources:

• How to Use the Autoscaling Application Block
• Autoscaling and Windows Azure
• Building Elastic, Autoscalable Solutions with Windows Azure (MSDN channel 9 video)

AcknowledgmentsAcknowledgments

These tutorials and the sample application were written by Rick Anderson and Tom Dykstra. We would like to thank the following people for their assistance:

• Barry Dorrans (Twitter @blowdart)
• Cory Fowler (Twitter @SyntaxC4 )
• Joe Giardino
• Don Glover
• Jai Haridas
• Scott Hunter (Twitter: @coolcsh)
• Brian Swan
• Daniel Wang
• The members of the Developer Advisory Council who provided feedback:
  • Damir Arh
  • Jean-Luc Boucho
  • Carlos dos Santos
  • Mike Douglas
  • Robert Fite
  • Gianni Rosa Gallina
  • Fabien Lavocat
  • Karl Ots
  • Carlos-Alejandro Perez
  • Sunao Tomita
  • Perez Jones Tsisah
  • Michiel van Otegem