The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
The process of setting up HLK devices, running the tests, collecting the results, packaging for all variants, submitting the package, retrieving the signed package, and integrating the package into your installation/redistributable software is anything but concisely documented. Many of the individual steps have various levels of documentation, but for the most part we all have the same workflow needs (ex: make a change and get it to our customer). I've got all the steps between code change and making an installer automated (with the exception of the HLK signing process).
Are people actually automating that process successfully? If so, are you able to integrate it into the rest of your CI process? I'd be really curious how folks are pulling this off. What does the device topology look like (ex: build machine(s), HLK server/client(s), how do they interact, etc. I find doing basic things like creating a proper .cab file for submission a PITA every time I need to make a new one. I'd love to replace the entire manual process with an automated process that has a single configuration file to account for anything unique to my driver.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Internals & Software Drivers||30 Nov 2020||LIVE ONLINE|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Developing Minifilters||Early 2021||LIVE ONLINE|