If you have an existing Azure web job with a schedule this plugin will update that job when you deploy your code. You just have to make sure the names match up. The Azure web job must have the exact same name as your console app project or a second job (without a schedule) will be created.
does not exist.
Jobs only seem to get added to the triggered subfolder despite choosing 'continuous'.
As per @rustd Pranav's blog post , there's been a major update to WebJobs, maybe time to review the addin. http://blogs.msdn.com/b/webdev/archive/2014/03/27/announcing-0-2-0-alpha2-preview-of-windows-azure-webjobs-sdk.aspx
I run a real estate website, and so I need the "Properties" folder in the root to map to my application, not VS's internal nonsense. So I have changed this value in the project:
And created a folder in the project called "AppProperties". But unfortunately, this add-in does not look for that variable, and instead hard-codes a lookup to the Project/Properties/WebJobs.xml file. This throws an error on my system, making the add-in useless.
Would it be possible to make this add-in lookup the variable instead of hard-coding the path, please?
I have version 0.1.3-beta. I seem to be having the EF6 problem. My console app references another project in my solution which references EF6. Unfortunately, I don't get the EF6 dll's in my webjob when I publish. In fact, I don't get them in my website either. Any ideas?
I just installed the plugin and linked a WebJob to a WebSite. I now get this build error - I'm on .NET 4.5.
The type 'System.IDisposable' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.