Sitecore Swamp

Dive in the Sitecore Swamp


Remove TFS workspaces

In command line prompt:

<workspacefoler>\"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\tf.exe" workspaces /remove:*

note: Visual Studio 12 is Visual Studio 2013

Sitecore Best Practice - MVC


  • Use space in item name to provide better experience for content author, consider using Display Name for long item names
  • Do not use hyphen in any item name, and avoid using other special characters
  • Always create your own username in Sitecore and login with it
  • Do not use item name for display (rendering)

Template and Field

  • ​​All template should created under /content/templates/[Client Name]:
    • Page Template
      • ​​Represents a type of page​
      • Has layout and renderings preset in standard value​
      • Inherited from Page Base​
    • Component Template
      • Represents a view model of a rendering
      • Grouped in folder which reflects the co​ntroller na​​me
      • Inherited from Component Base​
    • Data Template
      • ​Any other template which is neither component nor page
      • Grouped in folder which reflects the purpose of usage​
      • Use meaningful name for Template and Field name, and avoid using  to provide better experience for content author
  • D​o not use hyphen in name 
  • Try to provide the source for a template field to reduce the effort for content author to lookup the entire content tree
  • Use item GUID as Sitecore field source to reduce the Sitecore refactoring effort​​​​
  • Assign the sortorder for template field section. Please see below the suggested sortorder:
    • Content/Data: 0 - 990 (not need to change)
    • Configuration: 1000 - 9900
    • Setting: 10000 -
  • Configure a meaningful icon for template
  • Configure the insert options in template standard value to reduce the effort for the content author to lookup the entire template tree ​
  • Use title and short description of field item to provide content author intructional text for that field.  

​​Layout and Rendering

  • Use View Rendering when the view model is Sitecore the template from context data source item with simple logic
  • Use Controller Rendering when the view model is built with  complex logic
  • Sitecore rendering should be grouped as epic under \content\layouts\rendering\[Client Name]\[Function Area]\[view]


  • [Client Name].TDS.Core 
    • core database items 
  • [Client Name].TDS.Master 
    • Layout items - /sitecore/Layout/Layouts/[Client Name] 
    • Rendering items- /sitecore/layout/Renderings/[Client Name] 
    • Templates items - /sitecore/templates/[Client Name] 
    • System items - /sitecore/System exclude the dictionary items 
  • [Client Name].TDS.Master.Content 
    • Content Items /sitecore/Content 
    • Dictionary items - /sitecore/System/Dictionary/[Client Name] ​
    • Media Items /sitecore/Media Library
  • ​Only add items into TDS if it's necessary


  • ​Always patch the custom configuration in \App_Config\Include\custom\z.[configuration section].config​​.
  • To get the overview of Sitecore configuration, go to http://[sitename]/sitecore/admin/showconfig.aspx​​.
  • To get the overview of Sitecore cache, go to http://[sitename]/sitecore/admin/cache.aspx.

Display More Details in Visual Studio Build Output

If you demand more information from Visual Studio output when building the VS solution, here the way:

VS > Tools > Options > Projects and Solutions > Build and Run

By default, the minimal is selected, and it only displays the most important messages. Normally, I change it to Detailed, you will see the difference as much more information will be in the output. Together with VSColorOutput, you will have the best experience on the VS build output.

Sitecore Modules Compatibility Table

Here's awesome compatibility in between Sitecore versions (6.0 - 8.1) and major modules:

Sitecore admin password reset SQL

UPDATE [aspnet_Membership] SET Password='qOvF8m8F2IcWMvfOBjJYHmfLABc=' WHERE UserId IN (SELECT UserId FROM [aspnet_Users] WHERE UserName = 'sitecore\Admin') 

Upgrade to Sitecore 8 - When

Sitecore 8.1 has been released for a month now. If you are make yourself catch up with 6.x and they are going to out of mainstrean support by end of this year, and give another year for 7.1/7.2.
ProductInitial Release DateMainstream Support End DateExtended Support End DateSustaining Support End Date
Sitecore 8201531-Dec-201831-Dec-202131-Dec-2023
Sitecore 7.5201431-Dec-201731-Dec-202031-Dec-2022
Sitecore 7.2201431-Dec-201731-Dec-202031-Dec-2022
Sitecore 7.1201331-Dec-201631-Dec-201931-Dec-2021
Sitecore 7.0201331-Dec-201631-Dec-201931-Dec-2021
Sitecore 6.6201231-Dec-201531-Dec-201831-Dec-2020
Sitecore 6.5201130-Jun-201531-Dec-201731-Dec-2019
Sitecore 6.4201030-Jun-201531-Dec-201631-Dec-2018
Sitecore 6.3201030-Jun-201531-Dec-201631-Dec-2018
Sitecore 6.2200930-Jun-201531-Dec-201531-Dec-2017
Sitecore 6.1200930-Jun-201531-Dec-201531-Dec-2017
Sitecore 6.0200830-Jun-201530-Jun-201531-Dec-2016

What are the difference between the support phase:

Support TypeMainstream Support PhaseExtended Support PhaseSustaining Support Phase
Sitecore online documentation, knowledge base, and discussion forums access
Assistance with production incidents$
Security updates and fixes
Assistance with errors or unexpected behavior during installation or development
Addressing product defects as hotfixes or patches
Compatibility fixes for supported technology platforms
Timeline for each support phase, counted from the product’s general availability date
3 years6 years8 years


$Contact regional office for support options
-Not available

Following the mainstream