I have a project which I upgraded the Azure SDK to 2.5. I did the diagnostics changes and configured the diagnostics after deploying. After couple of re-deployments, I noticed that the diagnostics configuration is gone. It was no longer recording anything, so I had to re-configure the diagnostics from the visual studio. I use the TFS online with azure deployment workflow to deploy.
What am I doing wrong? Do I have to re-configure the diagnostics after re-deploying?
VSO currently doesn't implement the new WAD architecture, but the plan is to start supporting it with the next Azure SDK release. In the meantime you will need to manually apply the WAD configuration to your service using Visual Studio or Powershell.
Related
I'm using Visual Studio 2017. I've developed a web API and I'm publishing it to Azure. The API isn't showing up in the Azure Portal, but it is in the Azure Resource Explorer. I did some research, and I found this article that says the the API is being published with an outdated Azure SDK.
https://blogs.msdn.microsoft.com/waws/2017/03/31/publishing-azure-api-app-and-it-does-not-appear-in-the-portal/
I'm using the latest vesion of VS 2017, 15.1 (26403.7).
I've verified my API is being published with the "apiapp" kind property. The article says the fix is to update my Azure SDK, but that seems to be integrated into the "Azure development" workload in VS2017. I don't see any way to force an update.
Is this a problem with Visual Studio 2017? Or, is there some other way to update the Azure SDK? Can I fix this in the Azure Resource Manager, until it's fixed?
Any guidance would be appreciated.
This is a known bug with the publishing profile for dotnet Core applications in the latest Azure SDK.
Creating an API App in the Azure portal and then publishing to it from Visual Studio should tag the app correctly.
I used Visual Studio Team Services for deployment of an MVC website on azure and it was successful.
I also created deployment slots.
Now I would like to rollback the deployment, but I am unable to find the Active Deployment blade on portal.azure.com.
Update 1:
I went to Deployment Source>Choose Source>Visual Studio Team Service> Choose a project. When I clicked it, it did not show any project, although I have project on my Visual Studio Team Services.
I did it other way. I went to Visual Studio Team Services, and there established trust relationship between Azure and Team Services. I succeeded with deployment.
Two things need to be checked:
Check whether you have linked a VSTS:
Check whether your team projects are using Git version control. 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.
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
What is process to upload NodeJs project as Azure WebJob from Visual Studio.
I want to upload my nodeJs Project to azure as a WebJob from visual studio with out a WebAPP I am not able to find any blogs or articles to progress further.
Any suggestions?
There is an offical tutorial Deploy WebJobs using Visual Studio which you can refer to, but the deployment is within a WebApp.
However, I discovered a new preview feature Azure WebJobs as Api App on Azure new portal. I think it seems to satisfy your needs, please see and try at the link.
Hope it helps.
This question is problematic, WebJobs run always in the context of a WebApp, that's what they are designed for.
In the meantime Microsoft published Azure Functions https://azure.microsoft.com/en-us/services/functions/
which can do mostly the same and more, only problem is you'll be developing more functional (haha) as global objects/settings/environment variables aren't accessible (because there is no WebApp context).
I'm getting the following error while trying to publish an Azure cloud service (classic) from Visual Studio:
There's so little information in that error that I have no idea what to start fixing. Is there a more detailed log somewhere, and what steps (if any) need to be taken to enable it?
The solution for me that works is to refresh the Azure connection. I use for that the Server Explorer - expand the needed service branch lead to the solution.
The solution can be refresh the credentials as well. It may be connected with the Visual Studio or Azure SDK versions, so it is worth to try to start from reinstalling at least Azure SDK.
How do you redeploy an Azure WebJob? I can see in the Azure portal how to create a WebJob and do the initial upload, but the portal does not appear to allow re-uploading changes, am I right?
I've also looked in the Kudu interface but I don't see anywhere obvious there that allows uploading updates.
So when I make an update to a job how do I release the update.
Thanks.
The Azure portal currently doesn't support updating a WebJob but all you have to do is update the files in the correct place on your site which is: d:\home\site\wwwroot\app_data\jobs\{jobtype - triggered/continuous}\{jobname}'
Read more about this here: http://www.amitapple.com/post/74215124623/deploy-azure-webjobs/
As of Visual Studio 2013 Update 3 and Azure SDK 2.4 this is possible from within Visual Studio. Just right click and select Publish on the web job project.
How are you deploying ? If you use then this will generate the code in your solution to deal with the deployment. I am deploying and using this plugin with VS Team Services and Azure and it is working well.
http://visualstudiogallery.msdn.microsoft.com/f4824551-2660-4afa-aba1-1fcc1673c3d0