Add SLN file and make projects build in VS

[Eilon]

• Added new ActionsRunner.sln file with all the CSPROJ's in it
• Added Directory.Build.props that gets auto-included in all CSPROJ files under it
• Made default runtime platforms for Windows and Linux (to be 64bit) so that you don't have to specify it in order to build

Fixes #170
Fixes #172

[Eilon]

Looks like I failed on Mac build. Investigating.

[bryanmacfarlane]

I think we should recommend using VS Code on Mac. Actually, if we're xplat equal footing, should we just slant toward VS Code?

[Eilon]

I think that's fine for a recommendation, but it's nice to enable VS for Windows users to work on it too. Without this change (or something like it), right now it's not possible at all. (Without this change you can only open a project, but you can't build.)

[bryanmacfarlane]

Note that most folks work on Windows but code in VS but then build in via the cmd line to match what the CI does (dev == CI). However, I have no issue with enabling F5 VS build

[Eilon]

Yeah without these changes even if you do open a project you get several red squigglies because the undefined build vars lead some C# code to be excluded, leaving the project in an invalid state. With the changes in this PR, you can even compile the code. I'm not sure about F5 because I haven't gotten far enough to have an idea of what F5 should run 😄

[thboop]

@Eilon

Thanks for doing the legwork to add this in!

The TestUtil class is used on a majority of our tests, it expects an environmental variable that does not resolve when running inside Visual Studio (the path to the ./src folder). This means the Test Explorer has a large number of failing tests. I don't want to merge in Visual Studio support until we either have a known issue we can point users to or the tests run inside Visual Studio.

Overall the pr looks great ✅

[Eilon]

Indeed, I was unable to run unit tests in VS. I still think this PR is worthwhile even without being able to run tests in VS. The productivity boost of being able to build and get rich Intellisense, refactoring, and other features in VS is enormous all on its own.

[thboop]

Indeed, I was unable to run unit tests in VS. I still think this PR is worthwhile even without being able to run tests in VS. The productivity boost of being able to build and get rich Intellisense, refactoring, and other features in VS is enormous all on its own.

Agreed, I'll file an issue and merge this in

[Eilon]

Yeah I think filing an issue would be great. Perhaps a contributor can get it working! 😄

[thboop]

Filed #180

[thboop]

LGTM

[Eilon]

Thank you @thboop !