Home Dashboard Directory Help

CA0001 errors in TFS 2012 when executing builds by SWarnberg


 as Not Reproducible Help for as Not Reproducible

Sign in
to vote
Type: Bug
ID: 771950
Opened: 11/22/2012 6:58:53 AM
Access Restriction: Public
User(s) can reproduce this bug


After upgrading to TFS2012, we get the above Code Analysis error when executing builds. This happens from time-to-time, not always.
This was a known problem in TFS2008 because of a multi-threading issue in Static Code Analysis. It was, however, fixed in TFS2010, but now it seems to have been reinvented again in TFS 2012.

CA0001 : Rule=Microsoft.Performance#CA1811, Target={XXX}.#SerializeObjects(System.Collections.Generic.List`1<System.Object>) : Collection was modified; enumeration operation may not execute.
Sign in to post a comment.
Posted by Microsoft on 4/11/2013 at 6:39 PM
As we're still unable to reproduce this Code Analysis issue ourselves, I'm going to resolve this as Not Repro for now. If you can submit a zipped project that demonstrates this issue occurring, please do reactivate the bug so we can take a look.

Thanks again!

Alex Turner
Senior Program Manager
Visual Basic and C# Compiler
Posted by Microsoft on 3/12/2013 at 5:01 PM
Thanks for reporting this issue you've encountered with Visual Studio!

We've attempted to reproduce this build race condition ourselves, but have so far been unable to see it happen. We'll need you to attach a small demo project that shows this issue occurring. Once we have such a project, we can continue investigating this bug.

Thanks again!

Alex Turner
Senior Program Manager
Visual Basic and C# Compiler
Posted by Microsoft on 11/22/2012 at 6:44 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 11/22/2012 at 7:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.