Quantcast
Channel: jeff luo's Groups Activities
Viewing all articles
Browse latest Browse all 5

Check in failed due to Best practice when set Best Practice Error as Reject. is anything wrong?

$
0
0

Hi

this is my testing scenario. I enabled the VSS in 2012 RTM VM and set Best Practice Errors as Reject under Version Control ->  System Settings

then I set Warning Level as Error, and clearedthe option "use of labels for developer documentation" under specific checks -> tables.

after create a new table with leaving property DeveloperDocumentation as blank and try to check in the table. and it failed due to "xxx contains best practice errors" and in compiler output window, I can see BP error "mandatory property DeveloperDocumentation not specified".

but as stated in previous, I already cleared "use of labels for developer documentation" in BP.  as my understanding, it shouldn't fail due to this error. so I trace the code and find following codes

 

 

as we can see, in the allowCheckIn method in class SysTreeNode. a new variable bpParameters and call initValue for it. in the initValue of table SysBPParameters, it default all options using NOYES enum as YES. and then it was passed to SysBPCheck through args. and in the main of SysBPCheck perform the BP check base on this parameters setup. so it failed BP checking and return false for allowCheckIn. then failed check in procedure.

is it bug? if yes, is there any hotfix for it?


Viewing all articles
Browse latest Browse all 5

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>