Upgrade from `v4.5.2` to LTS (or STS) version

The following project file(s) target a .NET version that's no longer supported.
This is an auto-generated issue, detailed and discussed in [dotnet/docs#22271](https://github.com/dotnet/docs/issues/22271).

| Target version | End of life | Release notes | Nearest LTS TFM version |
| --- | --- | --- | --- |
| `v4.5.2` | N/A | [v4.5.2 release notes](https://devblogs.microsoft.com/dotnet/announcing-the-net-framework-4-5-2/) | `net48` |

- [ ] upgrades/matching-game-netframework/winforms/cs/MatchingGame.Logic/MatchingGame.Logic.csproj
- [ ] upgrades/matching-game-netframework/winforms/cs/MatchingGame/MatchingGame.csproj
- [ ] upgrades/matching-game-netframework/winforms/vb/MatchingGame.Logic/MatchingGame.Logic.vbproj
- [ ] upgrades/matching-game-netframework/winforms/vb/MatchingGame/MatchingGame.vbproj

Consider upgrading projects to either the Standard Term Support (STS) or Long Term Support (LTS) versions.

If any of these projects listed in this issue are intentionally targeting an unsupported version,
you can optionally configure to ignore these results in future automation executions.
Create a (or update the) *dotnet-versionsweeper.json* file at the root of the repository and
add an `ignore` entry following the
[globbing patterns detailed here](https://learn.microsoft.com/dotnet/core/extensions/file-globbing).

```json
{
"ignore": [
"**/path/to/example.csproj"
]
}
```

Start with the four listed .csproj and .vbproj files and inspect their target framework entries. Update each project from v4.5.2 to the nearest LTS TFM, net48, then build the C# and Visual Basic Matching Game projects to confirm the upgrade is complete.

Written by the indexing model from the issue text.