Improve/Add Build Automation including nuget packages for dev branch

[gismofx]

As Suggested by @SeanFeldman

Would be nice to have automation in place to build the package from master as well as a manual kicked off the pipeline to build preview packages for occasions such as this.

This will help with, for example, field-testing fixes made to dev branch by just using a nuget to test with rather than requiring an individual to fork and build from source

[SeanFeldman]

@gismofx where's Toast-Blazor-Calendar-600.png is coming from? It looks like it's not checked in.

[SeanFeldman]

I'm going to add it in the PR I'll raise.

[SeanFeldman]

@gismofx have a look at the changes I'm proposing in #41.
Once those are in place, I'll move on to GitHub actions to set up the CI/CD pipeline.

[SeanFeldman]

With #41 out of the way, a package is generated on Release and Debug builds, on any branch.
MinVer is used to control the package version (using tagging) and will be leveraged to push to NuGet.

@gismofx, I'll be looking into automation of the CI/CD. There will be certain things I can't do on the repo as I'm not a collaborator (specify secrets such as NuGet key, create and modify GitHub Actions, etc.). There are two options:

1. I do it on a fork and we transition it here after
2. You grant me a temporary collaborator access

Whichever works better for you.

[gismofx]

@SeanFeldman I'm fine making you a collaborator. This is probably easier. I'll work on that now.

I just want to know what/how things work and what we are changing. Maybe we document it here in the issue discussion for posterity? I'm open to other ideas too. Maybe a GitHub project?

[SeanFeldman]

Thank you.

The proposed changes are (we can discuss various options):

1. Introduce CI/CD that compiles, tests, and deploys the package automatically from the main branch when it's tagged. Currently, there are no automated tests but it will be an option to add later.
2. Deployment from feature branches to NuGet with a manual request (tagging)

[gismofx]

Thank you.

The proposed changes are (we can discuss various options):

1. Introduce CI/CD that compiles, tests, and deploys the package automatically from the main branch when it's tagged. Currently, there are no automated tests but it will be an option to add later.
2. Deployment from feature branches to NuGet with a manual request (tagging)

This sounds good. I've been planning to add some tests at some point, so would be good to know how to get that connected up.

[SeanFeldman]

Quick update - have not forgotten about this. On vacation till early August 🙂

[gismofx]

Quick update - have not forgotten about this. On vacation till early August 🙂

No worries. Thanks for the update. Enjoy vacation!

[gismofx]

Hi @SeanFeldman do you have an update on this feature?