Showing posts from 2014

Useful Nuget commands

Having the little knowledge of Nuget Commands is important if your company is thinking to adopt EPiServer Continuous Release Process.

In Visual Studio Click  Tools>Nuget Package Manager>Package Manage Settings, Select from Options, Package manager>Package Sources.
Click + Button and add an entry with
Name: EpiServer packages

After these setting you are ready to use EPiserver Nugets. Nuget Packages can be installed from 'Package manager Console' or 'Manage Nuget Packages For Solution' window.

Here are few useful nuget commands

To extract the SQL schema Changes Find the full article (

To update database after upgrade

In order to see the list of available versions of an episerver package you can use a command like this
Get-Package -ListAvailable -Filter EpiServer.Find -AllVersio…

Error handling in IIs 7

Not a new topic but I come across a situation when our offshore team was not able to see the error details. This is reminder if someone forgets that.

In IIS 7.0 The <httpErrors> element allows you to configure custom error messages for your Web site or application. <CustomErrors> won't work.

Click for further details on httperrors

httpError Elements

EPiServer Error handling

Example Production Enviornment Settings
<httpErrors errorMode="Custom" existingResponse="Replace">
      <error statusCode="404" path="/Page404.html" responseMode="ExecuteURL"/>
      <error statusCode="500" path="/500-error-page.html" responseMode="ExecuteURL"/>

Developers Environment Settings:
With Settings
<httpErrors errorMode="Custom" existingResponse="Replace"></httpErrors>
Error Details on screen will be like this

With Settings
<httpErrors erro…

Blocks for EPiServer Commerce Catalog Nodes

Can we use Blocks with Catalog nodes? In theory Yes, what can stop you. We had a requirement when CMS editor can add a Carousel Block to Catalog Nodes. But Block Gadget was not available in CMS Catalog Edit Mode. Only available gadgets were Catalog, Media, Latest and Versions. From architecture point of view I was convinced that we can add ContentArea for Catalog Nodes and Blocks can be reused for Catalog Nodes also. I googled the issue and find an answer by Linus. Its simple I want to keep solution as a self note.

Add the following section under your <> section in web.config and the blocks gadget should appear for the commerce view (given that you have not customized your view):<viewManager> <views> <add name="/episerver/commerce/catalog"> <settings> <add name="AddSharedBlocks" transformationType="Add" definitionName="EPiServer.Cms.Shell.UI.Components.SharedBlocksComponent" plugInArea="/epise…

Upgrade from CMS 6R2 to EPiServer 7 CMS and from EPiServer Community 4.1 to EPiServer Community 7

There is a requirement before upgrading a Community site with separate databases (CMS6r2 and Community 4.1) to EPiServer 7 and Community 7 is to merge the Community database with the CMS database. This is an instruction of how to accomplish this in MS SQL Server 2008 R2.

1. Startup
In the SSMS, right-click the Community database that shall be merged with the CMS database and generate a script.
2. Choose Objects
Select  “Select specific database objects” and then select Tables, Views, Stored Procedures and User-Defined Functions but not all objects within those boxes.  Objects to choose:



Stored Procedures

User-Defined Functions fnEPiServerCommon* fnEPiServerCommunity*
3. Set Scripting Options Save the script to a specific location and save to a single file. Then press the “Advanced button”. 4. Advanced Scripting Options General: Set “Types of data t…