MSDN > Home page del forum > Visual Studio Code Analysis and Code Metrics > FxCop 1.36 missing DoNotConcatenateStringsInsideLoops rule
Formula una domandaFormula una domanda
 

Con rispostaFxCop 1.36 missing DoNotConcatenateStringsInsideLoops rule

Risposte

  • venerdì 12 ottobre 2007 16.48Todd KingMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Hello,

     

    In FxCop 1.36 we have removed our data flow engine and all the associated data flow rules with it. I'm sorry to say CA1818 was one of those dataflow rules we removed. We are planning on adding those rules back in, in a future release once we have completed our work on our new data flow engine.

     

    -Todd

     

  • venerdì 12 ottobre 2007 17.51David M. KeanMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

     

    In saying that though, it is likely that we will not be recovering DoNotConcatenateStringsInsideLoops - this rule lack any real context as to whether a particular problem was really going to effect the performance of an application.

     

    However, the Profiler guys are looking at recovering this analysis in the future.

Tutte le risposte

  • venerdì 12 ottobre 2007 16.48Todd KingMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Hello,

     

    In FxCop 1.36 we have removed our data flow engine and all the associated data flow rules with it. I'm sorry to say CA1818 was one of those dataflow rules we removed. We are planning on adding those rules back in, in a future release once we have completed our work on our new data flow engine.

     

    -Todd

     

  • venerdì 12 ottobre 2007 17.51David M. KeanMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

     

    In saying that though, it is likely that we will not be recovering DoNotConcatenateStringsInsideLoops - this rule lack any real context as to whether a particular problem was really going to effect the performance of an application.

     

    However, the Profiler guys are looking at recovering this analysis in the future.