azure-webjobs

How do I setup Connection Strings for a WebJob project?

安稳与你 提交于 2019-12-03 06:42:04
问题 I am trying to setup a website and webjob, but get an error everytime I try to publish the webjob independently of the website (i.e. Selecting Publish as Azure WebJob from the context menu) C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5): Error : The 'MyWebJob.Models.MyDataEntities-Web.config Connection String' argument cannot be null or empty. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing

Azure WebJobs Deployment with Continuous Integration on Visual Studio Online

旧城冷巷雨未停 提交于 2019-12-03 04:58:09
问题 Friends, I am trying to setup Continuous Integration with Azure WebJobs. I have a Web and a WebJobs project in the solution. I have continuous integration and deployment already setup for the web app in Visual Studio Online (*.visualstudio.com). I also connected the WebJobs and the Web app using the Visual Studio ASP.Net extensions - Right click the WebSite project in VS 2013 > Add > Existing Azure WebJob project. It created webjobs-list.json file in the website project. I was expecting that

AzureWebJobsDashboard Configuration Error

佐手、 提交于 2019-12-03 04:24:54
I created a new Azure WebJob project in Visual Studio 2015 using .NET Framework 4.6. In the app.config, I set three connection strings: AzureWebJobsDashboard AzureWebJobsStorage MyDatabaseConnectionString The AzureWebJobsDashboard and AzureWebJobsStorage connection strings are identical and they're both pointing to my storage account. I'm including one of the connection strings -- since they're both identical, except the "name". <add name="AzureWebJobsDashboard" connectionString="DefaultEndpointsProtocol=https;AccountName=mystorageaccountname;AccountKey

Deploy azure website and webjobs in same sln using VSO - Error - There can be only one

夙愿已清 提交于 2019-12-03 03:33:58
I've got to a website and a webjob project in the same sln: Sritt (The website) Sritt.Webjob In properties of Sritt theres a webjobs-list.json with the following setting: "WebJobs": [ { "filePath": "../Sritt.WebJob/Sritt.WebJob.csproj" } I've configured the by VSTS build like this (with the new buildsystem): Solution: **\*.sln MSBuild Args: /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.stagingDirectory)" Building in VSTS gives me the following warning: C:\a\1\s\packages\Microsoft.Web.WebJobs.Publish.1

Failing with the Webjobs validation script

…衆ロ難τιáo~ 提交于 2019-12-02 20:54:19
问题 I am running the below script to validate my Webjobs whether they properly stopped or not after running my Webjobs stop and start scripts though PowerShell task in VSTS.But the below script is sometimes working properly and some times not properly.Because even after stopping my Webjobs,the validation script is saying the webjobs are not stopped.I am not sure why the script is throwing the error.I have double checked with the azure portal Whether the jobs are really stopped/started But in

How do I setup Connection Strings for a WebJob project?

假装没事ソ 提交于 2019-12-02 20:19:18
I am trying to setup a website and webjob, but get an error everytime I try to publish the webjob independently of the website (i.e. Selecting Publish as Azure WebJob from the context menu) C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5): Error : The 'MyWebJob.Models.MyDataEntities-Web.config Connection String' argument cannot be null or empty. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5): Error : The 'MyWebJob.Models.MoreDataEntities-Web.config Connection String' argument

azure webapp webjob node version

五迷三道 提交于 2019-12-02 20:10:11
问题 How can I define the node version that is used to run azure webjobs? The server currently executes my code with v0.11 and fails since I use features that require node >8 The web app itself runs on node 8 just fine, but the version for webjobs seems to be independent of the webserver itself. 回答1: On Azure WebApp, for Node.js runtime, there is a default version which be older that 0.10.40 or others like 0.11 as you said. If you want to change the default Node version for running your webjob,

Azure WebJobs Deployment with Continuous Integration on Visual Studio Online

蓝咒 提交于 2019-12-02 18:16:16
Friends, I am trying to setup Continuous Integration with Azure WebJobs. I have a Web and a WebJobs project in the solution. I have continuous integration and deployment already setup for the web app in Visual Studio Online (*.visualstudio.com). I also connected the WebJobs and the Web app using the Visual Studio ASP.Net extensions - Right click the WebSite project in VS 2013 > Add > Existing Azure WebJob project. It created webjobs-list.json file in the website project. I was expecting that when the Web app deployment happens to Azure Website after the Visual Studio Online build, it will

No parameterless constructor error in WebJobs with .NET Core and Ninject

孤人 提交于 2019-12-02 11:36:16
I'm trying to do a bit of a balancing act here. Currently Azure WebJobs don't support .NET Core. With some help, I created a .NET Core Console App and made it work as a WebJob. On top of that I'm trying to implement Ninject for DI. Code compiles fine but when I run it, I'm getting the "No parameterless constructor is defined for this object." error -- see below. I may be in a bit of unchartered territory here with Azure WebJobs, .NET Core 2.0 and Ninject but any idea what may be causing this? BTW, I had the same exact code running as a WebJob targeting .NET Framework. I needed to migrate to

Shared lock between App Service and Webjob

折月煮酒 提交于 2019-12-02 11:28:32
I want to have a shared lock between the Webjob and the App Service code. I have tried lock keyword as well as mutex in C# but they don't seem to be working. Another alternative I could think of is Blob lease which is also the locking mechanism used for locking within webjobs environments as written here . Do azure webjobs run in a totally separate environments from the App Service such that the shared locks are not working, or am I missing something ? Is there any other way ? WebJobs run in a separate process so a lock in C# will not work. Lease on a blob is one way to make a distributed lock