Differences
This shows you the differences between the selected revisions of the page.
| guide_microsoft_azure_webjob_sftp 2014-09-09 | guide_microsoft_azure_webjob_sftp 2025-02-14 (current) | ||
| Line 1: | Line 1: | ||
| ====== SFTP/FTPS file transfers in Microsoft Azure WebJob ====== | ====== SFTP/FTPS file transfers in Microsoft Azure WebJob ====== | ||
| - | If you need to export/backup data from your Microsoft Azure WebSite to a remote server or import data from the remote server to your WebSite, you can use WinSCP from Azure WebJob. | + | If you need to export/backup data from your Microsoft Azure App Service (Web Site) to a remote server or import data from the remote server to your App Service, you can use WinSCP from Azure WebJob. |
| - | The Azure WebJob is a script or an application run on Azure WebSite server that has a read/write access to your web site. The job can be executed on demand or schedule. To implement file transfers for the WebJob, you can either run WinSCP in [[scripting|a scripting mode]] from a batch file; use [[library|WinSCP .NET assembly]] from a [[guide_microsoft_azure_webjob_sftp#powershell|PowerShell script]] or develop [[guide_microsoft_azure_webjob_sftp#consoleapp|a (console) application]] that uses the WinSCP .NET assembly. | + | The Azure WebJob is a script or an application run on Azure App Service server that has a read/write access to your service (web site). The job can be executed on demand or schedule. To implement file transfers for the WebJob, you can either run WinSCP in [[scripting|a scripting mode]] from a batch file; use [[library|WinSCP .NET assembly]] from a [[#powershell|PowerShell script]] or develop [[#consoleapp|a (console) application]] that uses the WinSCP .NET assembly. |
| - | You can also use WebJob without having an actual web site as a cloud-hosted scheduled task. | + | You can also use the WebJob without having an actual app service (web site) as a cloud-hosted scheduled task. |
| - | + | ||
| - | **//Note that WinSCP 5.5.x and older is not compatible with a restricted Azure environment. You need to use WinSCP 5.6.x beta.//** &beta | + | |
| ===== [[structure]] WebJob structure ===== | ===== [[structure]] WebJob structure ===== | ||
| WebJob is a package that contains your job executable (e.g. a batch file or a console application) along with all supporting files (script, WinSCP executable, WinSCP .NET assembly, etc). Azure platform automatically tries to detect what executable is the main one. To ease this, you should name the main executable ''run.*'', e.g. ''run.bat'' for a batch file. | WebJob is a package that contains your job executable (e.g. a batch file or a console application) along with all supporting files (script, WinSCP executable, WinSCP .NET assembly, etc). Azure platform automatically tries to detect what executable is the main one. To ease this, you should name the main executable ''run.*'', e.g. ''run.bat'' for a batch file. | ||
| - | See [[guide_microsoft_azure_webjob_sftp#powershell|implementation sections]] below for examples of the package contents. | + | See [[#implementation|implementation sections]] below for examples of the package contents. |
| ===== [[deploying]] Deploying WebJob ===== | ===== [[deploying]] Deploying WebJob ===== | ||
| Line 17: | 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 app service page on Azure Portal ''portal.azure.com''; |
| - | * Switch to //WebJobs// tab; | + | * Switch to //WebJobs// page; |
| - | * Use //Add// command on bottom bar; | + | * Use //Add// command on top bar; |
| * Give your WebJob a name; pick your ZIP archive and set up how the job is run. | * Give your WebJob a name; pick your ZIP archive and set up how the job is run. | ||
| - | After your WebJob is uploaded, it is extracted to ''/site/wwwroot/App_Data/jobs/type/name'', where ''type'' is ''triggered'' for //Scheduled// and //On demand// jobs and ''continuous'' for //Continuous// jobs. From now on, you can [[guide_microsoft_azure#website|manage/update the job files using FTPS]]. | + | After your WebJob is uploaded, it is extracted to ''/site/wwwroot/App_Data/jobs/type/name'', where ''type'' is ''triggered'' for //Scheduled// and //On demand// jobs and ''continuous'' for //Continuous// jobs. From now on, you can [[guide_microsoft_azure#appservice|manage/update the job files using FTPS]]. |
| + | |||
| + | //You can also deploy the job using Visual Studio, see [[#consoleapp|C# Console Application]] section below.// | ||
| + | |||
| + | ==== [[deploying_auto]] Automating WebJob Update ==== | ||
| + | If you update your WebJob frequently, or if you have multiple instances of similar WebJobs, you can automate the update using WinSCP [[scripting]]. | ||
| + | |||
| + | First, learn how to [[guide_microsoft_azure#appservice|setup FTPS access to the WebJob (WebSite)]]. | ||
| + | |||
| + | Example script: | ||
| + | |||
| + | <code winscp> | ||
| + | open ftpes://winscp\winscp:mypassword@waws-prod-am1-234.ftp.azurewebsites.windows.net/ | ||
| + | put C:\myjob\* /site/wwwroot/App_Data/jobs/type/name/ | ||
| + | exit | ||
| + | </code> | ||
| + | |||
| + | Make sure you update the example with your actual [[guide_microsoft_azure#appservice|FTP credentials]], %%FTP%% host name, the job type (see above) and name. | ||
| + | |||
| + | //Learn how to [[guide_automation|*]].// | ||
| ===== [[environment]] WebJob Environment ===== | ===== [[environment]] WebJob Environment ===== | ||
| - | In WebJob environment, your web site data (as you see them over [[guide_microsoft_azure|FTPS]]) are accessible at ''D:\home''. The path is stored in an environment variable ''HOME''. Other useful environment variables are: | + | In the WebJob environment, your web site data (as you see them over [[guide_microsoft_azure|FTPS]]) are accessible at ''D:\home''. The path is stored in an environment variable ''HOME''. Other useful environment variables are: |
| ^ Variable name ^ Description ^ Example ^ | ^ Variable name ^ Description ^ Example ^ | ||
| - | | ''HOME'' | Web site root directory | ''D:\home'' | | + | | ''HOME'' | App service (web site) root directory | ''D:\home'' | |
| - | | ''WEBJOBS_DATA_PATH'' | Job data directory | ''D:\home\data\jobs\type\name''. | | + | | ''WEBJOBS_DATA_PATH'' | Job data directory | ''D:\home\data\jobs\type\name'' | |
| | ''WEBJOBS_NAME'' | Job name | | | | ''WEBJOBS_NAME'' | Job name | | | ||
| | ''WEBJOBS_PATH'' | Temporary directory, where job is running | ''C:\DWASFiles\Sites\~1sitename\Temp\jobs\type\name\lpej4hrk.fks'' | | | ''WEBJOBS_PATH'' | Temporary directory, where job is running | ''C:\DWASFiles\Sites\~1sitename\Temp\jobs\type\name\lpej4hrk.fks'' | | ||
| | ''WEBJOBS_RUN_ID'' | An unique ID of the job run (an UTC timestamp of the run). There's a data folder created for every run in ''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%'' | ''201409090707416329'' | | | ''WEBJOBS_RUN_ID'' | An unique ID of the job run (an UTC timestamp of the run). There's a data folder created for every run in ''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%'' | ''201409090707416329'' | | ||
| | ''WEBJOBS_TYPE'' | Job type | ''triggered'' or ''continuous'' | | | ''WEBJOBS_TYPE'' | Job type | ''triggered'' or ''continuous'' | | ||
| - | | ''WEBROOT_PATH'' | Web site root directory | ''D:\home\site\wwwroot'' | | + | | ''WEBROOT_PATH'' | App service (web site) root directory | ''D:\home\site\wwwroot'' | |
| - | | ''WEBSITE_SITE_NAME'' | Web site name | | | + | | ''WEBSITE_SITE_NAME'' | App service (web site) name | | |
| - | When the WebJob is executed, its files are cloned to a temporary folder (see ''WEBJOBS_PATH'') and the job is run there. So it makes no sense to store any data to job's working directory, as that is not persistent and is not accessible remotely. Use ''WEBROOT_PATH'' to locate either job's master directory (''%WEBROOT_PATH%\App_Data\jobs\%WEBJOBS_TYPE%\%WEBJOBS_NAME%'') or ''WEBJOBS_DATA_PATH'' to locate job's data directory. See [[guide_microsoft_azure_webjob_sftp#powershell|implementation sections]] below for examples. | + | When the WebJob is executed, its files are cloned to a temporary folder (see ''WEBJOBS_PATH'') and the job is run there. So it makes no sense to store any data to job's working directory, as that is not persistent and is not accessible remotely. Use ''WEBROOT_PATH'' to locate either job's master directory (''%WEBROOT_PATH%\App_Data\jobs\%WEBJOBS_TYPE%\%WEBJOBS_NAME%'') or ''WEBJOBS_DATA_PATH'' to locate job's data directory. See [[#implementation|implementation sections]] below for examples. |
| - | ===== Copying Session Log to Job Log ===== | + | ===== [[log]] Copying Session Log to Job Log ===== |
| - | The standard output of the job is redirected to a log file which you can display on Azure Management Portal. | + | The standard output of the job is redirected to a log file which you can display on Azure Portal. |
| - | It is useful to have WinSCP session log file included into the job's log. For that as the last step of the job, print the WinSCP session log to the standard output. See [[guide_microsoft_azure_webjob_sftp#powershell|implementation sections]] below for examples. | + | It is useful to have WinSCP session log file included into the job's log. For that as the last step of the job, print the WinSCP session log to the standard output. See [[#implementation|implementation sections]] below for examples. |
| - | To display the job log, go to //WebJobs// tab of your web site page on Azure Management Portal and click on a link in //Logs// column of the job. | + | To display the job log, go to //WebJobs// page of your app service on Azure Portal, select the job and click on the //Logs// button on the top bar. |
| ===== [[implementation]] Implementation ===== | ===== [[implementation]] Implementation ===== | ||
| ==== Using Scripting ==== | ==== Using Scripting ==== | ||
| - | //If your transfer/synchronization task is simple, use WinSCP scripting. For complex tasks, see below for solutions using WinSCP .NET assembly from a [[guide_microsoft_azure_webjob_sftp#powershell|PowerShell script]] or [[guide_microsoft_azure_webjob_sftp#consoleapp|console application]].// | + | //If your transfer/synchronization task is simple, use WinSCP scripting. For complex tasks, see below for solutions using WinSCP .NET assembly from a [[#powershell|PowerShell script]] or [[#consoleapp|console application]].// |
| - | //Start with learning how to [[guide_automation|automate file transfers (or synchronization) to FTP server or SFTP server]].// | + | //Start with learning how to [[guide_automation|*]].// |
| Comparing with generic WinSCP script examples, your Azure transfer job should: | Comparing with generic WinSCP script examples, your Azure transfer job should: | ||
| - | * have a wrapper batch file named ''run.bat'' so that Azure correctly identifies it as [[guide_microsoft_azure_webjob_sftp#structure|the main executable]]; | + | * have a wrapper batch file named ''run.bat'' so that Azure correctly identifies it as [[#structure|the main executable]]; |
| - | * the wrapper batch file should propagate WinSCP [[scripting#checking_results|exit code]], so that Azure correctly identifies failures (any non-zero exit code is a failure to Azure, the same for WinSCP); | + | * the wrapper batch file should propagate WinSCP [[scripting#result|exit code]], so that Azure correctly identifies failures (any non-zero exit code is a failure to Azure, the same for WinSCP); |
| * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%''); | * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%''); | ||
| - | * 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]]; |
| - | * print session log to a 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 Portal. |
| An example script (''script.txt'') that backs up the WebSite to a remote SFTP server: | An example script (''script.txt'') that backs up the WebSite to a remote SFTP server: | ||
| <code winscp> | <code winscp> | ||
| - | option batch abort | ||
| - | option confirm off | ||
| # Connect | # Connect | ||
| - | open sftp://user:password@example.com/ -hostkey="ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx" | + | open sftp://user:password@example.com/ -hostkey="ssh-rsa 2048 xxxxxxxxxxx..." |
| cd backup | cd backup | ||
| # Use a job run ID (timestamp) as a backup ID | # Use a job run ID (timestamp) as a backup ID | ||
| mkdir %WEBJOBS_RUN_ID% | mkdir %WEBJOBS_RUN_ID% | ||
| - | # Upload a whole web site | + | # Upload a whole app service/web site |
| put %WEBROOT_PATH%\* %WEBJOBS_RUN_ID%/ | put %WEBROOT_PATH%\* %WEBJOBS_RUN_ID%/ | ||
| exit | exit | ||
| Line 96: | Line 111: | ||
| rem Propagating WinSCP exit code to Azure | rem Propagating WinSCP exit code to Azure | ||
| - | exit %RESULT% | + | exit /b %RESULT% |
| </code> | </code> | ||
| - | A complete WebJob package (to be [[guide_microsoft_azure_webjob_sftp#deploying|deployed to Azure WebSite]]) consists of following files: | + | A complete WebJob package (to be [[#deploying|deployed to Azure App Service]]) consists of following files: |
| * ''winscp.com'' [[executables|executable]]; | * ''winscp.com'' [[executables|executable]]; | ||
| Line 114: | Line 129: | ||
| Comparing with generic WinSCP PowerShell examples, your Azure transfer job should: | Comparing with generic WinSCP PowerShell examples, your Azure transfer job should: | ||
| - | * have a wrapper batch file named ''run.bat'' so that Azure correctly identifies it as [[guide_microsoft_azure_webjob_sftp#structure|the main executable]] (Azure WebJob cannot run PowerShell scripts directly); | + | * have a wrapper batch file named ''run.bat'' so that Azure correctly identifies it as [[#structure|the main executable]] (Azure WebJob cannot run PowerShell scripts directly); |
| * the PowerShell script should propagate any error from WinSCP code to an exit code, so that Azure correctly identifies failures (any non-zero exit code is a failure to Azure); | * the PowerShell script should propagate any error from WinSCP code to an exit code, so that Azure correctly identifies failures (any non-zero exit code is a failure to Azure); | ||
| * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%''); | * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%''); | ||
| - | * 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]]; |
| - | * print session log to a 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 Portal; |
| - | * cannot use ''[[http://technet.microsoft.com/en-us/library/hh849877.aspx|Write-Host]]'' cmdlet in Azure WebJob as there is no console to write to, use ''[[http://technet.microsoft.com/en-us/library/hh849921.aspx|Write-Output]]'' instead. | + | * not use ''[[ps>microsoft.powershell.utility/write-host|Write-Host]]'' cmdlet as there is no console to write to in the Azure WebJob, use ''[[ps>microsoft.powershell.utility/write-output|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 app service/web site to a remote SFTP server: |
| <code powershell> | <code powershell> | ||
| Line 130: | Line 145: | ||
| # Setup session options | # Setup session options | ||
| - | $sessionOptions = New-Object WinSCP.SessionOptions | + | $sessionOptions = New-Object WinSCP.SessionOptions -Property @{ |
| - | ···$sessionOptions.Protocol = [WinSCP.Protocol]::Sftp | + | ········Protocol = [WinSCP.Protocol]::Sftp |
| - | $sessionOptions.HostName = "example.com" | + | ·······HostName = "example.com" |
| - | $sessionOptions.UserName = "user" | + | ·······UserName = "user" |
| - | $sessionOptions.Password = "mypassword" | + | ·······Password = "mypassword" |
| - | $sessionOptions.SshHostKeyFingerprint = "ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx" | + | ·······SshHostKeyFingerprint = "ssh-rsa 2048 xxxxxxxxxxx..." |
| + | } | ||
| $sessionLogPath = "$env:WEBJOBS_DATA_PATH\$env:WEBJOBS_RUN_ID\session.log" | $sessionLogPath = "$env:WEBJOBS_DATA_PATH\$env:WEBJOBS_RUN_ID\session.log" | ||
| Line 148: | Line 164: | ||
| $session.Open($sessionOptions) | $session.Open($sessionOptions) | ||
| - | $backupPath = "/home/user/backup/$env:WEBJOBS_RUN_ID";; | + | $backupPath = "/home/user/backup/$env:WEBJOBS_RUN_ID" |
| $session.CreateDirectory($backupPath) | $session.CreateDirectory($backupPath) | ||
| Write-Output "Uploading..." | Write-Output "Uploading..." | ||
| - | $session.PutFiles("$env:WEBROOT_PATH\*", "$backupPath/*").Check() | + | $session.PutFilesToDirectory($env:WEBROOT_PATH, $backupPath).Check() |
| } | } | ||
| finally | finally | ||
| Line 162: | Line 178: | ||
| $result = 0 | $result = 0 | ||
| } | } | ||
| - | catch [Exception] | + | catch |
| { | { | ||
| - | Write-Output $_.Exception.Message | + | Write-Output "Error: $($_.Exception.Message)" |
| $result = 1 | $result = 1 | ||
| } | } | ||
| Line 185: | Line 201: | ||
| </code> | </code> | ||
| - | A complete WebJob package (to be [[guide_microsoft_azure_webjob_sftp#deploying|deployed to Azure WebSite]]) consists of following files: | + | A complete WebJob package (to be [[#deploying|deployed to Azure App Service]]) consists of following files: |
| * ''winscp.exe'' [[executables|executable]]; | * ''winscp.exe'' [[executables|executable]]; | ||
| Line 194: | Line 210: | ||
| ==== [[consoleapp]] C# Console Application ==== | ==== [[consoleapp]] C# Console Application ==== | ||
| + | //If you are implementing your task using C# (console) application, you can use WinSCP .NET assembly to implement file transfer/synchronization. Implementing the task in C# may be useful for very complex and possibly continuous jobs.// | ||
| + | |||
| + | //Start with learning more about the [[library|WinSCP .NET assembly]], how to [[library_install|install it]] and see some [[library_examples|C# examples]].// | ||
| + | |||
| + | Comparing with generic WinSCP .NET assembly C# examples, your Azure transfer application should: | ||
| + | |||
| + | * have a wrapper batch file named ''run.bat'' so that Azure correctly identifies it as [[#structure|the main executable]];((There will be two ''.exe'' files, your application and ''winscp.exe'', so Azure won't know which one to pick up, unless you name your application ''run.exe''.)) | ||
| + | * propagate any error from WinSCP .NET library to its exit code, so that Azure correctly identifies failures (any non-zero exit code is a failure to Azure); | ||
| + | * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%''); | ||
| + | * 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 Portal or provide other means for accessing the log. | ||
| + | |||
| + | An example C# code that backs up the app service/web site to a remote SFTP server: | ||
| + | |||
| + | <code csharp> | ||
| + | using System; | ||
| + | using System.IO; | ||
| + | using WinSCP; | ||
| + | |||
| + | class Example | ||
| + | { | ||
| + | public static int Main() | ||
| + | { | ||
| + | int result; | ||
| + | string sessionLogPath = | ||
| + | Path.Combine( | ||
| + | Environment.GetEnvironmentVariable("WEBJOBS_DATA_PATH"), | ||
| + | Environment.GetEnvironmentVariable("WEBJOBS_RUN_ID"), | ||
| + | "session.log"); | ||
| + | |||
| + | try | ||
| + | { | ||
| + | // Setup session options | ||
| + | SessionOptions sessionOptions = new SessionOptions | ||
| + | { | ||
| + | Protocol = Protocol.Sftp, | ||
| + | HostName = "example.com", | ||
| + | UserName = "user", | ||
| + | Password = "mypassword", | ||
| + | SshHostKeyFingerprint = "ssh-rsa 2048 xxxxxxxxxxx..." | ||
| + | }; | ||
| + | |||
| + | using (Session session = new Session()) | ||
| + | { | ||
| + | session.SessionLogPath = sessionLogPath; | ||
| + | |||
| + | // Connect | ||
| + | Console.WriteLine("Connecting..."); | ||
| + | session.Open(sessionOptions); | ||
| + | |||
| + | string backupPath = | ||
| + | RemotePath.Combine( | ||
| + | session.HomePath, | ||
| + | "backup/" + Environment.GetEnvironmentVariable("WEBJOBS_RUN_ID")); | ||
| + | session.CreateDirectory(backupPath); | ||
| + | |||
| + | Console.WriteLine("Uploading..."); | ||
| + | string source = Environment.GetEnvironmentVariable("WEBROOT_PATH"); | ||
| + | session.PutFilesToDirectory(source, backupPath).Check(); | ||
| + | } | ||
| + | |||
| + | result = 0; | ||
| + | } | ||
| + | catch (Exception e) | ||
| + | { | ||
| + | Console.WriteLine("Error: {0}", e); | ||
| + | result = 1; | ||
| + | } | ||
| + | |||
| + | // Dumping session log to Azure log (standard output) when it exists | ||
| + | if (File.Exists(sessionLogPath)) | ||
| + | { | ||
| + | Console.WriteLine("Session log:"); | ||
| + | |||
| + | using (Stream sessionLog = File.OpenRead(sessionLogPath)) | ||
| + | using (Stream standardOutput = Console.OpenStandardOutput()) | ||
| + | { | ||
| + | sessionLog.CopyTo(standardOutput); | ||
| + | } | ||
| + | } | ||
| + | |||
| + | return result; | ||
| + | } | ||
| + | } | ||
| + | </code> | ||
| + | |||
| + | An example wrapper batch file (''run.bat'') that simply runs your application executable: | ||
| + | |||
| + | <code batch> | ||
| + | ConsoleApplication1.exe | ||
| + | </code> | ||
| + | |||
| + | A complete WebJob package (to be [[#deploying|deployed to Azure App Service]]) consists of following files: | ||
| + | |||
| + | * your application executable (e.g. ''ConsoleApplication1.exe''); | ||
| + | * ''winscp.exe'' [[executables|executable]]; | ||
| + | * ''winscpnet.dll'' [[library|.NET assembly]]; | ||
| + | * ''run.bat'' wrapper batch file; | ||
| + | * optionally [[public_key|a private key file]] for SSH authentication. | ||
| - | TODO | + | You can develop the WebJob (console) application as any other desktop console application. You can also start with //Azure WebJob// project template. |
| - | (*Particularly, when your WebJob is a console application, you may want to use Microsoft Visual Studio for Web to develop it, starting with Microsoft Azure WebJob from Microsoft Azure SDK. You can then use //Public as Azure WebJob// wizard to upload the file to the Azure web site and to setup job scheduling (if required).*) | + | With Visual Studio, 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://learn.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs#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]]). Easier is to use the [[library_install#nuget|NuGet package]]. When you submit the dialog, a publish process starts in 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://learn.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs|Develop and deploy WebJobs using Visual Studio - Azure App Service]]. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| - | * Guide to [[guide_microsoft_azure#website|connecting securely to a Microsoft Azure Web Site with FTPS]]; | + | * [[guide_microsoft_azure#appservice|*]]; |
| - | * [[http://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/|How to Deploy Azure WebJobs to Azure Websites]]; | + | * [[https://www.hanselman.com/blog/introducing-windows-azure-webjobs|Introducing Windows Azure WebJobs]]; |
| - | * [[http://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/|Use WebJobs to run background tasks in Microsoft Azure Websites]]. | + | * [[https://learn.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs|Develop and deploy WebJobs using Visual Studio - Azure App Service]]; |
| + | * [[https://learn.microsoft.com/en-us/azure/app-service/webjobs-create|Run background tasks with WebJobs in Azure App Service]]. | ||