Most of the asp.net application using session, especially data driven applications. Mostly these kind of application using “Inproc” mode of session. During development the developer does not face any kind of problem with the session. When deploy the application the problem arise one by one. In this post I just want to share some thoughts and my professional experience on this issue.
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<script type="text/javascript">
function DisableToolTip() {
// Get the object
var obj = document.getElementById('LnkBtn');
// set the tool tip as empty
obj.title = "";
}
</script>
</head>
<body>
<form id="form1" runat="server">
<asp:LinkButton runat="server" Text="Simple Link Button" ToolTip="Simple Button with Tool Tip" ID="LnkBtn" ClientIDMode="Static" ></asp:LinkButton>
<a href="#" id="lnkDisable" onclick="DisableToolTip();">Disable Tool Tip</a>
</form>
</body>
</html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<script src="Scripts/jquery-1.4.1.min.js" type="text/javascript"></script>
<script type="text/javascript">
$(document).ready(function () {
$("#lnkDisable").click(function () { $('#LnkBtn').attr({'title':''}); });
});
</script>
</head>
<body>
<form id="form1" runat="server">
<asp:LinkButton runat="server" Text="Simple Link Button" ToolTip="Simple Button with Tool Tip" ID="LnkBtn" ClientIDMode="Static" ></asp:LinkButton>
<a href="#" id="lnkDisable">Disable Tool Tip</a>
</form>
</body>
</html>
using System.Globalization;
using System.Threading;
public string changeName(string inputname)
{
string modifiedname = string.Empty;
string[] names = inputname.Split(' ');
foreach (string name in names)
{
CultureInfo cultureInfo = Thread.CurrentThread.CurrentCulture;
TextInfo txtinfo = cultureInfo.TextInfo;
string temp=txtinfo.ToTitleCase(name);
modifiedname = string.Concat(temp, " ");
}
return modifiedname;
}
After a last couple of month (serious 
Cross page posting is used to submit a page (page1.aspx) to another page (page2.aspx). However, the user can still able to access the first page’s (page1.aspx) controls, properties etc in the second page (page2.aspx). In order to access the first page’s control, we have to use “Previouspage” property.
