Skip to main content

Azure Functions integration with Visual Studio and CI

In one of my latest posts we took a look on Azure Functions and how we can write an Azure Function that extracts the GPS coordinates from a picture and draw them on the picture itself.

In this post we will look on:

  • How we can create and edit an Azure Function directly from Visual Studio
  • Run Azure Function on you development machine
  • Deploy Azure Function from Visual Studio
  • Setup continuous integration

How we can create and edit an Azure Function directly from Visual Studio
Until a few weeks before, we were able to create and manage Azure Functions only from the portal or using the API (e.g. using Power Shell library). Starting from now, there is a new tool for Visual Studio that allow us to create and write functions directly from Visual Studio. 
The tool allow us to run locally our functions and tests them. Pretty cool, especially when you need to write and maintenance more than a dozen of them. The current version is extremely stable. To tell you the truth, is expected to encounter issues, but works great.
The Azure Function tool comes with a Azure Function project template. Under this projects, each function will be added in a separate folder. The structure of the project and each function folder is the same to the one that we can find on Azure Portal, including function.json, project.json and run.csx.

There are multiple templates for functions, for different languages and triggers. I was able to find almost all the actions and binding that you can do from the portal.
For the case that we want to cover to use as trigger creation of a new file in OneDrive, I would recommend to create the function initially in the portal or at least the API Connection. If you already had the API Connection created, than you only need to specify in the binding the write connection - 'onedrive_ONEDRIVE'. You might encounter similar problems when triggers are SaaS or complex sources, but I expect that this will be solved in the future - we are still in beta.

Run Azure Function on you development machine
Running Azure Function on your local machine is like running any other web app locally. The trick is how you trigger different actions. For simple triggers, inputs and outputs things will go very smooth, but for more complex scenarios you might encounter small problems (tools are still in beta now). 
My experience was pretty good with time trigger functions, but for more complex one I had some issues running locally and I preferred to deploy them directly to Azure for now.

Deploy Azure Function from Visual Studio
The deployment is done in the same way as you would do a deployment of a web application. Write click on the project and click Publish. You'll need to specify an existing function app that you already created in the portal or create a new one. 
There is nothing special or different from deploying a web app.

As for an web app, you can attach a debugger to you function and do remote debugging. I'm so exited to see that nowadays remote debugging is simple and you don't need to lose 1 days to configure and to special setup.

Setup continuous integration
As any other services for Azure, Azure Functions is fully integrated with continuous integration system. Different types of repositories are supported, from GitHub to TFS. 
When you want to configure CI, you should remember that you'll configure it for the the Function App instance and not for each Azure Function. The configuration can be found in 'Function app settings > Deploy > Continuous Integration'.

Once you Setup the CI, any change done in your repository will trigger a build and a new deployment. You can have different Function Apps that are register to different branches, allowing us each sub-team has his own deployment and also have different environment in different branches, fully configured with CI.

If you configure as source for CI a repository where you have multiple projects, you might encounter during the CI process the following error:

Unable to determine which solution file to build

In this case don't panic. This happens because the CI is not able to identify what project you want to deploy. To resolve this problem you need to create a filed named '.deployment' in the root of the repository and specify the path to the project. In my case, I have on my GitHub repository the Azure Function project in the following path 'Azure/azure-function-extractgpslocation-onedrive-drawwatermark-git-ci-integration/'. This means that the .deployment' shall have the following content
project = Azure/azure-function-extractgpslocation-onedrive-drawwatermark-git-ci-integration

More about how you can customize the deployment using .deployment and Kudu can be found on this page.

In this post we saw the current integration of Azure Function with Visual Studio and Continuous Integration. Things are looking very good. Even if we are only in beta, the VS Tools are stable and full with features.
In the next post we will take an look on Azure Functions from functionality, features and price perspective. 


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.