I have a Windows 2003 Server notebook I use for development. I have a dozen or so IIS 6 sites, and recently decided to place WSS on here for use with BizTalk Server 2006.
Alas, the woes of WSS and hostile take-overs!!!
I installed WSS on the Default Web Site, added all of my exclude paths in WSS for the sites I needed to continue hosting/developing, and ran into the infamous “Trust” and “Session State” issues. In summary I made the following modifications to resolve these 2 issues:
<
httpHandlers>
<
clear />
<
add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory"/>
<!--
<add verb="*" path="/_vti_bin/*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />-->
<
add verb="*" path="*.aspx" type="Microsoft.SharePoint.ApplicationRuntime.SharePointHandlerFactory, Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
</
httpHandlers>
Notice I added the <clear/> and my own PageHandlerFactory, commenting out the SharePoint path.
Next I removed the comments on the name=”Session” handler a little lower in the file.
Finally, I changed the <trust level= from the WSS setting to “Full” Please see the following...
<
pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" />
<!--
<trust level="WSS_Minimal" originUrl="" />-->
<
trust level="Full"/>
Best Practice? No, absolutely not. But this is a development notebook and I get the full benefits of WSS and can still do all of my other ASP.Net 1.1 and 2.0 development unhindered now.
Hopefully this will help some others out there...