You searched for the word(s): userid:284543

More Search Options

RSS Available

• Re: "Stack Overflow at line: 0" error in Internet Explorer

  Hello It's been a while since your post, but it looks like others have had this problem too. I had a similar problem. In my case the old code base was ASPNET 1.1 which had been migrated to 2.0. The page would issue an alert with the Stack Overflow ... on the first call that used MaintainScrollPositionOnPostback. After that there were no errors. Firefox didn't present the error. As if turned out, the code still contained the old, depreciated function Page.SmartNavigation. There was no problem

  Posted to Client Side Web Development (Forum) by ajk-eis on 10/21/2009

• Re: WebResource.axd Error - "handler must be registered"

  UPDATE - MS has contacted me, and indicates that they feel this is in fact an error in ASPNET (and not Cold Fusion). Wildcard mappings are allowed and CF correctly redirects as it should. My apologies to Adobe. MS will be working on a hotfix for this problem. When it is available I will also let you know here. Cheers Alle

  Posted to Web Forms (Forum) by ajk-eis on 1/20/2008

• Re: WebResource.axd Error - "handler must be registered"

  So thank to the folks at MS we have an answer to this (at least in two of the cases above) - Randy and I both had Cold Fusion 8 installed on the IIS 7 boxes. UPDATE - See my next post. The culprit is - < add name = " AboMapperCustom-3325812 " path = " * " verb = " * " modules = " IsapiModule " scriptProcessor = " C:\ColdFusion8\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll " requireAccess = " None " responseBufferLimit = " 0 "

  Posted to Web Forms (Forum) by ajk-eis on 1/19/2008
  Filed under: Cold Fusion and ASPNET on IIS 7

• Re: WebResource.axd Error - "handler must be registered"

  Hi Randy, got someone from the IIS Core group working with me at http://forums.iis.net/p/1147595/1861983.aspx#1861983 You may want to watch that thread and add your experiences. Sign in is as is here. Alle

  Posted to Web Forms (Forum) by ajk-eis on 1/16/2008

• Re: WebResource.axd Error - "handler must be registered"

  The problem here is definately NOT SOLVED. We must be missing something. My workaround is just a hack to get the site up and running. Of course it doesn't run any worse than it did on IIS 6, but that means any future use of the validation controls (in a 3,5 site) doesn't work either (I tried that too, it really doesn't!). There must be a way to to run Integrated Mode with validation controls. Or can someone tell me how I can modify the standard validation controls so they will work in

  Posted to Web Forms (Forum) by ajk-eis on 1/16/2008
  Filed under: validation Controls, WebResource.axd

• Re: WebResource.axd Error - "handler must be registered"

  Hi Randy, I'm not the expert in IIS 7 (yet), but as I understand it running in Classic .NET Mode is basically the same running the App in IIS 6. Which of course means you are not able to use the advantages of IIS 7. Classic Mode is just a compatibility mode. The trouble is no matter what I do, even with Visual Studio 2008, adding an ASP 2.0 Validation Control (there are no others other than ASP 2.0) breaks the Application for IIS 7. Why bother with VS2008 and IIS 7 when I have to run in compatibility

  Posted to Web Forms (Forum) by ajk-eis on 1/16/2008

• Re: WebResource.axd Error - "handler must be registered"

  Hi Bill, hi Fredrik, I am having the same problem migrating a 2.0 App to IIS 7.0. It is definately the validation controls causing the issue. I made a simple test page (on XP / IIS 6.0) and deployed that to IIS 7.0. As long as there is no validator all is well. As soon as I add a validator then the error occurs and the site will not load. Attempts to add the suggested httpHandler do not work with a 500.23 Error, indicating that the configuration should be migrated (using appCmd.exe for example).

  Posted to Web Forms (Forum) by ajk-eis on 1/16/2008

• Re: Invalid postback or callback argument.

  To all, The problem that I had was with a DataList containing buttons that always raised the above exception when the button was clicked. The real root of the problem (opposed to the work around which in fact does work) was that the ViewState was enabled and the DataList DataBind() was still being called on every PostBack (not caught by an if (!IsPostBack)). I'm assuming that this causes the internal identities of the buttons to change (as seen by ASP 2.0) compared to the original page and causes

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by ajk-eis on 1/12/2006

• Re: Invalid postback or callback argument.

  Hello again Ting, I have investigated further, and find that this problem always occurs when the DataList has not been assigned a DataSource in the Designer Mode. I feel this is very poor practice, as I prefer using code beside for this. One work around is to assign the DataList a "dummy" DataSource at design time and then use the following in code to change to the actual DataSource in Code Beside: if (!IsPostBack) { DataList1.DataSourceID = "" ; //very important - the old Binding is removed !! DataList1

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by ajk-eis on 1/11/2006

• Re: Invalid postback or callback argument.

  Hello Ting, the truth of the matter is, the behaviour has been changed substantially. Changing the Page Directive to circumvent validation is certainly NOT the answer. If I create a DataList that is bound in code beside, and add any Button or ImageButton to the Item Template then the above error occurs when the control is clicked on the client. I can resolve this for a Button by setting the UseSubmitBehaviour property to false. I can not resolve it for an image button at all. If I however add the

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by ajk-eis on 1/11/2006