unmanaged c++ dll dependency not getting copied to application folder but different managed dll is

I have a VS2010 C++ application with dendencies/r开发者_StackOverfloweferences to two DLLs. After building the application the managed dll, call it A, gets copied to the application folder from its library folder. The other one, B, does not. I can delete A by hand rebuild and it always shows up.

I dread doing post build rules in B's vcxproj because I will soon have a 2nd application that also needs references to B.

I have compared the Reference settings between DLL A and DLL B and they appear to have the same settings, (copy local = true, false, false, true, false)

Thanks all.

---

The way that references are set up in VS2010 makes it look like this should work, and it would be extremely useful if it did. Unfortunately, Microsoft has pretty much made a policy of giving the finger to non-.NET developers since VS2005, and that trend continues with VS2010. This issue was reported to Microsoft.Connect where they confirmed that they could reproduce it, then closed it as "by design." So you probably will have to continue cobbling together an ugly set of post-build commands.