Manifest-based ETW provider - Decoding File Locations

Question

I am trying to add ETW tracing to a DLL (written in C++) I have created. I am using the manifest-based method.

Tracing is working, but it appears I need to set the "Decoding File Locations" in the manifest to an absolute path before building the DLL.

The DLL could be deployed anywhere though, so the decoding path varies depending on the user's installation.

Is there a way around this at all?

Thanks.

Can you add references and links where appropriate (e.g. the *manifest-based method*, documentation on *"Decoding File Locations"*). — IInspectable, Mar 29 '16 at 08:24

score 3 · Accepted Answer · edited Mar 25 '19 at 12:53

3

When installing the provider, be sure to set the switches /resourceFilePath and /messageFilePath to the path of your DLL. This will override the decoding file locations specified in the manifest that the DLL was built with.

e.g.:

wevtutil.exe /resourceFilePath:path_to_DLL /messageFilePath:path_to_DLL im path_to_manifest

edited Mar 25 '19 at 12:53

valiano

16,433
7
64
79

answered Mar 29 '16 at 23:49

emersond

46
1

Note that this method only works with Windows 7 or higher. – jamesd Mar 30 '16 at 00:44

Manifest-based ETW provider - Decoding File Locations

1 Answers1