chore: add Genetec Web Player projects to solution

[alafleur-genetec]

This pull request updates the Visual Studio solution file Genetec.Dap.CodeSamples.sln to add new sample projects related to the Genetec Web Player, along with their build configurations and solution folder organization.

Addition of new Genetec Web Player sample projects:

• Added a new solution folder Genetec Web Player and included three new sample projects: GwpDesktopPlayerSample, GwpMinimalApiSample, and GwpRazorPagesSample to the solution.

Build configuration updates:

• Added full sets of build and configuration mappings (Debug/Release, .NET 8/.NET 4.8.1) for each of the new sample projects, ensuring they can be built in all supported configurations.

Solution folder organization:

• Associated the new sample projects with the Genetec Web Player solution folder for better organization within the solution explorer.

[Copilot]

Pull request overview

This PR updates the Samples/Genetec.Dap.CodeSamples.sln solution to include Genetec Web Player sample projects and organize them under a new “Genetec Web Player” solution folder.

Changes:

• Added a new solution folder: Genetec Web Player
• Added three projects to the solution: GwpDesktopPlayerSample, GwpMinimalApiSample, GwpRazorPagesSample
• Added configuration/build mappings and nested-project entries to place the projects under the new solution folder

Comments suppressed due to low confidence (2)

Samples/Genetec.Dap.CodeSamples.sln:1499

• The solution’s *_NET481 configurations currently build this project (ActiveCfg/Build.0 point to Debug/Release). Since this project targets only net8.0, building the solution in Debug_NET481/Release_NET481 will still attempt to compile it and can break NET481-only build environments. Consider removing the Build.0 entries for the *_NET481 solution configurations (so it’s excluded from those builds), or update the project to support net481 / add matching Debug_NET8/Debug_NET481 configurations.

		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug_NET481|Any CPU.ActiveCfg = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug_NET481|Any CPU.Build.0 = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug_NET8|Any CPU.ActiveCfg = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug_NET8|Any CPU.Build.0 = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Debug|Any CPU.Build.0 = Debug|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Release_NET481|Any CPU.ActiveCfg = Release|Any CPU
		{C7C206CB-5A5E-84E9-9A3E-23FA0D563E7F}.Release_NET481|Any CPU.Build.0 = Release|Any CPU

Samples/Genetec.Dap.CodeSamples.sln:1511

• The solution’s *_NET481 configurations currently build this project (ActiveCfg/Build.0 point to Debug/Release). Since this project targets only net8.0, building the solution in Debug_NET481/Release_NET481 will still attempt to compile it and can break NET481-only build environments. Consider removing the Build.0 entries for the *_NET481 solution configurations (so it’s excluded from those builds), or update the project to support net481 / add matching Debug_NET8/Debug_NET481 configurations.

		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug_NET481|Any CPU.ActiveCfg = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug_NET481|Any CPU.Build.0 = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug_NET8|Any CPU.ActiveCfg = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug_NET8|Any CPU.Build.0 = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Debug|Any CPU.Build.0 = Debug|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Release_NET481|Any CPU.ActiveCfg = Release|Any CPU
		{F6FEAE2D-E83E-FC41-0209-C18D1E6DB7C0}.Release_NET481|Any CPU.Build.0 = Release|Any CPU

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.