Differences
This shows you the differences between the selected revisions of the page.
| 2016-02-04 | 2016-02-27 | ||
| hashtable style sessionoptions initilization (martin) | https (martin) | ||
| Line 15: | Line 15: | ||
| * Pack all the job files into a ZIP archive; | * Pack all the job files into a ZIP archive; | ||
| - | * Navigate to your web site page on [[http://manage.windowsazure.com/|Azure Management Portal]]; | + | * Navigate to your web site page on [[https://manage.windowsazure.com/|Azure Management Portal]]; |
| * Switch to //WebJobs// tab; | * Switch to //WebJobs// tab; | ||
| * Use //Add// command on bottom bar; | * Use //Add// command on bottom bar; | ||
| Line 134: | Line 134: | ||
| * locate source or destination paths of the transfer using WebJob [[#environment|environment variables]]; | * locate source or destination paths of the transfer using WebJob [[#environment|environment variables]]; | ||
| * [[#log|print the session log to the standard output]], so that it is available from Azure Management Portal; | * [[#log|print the session log to the standard output]], so that it is available from Azure Management Portal; | ||
| - | * not use ''[[http://technet.microsoft.com/en-us/library/hh849877.aspx|Write-Host]]'' cmdlet as there is no console to write to in the Azure WebJob, use ''[[http://technet.microsoft.com/en-us/library/hh849921.aspx|Write-Output]]'' instead. | + | * not use ''[[https://technet.microsoft.com/en-us/library/hh849877.aspx|Write-Host]]'' cmdlet as there is no console to write to in the Azure WebJob, use ''[[https://technet.microsoft.com/en-us/library/hh849921.aspx|Write-Output]]'' instead. |
| An example PowerShell script (''backup.ps1'') that backs up the WebSite to a remote SFTP server: | An example PowerShell script (''backup.ps1'') that backs up the WebSite to a remote SFTP server: | ||
| Line 312: | Line 312: | ||
| You can develop the WebJob (console) application as any other, even using //Visual Studio Express for Windows Desktop//. If you are using //Visual Studio Express for Web//, you can use //Microsoft Azure WebJob// project template. It's basically the same template as a //Console Application// in the Desktop edition.((Web edition does not have //Console Application// template.)) | You can develop the WebJob (console) application as any other, even using //Visual Studio Express for Windows Desktop//. If you are using //Visual Studio Express for Web//, you can use //Microsoft Azure WebJob// project template. It's basically the same template as a //Console Application// in the Desktop edition.((Web edition does not have //Console Application// template.)) | ||
| - | With //Visual Studio Express for Web// (2013 edition with Update 3)((For older versions you need Azure SDK.)) you can ease [[#deploying|the deployment]] using command //Publish as Azure WebJob//, which is available in the project context menu in //Solution Explorer//. It opens //[[http://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/#configure|Add Azure WebJob]]// dialog that allows you to name your job and setup how it is run (including scheduling). Make sure you add all additional files needed for the job (i.e. ''winscp.exe'', ''run.bat'' and private key, as shown above) to the project with //Build Action// set to //Content// to have them deployed (see also [[library_install#vs|Using WinSCP .NET assembly from Visual Studio]]). When you submit the dialog, a publish process starts on the background in //Web Publish Activity// pane. Next time you publish, after making changes to the project, only modified files are uploaded. See also [[http://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/|How to Deploy Azure WebJobs to Azure Websites]]. | + | With //Visual Studio Express for Web// (2013 edition with Update 3)((For older versions you need Azure SDK.)) you can ease [[#deploying|the deployment]] using command //Publish as Azure WebJob//, which is available in the project context menu in //Solution Explorer//. It opens //[[https://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/#configure|Add Azure WebJob]]// dialog that allows you to name your job and setup how it is run (including scheduling). Make sure you add all additional files needed for the job (i.e. ''winscp.exe'', ''run.bat'' and private key, as shown above) to the project with //Build Action// set to //Content// to have them deployed (see also [[library_install#vs|Using WinSCP .NET assembly from Visual Studio]]). When you submit the dialog, a publish process starts on the background in //Web Publish Activity// pane. Next time you publish, after making changes to the project, only modified files are uploaded. See also [[https://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/|How to Deploy Azure WebJobs to Azure Websites]]. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| Line 318: | Line 318: | ||
| * Guide to [[guide_microsoft_azure#website|connecting securely to a Microsoft Azure Web Site with FTPS]]; | * Guide to [[guide_microsoft_azure#website|connecting securely to a Microsoft Azure Web Site with FTPS]]; | ||
| * [[http://www.hanselman.com/blog/IntroducingWindowsAzureWebJobs.aspx|Introducing Windows Azure WebJobs]]; | * [[http://www.hanselman.com/blog/IntroducingWindowsAzureWebJobs.aspx|Introducing Windows Azure WebJobs]]; | ||
| - | * [[http://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/|How to Deploy Azure WebJobs to Azure Websites]]; | + | * [[https://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/|How to Deploy Azure WebJobs to Azure Websites]]; |
| - | * [[http://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/|Use WebJobs to run background tasks in Microsoft Azure Websites]]. | + | * [[https://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/|Use WebJobs to run background tasks in Microsoft Azure Websites]]. |