GitHubSync update

.config/dotnet-tools.json

@@ -0,0 +1,12 @@
+{
+  "version": 1,
+  "isRoot": true,
+  "tools": {
+    "cake.tool": {
+      "version": "6.0.0",
+      "commands": [
+        "dotnet-cake"
+      ]
+    }
+  }
+}

.github/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+Thanks you for your interest in contributing - Please see our our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+
+### Bug Fixes
+
+If you're looking for something to fix, please browse the open issues.
+
+Follow the style used by the [.NET Foundation](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/coding-style.md), with a few exceptions:
+
+- Apply readonly on class level private variables that are assigned in the constructor
+- 4 SPACES - tabs do not exist :)
+
+Read and follow our [Pull Request template](PULL_REQUEST_TEMPLATE.md) if you are submitting fixes.
+
+### Feature Requests
+
+To propose a change or new feature, please make use the feature request area in issues.
+
+#### Non-Starter Topics
+The following topics should generally not be proposed for discussion as they are non-starters:
+
+* Large renames of APIs
+* Large non-backward-compatible breaking changes
+* Avoid clutter posts like "+1" which do not serve to further the conversation
+
+#### Proposal States
+##### Open
+Open proposals are still under discussion. Please leave your concrete, constructive feedback on this proposal. +1s and other clutter posts which do not add to the discussion will be removed.
+
+##### Accepted
+Accepted proposals are proposals that both the community and core team agree should be a part of projects. These proposals are ready for implementation. These proposals are available for anyone to work on unless it is already assigned to someone.
+
+If you wish to start working on an accepted proposal, please reply to the thread so we can mark you as the implementor and change the title to In Progress. This helps to avoid multiple people working on the same thing. If you decide to work on this proposal publicly, feel free to post a link to the branch as well for folks to follow along.
+
+###### What "Accepted" does mean
+* Any community member is welcome to work on the idea.
+* The maintainers _may_ consider working on this idea on their own, but has not done so until it is marked "In Progress" with a team member assigned as the implementor.
+* Any pull request implementing the proposal will be welcomed with an API and code review.
+
+###### What "Accepted" does not mean
+* The proposal will ever be implemented, either by a community member or maintainers.
+* The maintainers are committing to implementing a proposal, even if nobody else does. 
+
+##### In Progress
+Once a developer has begun work on a proposal, either from the team or a community member, the proposal is marked as in progress with the implementors name and (possibly) a link to a development branch to follow along with progress.
+
+#### Rejected
+Rejected proposals will not be implemented or merged into the code base. Once a proposal is rejected, the thread will be closed and the conversation is considered completed, pending considerable new information or changes..

.github/FUNDING.yml

@@ -0,0 +1,8 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: WildGums-oss # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+custom: # Replace with a single custom sponsorship URL

.github/ISSUE_TEMPLATE/---support-request.md

