I have a question, I created recently an API app using visual studio 2017, I noticed that the name of the app says it's "API app host" which is different from the earlier one created a year ago "API app".
the problem that I am facing is that while I am trying to publish using visual studio 2017, the application that has "API host app" isn't listed at all as a candidate in the list.
as a workaround I am downloading the publish profile from azure portal and using that to publish using visual studio, as the last one can't find the targeted API app in the list.
is this a known issue ?
this picture shows that we have two types of API apps, API App and API app host
Make sure you have the Azure SDK 2.5.1 Release installed on your VS, you should be able to see something similar to the image below, this is how you can publish to App Api.
Related
I appears that the Cloud Explorer has now been retired in Visual Studio 2022.
This was something that I used many time a day and will sorely be missed.
I used to be able in the Cloud Explorer select the app service, right click, and attach the debugger to the app. In Visual Studio 2022 I can find no way of attaching the debugger the the remote Azure app service. Also browsing the web I can't find any documentation on how to do this. Can someone supply directions on how to do this, or point me to the documentation on how to debug an Azure app on the remote server.
Currently there's an option to debug Azure App Service.
Instead of using the cloud explorer you may create a publish profile and attach a debugger from there:
All in VS 2022.
I’ve had the same problem, trying to do remote debug an App Service with VS2022. I just realised that the top dropdown box “Connection Type” on Debug | Attach to Process... dialog gives you an option “Microsoft Azure App Services” (I'm using ver 17.2.4). Clicking the Find button lets you select target App Service. You can then select the target process. (Attaching from the Publish dialog doesn’t let you select the process - you may have a number of apps on virtual directories).
One thing I noticed and confusing; the listening port is not 4026 but 4024 even though you specify VS2022 on the Azure Portal in my case. Telnet or Psping to 4026 – no response. If you do the above way, this doesn’t matter but if you select Connection Type: “Default” and specify host:port, then the port should be 4024. You can remotely debug Azure Function in this way.
Today with Visual Studio 2022 you can use the Connected Services node under a given project:
Once you connect to an app service, you'll have access to attach the debugger:
Microsoft Learn Module
Remotely debug ASP.NET Core apps hosted on Azure App Service using Visual Studio
More info here:
Manage the resources associated with your Azure accounts in Visual Studio Cloud Explorer
Overview: Connected Service
I'm getting the following error when I try to access the App Service node in the Server Explorer after connecting to my Azure Subscription.
Here's the complete Error Message.
---------------------------
Server Explorer
---------------------------
Unable to retrieve Web Apps from some subscriptions:
Subscription Visual Studio Premium with MSDN: The resource type 'apiapps'
could not be found in the namespace 'Microsoft.AppService' for api version
'2015-03-01-preview'. The supported api-versions are '2015-03-01-alpha'.
---------------------------
OK
---------------------------
I am able to access other nodes, just not the App Service node wherein I have 2 Apps installed and running. 1 is a Web App, the other is an Api App that I originally published as a ASP.Net Core API App.
Due to this, I'm having to FTP into the Site and browse through log files and download them to view them. Very time consuming and distressing.
Even after I deleted the ASP.Net Core API app I am still not able to access this node from within Visual Studio 2015.
I'm following the procedure to create a Xamarin app with a mobile app backend in Azure.
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-dotnet-backend-xamarin-android-get-started-preview/
I've create the mobile app in the portal and downloaded the backend runtime and xamarin solutions. When I try to publish the backend runtime, the instructions indicate that the one I just created should show up 'Existing Web Apps'. Mine shows nothing.
My questions are:
1) How can I troubleshoot what shows up in the 'Existing Web Apps'?
2) Is it reasonable to just create a new web app from the VS Publish dialog?
3) If not, where should I place the publish profile that I can download from the azure portal?
Regards,
Rajesh
1.a. Ensure you're using the right azure suscription from VS
1.b. Logout and add your subscription login again
Yes it's reasonable
You can put it wherever you want. From VS website project goto publish settings
4. Then select import
5.And Finally browse the publish settings file
I have had issues with Visual Studio finding the existing apps. I tend to download the publish settings and use that instead. This works fine.
Alternatively, create a git repository and check the code into the git repository. Check out this article for instructions: https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/
Personally, I post my code to a branch of my git repository on GitHub and link the continuous deployment option of the Azure App Service to that. You can find my blog about this topic here: http://shellmonger.com/2015/08/29/continuous-deployment-nodejs-and-microsoft-azure/ - it's for NodeJS but the concept and methodology is the same.
I've been attempting to create a new MVC web application in visual studio and have it hosted in Microsoft Azure. If I choose to have a database server it fails with the following error.
Creating Microsoft Azure Web App
Creation of Microsoft Azure Web App failed. Object reference not set to an instance of an object.
If I don't select the option to have a database the web site is created in my azure account.
Can anyone tell me what this error is suppose to mean.
Make sure you are using the latest SDK version. There was a bug in 2.5.1 that is fixed in 2.6. Also make sure you're creating the database in the same resource group as the web app.
I´m currently trying to set up an azure mobile service .net backend for an app. I´m using visual studio express 2013 for Windows / for Web. I installed all available updates and the recent azure sdk (2.4).
My problem now is that there is no "Azure Mobile Service" project template and mobile services is even not displayed beneath the azure entry in the server explorer.
What did I miss to install?
Many thanks in advance!
UPDATE:
I tried to set up the mobile service with visual studio express 2012 but I stuck at the same problem. Neither the mobile service template nor the option in the server explorer is present.
I just downloaded Visual Studio 2013 Express for Windows with Update 3 from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=43729
I then had the mobile services node in the Server Explorer. However, the project template still isn't there.
This was with Azure SDK 2.3 already installed and also tested with Azure SDK 2.4.
The project templates ship with Visual Studio SKUs and their updates, and I believe Mobile Services is only shipping with Pro and Ultimate for now.
One option to get that starting project is to provision your mobile service in the portal making sure to select the .NET backend. Then on the quickstart page of the portal (the little cloud to the left of the dashboard tab) select the link to create a new application. You will get an option to download the starter solution for the .NET backend (for windows apps it will also download the client). That is basically the same project you would get by choosing File -> New Project in VS pro or ultimate. You can then open the solution in VS Express for Web 2013 but not VS Express for Windows.
To publish the mobile service you'll need to do the following:
Go back to the portal and on the Dashboard page for your mobile service click the Download Publish Profile link and save to your local machine
Right-click the project in the Solution Explorer and choose "Publish"
Import the publish profile you downloaded in step #1 and finish the publish process
So if you want to use the express versions of VS 2013, make sure you have all the updates then:
Use VS 2013 For Windows to manage your mobile service in server explorer and build your windows clients
Use VS 2013 For Web to build your Azure Mobile Service back end project, run locally, and publish using the publish profile.