I was having a problem with this fxcop rule today CA2227. This error was being thrown out on all the Associations when using the Linq to sql templates here: http://l2st4.codeplex.com/
Well of course we cannot have that as this violates checkin policy, so what I did was add this line here to the template:
[GeneratedCodeAttribute("Microsoft.VisualStudio.Editors.SettingsDesigner.SettingsSingleFileGenerator", "9.0.0.0")]
I googled this problem and landed on Andre Loker's blog here. I understood the problem as he prensented it, but umm Microsoft is doing this..Yes.
So I dug deeper..and came here:
Yes, it is a problem, but the workaround is against our policy, so onward...bound to here
Great justification and it fit my needs. Yes there is some evil when using code generations, but I like having more control and the linq to sql T4 templates give me that.
Hope this helps someone else.
ba1dfbf8-d5d2-4b8f-8a9e-cbf462b0c8b6|1|5.0
.Net , C#
fxcop ca2227 linq to sql