Can we use release pipeline to deploy app on clients on-premises server? - azure-pipelines-release-pipeline

I am just wondering if we can use the Release pipeline service to deploy the build on our clients' on-prem servers or the services are restricted to use within the organization?

Can we use release pipeline to deploy app on client's on-premises server?
Yes.
If you are using the classic UI release pipeline, firstly, you need to create a deployment group on your client's on-premises server and use it in your release pipeline.
Then you can use some tasks to deploy, such as IIS Web App Deploy task, Copy Files task.
If you are using the yaml pipeline, you need to create a self-hosted agent on client's on-premises server.
You can click Self-hosted Windows agents for creating Windows agents, Self-hosted Linux agents for Linux and Self-hosted macOS agents for macOS.
The following steps are similar to those in the classic UI pipeline.

Related

Can we use Azure SSIS IR runtime to move data from on-premise to Azure Sql Database?

I am new to Azure. I have a requirement to move data from on-premise to Azure SQL database. However, I have to use/execute the existing SSIS packages on Azure. I am thinking of using SSIS IR for executing SSIS packages. With this IR, is it also possible to move data from on-premise to Cloud or do I need a self hosted IR as well?
Thanks!
is it also possible to move data from on-premise to Cloud
Yes but you need to join the SSIS-IR to a VNET which in turn has connectivity to on prem.
https://learn.microsoft.com/en-us/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network
VNET connectivity to on prem is achieved with a VPN or Express link from on prem to your VNET. There are varying degrees of complexity.
If you are going to undertake a lot of hybrid network projects (on prem joined to Azure) you should begin provisioning a VPN or Express route now.
According to the official document:
Self-hosted IR:
You can connect to the on-premise SQL Server via Self-hosted IR in Azure Data Factory. You can set up a Copy activity in ADF to copy data from on-premise db to Azure SQL.
You will need to install Self-hosted IR on an on-premises machine or a virtual machine inside a private network.
It has high availability and scalability, you can install Self-hosted IR on multiple compute nodes and form a group.
Azure-SSIS Integration Runtime:
To lift and shift existing SSIS workload, you can create an Azure-SSIS IR to natively execute SSIS packages.
You need to do:
Deploy SSIS packages to Azure.
Create an Azure-SSIS integration runtime in data factory.
Pricing:
Self-hosted integration runtime princing.
SQL Server Integration Services Pricing
After comparing prices, we can see SSIS IR is more expensive than Self-hosted IR.
Conclusion:
I suggest you to use Self-hosted IR directly, it is simpler, more convenient and cheaper.

Azure DevOps Deploying a .NET Desktop App to a local machine

I am having trouble trying to figure out how to get the .ZIP archive which is produced in a build pipeline for a Desktop App.
I would like to get the .ZIP archive deployed to one or more VMs in my test lab (not in the azure cloud).
I have seen tutorials on how to do this for Websites, but none for deploying a .NET Winforms Applications which is produced as a .zip artifact in my pipeline.
Any help in pointing me to some guidance on how to make this happen would be greatly appreciated.
You'll need to install an agent to a machine on your network and put it into an agent pool.
https://social.technet.microsoft.com/wiki/contents/articles/53386.azure-devops-create-configure-agent.aspx
Once you've done this, you'll be able to deploy to machines on your network the same way that an Azure Build Agent can deploy to a machine in Azure.

How can I use msdeploy in GitHub Actions with Cloud Runners?

I am setting up continuous deployment in Windows and it works with self-hosted runner as I have installed Web Deploy in my server but how can I access it using cloud runners?

Testing Windows Store app with Visual Studio Team Services

I'm trying to set up continuous integration testing for a Windows Store (8.1) app on Visual Studio Team Services (formerly Visual Studio Online).
Setting up build was fairly easy, but I have not been able to get it to run my unit tests on a Hosted Agent. So far I have:
Added /t:Publish to the build to produce the test runner .appx
Created a Powershell script to install the appropriate certificates onto the agent
Modified the test search path to find the .appx
Now, I'm getting errors about installing a developer license:
Error: Could not start test run for unit tests for Windows Store app: No valid developer license found for running unit tests for Windows Store apps. Please install/renew your developer license..
It does not appear to be possible to add a developer license strictly from Powershell or Command Prompt, so is there some other way of running the tests on a Hosted Agent?
Assuming you are using vNext build and Universal Windows Platform template by following this article.
As the developer license is deprecated in the Windows 10 operating system, Universal Windows Platform template doesn't require developer license. But if the computer that hosts the build agent will be used to perform unit tests for windows 8.x, developer license must be installed on the computer.
So, there is no way to run tests for Windows 8.1 on Hosted Agent. You need to deploy a Windows build agent or set up an on-premises build controller + build agent to test Windows 8.1 application.

Application sharing

I Have a windows application made using VB.net and Mysql database. I want to install it on a Local network to be used by several users on different windows machines. How best can I do this?
You should have a look at
ClickOnce - A new VB.NET 2005
Deployment Tool
Using ClickOnce Deployment in
VB.NET
ClickOnce: Delivering .NET
Applications Via the Net
ClickOnce Deployment for Windows
Forms Applications
ClickOnce Deployment in .NET
Framework 2.0
You will have to install the application on each computer. But you can have on machine running the MySQL server to which the application will connect. This way all users can access the same data.