I have an existing project with three web apps (two web API and a front end). I would like to deploy to Azure all three with a single click of Publish using the Publish Web wizard.
I installed the Azure SDK and tried to create a new Cloud Service, but this install the VMs and the storage emulator, that I don't need at all and slows down my PC.
I tried with Azure Resource Group to add to an existing project, but the Deploy button remains disabled, like it failed to connect to the web site project.
What is the recommended way to do this?
I am using Visual Studio 2015
Thx.
You do not need to install the emulator for the deployment to work, just download the parts you need from http://www.microsoft.com/en-us/download/details.aspx?id=48178 (assuming you want SDK 2.7).
It's not really clear from your question if you want to deploy a Cloud Service or a Web App. If you want to deploy a Cloud Service, you can add all 3 projects as roles and they will all be published within a single deployment (just one click to Publish). But, if what you want is to deploy them as web apps, you will need to do it in 3 different apps, which means 3 clicks to publish.
Related
I am trying to get an Azure App Service to recognize my Web Job - meaning to show it in the portal under "Web Jobs" in the App Service. And to also run it on the schedule defined with a TimerTrigger attribute.
It is a .NET Core 2.2 Console Application with multiple web job classes in it. The App Service it runs within is a separate project and web site. I am able to publish it from Visual Studio and it shows as it should under Web Jobs in the Web App. But if I delete it and try the publish from Octopus to the same place WITHOUT doing the VS 2017 publish first, it won't show up.
My issue is that in a new environment, the Web Job does not get created when I use Octopus to deploy the Web Job files as described here:
http://blog.amitapple.com/post/74215124623/deploy-azure-webjobs
by setting the physical path in my Octopus package deployment:
App_Data\jobs\continuous\myjob
This is the same path as when I publish from Visual Studio 2017.
Related to this question, but there seems to be a step missing since the files are in the right place, but the web job does not appear in the portal.
How to deploy azure webjob using Octopus
Is there some additional ssetup or registration step for the Web Job to run or should the App Service just recognize the web job is there when the files appear in the correct place? Restarting the app service does not help.
Since you have a web app along with a web job, I would follow the steps outlined at https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app/deploying-web-jobs. You can build your project using .nuspec to get your .npkg and push/upload the package to Octopus.
Hope that helps.
I've got an OWIN Self-Hosted SignalR app. I'm looking for a way to automatically deploy it to a different server (one is local, one is in Azure cloud) from Visual Studio. I'm not using IIS, I want to run it either as a normal app or as a Windows service.
What are my options?
I advise you to consider using TopShelf
and here is the Nuget Package
All you need is to build and deploy the bin folder then just run one command
I have an existing Web API project published as a 'API App' on Azure. I recently added a "staging" deployment slot that I'd like to publish future versions of the API App before Swapping over to production. However, if I try to create a new publish profile in VS 2015 (or 2017), all my Web Apps are listed except the API App - so there is no way to select the existing deployment. Put this another way, if I delete the publish profile I have no way to publish the project using the Publish wizard (unless I download the publish profile from Azure, but I still have no way to change the deployment slot - that I know of).
I can see my API App in Cloud Explorer OK.
Any ideas?
I think you should be able to go to "deployment slots" in your web app click on a staging slot and then on the right side you will have your staging blade and then ou can download publish profile that is specific to staging slot:
According to your first screenshot, we could find that there are multiple resource groups in current subscription, but you just check the API App in resource group InergySystemsMain, please make sure if the API App belongs to other resource group.
Besides, as RAS said, we could download publish profile of Azure app service from Azure portal to local, and then we could import this publish profile file in Visual Studio.
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
Every example I've seen on how to deploy an MVC application to Windows Azure is using the Visual Studio Publish tool, my problem is that my application is deployed with a custom msbuild file (.proj).
I cannot change the way it is deployed, so is there a way to deploy to azure without publishing? Something like copying the directory result of my custom build to some azure directory.
Thanks for letting us know that it is for Windows Azure Web Role. You can use Automated Build and Deployment with Windows Azure SDK 1.6 blog to deploy directly from ccproj file. Even if it is written with SDK 1.6, you sure can use exact details with SDK 1.7 as well.
You can also take a look at Using MSBuild to deploy to multiple Windows Azure environments blog as well.