Code changes needed to get the project running on Linux pipeline #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based off PR #97 so it must be merged with it
Description
Changes in the project and code to get them running on a Linux pipeline in Azure DevOps
Changes
Details
We got a pipeline deploying a TestBot to Linux running in Azure DevOps.

For this, we took as a starting base the TestBot pipeline Nightly-Build-Test which is deploying a bot on Windows, but made some modifications to get it running under Linux.
Changes done to the pipeline
New tasks:
• We had to remove the Visual Studio Build solution step because It wasn't compatible with the Linux platform and replace it by the MSBuild Build solution step. Due to this change, we had to…
• Replace both the Use NuGet 4.9.1 and the NuGet restore by a dotnet restore step.
• We added a PowerShell step to add the section
RuntimeIdentifiersto three projects that required itExisting tasks:
• We had to change the zip filename in the az webapp deployment command at the Create Resources step, leaving the line as:
• We had to change the PowerShell script that was running on the task Get Bot Keys to the following:
Changes done to the code
• We had to change backslashes hardcoded in several parts of the code since they need to be forward slashes in Unix. For this, we will use System.IO.Path.Combine in the final PR.
• We had to change some oversighted capitalization in filenames and paths that was running well on Windows but didn't on Unix, due to the latter being case-sensitive.