Include Session state serializer and trace messages

[GoogleCodeExporter]

I would propose to implement a Session state serializer. Take a look to 
http://www.codeproject.com/aspnet/exploresessionandcache.asp. I think it 
would be nice to have something like this. 

Another idea would be to save trace messages of a page. 
http://msdn2.microsoft.com/en-us/library/b0ectfxd.aspx. 

Kind regards 
Daniel

Original issue reported on code.google.com by Daniel.C...@gmail.com on 26 Jun 2007 at 8:11

[GoogleCodeExporter]

I totally forgot to insert a Summary. 
Summery: include Session state serializer and trace messages

Original comment by Daniel.C...@gmail.com on 26 Jun 2007 at 8:17

[GoogleCodeExporter]

Fixed summary.

Original comment by azizatif on 26 Jun 2007 at 8:38

• Changed title: Include Session state serializer and trace messages
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Ideally, this issue should be split into two separate ones. One that addresses 
including session state and another including trace messages. For now, this 
being 
marked as low priority as it may slip to the next milestone so that it doesn't 
delay 
v1.0 further.

Original comment by azizatif on 30 Oct 2007 at 9:33

• Added labels: Component-Logic, Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 188 has been merged into this issue.

Original comment by azizatif on 31 Oct 2010 at 1:14

[GoogleCodeExporter]

I have attached a patch for the first point in this ticket.

The patch will enumerate the session contents into the stored error object. It 
will also append it to the /details view and the email sent.

I have just used .ToString() to display the value. I could optionally put in a 
check for ISerializable but I wanted to keep it as simple as possible.

Original comment by iai...@hotmail.com on 24 Mar 2012 at 12:49

Attachments:

• elmah-sessionVariables.patch

[GoogleCodeExporter]

This issue has been migrated to:
https://github.com/elmah/Elmah/issues/12
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:15