Add Build Script

[MeikTranel]

For contributors it is common practice to look at the readme.md and look for a how to build section. This is where a build script should exist that does the whole stack: setup, test and package - one console command should set off the whole thing.

This can be the same script that'll end up being called by future CICD integration.

[abergs]

I agree, would be nifty.
I have never done a ps1 script for similar for building dotnet solutions. All the CI tooling I've used have come with the "Use MSBuild" option.

[lennybacon]

I think msbuild would be fine. The idea is to have a start script/command to get it up and running.

[MeikTranel]

The largest project i'm managing currently is entirely based on MSBuild logic. It includes several hundred C#, .NET and Delphi projects and with these kinds of projects MSBuild really is a strong suite. For small projects with single entry points, when dotnet pack on a solution file is all thats needed to produce release artifacts, i prefer things like Cake to control different steps. I'd much prefer PSake, as that would reduce some issues with VSCode-Omnisharp and Cake... but i haven't had enough experience with it yet.

[abergs]

Added simple scripts in 14f5b95
Closing - but feedback is welcome 👍

[MeikTranel]

looks good to me, now put this somewhere in a CI environment. Appveyor, Azure DevOps, Travis... the sky is the limit here. They all give open source projects free build pipelines.

[abergs]

Should also add a note in Readme as well as a test script.

[MeikTranel]

Yes, i'm opening an issue to track CI setup for you.