Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Code analysis error during Check in to TFS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    When I'm trying to check in to TFS there's an error:
    "An unexpected error occurred while evaluating the Code Analysis check-in policy. The error might be transient. Try again." https://docs.microsoft.com/en-us/visualstudio/code-quality/code-analysis-policy-errors?f1url=https%3A%2F%2Fmsdn.microsoft.com%2Fquery%2Fdev15.query%3FappId%3DDev15IDEF1%26l%3DEN-US%26k%3Dk(vs.codeanalysis.policyfailures)%26rd%3Dtrue&view=vs-2019

    There is no extra information by clicking on this error. I've tried to check the requirements from the reference, but that didn't help.
    The solution contains .Net Core 2.0 projects and .Net Framework 4.6.2 projects

    TFS settings set Microsoft Extended Correctness Rules, project rules are the same, checkbox "Enable Code analysis on build" checked.
    The solution was rebuilt, also I've tried to run Code Analysis on Solution with result "Code Analysis Complete -- 0 error(s), 20 warning(s)"
    The same error happens in VS2017 and VS2019 

    I really appreciate any help!
    Tuesday, June 4, 2019 4:05 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Asteron 1204,

    Thank you for posting here.

    For your question is more related to TFS, you could get help from StackoverFlow.

    https://stackoverflow.com/questions/tagged/tfs

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions. 

    Best Regards,

    Wendy

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, June 5, 2019 5:36 AM