Month: November 2013

Design time error, Session state can only be used when enableSessionState is set to true


Hello, i got this error last week, so i wanted to blog about the solution:

The full error is:
Session state can only be used when enableSessionState is set to true,
either in a configuration file or in the Page directive.
Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the
<configuration>\<system.web>\<httpModules> section in the application configuration.

Despites the sessionState mode property, enableSessionState property is used to specify whether the session state is enabled. It can be set either in a configuration file or in the Page directive.

1. Page Directive, see if you have enableSessionState set to false.

<%@ Page … enableSessionState=”True” %>

2. Enable session state for all the pages in the Web application in Web.Config file <pages enableSessionState=”true” enableViewState=”true” … />

We have KB on this, you can see more details here: http://support.microsoft.com/kb/307598

add SessionStateModule to system.web section, it should be added tosystem.webServersection.

<system.webServer> <modules> 
<remove name="Session" />
<add name="Session"
type="System.Web.SessionState.SessionStateModule,
System.Web, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>
</modules> </system.webServer>

enjoy 😉

Advertisements

Sharepoint 2013 Create a Master Page based on Seattle.master with VS 2012


Cool blog and excellent Post !!

Raquel Aline kb

Create a new project:

Branding

Configure as a Sandbox Solution:

Branding1

Add a new Module to your project:

Branding2

Download a copy of Seattle.master:

Branding3

Add the copy to your module, rename to CustomMaster.master, and Change your elements.xml file to point to _catalogs\masterpage folder:

Branding4

Change your masterpage, to include a welcome message:

Branding7

Deploy your solution and change your Site master page:

Branding5

Verify that it shows your welcome message:

Branding6

View original post

Assembly signing failed; output may not be signed


Hello

I kept getting this error in my solution builds.

Assembly signing failed; output may not be signed — Error signing assembly — The process cannot access the file because it is being used by another process.

The solution I found was to go to Tools –> Options –> Projects and Solutions –> Build and Run and assign the parallel project build number to 1.

This will make your builds slower since it will only compile 1 project at a time, but I have seen this type of issue go away once I backed down on the parallel compiling.