Ok. So I used Web Apps Migration Assistant to migrate our enterprise web app to Azure. But I am at a total loss now as to how to create a local solution connected to that web app and how to sync everything from Azure into VS Team Services. I've tried to connect via FTP and use Publish from there but I've run into a filename too long issue.
Additional data from comment:
In the short term I've tried Open->Website in VS through FTP but get filename length errors when publishing. So basic question is how do you create a project in VS with EXISTING code in Azure Web App.
The Azure Web App project/files can’t be sync to VS Team Services or local, but the project in VS Team Services can be sync (deploy) to Azure Web App, for this way, you can make changes to your project in Visual Studio and push changes to VS Team Services, then the changes can be sync to Azure Web App.
Simple steps:
Push code to VS Team Services git repository
Configure Continuous deployment for Azure Web App
Make changes and push to VS Team Services git repository
More information, you can refer to: Continuous deployment to Azure for ASP.NET Core, with Visual Studio and Git.
So I recommend that you can push your enterprise web app project to VS Team Services, then refer to previous steps.
Related
We have a App Service Enviroment https://learn.microsoft.com/en-us/azure/app-service/environment/intro I have set up an App in but I am struggling to either publish from my machine (I've added the URLs to my HOSTS file and I can see it in a browser) and cant see a clear way to publish it from Azure Dev Ops (my preferred option).
I'd be happy to be pointed to TFM but everything I find is out of date / not near the options I can see in Dev Ios or Visual Studio (2019 / 2019 Preview).
EDIT: Also note this is a multi project solution (various console apps, an API and a website it is the API / Website I want to publish)
EDIT 2: So "its always DNS" it was a DNS issue in trying to publish from Visual Studio
You can check these two links:
https://learn.microsoft.com/en-us/visualstudio/deployment/quickstart-deploy-to-azure?view=vs-2019
https://learn.microsoft.com/en-us/azure/app-service/deploy-continuous-deployment?tabs=github
If you use Visual Studio, see: Deploy an ASP.NET Web App in Azure App Service.
If you use Azure pipeline, this doc: Deploy an Azure Web App provides a tutorial to build web app and then deploy to an Azure Web App. Also see this video for detailed guidance: Build and deploy to an Azure Web App using VSTS (Quick Starts).
BTW, there are a few useful tools: Azure DevOps Labs, Azure DevOps Services Demo Generator, and DevOps Starter which will help you to get started with Azure DevOps services to automate software delivery and meet business needs.
I have created a Xamarin Android App that uses Azure for the back end. It seems that it would be better to host it in an App Service, but in Visual Studio 2017 Community, the only option seems to be to host it in a Classic Could Service. In VS, I created a Cloud Service project and added the WCF Project as a Role. Is there a better way to do this?
If you can't use Visual Studio Web Deploy, you can use FTP to deploy your compiled project. The FTP information is located in the Overview blade of the App Service. In the same blade, you can also click on the Publish Profile button to download an XML file containing credentials for Web Deploy and FTP.
Here's a video explaining the whole process.
I'm trying to automatically deploy from Team Services (was Visual Studio Online) after a successful build a C# program to an azure app service without success.
I can only do it to a cloud service (classic) rather app service.
I've seen that I could plug Team Services directly to the app service with "deployment source" (I did tried so far because both tenant, Team Services & Azure one are different and requires some effort)
but wouldn't it break the normal release / test process from Team Services?
I can only find little information over internet regarding these topics ...
Any help would be appreciated.
You can also add a FTP Upload task in your build definition to publish the output to Azure App Service via FTP Method.
To publish to an Azure App Service, you need to use either of the following Agent tasks:
Here is a walkthrough: https://www.visualstudio.com/en-us/docs/build/apps/aspnet/aspnet4-to-azure
When making a new build definition, it is easiest to choose the Deployment -> Azure WebApp option.
I am trying to link the Azure Functions deployment to integrate with Visual Studio Team Service however once I select VSTS as the source, it doesn't show any other projects.
I have other web apps in my account which feed from a VSTS project.
The reason this is important to us is because of the workflow. We currently use AWS API Gateway + Lambda for our webhooks however it doesn't fit our development/deployment workflow.
When you select "Visual Studio Team Services" as deployment source from New Azure Portal, it is using Kudu service which is designed for Git version control. So it will only show the projects with "Git" repositories.
Kudu is the engine behind git deployments in Azure Web Sites. It can
also run outside of Azure.
If you want to deploy the TFVC project, try with Azure Classic Portal. You can refer to this article for details: Continuous delivery to Azure using Visual Studio Team Services
While using Github (or anything other than Visual Studio Team Services) I can use the following page to customize deployment: https://github.com/projectkudu/kudu/wiki/Customizing-deployments
I'd like to customize my deployment as I currently have both a web app and a web api project. I want the web app to be deployed, as default it deploys the web api project. Using project Kudu the settings (.deployment file or even better, the app settings on Azure itself) works great, but not when you deploy from Visual Studio Team Services.
I've spoken with David Ebbo from Project Kudu, and he explained that VS Team Services doesn't use Kudu at all, but probably MS Build. So my question is, how to specifically deploy the web app.
I managed to change the Build Definition and specify the web app .csproj as the Projects To Build. This works. However, I also want to deploy my web api.
Deploying the web api project with Kudu is easy as I can create a separate website, connect to the some repository (and solution) and specify the Project App setting so that it deploys the correct .csproj. How should we do this for MS Build? When I change the Build Definition, it will always deploy the project specified in there.
Just saw another answer on Stackoverflow that looks to solve this problem: Publish Multiple Projects to Different Locations on Azure Website