SharePoint Customization Analysis Framework (SPCAF)

Farm/Sandboxed Solutions

Declare attribute 'Title' and 'Description' in Solutions

Define AssemblyFileVersion in Assembly

Do not store Urls hardcoded in Assembly

Do not inherit WebParts from Microsoft.SharePoint.WebPartPages.WebPart

Do not make SiteDefinition visible in the whole farm

Declare attribute 'Description' in Features

Declare attribute 'Version' in Features

Make Features with scope 'Farm' or 'WebApplication' visible

Consider to make Feature with scope 'Web' or 'Site' hidden

Declare attribute 'Title' and 'Description' in FeatureActivitationDependencies

Define attribute 'ReceiverAssembly' in Feature as full qualified assembly name

Declare all FieldTypes in a single file

Declare attribute 'Inherits' in ContentTypes

Define attribute 'ID' in ContentTypes uppercase

Declare 'TemplateType' and 'FeatureId' for external ListInstance

Declare attribute 'Description' in CustomActionGroup

Declare attribute 'Sequence' in DelegateControl.

Declare attribute 'Id' in DelegateControl.

Declare property 'Title' and 'Description' in WebPart

Do not write in ASPX Pages 'Register' tags in a single line

Avoid inline JavaScript in ASPX Pages

Avoid inline CSS in ASPX Pages

Do not write in ASPX Pages 'Register' tags in a single line

ASPX pages should write the Register tag in separate lines to improve readability of the code.

CheckId	SPC046901
TypeName	ASPXPageShouldProvideRegisterTagsInSeparateLines
Severity	Warning
Type	ASPXFile

The ASPX page should write Register tag in separate lines to improve readability of the code.

Message Suppression

Copyright © 2009 - 2020 Rencore

SharePoint Customization Analysis Framework (SPCAF), 7.15.0.0

Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.