Swimburger

After some recent discussions about the C# events their drawbacks, specifically with async callbacks, I prototyped a couple of alternative event APIs for a Speech-To-Text library that I'm working on.

Please let me know which one you prefer, or better alternatives. 🙇

Option 1

For each event, have an event object to which you can subscribe and unsubscribe.

Swimburger

[CmdletBinding()]
param (
    [Parameter(Mandatory = $True)]
    [string]
    $ChromeDriverOutputPath,    
    [Parameter(Mandatory = $false)]
    [string]
    $ChromeVersion, 
    [Parameter(Mandatory = $false)]
    [Switch]

Swimburger

Param( 
    [Parameter(Mandatory = $true)] 
    [string] $ResourceGroupName, 
    [Parameter(Mandatory = $true)] 
    [string] $AppServiceName, 
    [Parameter(Mandatory = $true)] 
    [string] $SubscriptionId, 
    [Parameter(Mandatory = $true)] 
    [string] $RulePriority
)

Swimburger

Param(
    [Parameter(Mandatory=$true)]
    [string] $Url, 
    [Parameter(Mandatory=$true)]
    [int] $MaxPages, 
    [bool] $IncludeImages = $true, 
    [bool] $StayOnDomain = $true, 
    [bool] $IgnoreFragments = $true)

Add-Type -AssemblyName System.Web

Swimburger

using Hangfire;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddHangfire(configuration => configuration
    .UseSimpleAssemblyNameTypeSerializer()
    .UseRecommendedSerializerSettings()
    .UseInMemoryStorage());

builder.Services.AddHangfireServer();

Swimburger

private static void ChangeEmptyStringToNull(IConfigurationSection configSection)
{
    if (configSection == null) return;
    if (configSection.Value == "") configSection.Value = null;
    foreach (var childConfigSection in configSection.GetChildren())
    {
        ChangeEmptyStringToNull(childConfigSection);
    }
}

Swimburger

{
  "description": "Send Message and Wait until Delivered",
  "states": [
    {
      "name": "Trigger",
      "type": "trigger",
      "transitions": [
        {
          "event": "incomingMessage"
        },

Swimburger

using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.Filters;
using Twilio.AspNet.Core;
using Twilio.TwiML;

namespace TwimlErrorMessageAttribute.Controllers;

[Route("twilio")]
public class TwilioController : Controller
{

Swimburger

<rule name="Add trailing slash" stopProcessing="true">
    <match url="(.*[^/])$" />
    <conditions>
        <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
        <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
    </conditions>
    <action type="Redirect" redirectType="Permanent" url="{R:1}/" />
</rule>  

Swimburger

Fixing breaking changes in the TwiMLResult class for Twilio.AspNet v7 release

The v7 release removed the string and XDocument overload for the TwiMLResult constructor. One solution to this is to stop using string and XDocument and replace the code using the MessagingResponse and VoiceResponse classes, so you can keep using TwiMLResult. However, if you want to keep using string and XDocument, I'll share some before and after code for string and XDocument for both ASP.NET Core MVC and ASP.NET MVC on .NET Framework.

ASP.NET Core MVC

Before v7 using string: