Azure Notification Hub：SendTemplateNotificationAsync在.NET Core中是否可用？

Absolutely, SendTemplateNotificationAsync should work seamlessly in your current setup—here’s why, plus key checks to ensure everything runs smoothly:

Key Reasons It’ll Work #

• Preview Hub Compatibility: Azure Notification Hub preview instances support all core notification features, including template-based notifications. The preview label typically means new features are being tested, but standard operations like template sends remain fully functional.
• Your Existing Setup Validates the Foundation: Since you’ve already registered devices successfully and can send test notifications via the Azure Portal, your hub is properly configured with iOS (APNs) credentials, and device registrations are valid. This foundation directly supports template notification sends from code.

Critical Checks to Avoid Issues #

1. Verify Template Registration Matching
   Ensure that when you registered your iOS devices, you associated them with a template that includes placeholder values (e.g., "alert": "$(attendanceMessage)"). The keys in the dictionary you pass to SendTemplateNotificationAsync must exactly match these placeholders (case-sensitive).

2. Map Your ApiAttendanceModel Correctly
   Your model’s fields need to align with the template’s placeholders. For example, if your template uses $(shiftTime) and $(location), your ApiAttendanceModel should expose those properties, and you’ll need to map them to the parameter dictionary in your endpoint:

   var templateParams = new Dictionary<string, string>
   {
       { "shiftTime", model.ShiftTime.ToString() },
       { "location", model.Location }
   };
   

3. Use the Latest SDK
   Make sure you’re using the Azure.Messaging.NotificationHubs NuGet package (the modern replacement for the deprecated Microsoft.Azure.NotificationHubs). This SDK is fully compatible with preview hubs and handles template sends reliably.

Example Implementation Snippet #

Here’s how your endpoint might look with proper SendTemplateNotificationAsync usage:

private readonly NotificationHubClient _notificationHubClient;

// Inject the client via dependency injection (configured with your hub connection string/name)
public AttendanceController(NotificationHubClient notificationHubClient)
{
    _notificationHubClient = notificationHubClient;
}

[HttpPost]
[Route("TestMessage")]
public async Task<IActionResult> NotifyByTemplate([FromBody] ApiAttendanceModel model)
{
    try
    {
        var templateParameters = new Dictionary<string, string>
        {
            // Map model properties to your template placeholders
            { "attendanceMessage", model.NotificationText },
            { "attendanceId", model.AttendanceId.ToString() }
        };

        // Send to all devices, or filter by tags if needed
        var sendOutcome = await _notificationHubClient.SendTemplateNotificationAsync(templateParameters);
        
        return Ok($"Notification dispatched successfully. Status: {sendOutcome.State}");
    }
    catch (Exception ex)
    {
        return BadRequest($"Failed to send notification: {ex.Message}");
    }
}

Debugging Tips if Things Go Wrong #

• Check the Azure Portal > Notification Hub > Monitoring > Logs for detailed error messages (e.g., invalid device tokens, template placeholder mismatches).
• Confirm that the device registrations in your hub are linked to the correct template (you can view this in the Portal under Device Registrations).
• Test with a minimal template and parameter set first to rule out complex mapping issues.

内容的提问来源于stack exchange，提问作者LittleFunny