Updates to VS 2022 Build Process

[michael-hawker]

Existing Build got broken with environment changes it seems, so worked to bring us up to VS 2022 VM and build system on .NET 6.

Includes:

• Updating dependencies
• Removes Cake!
• Uses dotnet/msbuild to build in Azure DevOps directly
• Moves Stylecop to .editorconfig
• Moves to .NET 6 for build and targets
• Fixes build configuration for CI to only build required libraries and not samples
• Renames Net5Windows example to NetWindows

PR Type

What kind of change does this PR introduce?

• Refactoring (no functional changes, no api changes)
• Build or CI related changes

What is the current behavior?

Can't Build repo in VS 2022 and in CI

What is the new behavior?

Can build in VS 2022 locally, on commandline, and in CI

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

Other information

[ghost]

Thanks michael-hawker for opening a Pull Request! The reviewers will test the PR and highlight if there is any merge conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[michael-hawker]

@niels9001 @Arlodotexe mind taking a look? Think this is a fairly straight-forward swap out in the end; but took a bit of trial and error (realized tests are interactive currently, and build variable wasn't being replaced).

Would like to merge this in the morning and then close out the remaining open PRs together so we can get a new 7.1.3 out. I notified @Richasy to help test out the PR bits as well in comparison to 7.1.2 to ensure we don't get any surprises.

Though did a quick comparison in NuGet Package Explorer:

7.1.2 packages:

New PR packages:

Outside of the signing step (which was unchanged, just not done for PRs), the package construction looks identical to me.

[niels9001]

@michael-hawker Yeah packages look pretty much identical and no unexpected changes as far as I can judge :). Good if @Arlodotexe can do a quick scan as well :)

[michael-hawker]

Not sure of the old behavior of the Unit Tests, or something changed with an MSAL update or something:

Seems to have to do with auto-signin but setting that property to false doesn't help. We'll have to shore up tests in the future later if we invest more in larger changes and investments to the library in the future.