Friday Fact: VS Code Do Not Allow Logic Apps Standard Incremental Workflow Deployment
When working with Logic Apps Standard in Visual Studio Code, it’s important to note that deploying a workflow from one project can overwrite existing
Resolving Git Push Conflicts inside Visual Studio
If, while committing your git changes through Visual Studio, you faced the following errors: Error:Error encountered while pushing to the remote
BizTalk Server CI/CD from zero to hero whitepaper
Historically, deploying BizTalk Server solutions across environments is or can be a complicated process depending on how complex is your solution There are
Microsoft Integration and Azure Stencils Pack for Visio: New version available (v7.3.1)
The full 73 version is complete with the release of v731 This was a massive work of adding new shapes of new services that appear on Azure and changing the
DevOps – Multi environment variables/ groups
This is a topic that has been asked to me a few times, making me wonder how hard it actually was Working with this nearly every day makes us assume some
Logic Apps: CI/CD Part 3- Building your Azure Pipeline
In the previous posts of these series, we've talked about how to build and prepare your Logic App for CI/CD In this last post, I'll show you how to build your
BizTalk Server: Automation Deployment with Azure DevOps – Deploying the Project
Following Sandros last post on BizTalk Server: Automation Deployment with Azure DevOps – Create a build agent, we're going to show how to create the
BizTalk Server: Automation Deployment with Azure DevOps – Create a build agent
Historically, deploying BizTalk Server solutions across environments is or can be a complicated process depending how complex is your solution There are many
Microsoft Integration and Azure Stencils Pack for Visio: New version available (v7.2.0)
I'm not a Dynamics 265 expert, and Dynamics 365 is not my focus area Nevertheless, I couldn't ignore the flood of requests to add the new Dynamics 365 logos,
BizTalk Property Schema Error: The type name ‘…’ does not exist in the type ...
I'm just playing with BizTalk Server doing a small proof-of-concept using BizTalk Server and Azure Service Bus, and I was surprised with a few bunches of