SPC060101: Consider the deployment of solution per web application and not globally
SPC060103: Do not deploy prohibited assemblies
SPC060105: Do not deploy thumbs.db
SPC060106: Do not reset webserver
SPC060107: Define mode 'Recycle' for Solution upgrade
SPC060108: Do not deploy files directly into system folder
SPC060111: Do not deploy batch files (.bat)
SPC060112: Do not deploy PowerShell scripts (.ps1)
SPC060113: Do not deploy setups (.msi)
SPC060201: Deploy Assembly which must run in full trust to GAC
SPC060202: Avoid deployment of Assembly to GAC if it is not necessary
SPC060203: Do not deploy assembly with DEBUG mode
SPC060204: Do not deploy SharePoint assemblies
SPC060205: Do not deploy assembly multiple times
SPC060206: Do not deploy empty Assemblies
SPC060209: Do not deploy SPWebConfigModifications via features
SPC060303: Do not deploy RootFile to TEMPLATE folder
SPC060304: Do not deploy RootFile multiple times
SPC060401: Do not deploy Images to LAYOUTS folder
SPC060402: Deploy only Images to IMAGES folder
SPC060403: Deploy binary files (like Assemblies) to ClientBin folder
SPC060404: Do not deploy TemplateFile multiple times
SPC060405: Do not deploy files of a Feature as TemplateFile
SPC060501: Do not deploy Features ElementFiles as Resources
SPC062101: Deploy missing image for Feature
SPC062102: Deploy missing ElementManifest or ElementFile in Feature
SPC062103: Do not deploy feature with same folder name multiple times
SPC062104: Do not deploy feature with same ID name multiple times
SPC062111: Do not deploy empty ElementManifests in Features
SPC067201: Do not deploy Webservice (.asmx) to LAYOUTS folder
SPC067202: Do not deploy Administration Webservice (.asmx) to ADMIN folder
SPC067601: Do not deploy a WCF Webservice (.svc) to LAYOUTS folder
SPC067602: Do not deploy a WCF Administration Webservice (.svc) to ADMIN folder
SPC067701: Deploy missing image for WebTemplate

SPC060501: Do not deploy Features ElementFiles as Resources

Resource files can be used to deploy resources to an existing Feature folder. If the target Feature is part of the same solution package binary files should be deployed as ElementFile in the Feature. If the target Feature is not part of the package it does make sense to use Resources (e.g. to deploy additional languages to existing features).

TypeName: DoNotDeployFeatureFilesAsResource
CheckId: SPC060501
Severity: CriticalWarning
Type: ResourceDefinition
Resolution

Bad deployment of file 'WebParts.xml':

<Solution xmlns="http://schemas.microsoft.com/sharepoint/">
   <Resources>
      ...
      <Resource Location="FEATURENAME\WebParts.xml" />
      ...
   </Resources>
   <FeatureManifests>
      <FeatureManifest Location="FEATURENAME\feature.xml" />
   </FeatureManifests>
</Solution>


Better depoy the 'WebParts.xml' as ElementFile in the Feature FEATURENAME:

<Feature xmlns="http://schemas.microsoft.com/sharepoint/" ... >
   <ElementManifests>
      ...
      <ElementFile Location="WebParts.xml" />
      ...
   </ElementManifests>
</Feature>

comments powered by Disqus

Copyright © 2013 RENCORE AB. All Rights Reserved

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

SharePoint Code Analysis Framework, Version 4.5.2.7855, see www.spcaf.com for more information