I am migrating a complex mixed C++/.NET solution from VS2008 to VS2010.
The upgraded solution works in VS2010, but the build system is always refereshing one C++/CLI assembly. It doesn't recompile anything, but the linker touches the file. The causes a ripple effect downstream in the build as a whole bunch of dependent then get rebuilt.
Any ideas on how to find out why it thinks it needs to relink the file? I've turned on verbose build logging, but nothing stands out.