• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "asp.net dropdownlist strange behaviour"

Collapse

  • DimPrawn
    replied
    Originally posted by NickFitz View Post
    And that, right there, is one reason ASP.NET is such a bunch of fail.

    "Hey, let's wrap every page in a form tag and have a humungous hidden field to preserve state for the whole thing!"

    "What about the case when a page needs multiple forms?"

    "Nah, that'll never happen..."

    Cue tortuous workarounds when you want a simple search form on the same page as another form, such as a blog comment form...
    I have to say the whole sorry Web Forms ASP.NET idiom is complete garbage. It was obviously designed by a Win Forms fat-client team who had almost zero exposure and understanding of the web beyond "the Intranet with IE as the client browser".

    There are so many bad design decisions in there and the most annoying thing is they make the process one work-around after another to create clean SEO friendly websites.

    The future is the MVC framework.

    http://www.asp.net/mvc/

    Leave a comment:


  • NickFitz
    replied
    Originally posted by scotspine View Post
    of course there's a form tag in the master page...
    And that, right there, is one reason ASP.NET is such a bunch of fail.

    "Hey, let's wrap every page in a form tag and have a humungous hidden field to preserve state for the whole thing!"

    "What about the case when a page needs multiple forms?"

    "Nah, that'll never happen..."

    Cue tortuous workarounds when you want a simple search form on the same page as another form, such as a blog comment form...

    Leave a comment:


  • scotspine
    replied
    noooo - i'd blagged a whole load of one of the htmlers' markup and was swapping out all the old controls for .not controls but hadn't spotted that a form tag had been left in. of course there's a form tag in the master page...etc etc.

    Leave a comment:


  • DimPrawn
    replied
    autopostback = true by any chance?

    Leave a comment:


  • scotspine
    replied
    it's ok. i'm being thick again

    Leave a comment:


  • scotspine
    started a topic asp.net dropdownlist strange behaviour

    asp.net dropdownlist strange behaviour

    i've got a d/downlist which is hosted in a masterpage. it works fine in all pages on the site except 2. on these 2 pages, whenever i try to select from it, it immediately resets itself back to the default 'please select' option. has anyone seen this before? any ideas?
Working...
X