Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disladies clothObject reference not set to an instance of an objeabled before deploying into production scenario.

<configuration>

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Stack Trace:

</configuration>

<compilation debug="true"/>

<system.web>

[NullReferenceException: Object reference not set to an instance of an object.] AspDotNetStorefrontCommon.AppLogic.IsMobile() +172 AspDotNetStorefront.Global.Application_BeginRequest(Object sender, EventArgs e) +205 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Note that this second technique will cause all files within a given applicaladies clothingtion to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

</system.web>

or:

ladies clothObject reference not set to an instance of an obje, Source Error:

2) Add the following section to the configuration file of your application:

<%@ Page Language="C" Debug="true" %>