Code Analysis Policy not Migrating to Team System clients

We have a nightmare of a problem.

Our team has dilligently gone through every single item in the code analysis check-in policy and selected, selected or marked as warning what is appropriate for our project.

"Migrate Code Analysis Policy Settings to Solution"

We all migrated the policy down but discovered we had made some poor decisions that made building nearly impossible. In some cases we corrected our code and in others we concluded the rule is incompatible with our approach. As a result we changed the server policy.

Now, when the team developers attempt to migrate there is a "success" message but the old rules continue to apply. We can manually go in and change the policy on the client, but in some cases (like web sites) we cannot make this change as the option is not in the properties dialog.

Is anyone else having this issue and is there a workaround?

The nightmare is that the policy was originally automatically migrated on a solution level but we have to make the manual change on a project level. We have many projects resulting that a single change equallying a serious effort.

Best regards, Jerry Nixon

[1140 byte] By [JerryNixon] at [2007-12-17]
# 1

Is the new policy 'less restrictive' than the old policy? The migration feature was design to be non destructive so if an individual project wanted to maintain a stricter standard than the official policy, the migration gesture would not toss the stricter settings.

If you turned off all th rules and then migrated, you would have the minimal setting as required by policy.

Sean Sandys, VSTS

SeanSandys-MS at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified