microsoft
Use the latest versions of headers available in the Kit by default (short term), and be metadata configurable (medium term)
Not to be addressed in this pr, but we should track making all of these use the latest in the short term, and be metadata configurable in the medium term
Originally posted by @wmmc88 in https://github.com/microsoft/windows-drivers-rs/pull/411#discussion_r2181231269
@svasista-ms is this meant to track ALL of the metadata config changes or just UCX? what about all the other places where we currently just "get latest" (ex. some of the other class extension headers do this. pretty much all of the versioned headers do)
@wmmc88, I created this to track all the versioned headers that can metadata configurable (or fallback to latest available).
@wmmc88, I created this to track all the versioned headers that can metadata configurable (or fallback to latest available).
Okay i think you need to break this down so that it is actionable (maybe use sub-issues?). We need to identify a list of all the headers that need to be handled with this. Then for each, we need to have to implement the same fix as in #411. And have a separate task to track adding it to the metadata
Sure @wmmc88, we can track adding to metadata in a separate issue. Regarding the list of headers that need such handling, we could start with those available in Visual Studio for C/C++ drivers.
The following image is Driver Settings for a KMDF driver.
Once we have a prioritized list, I will create sub-issues for each.
I think the metadata-configured part of this issue is covered by #299 .
Sure @wmmc88, we can track adding to metadata in a separate issue. Regarding the list of headers that need such handling, we could start with those available in Visual Studio for C/C++ drivers. The following image is
Driver Settingsfor a KMDF driver.Once we have a prioritized list, I will create sub-issues for each.
@svasista-ms that list seems fine to me, but be sure that you know which folders each of those names corresponds to