NOTE: I know the various reasons to avoid using the session, but this is a project I\'ve inherited, so please skip that part of any replies :)
Since it\'s a solved probl
The old patch that can be dug up is unfortunately a little outdated with Elmah now. Here's what I did to log session variables in version 2.0.15523.27 Based on an older patch found here: https://storage.googleapis.com/google-code-attachments/elmah/issue-12/comment-5/elmah-sessionVariables.patch
In Error.cs
Import System.Web.SessionState
using System.Web.SessionState;
Find:
private NameValueCollection _serverVariables;
private NameValueCollection _queryString;
private NameValueCollection _form;
private NameValueCollection _cookies;
Add below:
private NameValueCollection _sessionVariables;
Find:
_serverVariables = CopyCollection(request.ServerVariables);
_queryString = CopyCollection(qsfc.QueryString);
_form = CopyCollection(qsfc.Form);
_cookies = CopyCollection(qsfc.Cookies);
Add below:
_sessionVariables = CopyCollection(context.Session);
Find:
public NameValueCollection Cookies
{
get { return FaultIn(ref _cookies); }
}
Add below:
///
/// Gets a collection representing the session variables captured as part of the diagnostic data
///
public NameValueCollection SessionVariables
{
get { return FaultIn(ref _sessionVariables); }
}
Find:
copy._serverVariables = CopyCollection(_serverVariables);
copy._queryString = CopyCollection(_queryString);
copy._form = CopyCollection(_form);
copy._cookies = CopyCollection(_cookies);
Add below:
copy._sessionVariables = CopyCollection(_sessionVariables);
Find:
private static NameValueCollection CopyCollection(NameValueCollection collection)
Add above:
private static NameValueCollection CopyCollection(HttpSessionStateBase sessionVariables)
{
if (sessionVariables == null || sessionVariables.Count == 0)
return null;
var copy = new NameValueCollection(sessionVariables.Count);
for (int i = 0; i < sessionVariables.Count; i++)
copy.Add(sessionVariables.Keys[i], sessionVariables[i].ToString());
return copy;
}
In ErrorJson.cs
Find:
Member(writer, "queryString", error.QueryString);
Member(writer, "form", error.Form);
Member(writer, "cookies", error.Cookies);
Add below:
Member(writer, "sessionVariables", error.SessionVariables);
In ErrorXml.cs
Find:
case "form" : collection = error.Form; break;
case "cookies" : collection = error.Cookies; break;
Add below:
case "sessionVariables": collection = error.SessionVariables; break;
Find:
WriteCollection(writer, "form", error.Form);
WriteCollection(writer, "cookies", error.Cookies);
Add below:
WriteCollection(writer, "sessionVariables", error.SessionVariables);
In ErrorMailHtmlPage.cshtml
Find:
@(RenderPartial())
Add above:
@foreach (var collection in
from collection in new[]
{
new
{
Id = "SessionVariables",
Title = "Session Variables",
Items = error.SessionVariables,
}
}
let data = collection.Items
where data != null && data.Count > 0
let items = from i in Enumerable.Range(0, data.Count)
select KeyValuePair.Create(data.GetKey(i), data[i])
select new
{
collection.Id,
collection.Title,
Items = items.OrderBy(e => e.Key, StringComparer.OrdinalIgnoreCase)
}
)
{
@collection.Title
Name
Value
@foreach (var item in collection.Items)
{
@item.Key
@item.Value
}
}
After making changes to ErrorMailHtmlPage.cshtml in Visual Studio, right click on the file and "Run Custom Tool" to generate the code for ErrorMailHtmlPage.generated.cs
In ErrorDetailPage.cshtml
Find (at the end of the file):
@*
}
*@
Add above:
@{
var sessioncollection = new
{
Data = error.SessionVariables,
Id = "SessionVariables",
Title = "Session Variables",
};
//
// If the collection isn't there or it's empty, then bail out.
//
if (sessioncollection.Data != null && sessioncollection.Data.Count > 0)
{
var items =
from i in Enumerable.Range(0, sessioncollection.Data.Count)
select new
{
Index = i,
Key = sessioncollection.Data.GetKey(i),
Value = sessioncollection.Data[i],
};
items = items.OrderBy(e => e.Key, StringComparer.OrdinalIgnoreCase);
@sessioncollection.Title
@*
// Some values can be large and add scroll bars to the page
// as well as ruin some formatting. So we encapsulate the
// table into a scrollable view that is controlled via the
// style sheet.
*@
Name
Value
@foreach (var item in items)
{
@item.Key
@item.Value
}
}
}
After making changes to ErrorDetailPage.cshtml in Visual Studio, right click on the file and "Run Custom Tool" to generate the code for ErrorDetailPage.generated.cs
Now you can build (I just used the build.cmd file that was included with the project) and grab the ddl files from bin that are needed.
You may also have to modify the web.config in your project now to include the version on any references to Elmah. If you're using Resharper you can just click on each of these and fix them. (There's probably a different way this is supposed to be done to avoid this but I'm not sure and I wasn't too worried about figuring it out)
An example of one of them though would be changing
to