index > Team Foundation Server - Reporting > code churn - ignore binary files?

code churn - ignore binary files?

Is there any way to get the reports to ignore code churn that occurs in binary files? For example, we have a custom references directory that contains several assemblies.

When the assemblies are checked in, the code churn goes to several hundred thousand lines of code... Which is wrong.

What can I do?

Thanks,

MRG Document Technologies

Chris Lively

Okay, we gave up and pulled the assemblies out of our custom references directory.

MS, one thing to consider for a future release of Team Foundation Server is project dependencies. It would be nice if any dependencies required to build a project were automatically installed on the machine at the time that the project is checked out.

OR

Simply allow us to have directories that when modified (files updated, deleted, added) do not count toward the code churn.

Thanks,

MRG Document Technologies

Chris Lively

Hi Chris,

Thanks for your feedback - we will consider it in future releases.

I'm not sure why those binary files are not getting recognized as binary by the Version Control. Code churn for binary files is not supposed to be recorded. One thing you can do is when you add the binary file to version control is to explicitly specify it as a binary file. eg,

tf add file1.dll /type:binary

This will definitely register this file as binary to the system and its code churn will not be recorded.

Hope that helps!

Mauli

Mauli Shah - MSFT

Hi Mauli,
Thanks for the reply, but that didn't help. The files were marked as binary in team foundation. When I pulled the assemblies out of that folder my code churn jumped to around 1.4 million lines.

Today the code churn reports are more reasonable, but I think they are still out of whack. According to the report 2 of my developers churned about 56000 lines. I know what they worked on and that is way excessive.

How can I figure out exactly what it's counting as churn?

Thanks!

MRG Document Technologies

Chris Lively

In the Code Churn table in TfsWarehouse database, you will see all the entries for the files/changesets that is considered "churn".

Could you please run "tf properties" on the binary files? That way we can see if the system actually recognizes them as binary.

Thanks,

Mauli

Mauli Shah - MSFT

Hi Mauli,
Thanks for the help; however, I decided to just write my own code churn report based on the [dbo.Code Churn] table. The out-of-the-box "Quality Indicators" report went from 40000 to 60000 lines of code change a day down to zero for a solid week. I think you guys must have a join in the sql query that isn't quite right.

Mine shows net changed and lines added by day across the project. Both of which are in line with expectations.

MRG Document Technologies

Chris Lively

reply 6