Thanks for looking into this. So that I’m clear, when you say that “they are mistakenly marked,” do you mean that WACK mistakenly marks them as Debug when they are actually Release? Or, is it that your IDE/compiler creates a Debug mode DLL even though you want it to create a Release one?
It turns out that this particular “debug mode” test is not a showstopper for getting an app into the Windows Store. The FAILED “Debug configuration test” is within the optional tests section of WACK results reporting:
Results for optional tests
The tests in this section are informational only and will not be used to evaluate your app during Windows Store onboarding. Investigating failures is recommended to ensure that users will not be impacted.
However, it still would be nice to have a fix for this in a future update, since it’s possible that this test may not be an optional in the future.