Differences

This shows you the differences between the selected revisions of the page.

2018-10-03 2018-11-09
https for www.hanselman.com (martin) footnote after punctuation (martin)
Line 216: Line 216:
Comparing with generic WinSCP .NET assembly C# examples, your Azure transfer application should: 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''.));+  * 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);   * 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%'');   * enable session logging to a unique job run directory (''%WEBJOBS_DATA_PATH%\%WEBJOBS_RUN_ID%'');

Last modified: by martin