TraceLogging Vs WppTracing

Hi Guys,
I went through this published article:-

https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/tools-for-software-tracing

I have a driver which uses WPP tracing (which I thought what driver should be using), but I am hearing from different people that WPP is old and TraceLogging/Etw is the way to go.
My Driver uses TraceEvents macros with “tmh” file, had WppTracing set to true in the vcproject files. It needs PDB file to interpret the messages.

For the TraceLogging it seems that the PDB file is not needed and the driver binary has built in information about this.

Can someone please clarify that if we have to release a driver today what logging mechanism should be used (WPP or TraceLogging/Etw)?

Thanks.
Aj

They’re inherently different facilities.

For unstructured, easy, logging in the Release Build of a driver, WPP is still they way to go, IMHO.

It’s what we use here at OSR.

Peter

Thank you Peter!! This is what I was looking for.

https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/tools-for-software-tracing