[BUG] Significant amount of build warnings via msbuild.exe

[mjr4077au]

Describe the bug

Hi there. We currently build this project via msbuild.exe so we can digitally sign the DLLs we generate. It's something I've noticed in the past, but a lot of projects that (presumably) rely on dotnet build seem to miss a lot of warning cases that msbuild.exe reports on.

The warnings we receive are attached, most are fairly minor.

warnings.log

Reproduction

1. Build the project using Visual Studio or msbuild.exe from the command line.
2. Observe the warnings above as they're received on-screen.

Suggested Solution

Review each warning and address the underlying problem.

Library Version

0.10.1

Operating System

Windows 11

Framework

.NET Framework

Framework Version

4.7.2

Source of Package

Self-Compiled

Additional Notes

No response

Validations

• [x] Check that there isn't already an issue that reports the same or similar problem.
• [x] Check that this is a bug in the library that should be fixed, not a feature, also this is not about the documentation. (Or please choose the right repo and template.)
• [x] This is one single problem, or a few problems with the same cause. (If you want to report multiple problems, please create one issue for every single problem.)
• [x] You've checked that this problem still exists in the latest version. (Keep in mind that we don't provide any support for old versions.)
• [x] You know that we can't guarantee that we will satisfy your request. This is not really our duty to do everything anyone asks for. Also, you will treat our staff, contributors, and other users with respect and kindness.
• [x] You're sure there's something wrong with the library itself, not how you're using it. (If you are having issues using it and need help, please go to discussion.)

[NotYoojun]

Most of the warnings are harmless and can be safely ignored. If you really need to dismiss them you may want to set the ignored warnings in the csproj file.

[mjr4077au]

Agreed but thought I'd ask about it anyway. Would you be open to a PR to address some/all of them? Some of them are simple things, such as unused fields in classes that may have been left behind from refactoring (unless they're accessed reflectively, etc)