Montag, 11. Juli 2011 19:59I have a custom build activity that references Microsoft.VisualStudio.Coverage.Analysis. When the custom assembly is loaded by the build I get errors in the event log saying that "Microsoft.VisualStudio.Coverage.Symbols.dll or one of its dependencies could not be loaded. "The module was expected to contain an assembly manifest." However, if I run the assembly (it is an executable) it doesn't have any issues. Any ideas what could be wrong?
Dienstag, 12. Juli 2011 07:40Moderator
What command line you used in the custom build event?
As far as I know, Microsoft.VisualStudio.Coverage.Symbols.dll is a native module which contains no manifest, if your executable works well, you may just ignore the error.
Eric Yang [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Dienstag, 12. Juli 2011 16:27The executable seems to work (they call it from another workflow using the InvokeProcess activity), but when the build service runs it seems like it tries to load Microsoft.VisualStudio.Coverage.Symbols.dll as a managed assembly and fails. This causes my activity library to fail to load and my build workflow to fail immediately.
Donnerstag, 14. Juli 2011 08:01Moderator