MSDN > フォーラム ホーム > Visual Studio Code Analysis and Code Metrics > FxCop 1.36 missing DoNotConcatenateStringsInsideLoops rule
質問する質問する
 

回答済みFxCop 1.36 missing DoNotConcatenateStringsInsideLoops rule

回答

  • 2007年10月12日 16:48Todd KingMSFT, モデレータユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     回答済み

    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

     

  • 2007年10月12日 17:51David M. KeanMSFT, モデレータユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     回答済み

     

    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.

すべての返信

  • 2007年10月12日 16:48Todd KingMSFT, モデレータユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     回答済み

    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

     

  • 2007年10月12日 17:51David M. KeanMSFT, モデレータユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     回答済み

     

    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.