StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11346608
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-05T14:37:26.603
FavoriteCount
0
LastActivityDate
2012-07-05T16:01:09.420
LastEditDate
2012-07-05T16:01:09.420
LastEditorUserId
572585
OwnerUserId
572585
ParentId
11329419
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Oddly enough, the day after I attempted to answer this, a co-worked asked me to help with the same problem, so here's what I'm up to so far... (Bare in mind that while I've been developing in .Net for a number of years, I've never had need to delve that deeply into the page life cycle, ViewState or any of the hideously complicated bits that keep better dev's up at night) Initially, I thought that overriding the PostBack event in JavaScript would allow me to edit the form post and remove the offending characters, so I tried it with a simple alert, but the potentially dangerous Request.Form was still appearing, so whatever's causing it is happening before the PostBack event is being fired. So, after investigating the <a href="http://msdn.microsoft.com/en-us/library/ms178472.aspx" rel="nofollow">page life cycle</a>, overriding every method I could and doing a whole lot of debugging, I found that the error is being throw in the DeterminePostBackMode method. Now, by my understanding, this method looks at the form post and converts it to a NameValueCollection, so I built my own NameValueCollection, stripping out the "<" character (I only tested with that character to start with). <pre><code>Protected Overrides Function DeterminePostBackMode() As System.Collections.Specialized.NameValueCollection Dim stream As New System.IO.StreamReader(Request.InputStream) Dim nvCollection As New System.Collections.Specialized.NameValueCollection() Dim _split() As String = stream.ReadToEnd().Split("&") If _split.Length > 1 Then For i As Integer = 0 To _split.Length - 1 Dim kv() As String = _split(i).Split("=") Dim _key As String = HttpUtility.UrlDecode(kv(0)) Dim _value As String = HttpUtility.UrlDecode(kv(1)) If _value.Contains("<") Then _value = "" nvCollection.Add(_key, _value) Next End If 'For Each s As String In nvCollection ' Response.Write(String.Format("{0}={1}", s, nvCollection(s))) 'Next Return nvCollection End Function </code></pre> And that worked brilliantly, the offending value was being stripped out and the NameValueCollection was being returned without causing an error... Except I was still seeing the error message. At the moment, I've tracked it to the PreInit page event, and I'm trying to figure a way around it, I'll update this as I make progress. UPDATE: I'm now fairly sure that the issue ISN'T with the values being stored in the ViewState. After reading <a href="http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx" rel="nofollow">this</a> excellent article on ViewState, I tried setting the value of a TextBox to <code>"<script"</code> declaratively, which means it shouldn't be stored in the ViewState, which means that the error isn't caused by processing being carried out on the ViewState. I think.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPreventing the yellow screen of death
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDark Hippo
UserOwnerUserId
1. USDark Hippo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.