Data caching is a core concept in the web dominated world that we live in. The premise is that we should not have to go back to retrieve data from a data store for every single web request when the data is unchanged, thereby sharing data across web requests. This offers huge performance advantages because all latency related to data fetching, query processing and transmission is eliminated for requests that use the same data.
It is possible to manipulate the web.config file globally by using a little known feature in SharePoint that allows developers to describe a set of changes by using an XML customization file. In fact, both SharePoint and MOSS use this mechanism to publish web.config changes when a web application is created. Create the customization file The customization file is used by SharePoint to apply changes to the web.config file when a web application is created.
You are probably familiar with the fact that SharePoint now has the capability to host site with anonymous access turned on. I learned the hard way that item level permissions do not participate in the anonymous access behavior the way you might expect. When an item does not inherit permissions, it is not possible to enable anonymous access on that item. Note the document library permission settings menu: Here’s the same menu for an item which is not inheriting permissions from the parent library:
When creating custom controls it is often must easier to create a control using the “User Control” development model instead of the “Server Control” model. Server controls generally have a more “low level” feel and dictate that the developer build the control’s rendering from scratch. Either by building a control tree or by constructing the rendered output in code. Alternatively user controls have nice separation of code and presentation by virtue of having a markup file (.
As SharePoint becomes more prevalent in the custom application development realm, there has been some friction and malcontent expressed in relation to deployment processes, team development methods and application upgrade paths. I believe that Microsoft has fallen short on providing the tools necessary to promote and support custom application development on the SharePoint platform. In my opinion, the SharePoint platform should not limit nor impede my ability as a custom application developer to deliver solutions that follow the same deployment principals as any other custom asp.