Wrox Programmer Forums
|
BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0
This is the forum to discuss the Wrox book ASP.NET 2.0 Website Programming: Problem - Design - Solution by Marco Bellinaso; ISBN: 9780764584640
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old October 17th, 2006, 11:19 AM
Authorized User
 
Join Date: Oct 2006
Posts: 11
Thanks: 0
Thanked 0 Times in 0 Posts
Default Internet Explorer kills my app !!! :0(


Hello!
I have the weirdest problem ever..!!
At the very end of chapter 2...I have the theme selector drop-down, and I have two pages: Default.aspx and Contact.aspx. Contact.aspx is a really small & simple page with just one text field in it...

When I test my "beer" app in Mozilla browser, everything works like a charm..I can switch between two themes in both .aspx pages, no problems. Everything builds and compiles and there are absolutely no debugging errors.

However, when I run in Internet Explorer...When I try to switch between themes in Default.aspx, the themes are NOT switched and nothing happens. And when I try to switch between themes in Contact.aspx, Internet Explorer explodes all together, and yeilds the following meaningful output:

************************************************** *****************
Server Error in '/TheBeerHouse' Application.

Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ArgumentException: Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.]
   System.Web.UI.ClientScriptManager.ValidateEvent(St ring uniqueId, String argument) +358
   System.Web.UI.Control.ValidateEvent(String uniqueID, String eventArgument) +108
   System.Web.UI.WebControls.TextBox.LoadPostData(Str ing postDataKey, NameValueCollection postCollection) +22
   System.Web.UI.WebControls.TextBox.System.Web.UI.IP ostBackDataHandler.LoadPostData(String postDataKey, NameValueCollection postCollection) +11
   System.Web.UI.Page.ProcessPostData(NameValueCollec tion postData, Boolean fBeforeLoad) +380
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2965
************************************************** *******************

Does anyone happen to have an idea why would this be happening ? Like
I said, there are no compiling/debugging errors...

Thanks a bunch for any feedback,

--fluffy

 
Old October 17th, 2006, 12:02 PM
Authorized User
 
Join Date: Oct 2006
Posts: 11
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Actually, I managed to get rid of that long "error stack" that Internet Explorer has thrown at me, by adding the "EnableEventValidation="false""
attribute in the @Page directive of Default.aspx. I'm not sure whether
that fixes the problem per se, but at least i made it go away..
:)
But the themes still don't get changed in Internet Explorer...Is there
any way to debug this matter ???

thanks,

--fluffy


 
Old October 17th, 2006, 06:28 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 917
Thanks: 0
Thanked 0 Times in 0 Posts
Default

You should not have to set that to false. Did you try the code in the code download?

Eric






Similar Threads
Thread Thread Starter Forum Replies Last Post
Automating Internet explorer viruthachalams C# 1 July 18th, 2007 09:06 AM
automation of internet explorer khan091 C# 2 July 5th, 2007 05:54 PM
Internet Explorer cannot open the internet site cathiec ASP.NET 2.0 Basics 1 October 22nd, 2005 01:30 PM
Internet Explorer JelfMaria VB How-To 10 April 27th, 2005 03:58 PM
Internet Explorer embeded App bwood415 Pro VB 6 1 September 7th, 2004 11:20 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.