@@ -0,0 +1,16 @@
+---
+name: "\U0001F62C Support Request"
+about: Having Trouble - ONLY contributors to other OSS projects OR people who are
+  funding this project can submit these! If you aren't one of these, expect the ban
+  hammer to fall
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+ONLY active OSS contributors OR people who buy us a coffee can ask questions here. If you don't do either of these things - DO NOT FILE HERE :)
+
+Give as much details as humanly possible if you want any sort of answer!
+
+Enter Question Below (don't delete this line)

.github/ISSUE_TEMPLATE/--bug.md

@@ -0,0 +1,36 @@
+---
+name: "\U0001F99FBug"
+about: Create a report to help us improve
+title: ''
+labels: "s/unverified, t/bug \U0001F47E"
+assignees: ''
+
+---
+
+# IF YOU DON'T ANSWER THIS TEMPLATE - THE BOT WILL AUTOMATICALLY CLOSE YOUR ISSUE!
+
+## Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)
+
+ - [ ] WPF
+ - [ ] Blazor WASM
+ - [ ] .NET Core
+
+## Component
+
+What component is this issue occurring in?
+
+## Version of Library
+
+
+## Version of OS(s) listed above with issue
+
+
+## Steps to Reproduce
+1.
+2.
+3.
+
+## Expected Behavior
+
+
+## Actual Behavior

.github/ISSUE_TEMPLATE/--feature-request.md

@@ -0,0 +1,19 @@
+---
+name: "\U0001F354Feature Request"
+about: Suggest an idea for this project
+title: ''
+labels: "s/unverified, t/enhancement \U0001F423"
+assignees: ''
+
+---
+
+# IF YOU DON'T ANSWER THIS TEMPLATE - THE BOT WILL AUTOMATICALLY CLOSE YOUR ISSUE! 
+
+## Summary
+Please provide a brief summary of your proposal. Two to three sentences is best here.
+
+## API Changes
+Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some "example" code of usage of your new API.
+
+## Intended Use Case
+Provide a detailed example of where your proposal would be used and for what purpose.

.github/ISSUE_TEMPLATE/--thank-you.md

@@ -0,0 +1,10 @@
+---
+name: "❤️Thank You"
+about: Just want to say thank you, this is the one to do it in
+title: Thank You
+labels: ''
+assignees: ''
+
+---
+
+Leave Your Message Below (don't delete this line though)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+### Description of Change ###
+
+<!-- Describe your changes here -->
+
+### Issues Resolved ### 
+
+<!-- Please use the format "fixes #xxxx" for each issue this PR addresses -->
+
+- fixes #
+
+### API Changes ###
+
+<!-- List all API changes here (or just put None) -->
+
+None
+
+### Behavioral Changes ###
+
+<!-- Describe any changes that may change how a user's app behaves or appears when upgrading to this version of the codebase. -->
+
+None
+
+### Testing Procedure ###
+
+<!-- Please list the steps that should be taken to properly test these changes on each relevant platform. If you were unable to test these changes yourself on any or all platforms, please let us know. Also, if you are able to attach a video of your test run, you will be our personal hero. -->
+
+### PR Checklist ###
+
+- [ ] I have included examples or tests
+- [ ] I have updated the change log or created a GitHub ticket with the change
+- [ ] I am listed in the CONTRIBUTORS file (if it exists)
+- [ ] Changes adhere to coding standard
+- [ ] I checked the licenses of Third Party software and discussed new dependencies with at least 1 other team member

.github/dependabot.yml

@@ -0,0 +1,24 @@
+version: 2
+registries:
+  nuget-feed-default:
+    type: nuget-feed
+    url: https://api.nuget.org/v3/index.json
+
+updates:
+- package-ecosystem: github-actions
+  directory: "/"
+  schedule:
+    interval: weekly
+
+- package-ecosystem: nuget
+  directories:
+    - "/src"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: "*Analyzers"
+    versions:
+    - ">= 0"
+  registries:
+  - nuget-feed-default

.github/lock.yml

@@ -0,0 +1,38 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads
+
+# Number of days of inactivity before a closed issue or pull request is locked
+daysUntilLock: 4
+
+# Skip issues and pull requests created before a given timestamp. Timestamp must
+# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
+skipCreatedBefore: false
+
+# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
+exemptLabels: ["pinned", "planned"]
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+lockLabel: false
+
+# Comment to post before locking. Set to `false` to disable
+lockComment: >
+  This thread has been automatically locked since there has not been
+  any recent activity after it was closed. Please open a new issue for
+  related bugs.
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings just for `issues` or `pulls`
+# issues:
+#   exemptLabels:
+#     - help-wanted
+#   lockLabel: outdated
+
+# pulls:
+#   daysUntilLock: 30
+
+# Repository to extend settings from
+# _extends: repo

.github/stale.yml

@@ -0,0 +1,19 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 60
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+  - planned
+  - nostale
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

.github/support.yml

@@ -0,0 +1,23 @@
+# Configuration for Support Requests - https://github.com/dessant/support-requests
+
+# Label used to mark issues as support requests
+supportLabel: support
+
+# Comment to post on issues marked as support requests, `{issue-author}` is an
+# optional placeholder. Set to `false` to disable
+supportComment: >
+  :wave: @{issue-author}, we use the issue tracker exclusively for bug reports
+  and feature requests. However, this issue appears to be a support request.
+  Please use our support channels to get help with the project.
+
+# Close issues marked as support requests
+close: true
+
+# Lock issues marked as support requests
+lock: false
+
+# Assign `off-topic` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Repository to extend settings from
+# _extends: repo

.github/workflows/build-and-test.yml

@@ -0,0 +1,36 @@
+name: Build and test
+
+on:
+  push:
+    branches:
+      - develop
+      - master
+  pull_request:
+
+#permissions:
+  #pull-requests: write
+  #contents: write
+
+jobs:
+  build-and-test:
+    runs-on: windows-latest # Required for some (WPF) projects
+
+    steps:
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        id: checkout
+        with:
+          fetch-depth: 0
+
+      - name: Setup .NET Core
+        id: setup-dotnet
+        uses: actions/setup-dotnet@2016bd2012dba4e32de620c46fe006a3ac9f0602 # v5.0.1
+        with:
+          dotnet-version: '10.0.x'    
+
+      - name: Cake Action
+        id: cake-action
+        uses: cake-build/cake-action@d218f1133bb74a1df0b08c89cfd8fc100c09e1a0 #v3.0.1
+        with:
+          target: BuildAndTest
+          arguments: |
+            IsCiBuild: true