When trying to put your LogicApp code in a CICD pipeline, it is always problematic getting your code into a proper template.
Obviously switching to ‘LogicApp Code View’ is an option, but there is a better solution to this problem.
LogicAppTemplate is a PowerShell commandlet that makes is very easy to get the content (even automatically) of the app and save it to disk.
The usage is very simple, open up a PowerShell window and execute the next command:
Check out this gist
Big thanks to Jeff Hollan who authored this!
Recently my team and I were building and debugging LogicApps. At one point we seemed to have disappearing code within our code of these apps.
Obviously something is wrong when we were editing these apps.
Please note that we’ve got many LogicApps with custom code and mappings that we code using the code view, because not all properties can be set using the designer.
The problem arises when you are in ‘Logic App Code View’, and switch to ‘Logic App Designer’.
When switching back, the following popup arises:
In this case, we did not change anything, just switched to designer and back.
But, this is actually what triggers this problem.
Thanks to ‘Versions’ you can quickly see and use WinMerge (or any other tool) to compare the files:
In this sample, the ‘queueType’ magically disappeared, but in other cases other mappings of JSON object were deleted.
Always check, when the designer asks you to ‘Save changes’, if you actually made any changes.
I hope this helps someone out, it gave me and my team a real headache finding this out.
Azure Functions are a great example of how serverless is conquering the cloud world we live in today. There are also many blogs in how-to-write-functions out there, of which the latest use the precompiled functions, in Visual Studio 2017.
Think of a scenario, where you want to test a LogicApp against your function, but that app obviously cannot connect to localhost. You have two options; You can deploy the Functions app to Azure and use remote debugging or you can use your own localhost, with the use of ngrok.
This blog will explain how to debug locally, when using other services in the cloud.
Continue reading “Debugging Azure Functions with LogicApps locally”
Deploying LogicApps with VSTS is easy. You can create a new project using the steps defined in this post and you are all set with deployment settings in place.
But, when you add more and more LogicApps your JSON file will grow and you might be better off putting each LogicApp within its own JSON. Not to speak of the parameters running wild within your files…
This post will explain how to set this up, and what is needed in your VSTS builds to enable the deployment of all the linked apps.
Continue reading “Deploy LogicApps using linked templates”
In this blog I will explain how to separate your settings from your configuration files, when deploying from VSTS. I will show with an example how you can deploy your WebApp and store all variables in VSTS, eliminating the need for developers to have all settings and configurable values within Web.config transformation files.
When deploying your WebApp to various on-premise environments from VSTS, you can use Web.config transformations for separation of your various variables. But, sometimes, the *.Config transformations do not meet your needs.
Continue reading “Using tokens for custom settings in VSTS CICD Pipelines”
There are many methods of testing your application. Great tools like Selenium are widely used, and developers (should) write unit tests for their code. In a DevOps team, we want to run tests automated, ideally using continuous integration tools like TeamCity or Release Manager.
This post will show an example of testing your AngularJS fully automated from within Visual Studio or your continuous integration tooling.
Continue reading “End-to-End testing AngularJS apps from Visual Studio”