eBFP for Windows should use the new PackageReference nuget import style

[Alan-Jowett]

eBFP for Windows should use the new PackageReference nuget import style

[ygvalent]

Based on my research and experiments, it is possible to use PackageReference nuget import style for there projects, There are caveats, however:

• Wix must be upgraded to at least v4 (PackageReference first introduction), v5 or better yet v6. There are licensing caveats with v6, see next comment
• vcxproj projects should support the change natively in this repository and sub-modules
• CMake scripts in this repository and sub-modules must be reviewed and updated to generate proper references
• PowerShell scripts in this repository and sub-modules must be reviewed and updated to run fix paths and restore at appropriate times.
• Various projects import .props files with WDK/SDK references. These must be reviewed as well.

[ygvalent]

Update and a question for @Alan-Jowett: Wix v6 requires Open Source Maintenance Fee payment for continued usage paid by becoming a sponsor. I see that "Microsoft Open Source and Samples" is already in the sponsor list. Is it safe to assume that upgrading installer project and developing one for ntosebpfext using Wix v6 will be in compliance with FireGiant's licensing terms from Microsoft point if view?

Additionally, Wix v3.14.1 currently used by the project is in maintenance since March 2024 and its repository was archived. This tells me that even if a critical issue is found in v3, authors will push to upgrade to newer versions. That said, Wix4 and Wix5 were superseded by Wix6.

[shankarseal]

@shankarseal to follow up.

[shankarseal]

@ygvalent, per my conversation with Microsoft OSS folks, yes, we can use Wix 6 in the eBPF for Windows repo.