TFS 2017: policy check works on check

Question

I have the usual TFS validation policy that is used for some projects in the company. Some of the projects are huge, and for them, political policy takes about 10 seconds. It's okay to spend 10 seconds every time someone checks, because he will prevent the occurrence of problems that can take hours. Therefore, politics really helps. The problem I am facing is that VS launches the policy not only for checks, but also fires it from the scan and saves the extracted file. It really annoys everyone. And now I see that the developers have disabled the policy to avoid VS hanging.

Does anyone know why Visual Studio will enforce the policy during validation and save?

I don't think VS has any settings that could prevent a launch other than checkin, but is there a way in the code so that I can determine if the action is Checkin, checkout or save so that I can write my logic respectively?

Answer 1

Typically, a validation policy only works when validating pending changes. Therefore, please double check if the problem is really caused by the user registration policy.

For a registration policy, you can disable it when checking files for editing, and then enable it when you want to check for pending changes.

To enable registration policy

• , .
• .
• , , .
• .

• , .
• .
• , , .
• .

. .

---

UPDATE:

, , ?:

TFS .

, , .

VS , , : https://docs.microsoft.com/en-us/vsts/tfvc/set-enforce-quality-gates?view=tfs-2017#in-this-section