Azure DevOps is integrated and independent tools supporting your DevOps practices with any language, any platform and any cloud. Azure DevOps is the platform for developers, testers and integrators. Come up with two major flavors - DevOps Service , and DevOps Server . Main services are Boards , Repos , Pipeline , Test Plans , and Artifacts . Below are details about Services and Server. Let us compare Services and Server options here. Azure DevOps Services Provided as a cloud service Microsoft hosted and managed New capabilities and fixes released every three weeks Simplified server management A transition from capital expenditures (servers and the like) to operational expenditures (subscriptions) Connect over the public internet (for example, https://contoso.visualstudio.com) authenticate with Microsoft account credentials or with Azure AD credentials Azure DevOps Server Installed in your datacenter or your cloud Managed, patched and controlled by you Provides...
Setting up build and release pipeline always tedious and we face many build related issues. Here is one common error I face couple of times while setting app Web or windows apps in Azure DevOps After placing the code in repos, and creating the build pipeline and run it, you can face the following error ##[error]D:\a\8\s\<your solution file>.sln.metaproj(0,0): Error MSB4126: The specified solution configuration "release|$(BuildPlatform)" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. To understand what is target platform defined in your project you need to visit or open the solution(.sln) file and review the following sections. In my case, this has been defined as x86 as target platform. ...
On-premise data gateway - one of the important feature/service Azure Fabric platform is using to bring your on-premise data into Azure cloud. The data movement is secure and encrypted. You can review my my earlier post https://splaha.blogspot.com/2025/03/use-on-premise-gateway-in-fabric-and.html where I explain how to configure On-premise data gateway using Step 1 and Step 2. In this exaple, I'm going to use the same data conenction to pull my on-premise SQL tables using custom join SQL into Lakehouse. The entire post is self explanatory with step-by-step snapshot. I hope this will help you to understand each and individual steps as well as to execute the same at your end. Let's start with my on-premise SQL server details. As you can see the below picture, it talks about the database Employee where there are two tables EMP and DEPT. I'm going to use the same SQL into Fabric to pull the data. I assume you already created the on-premise data gateway using my earlier post...
Comments
Post a Comment