Azure Funda

In this blog, I am going to cover some of the most frequent issues/requirements people face when developing Azure Functions via Visual Studio. These topics are based on my learnings while developing Azure Functions and I wanted to share the same with community out there. Here are the topics that I will cover in this blog post - Local Debugging of Service Bus Triggered Azure Functions Solving CORS Issue - Local Debugging and after deployment to Azure Run Azure Functions Locally on a different Port Debug Timer Triggered Azure Functions So let's get started. Local Debugging of Service Bus Triggered Azure Functions When you try to debug your Service Bus triggered Azure Function locally, you would need to ensure that there are no other listeners active for your Service Bus Topic and Subscription. Listeners here refer to other people trying to debug on same Service Bus, Topic and Subscription, other Azure Functions or any WebJobs deployed on Azure and running c...

Recently, I was building an Azure Function from Visual Studio and encountered an issue with the auto generated Function.cs class file. My requirement was to create an Azure Function that would get triggered as soon as we receive a message on an Azure Service Bus Topic. For this I tried to use the Project template available in Visual Studio 2017. Unfortunately, when I tried to provide all the required values, and run the function, I got following error: First you get a warning which says: Warning: Cannot find value named 'Endpoint=sb:......' in local.settings.json that matches 'connection' property set on 'serviceBusTrigger' in '\Source\repos\FunctionApp1\MyFunction\bin\Debug\net461\Function1\function.json'. You can run 'func azure functionapp fetch-app-settings <functionAppName>' or specify a connection string in local.settings.json. This warning was followed by an error: [2/12/2018 9:48:05 AM] A ScriptHost error has occurre...

I will be using Plugin Registration tool to register Service Endpoint for Azure Service Bus Topic in my trial Microsoft Dynamics 365 CE Instance. Here are the steps to you need to follow: Step 1. Login to your Microsoft Dynamics 365 CE instance using plugin registration tool. Step 2. Once logged in, Press “Ctrl + E”, or from file menu, go to Register -> Register New Service endpoint. Step 3. Enter your Azure Service Bus Connection String in the shown popup, and click OK. Step 4. You will be presented Service Endpoint Registration popup, where you need to enter following details: Name: ASB Topic Endpoint (a friendly name to your service endpoint) Designation Type: Topic Topic Name: test_internal (enter your ASB Topic Name here) Message Format: JSON (can be .NET Binary, and XML as well) User Information Sent: None (can choose to pass on User ID as well) After entering these details, click on Save. Step 5. The Service...