I started my learning of Azure Functions, I.e. Service-less computing by writing this .NET Core Console application which calls the following Azure Functions each with a different trigger type. I hosted the console application on GitHub here. You will need the .NET Core runtime installed on your work station to run the console app, check […]
Read More →
The scenarios in which you can and cannot move an Azure App Service are nicely documented here “App Service limitations”. I also wrote an article about this as well here “Moving an Azure App Service”. It is possible to move your Azure App Service between subscriptions and resource groups. Like I have stated many times […]
Read More →When you enable AlwaysOn it means that the application pool will not be shutdown after the idle timeout threshold is breached. I wrote about this threshold here and here. The point here is that after a cold start of your application, AlwaysOn will send a request to the ROOT of your application. Whatever file is […]
Read More →I worked on this issue and wanted to write it down because I love it when I can execute the WinDbg commands in my “Must use, must know WinDbg commands, my most used” article and find the reason for the problem. I executed !sos.threadpool and did see that the CPUs were pretty high, as seen […]
Read More →Which way did he go George, which way did he go? (*) When you create an Azure Function App, a requirement to complete the operation is the selection or creation of an Azure Storage Account where the content (code, json, etc…), required to run the Azure Functions are to be stored. Make sure the Storage […]
Read More →Azure is so awesome because the features it provides are so very dynamic and flexible. The platform provides a starting point for the fruition of ideas, ideas only limited by ones imagination. With its dynamic nature and the flexibility it delivers to consumers, sometimes you just need a note to get your ideas optimally flowing […]
Read More →According to this “Operating system functionality on Azure App Service” and my interpretation, it means if you attempt to use named pipes (*)(*) for anything other than inter-process communications (*) that it will not work. I was coding some stuff and was getting these errors: SqlException: A network-related or instance-specific error occurred while establishing a […]
Read More →
Here is what I wanted to do. Add some code like this to my ASP.NET application. using System.Diagnostics; … System.Diagnostics.Trace.WriteLine(“System.Diagnostics.Trace.WriteLine() in the Page_Load method”); Trace.Write(“Trace.Write() in the Page_Load method”); System.Diagnostics.Trace.TraceError(“System.Diagnostics.Trace.TraceError() in the Page_Load method”); System.Diagnostics.Trace.TraceWarning(“System.Diagnostics.Trace.TraceWarning() in the Page_Load method”); System.Diagnostics.Trace .TraceInformation(“System.Diagnostics.Trace.TraceInformation() in the Page_Load method”); Then I wanted to write those logs out to […]
Read More →
A method to 100% shutdown the public endpoint of an App Service running in the public tenant is not provided. However, you can create an ILB ASE (which is not a public tenant) or you can restrict the access using an IP Restriction. Here is some information on the detailed feature for setting this up […]
Read More →
I wrote a few articles that discuss how and or why you would need to know the apiVerion api-version when calling Azure REST APIs or making a deployment with an Azure Resource Manager (ARM) template. Azure Function 400 Bad Request How to disable/enable HTTP/2, Azure App Service Using Postman to call Azure REST APIs Make […]
Read More →