I will admit that Regex and I do not speak anymore. In fact, even when we did it was never a really nice conversation and sometimes ended in me cursing and/or leaving the room. If you have had this same experience when creating custom routes in ASP.NET MVC then you know what I'm talking about. IRouteConstraint IRouteConstraint has been around for some time in MVC, but it is also available in Web API too because of course it is based on the same stack for routing. Undoubtedly, the most difficult part of routes is debugging or getting the Regex right. I recently re-lived this experience when having to create a custom API route for a project something...
- Searching docs using a .NET Core global tool
- Cross platform code coverage arrives for .NET Core
- Monitoring issues on Stack Overflow with serverless, CosmosDB and Teams
- Enabling Kubernetes Beta on Docker
- shell.azure.com - look Mom no install!
- Kompose - Docker-Compose to Kubernetes with ease!
- Running the Azure Functions runtime in containers on Kubernetes and more
- Push your images to Azure CDN on publish with gulp
- dotnet new angular to Azure with Docker using CLI
- Angular 2: Application Settings using the CLI Environment Option
- Troubleshooting Installing .NET Core 1.1 RTM on OSX
- Using Apache Web Server as a reverse-proxy for ASP.NET Core
- Deploying an Angular 2 App to Azure with Github