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.
Related
We have a mobile app service on Azure Portal.
We are a team with 3 members.
We hope to contribute to the server code (C#) together.
How can other teammates download the code which is published by one of us?
We could get the published files from azure WebApp with Azure kudu tool(https://www.sitename.scm.azurewebsites.net/), but the files are compiled, not the source code.
In your case, your team members could push your code to source control server such as github, VSTS,etc. Then team members could work together. And Azure WebApp(Mobile App) Allows us to continuous Deployment to Azure App Service. We could config Deployment options in azure portal.
In your app's menu blade in the Azure portal, click APP DEPLOYMENT > Deployment options. Click Choose Source, then select the deployment source.
I try to attach a debugger to a deployed Azure App Service app and it gives me an error. Why is this?
I enabled the remote debugging from my app dashboard in Azure Portal, but selected VS 2015, because there is not an option for 2017..
I found the post by this guy while doing the research:
link
I have a number of web apps hosted in Azure. These can be navigated to by their URL and are live and running correctly. If I use the server browser in Visual Studio 2015 I can see the correct web apps... AND previously deleted web apps.
However in the new Azure portal one of my web apps is missing. What do I need to do to get the new portal to recognise all of my web apps and should I be worried about visual studio displaying old deleted ones?
This is a sync issue that happens occasionally, and that we can fix for you. In order to do this, please share the name of any site in your subscription. You can create a temporary dummy site for that purpose if you like.
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.
I have gone through the Lab AdvancedWebAndWorkerRoles which you have provided in the latest training kit WAPTK. I followed the steps in Exercise 1:registering sites,Applications and Virtual directories .It is running fine in windows azure emulator(locally),but i cannot find any steps to host in the windows azure management portal.
Can any one suggest(steps) how to host the same application in the windows azure management portal?
We know how to deploy applications in windows azure portal.As i had mentioned in my question about the Exercise 1:registering sites,Applications and Virtual directories in the training kit WAPTK ,we want to create the similar application and host in the azure.The steps to host the Exercise 1 application in management portal is not mentioned in the training kit.We tried to host the application in windows azure portal but it is not working as the ServiceDefinition.csdef include some different configurations.We wanted to know the steps to host that application in management portal.
Under the Introduction to Windows Azure lab, look at Exercise 3: Publishing a Windows Azure Application. This shows how to publish via the portal. The basic steps:
Build your Windows Azure service in Visual Studio, but tell it not to publish. Just generate the package file and configuration file.
Create a new hosted service. This gets a name like myapp.cloudapp.net. You'll need to find a unique DNS prefix.
Select the generated package file and configuration file, from the portal, which results in your service being launched. This takes a few minutes, and you can watch its status via the portal.
You may also publish directly from Visual Studio. See this MSDN article for instructions on setting up Visual Studio correctly (which basically imports your publishing settings from the portal). Visual Studio can perform all of the steps without having you to actually do anything in the portal (aside from exporting your publish settings).