Page view counter

Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

Rate It (15)

Last post 06-29-2009 3:35 AM by meetmanthan. 302 replies.

Sort Posts:

  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    01-31-2006, 3:10 PM
    • Loading...
    • joteke
    • Joined on 06-16-2002, 11:24 AM
    • Kyro, Finland
    • Posts 6,874
    • Points 45,946
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs

    Eilon,

    in my test bed I already had event validation disabled, e.g the config file as:

    <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Always" />

    and the issue exists (even if event validation is disabled).

    If I change it to:

     <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Never" />

    I didn't  touch the event validation, and it started to work out. Perhaps it's some other more complicated thing behind the scenes than event validation, or is still related to it?

    Stack trace is:

    [HttpException (0x80004005): Unable to validate data.]
       System.Web.Configuration.MachineKeySection.GetDecodedData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Int32& dataLength) +358
       System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +199

    [ViewStateException: Invalid viewstate.
    Client IP: 127.0.0.1
    Port:
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; MSVS 8.0.50727)
    ViewState: VXTPKwRXoX61Y4cvIJH/o7LcvXDyqoTxh5PLFbKrbsZg0i12uRF4wJHFBOpVvxP/Hx1RnJWq8FRR6fqiFSdZukxCS5H+uqtGAcHmPiTbDDaLy8WZF9Xj1nethdNsVOswTNGaB9Jo2PK+7p3dcDc+v/Ui35vs/nI8yTIz6bPjCLfxi9tI+SWcy9l+SUfwMp3JSgUVWoQ33JdrV9bY5yt5Fj5J1BYm1CwxMmIivv6Bu1YMKChv1E0m3Iknaf22dMHksCWyiX7W0jnqNPvqkufq6vrn9WZL0cgNFKtZJNWiQOBIi6hVkDmRbAMYh0cugqOhD9aFF8amv/Wr62y2sUGiBt/tdqFW2eb6+YMMuMYbtWuGJeMvzJW2qyMxpHMxLQAmf5BbP0GSaEhLrE7jcFdDiEkJy2id5TVevZnLH5e4zbaGu4wkN1f8tSMLp57xOOXKmiJT5lXk1w3sdp5S3sgEdKjpiqPkbtjA6mW9XZukWtGupc2wPStf09dw1wRuJ7epV6YQbf39feDeNKQPNIQEpntPh+lJPcKymH8xaKcSmZH3v8I5NfcmHPPpcOET/ZWVjt++tmZh211LIQYcA4v9GT96tVZsxdwDhZ+8qFLIo0VzOhLeK3r+UhXqR1vh29TfccG6ZKpY3x4l4v5G7qKzsQkrW2Fgo/3W4QToO96EiY9dMQQF6qAuGlJUp/++/Lv3pXXIq7MSEC3yRF/cHmT3AEDhi6LhCv2d52ZZLqFH2oUbt6v2f/JOSZ1wtGvyyssOhNER0mdU3XXCDR0ZcR+mZvwYPjK3HBdHtIqW+aozTs4PEPCvqK1ZDZpcuipsFtgUJOL+ey8cs+bZs9Ci8C...]

    [HttpException (0x80004005): Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.]
       System.Web.UI.ViewStateException.ThrowError(Exception inner, String persistedState, String errorPageMessage, Boolean macValidationError) +119
       System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +236
       System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +5
       System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37
       System.Web.UI.HiddenFieldPageStatePersister.Load() +222
       System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +80
       System.Web.UI.Page.LoadAllState() +35
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7965
       System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +158
       System.Web.UI.Page.ProcessRequest() +85
       System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +20
       System.Web.UI.Page.ProcessRequest(HttpContext context) +110
       ASP.example_aspx.ProcessRequest(HttpContext context) in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\viewstateproblem\ef8b89df\95cd01e0\App_Web_gmubbdee.0.cs:0
       System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +317
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +65


     If you pick download provided earlier:
    http://www.espace.ch/viewstateProblem.rar , you can repro it .

    Thanks,

    Teemu Keiski
    Finland, EU
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    01-31-2006, 4:05 PM
    • Loading...
    • Eilon
    • Joined on 06-26-2002, 6:14 PM
    • Redmond, WA
    • Posts 866
    • Points 4,828
    • AspNetTeam

    I suspect it's probably related. If you look, there's actually one other hidden field that gets rendered at the bottom of the <form> tag:

     <input type="hidden" name="__VIEWSTATEENCRYPTED" id="__VIEWSTATEENCRYPTED" value="" />

    I suspect that if that field is not posted back to the server, that view state might fail as well.

    In general, the entire page must be loaded in order to be able to do a postback properly. You can try to verify this by doing an HTTP trace and seeing which fields actually end up getting posted to the server when you: 1. Wait for the page to load; and 2. Don't wait for the page to load. Any differences between those two traces will most likely indicate the cause of the error.

    Thanks,

    Eilon

    Blog: http://weblogs.asp.net/LeftSlipper/
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 4:23 AM
    • Loading...
    • crystal.net
    • Joined on 01-19-2006, 1:11 PM
    • Posts 20
    • Points 100

    first of all i wanna thank you both, joteke and eilon, for analyzing/supporting this thread!

    "if you guys add this to web.config, does it still reproduce?
    <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Never" />"

    this workaround (switching off the whole event validation security) works great. all our applications are running fine now on asp.net 2.0 final with property viewStateExncryptionMode set to Never!

    i've also analyzed the rendered source code => hidden fields "__VIEWSTATEENCRYPTED" and "__EVENTVALIDATION". they are really rendered at the bottom of the <form> tag:

    that's obviously a sequentially rendering bug which has to be fixed, don't you think?

    => that important sequential logic reminds me of first steps scripting javascript stuff!

    "One work around is of course to just disable event validation, but you have to be aware of the security implications."

    disabling event validation is the single solution in my case!

    "Alternatively, just never post back before the form has finished rendering. Of course, that's hard to tell your users, but perhaps you could disable the UI until the form has rendered?"

    that's hard to tell your users.... i'd say that's impossible to get user's understanding for waiting ;-)
    on the other hand, can you explain me how i should disable UI until the form has rendered?

  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 4:55 AM
    • Loading...
    • xpedite
    • Joined on 01-24-2006, 12:16 AM
    • Posts 6
    • Points 30

    Mate this is not the case. To suggest that the application is failing because the user is clicking the button too soon is ludicrous. You need to knuckle down and sort this one out otherwise you will have 0 people developing .Net2 applications. We are all waiting.

     

  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 4:55 AM
    • Loading...
    • crystal.net
    • Joined on 01-19-2006, 1:11 PM
    • Posts 20
    • Points 100

    oh, i forgot to mention an important thing:

    you may remember i wrote reported problem only occurs using "DataKeyNames" in GridView. AND THIS IS ABSOLUTELY CORRECT! just have a look at rendered source code. if you are using property "DataKeyNames" you'll get rendered hidden field "__VIEWSTATEENCRYPTED". if you aren't using it, the hidden form field doesn't exist!

    => so i think this whole event validation/encryption stuff is NOT proper!

  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 5:18 AM
    • Loading...
    • joteke
    • Joined on 06-16-2002, 11:24 AM
    • Kyro, Finland
    • Posts 6,874
    • Points 45,946
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs
    Eilon wrote:

    I suspect it's probably related. If you look, there's actually one other hidden field that gets rendered at the bottom of the <form> tag:

     <input type="hidden" name="__VIEWSTATEENCRYPTED" id="__VIEWSTATEENCRYPTED" value="" />

    I suspect that if that field is not posted back to the server, that view state might fail as well.

    In general, the entire page must be loaded in order to be able to do a postback properly. You can try to verify this by doing an HTTP trace and seeing which fields actually end up getting posted to the server when you: 1. Wait for the page to load; and 2. Don't wait for the page to load. Any differences between those two traces will most likely indicate the cause of the error.

    Thanks,

    Eilon

    I had a look at the posted content with Fiddler, but I missed that. Makes 100% sense now, thanks!

    Thanks,

    Teemu Keiski
    Finland, EU
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 11:11 AM
    • Loading...
    • joteke
    • Joined on 06-16-2002, 11:24 AM
    • Kyro, Finland
    • Posts 6,874
    • Points 45,946
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs
    crystal.net wrote:

    oh, i forgot to mention an important thing:

    you may remember i wrote reported problem only occurs using "DataKeyNames" in GridView. AND THIS IS ABSOLUTELY CORRECT! just have a look at rendered source code. if you are using property "DataKeyNames" you'll get rendered hidden field "__VIEWSTATEENCRYPTED". if you aren't using it, the hidden form field doesn't exist!

    => so i think this whole event validation/encryption stuff is NOT proper!

    To clarify, that's because GridView requests View state to be encrypted, since those ID's in database might require secure handling (e.g it does that if DataKeyNames are set). viewStateEncryptionMode setting in config (or corresponding property on Page class) overrides that behaviour. Default mode, Auto, is to encrypt if controls require that, otherwise not.

    Thanks,

    Teemu Keiski
    Finland, EU
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-01-2006, 5:53 PM
    • Loading...
    • vtjoeh
    • Joined on 02-01-2006, 10:50 PM
    • Posts 1
    • Points 5
    I ran into the same problem  It turns our I had an extra <form></form> tag in my code because I was cutting and pasting some Javascript.  Once I removed the extra <form> tag, it worked great. 
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-02-2006, 2:57 AM
    • Loading...
    • crystal.net
    • Joined on 01-19-2006, 1:11 PM
    • Posts 20
    • Points 100

    @joteke

    "To clarify, that's because GridView requests View state to be encrypted, since those ID's in database might require secure handling (e.g it does that if DataKeyNames are set). viewStateEncryptionMode setting in config (or corresponding property on Page class) overrides that behaviour. Default mode, Auto, is to encrypt if controls require that, otherwise not."

    okay, that makes sense. thanks for clarifying :-)


    @Eilon

    there are still two questions unanswered:
    "i've also analyzed the rendered source code => hidden fields "__VIEWSTATEENCRYPTED" and "__EVENTVALIDATION". they are really rendered at the bottom of the <form> tag:
    that's obviously a sequentially rendering bug which has to be fixed, don't you think?"

    and

     
    "can you explain me how i should disable UI until the form has rendered
    ?"


    @vtjoeh

    maybe we had the same error message, but we've "solved" (workaround) another bug in this thread.

  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-06-2006, 2:50 AM
    • Loading...
    • crystal.net
    • Joined on 01-19-2006, 1:11 PM
    • Posts 20
    • Points 100
    @Eilon

    no answer is also an answer ;-)
    thanks anyway.
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-06-2006, 3:16 AM
    • Loading...
    • joteke
    • Joined on 06-16-2002, 11:24 AM
    • Kyro, Finland
    • Posts 6,874
    • Points 45,946
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs

    If you want to express feedback to the product team , you can also use MSDN Feedback Center. That way you can ensure that they have taken note of it (they usually respond there with some guidelines related to the specific issue like are they going to do anything)

    http://lab.msdn.microsoft.com/productfeedback/

    Post the link to the reported issue here.

    Thanks,

    Teemu Keiski
    Finland, EU
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-06-2006, 2:34 PM
    • Loading...
    • Eilon
    • Joined on 06-26-2002, 6:14 PM
    • Redmond, WA
    • Posts 866
    • Points 4,828
    • AspNetTeam

    Hi again,

    I don't know of a very good way to disable all the elements on the form, however here's a code snippet that shows part of a technique:

        function disableElements(elements) {
            for (var i = elements.length - 1; i >= 0; i--) {
                var elmt = elements[i];
                if (!elmt.disabled) {
                    elmt.disabled = true;
                }
                else {
                    elmt._wasDisabled = true;
                }
            }
        }

        function disableFormElements() {
            disableElements(_form.getElementsByTagName("INPUT"));
            disableElements(_form.getElementsByTagName("SELECT"));
            disableElements(_form.getElementsByTagName("TEXTAREA"));
            disableElements(_form.getElementsByTagName("BUTTON"));
            disableElements(_form.getElementsByTagName("A"));
        }

        function enableElements(elements) {
            for (var i = elements.length - 1; i >= 0; i--) {
                var elmt = elements[i];
                if (!elmt._wasDisabled) {
                    elmt.disabled = false;
                }
                else {
                    elmt._wasDisabled = null;
                }
            }
        }

        function enableFormElements() {
            enableElements(_form.getElementsByTagName("INPUT"));
            enableElements(_form.getElementsByTagName("SELECT"));
            enableElements(_form.getElementsByTagName("TEXTAREA"));
            enableElements(_form.getElementsByTagName("BUTTON"));
            enableElements(_form.getElementsByTagName("A"));
        }

    Make sure that the variable _form is set to the ASP.net form on the page. Then just call enableFormElements() and disableFormElements(). As far as when exactly do you call them, I'm not entirely sure how that works with the DOM, etc.

    Either way, definitely send us some official feedback through the link mentioned earlier.

    Thanks,

    Eilon

    Blog: http://weblogs.asp.net/LeftSlipper/
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-07-2006, 12:29 AM
    • Loading...
    • joteke
    • Joined on 06-16-2002, 11:24 AM
    • Kyro, Finland
    • Posts 6,874
    • Points 45,946
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs
    Eilon wrote:

    Either way, definitely send us some official feedback through the link mentioned earlier.

    Thanks,

    Eilon

    Yup, I did one: http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=e08714b5-35cc-4520-9876-fe2851018453

    Thanks for taking time to suggest the other workaround,

    Teemu

    Thanks,

    Teemu Keiski
    Finland, EU
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-07-2006, 5:15 AM
    • Loading...
    • crystal.net
    • Joined on 01-19-2006, 1:11 PM
    • Posts 20
    • Points 100
    thanks you both.
  • Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

    02-09-2006, 1:50 AM
    • Loading...
    • ttbmanda
    • Joined on 02-09-2006, 6:16 AM
    • Posts 2
    • Points 10

    I've been getting the same message, intermittently, even after adding <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Never" /> to web.config. In the hope that it helps, here's some of the code. Note the third item in the EditItemTemplate.

    <asp:GridView ID="GridView1" runat="server" AllowPaging="True" AutoGenerateColumns="False" DataKeyNames="dlID" DataSourceID="ObjectDataSource1" Width="628px" PageSize="5" CellPadding="4" ForeColor="#333333" GridLines="None" RowHeaderColumn="dlID">

    <Columns>

    <asp:CommandField ShowEditButton="True" />

    <asp:BoundField DataField="dlID" HeaderText="Lead ID" InsertVisible="False" ReadOnly="True"

    SortExpression="dlID" />

    <asp:TemplateField HeaderText="User Name Address Etc">

    <ItemTemplate>

    <asp:FormView ID="FormView1" runat="server" DataKeyNames="dlID"

    DataSourceID="ObjectDataSource1" OnPageIndexChanging="FormView1_PageIndexChanging" Width="731px" Height="43px">

    <PagerSettings Mode="NextPrevious" />

    <EditItemTemplate>

    <asp:Label ID="dlIDLabel1" runat="server" Text='<%# Eval("dlID") %>'></asp:Label><br />

    dlUSERID:

    <asp:TextBox ID="dlUSERIDTextBox" runat="server" Text='<%# Bind("dlUSERID") %>'>

    </asp:TextBox><br />

    STATE:

    <asp:Label ID="adSTATELabel1" runat="server" Text='<%# Eval("adSTATE") %>'>

    </asp:Label><br />

    dlLANGUAGE:

    <asp:TextBox ID="dlLANGUAGETextBox" runat="server" Text='<%# Bind("dlLANGUAGE") %>'>

    </asp:TextBox><br />

    dlTYPE:

    <asp:TextBox ID="dlTYPETextBox" runat="server" Text='<%# Bind("dlTYPE") %>'>

    </asp:TextBox><br />

    dlSTATUS:

    <asp:TextBox ID="dlSTATUSTextBox" runat="server" Text='<%# Bind("dlSTATUS") %>'>

    </asp:TextBox><br />

    dlNAME:

    <asp:TextBox ID="dlNAMETextBox" runat="server" Text='<%# Eval("dlNAME") %>'>

    </asp:TextBox><br />

    dlPHONE:

    <asp:TextBox ID="dlPHONETextBox" runat="server" Text='<%# Bind("dlPHONE") %>'>

    </asp:TextBox><br />

    adADDRESS:

    <asp:TextBox ID="adADDRESSTextBox" runat="server" Text='<%# Bind("adADDRESS") %>'>

    </asp:TextBox><br />

    adCITY:

    <asp:TextBox ID="adCITYTextBox" runat="server" Text='<%# Bind("adCITY") %>'>

    </asp:TextBox><br />

    adZIP:

    <asp:TextBox ID="adZIPTextBox" runat="server" Text='<%# Bind("adZIP") %>'>

    </asp:TextBox><br />

    wpPRINCIPAL:

    <asp:TextBox ID="wpPRINCIPALTextBox" runat="server" Text='<%# Bind("wpPRINCIPAL") %>'>

    </asp:TextBox><br />

    wpINTEREST:

    <asp:TextBox ID="wpINTERESTTextBox" runat="server" Text='<%# Bind("wpINTEREST") %>'>

    </asp:TextBox><br />

    wpPAYMENT:

    <asp:TextBox ID="wpPAYMENTTextBox" runat="server" Text='<%# Bind("wpPAYMENT") %>'>

    </asp:TextBox><br />

    wpMINIMUM:

    <asp:TextBox ID="wpMINIMUMTextBox" runat="server" Text='<%# Bind("wpMINIMUM") %>'>

    </asp:TextBox><br />

    wpFICO:

    <asp:TextBox ID="wpFICOTextBox" runat="server" Text='<%# Bind("wpFICO") %>'>

    </asp:TextBox><br />

    lsFACEVALUE:

    <asp:TextBox ID="lsFACEVALUETextBox" runat="server" Text='<%# Bind("lsFACEVALUE") %>'>

    </asp:TextBox><br />

    dlCALLRESULT:

    <asp:TextBox ID="dlCALLRESULTTextBox" runat="server" Text='<%# Bind("dlCALLRESULT") %>'>

    </asp:TextBox><br />

    dlREASON:

    <asp:TextBox ID="dlREASONTextBox" runat="server" Text='<%# Bind("dlREASON") %>'>

    </asp:TextBox><br />

    dlDATEAVAILABLE:

    <asp:TextBox ID="dlDATEAVAILABLETextBox" runat="server" Text='<%# Bind("dlDATEAVAILABLE") %>'>

    </asp:TextBox><br />

    dlDATEOUT:

    <asp:TextBox ID="dlDATEOUTTextBox" runat="server" Text='<%# Bind("dlDATEOUT") %>'>

    </asp:TextBox><br />

    dlDATEIN:

    <asp:TextBox ID="dlDATEINTextBox" runat="server" Text='<%# Bind("dlDATEIN") %>'>

    </asp:TextBox><br />

    dlDATEIMPORTED:

    <asp:TextBox ID="dlDATEIMPORTEDTextBox" runat="server" Text='<%# Bind("dlDATEIMPORTED") %>'>

    </asp:TextBox><br />

    dlSOURCE:

    <asp:TextBox ID="dlSOURCETextBox" runat="server" Text='<%# Bind("dlSOURCE") %>'>

    </asp:TextBox><br />

    naFIRST:

    <asp:TextBox ID="naFIRSTTextBox" runat="server" Text='<%# Bind("naFIRST") %>'>

    </asp:TextBox><br />

    naLAST:

    <asp:TextBox ID="naLASTTextBox" runat="server" Text='<%# Bind("naLAST") %>'>

    </asp:TextBox><br />

    phAREACODE:

    <asp:TextBox ID="phAREACODETextBox" runat="server" Text='<%# Bind("phAREACODE") %>'>

    </asp:TextBox><br />

    phPHONE:

    <asp:TextBox ID="phPHONETextBox" runat="server" Text='<%# Bind("phPHONE") %>'>

    </asp:TextBox><br />

    wpHOMEVALUE:

    <asp:TextBox ID="wpHOMEVALUETextBox" runat="server" Text='<%# Bind("wpHOMEVALUE") %>'>

    </asp:TextBox><br />

    dlUNIQ:

    <asp:TextBox ID="dlUNIQTextBox" runat="server" Text='<%# Bind("dlUNIQ") %>'>

    </asp:TextBox><br />

    <asp:LinkButton ID="UpdateButton" runat="server" CausesValidation="True" CommandName="Update"

    Text="Update">

    </asp:LinkButton>

    <asp:LinkButton ID="UpdateCancelButton" runat="server" CausesValidation="False" CommandName="Cancel"

    Text="Cancel">

    </asp:LinkButton>

    </EditItemTemplate>

    (Apologies for not yet having figured out how easily to avoid that extra cut-and-paste white space.)

    As I was saying, adding the viewState stuff to web.config temporarily fixed the problem (aka "worked around yet another set of well-intentioned but ultimately unhelpful-at-best Microsoft defaults"). It reoccured later, presumably explained by the overrides to which the earlier MVP post refers, went away again after a re-boot, came back again out of nowhere because the parameters had magically capitalized themselves, went away after I repaired that, and has reappeared once more.

    This last occurrence was on the first look after changing that third item from a "Bind" TextBox to an "Eval" label.

    I honestly hope the preceding information is helpful to you guys somehow. This next bit is less likely to be.

    My diagnosis is that this obstacle is among a set of those that are raised on the SomethingOtherwiseLikelyToBeHelpful event.

    More seriously - actually, all joking aside - please add my voice to those who cry out for relief from security cures that are much MUCH worse that the sickness. Granted, my little application needs fairly little security, and I'm new to the technology. But I'd be happy to have a few thousand dollars every year hacked out of my retirement account if I never have to see another viewstate mac machine policy message result from a default to postback validation.

    While you're at it, can you work on the child seat laws? I live two miles from the beach, but couldn't drive my visiting nephews to it. Thanks.

Page 2 of 21 (303 items) < Previous 1 2 3 4 5 Next > ... Last ยป