Since integrating our repos, there have been a number of changes in PRs that touch the encoding of the file, adding or removing a BOM as the editor in question decides. I've standardized on UTF-8 with BOM, as we do in roslyn, and put it in the .gitattributes so it should hopefully stay consistent.
@ryanbrandenburg pointed out my change from `. .\activate.ps1` to `.\activate.ps1` in the build from source PR. I've been `.\activate.ps1` and haven't run into any particular issues, however, it's not the recommended way to source due to [scoping](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_scripts#script-scope-and-dot-sourcing). dotnet/aspnetcore enforces this dot sourcing, so I copied over the script changes here.
Also noticed startvs.cmd had changed so brought that over as well.
Fred Silberberg
Tanay Parikh
Ajay Bhargav Baaskaran