Skip to main content
23 events
when toggle format what by license comment
Oct 15, 2015 at 18:10 comment added snowYetis It is awful dude. Webforms are horrible. They are the worst thing ever. I have not read any comment or post on this page besides yours because my mind has been made up for years and that is, I hate Webforms. The worst is combining Webforms with the AJAX Toolkit or even worse Telerik's AJAX Webcontrols. I accepted a job that mostly used webforms because they give 6 weeks of vacation. Even with the 6 weeks of vaction I wake up every day regretting my decision. ASP.Net MVC is not bad though. Anyways, sorry you had to enter the world of Webforms. You can now run back to the PHP world happy.
Dec 11, 2013 at 18:31 comment added CodesInChaos Another issue with your example is that it's vulnerable to CSRF attacks. (But that'd also be true if you used POST without an Anti-CSRF token)
Dec 11, 2013 at 18:29 comment added CodesInChaos Because the HTTP specification says so. "In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered "safe"."
Dec 11, 2013 at 18:19 comment added iveqy @CodesInChaos why?
Dec 11, 2013 at 15:49 comment added CodesInChaos Don't use GET to modify something. At minimum you should use POST, but preferably DELETE.
Oct 23, 2013 at 18:41 history closed gnat
Jim G.
CommunityBot
Needs details or clarity
Oct 23, 2013 at 7:32 comment added iveqy @lunchmeat317 I would appreciate links since my google-fu doesn't match yours.
Oct 23, 2013 at 1:56 comment added user26452 I honestly think that this is more of a Google question. "Why was webforms built the way it was" seems to be fairly common knowledge across the internet, especially considering that it was built over ten years ago....
Oct 22, 2013 at 14:28 answer added Murph timeline score: 0
Oct 22, 2013 at 7:23 history edited iveqy CC BY-SA 3.0
edited title
Oct 22, 2013 at 7:00 answer added Grofit timeline score: 8
Oct 22, 2013 at 6:59 vote accept iveqy
Oct 22, 2013 at 6:47 review Close votes
Oct 23, 2013 at 18:41
Oct 22, 2013 at 6:39 comment added Jim G. @iveqy: Language matters. Believe me - I get fired up about poor frameworks too (and ironically, PHP is one of them!). And in a chat room you're perfectly free to say that something "sucks", but not here, not in a question. You'd be better off if you reworded your confusion with and criticism of ASP.NET Web Forms in a much more objective manner.
Oct 22, 2013 at 6:34 history edited Jim G. CC BY-SA 3.0
edited tags; edited title
Oct 22, 2013 at 6:33 comment added iveqy @JimG. Then please give me pointers on how to formulate it better. I must be possible to ask about the pros and cons of different designs even when they're competing against eachother.
Oct 22, 2013 at 6:31 comment added Jim G. Please excuse the somewhat rantish question. This overture does not excuse the "rantish" question. Also, ASP.NET Web Forms is yesterday's news. Prefer ASP.BET MVC. Always.
Oct 22, 2013 at 6:28 history edited iveqy CC BY-SA 3.0
added 720 characters in body
Oct 22, 2013 at 6:19 comment added iveqy It's really hard to point out something you see as a flaw without making it a rant. I really tried, and it seems that I failed. I would gladly accept any more specific pointers on how to rewrite it better (as I'm interested in good answers I will of course try to formulate as good question as I can).
Oct 22, 2013 at 6:16 comment added dcaswell I don't see the valid question. Using ViewState is optional and ASP.NET works with AJAX and JSON.
Oct 22, 2013 at 5:58 answer added Rowan Freeman timeline score: 6
Oct 22, 2013 at 5:57 comment added Bart van Ingen Schenau There seems to be a valid question in there, but it is hard to read around the rant that is there also. Can you reformulate your question such that it doesn't read like an anti-asp.net rant?
Oct 22, 2013 at 5:45 history asked iveqy CC BY-SA 3.0