Sorry, took me a while to find the time to look at this.

I’ve never used it before, but there’s an Activation Context API. Using that API, you can explicitly control which manifest file (or resource) to use, instead of having Windows default to appname.exe.manifest.

I built a quick test project, and that worked nicely (note that the sample code on MSDN seems to lack a call to ReleaseActCtx() — not sure how important that is, but still). I assume this would work as well from a WinUnit test DLL, but I didn’t try that.

I am wondering if this is possible without creating an application manifest?

My scenario is different in that I am using a third party test runner exe, winunit.exe.

Any ideas?

Thank you.