Operational Services

AJAX applications can have one pitfall: the browser can't handle the history state, so the usual features don't work (back, forward, refresh, etc.). To overcome this you need to explicitly add browser history support. With ASP.NET (since 3.5 SP1) it's pretty straightforward. To do that you have to enable history in the ScriptManager and make an event handler for navigation.

This error message can have different causes. I will talk about one of them, that I found reading the ASP.net forums (Bug : Setting ScriptPath). This is the type of error that can drive someone insane.

Using standard .NET functionality it is easy to share the authentication cookie accross several sites when using Forms Based Authentication, even if these applications reside on different servers. It requires some minor changes to web.config and the authentication code.

Sometimes you will see the error "Resource not found" in a .NET application, but without specifying which resource is missing. In this article it is explained how to find out more about which resource is causing this.

Sometimes you will find the need to upload files larger than the default SharePoint limits allow. In this article it is explained not only how to increase the maximum permitted size limits, but also the execution and connection timeout limits, which will need to be increased for large files.