Проверять на дубликаты ID и существование полей в решении

При copy&paste и большом кол-ве полей зачастую можно упустить уникальность ID/названий полей, а также отсутствие описания поля.

Id #13378 | Release: None | Updated: Jan 19, 2015 at 9:29 PM by dvd73 | Created: Dec 23, 2014 at 11:53 AM by dvd73

Repeat calculated fields declarations in list schema

If you use ContentTypeRef in your list template be sure that all calculated fields from it are repeated. Тоже самое для lookup полей. Lookup поля надо объявлять в одной фиче без аттрибута List и ...

Id #13377 | Release: None | Updated: Jan 3, 2015 at 5:20 PM by dvd73 | Created: Dec 23, 2014 at 11:12 AM by dvd73

Not provisioned entity

Any xml manifest is not included into feature consider as not provisioned.

Id #13350 | Release: December 2014 | Updated: Dec 8, 2014 at 4:05 PM by dvd73 | Created: Dec 8, 2014 at 2:42 PM by dvd73

AfterProperties/BeforeProperties unsafe casting & NULL ref exceptions

While using SPItemEventProperties, the following code is unsafe: properties.AfterProperties["Contracts"].ToString() properties.BeforeProperties ["Contracts"].ToString() The rule should suggest to...

Id #13341 | Release: December 2014 | Updated: Dec 5, 2014 at 3:51 PM by dvd73 | Created: Dec 3, 2014 at 11:52 PM by avishnyakov

Avoid different internal and static names for fields

It might be suggested to avoid having different internal/static names. <Field Name="ContractId" StaticName="ContactIdInSP" /> <Field Name="ContractOrder" StaticName="ContactOrderInSP" /> Having...

Id #13339 | Release: December 2014 | Updated: Dec 5, 2014 at 8:03 PM by dvd73 | Created: Dec 3, 2014 at 12:08 AM by avishnyakov

Avoid mixed "ID" and "Id" in static/internal field names

It might be suggested to avoid mixing up "ID" and "Id" while crafting field: <Field ID="{75c93cbc-03a9-4a3e-9d25-2355bede2f12}" Name="ContractID" /> <Field ID="{75c93cbc-03a9-4a3e-9d25-2355bede2f...

Id #13338 | Release: December 2014 | Updated: Dec 8, 2014 at 4:48 PM by dvd73 | Created: Dec 3, 2014 at 12:02 AM by avishnyakov

Do not get UTC time from DateTime type

SharePoint web site (SPWeb) has it own regional settings with time zone, independent from Windows. You need to bear in mind all datetime conversion procedures to consider site regional settings. D...

Id #13320 | Release: December 2014 | Updated: Nov 27, 2014 at 3:28 PM by dvd73 | Created: Nov 14, 2014 at 7:57 PM by dvd73

Do not provision lookup field BEFORE related list

Насколько плохо делать provision филдов(spfield) в фиче scope=site? Явных противопоказаний нет, но есть один момент который важен. Если поле типа Lookup и List !=Self, то если на момент активации ф...

Id #13311 | Release: December 2014 | Updated: Dec 8, 2014 at 3:32 PM by dvd73 | Created: Nov 5, 2014 at 7:04 AM by dvd73

Xml Comment in Elements File can Break your Content Type

I'm fully with that

Id #13298 | Release: December 2014 | Updated: Nov 28, 2014 at 3:45 PM by dvd73 | Created: Oct 23, 2014 at 9:37 AM by dvd73

Provision calculated field correctly

Calculated field must specify display name in formula section The Calculated Site Columns are only accepted with formula using Internal Names, List Columns only using Display Names. Link

Id #13296 | Release: None | Updated: Dec 8, 2014 at 4:06 PM by dvd73 | Created: Oct 22, 2014 at 3:53 PM by dvd73