I have never seen this problem with the version of VS 11 paired with WDP1 8102 or other pre-beta builds until the version of Visual Studio 11 released on 2/29/12 for Consumer Preview 8250.
I now see the following error consistently on both of my PCs, and other devs here are reporting exactly the same.
mt.exe : general error c101008d: Failed to write the updated manifest to the re
source of file "F:\AccuRev\Voyager_DevHead.pc2.1\Voyager\Build\Bin\x86\Checked\
xr-CoreInterop.dll". The process cannot access the file because it is being use
d by another process. [F:\AccuRev\Voyager_DevHead.pc2.1\Voyager\Src\Core\Intero
I found many bugs in Connect related to MT.EXE, but none seemed to reference MSBuild as the process holding a newly built dll open and causing MT.EXE to therefore fail. I also tried turning off AV (Microsoft Security Essentials) because many bugs in Connect referenced that as a potential conflict with MT.EXE, but that didn’t fix this. Therefore this appears to be a new and different bug.
One of my PCs is an old dual core 4GB Dell Optiplex 780 with 8250 x86. The other is a fast new Dell Optiplex 990 with 16 GB and quad cores. So if it is a race condition, it happens across a broad spectrum of hardware.
We are developing V4 print drivers for Win8. Our solution contains a mixture of C++/Win32 dlls, C# assemblies, and C# applications. We created all the project files using VS 11 – In other words, they are new, not converted or upgraded. The dll for which MT.EXE fails is compiled with the /clr flag and contains both C++/CLI and native C++ code.
This will cause all of our our automated builds, such as our nightly build to fail, so this is blocking our adoption of this release.
Thanks in advance for your time and help!