NodeJs project as a Azure WebJob - node.js

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).

Related

How to deploy a C# Console app to Azure App Service using Github Actions

I am trying to deploy a C# Console app. (which inserts data from a third party API to Azure SQL) using Github Actions (push to Azure App Service), and I need some guidance for an option.
I pushed my C# code into Github from my Visual Studio solution in my laptop.
I chose this option ("Deploy .Net Core app to an Azure Web App") at Github Actions:
This is result that I got:
Did I choose wrong option here?
Do I need to create a Web App?
We can deploy the console application into Azure app service using an Azure WebJob. To get complete idea on WebJob. But the performance of the application is not guaranteed. To deploy using Visual Studio. To deploy the application when the WebJob is already created use the link.
To schedule a WebJob
To schedule the WebJob refer the link.

Azure function app deployment working with VS 2017 but not with Azure Web App deploy task

I have release azure function app from VSO Azure App Service Deploy release task,
it gives:
System.Nets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions I searched on google, people say the sockets get expired but i am using S3 pricing tier
I have then released the same function app from Visual Studio 2017 which runs perfectly fine without any exceptions.
I am attaching the artifacts, build assets, release pipeline details, please help. I will not be able to move to production unless this issue is resolved.
Structure of Artifacts which is not working
Structure of artifacts which is working fine-published from VS2017
Here is the github link for more details regarding the issue.
https://github.com/microsoft/azure-pipelines-tasks/issues/11345
I had to give a proper storage connection string for the following, instead of UseDevelopmentStorage=true,

Azure WebJobs get deleted each time I redeploy?

Are Azure WebJobs get deleted each time when I redeploy? I found those WebJobs mysterious disappeared, so I guess maybe it's because I redeployed my app but didn't go to Azure portal to re set WebJobs again.
If that's the case, it is really a trouble to re set WebJobs again and again. Is there a way to automate this?
I deploy from Visual Studio. I read somewhere saying I can put my WebJobs (e.g. xxx.ps1) under App_Data/jobs/continuous/, and then whenever I deploy, the WebJobs will be deployed automatically. I did that, but I didn't see those WebJobs in my Azure portal.
See https://learn.microsoft.com/en-us/azure/app-service-web/websites-dotnet-deploy-webjobs for instructions on how to add WebJobs to your Web App from VS. Note that you don't need to worry about the App_Data/jobs/continuous folder, as that's taken care of by VS deployment.
Note that this is supported for ASP.NET but not yet for ASP.NET Core.

Redeploying an Azure WebJob

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

Azure Continuous Deployment from Visual Studio Team Services with multiple projects

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

Resources