Like I said in my frist response; I'm probably splitting hairs too much. My point was simply that if you take a normally developed ASP.Net website where the developer doesn't specifically plan for browsers lacking javascript, and someone surfs there with
a browser that is javascript *capable* but javascript *deactivated* then the postback functionality will not work properly. While that doesn't always matter, I've worked in domains where it does. What you're describing relies on detecting browser capabilities,
not browser settings. I understand what you're saying, though, and I really wasn't trying to spawn a debate, merely make the point that javascript is prevalent in ASP.Net whether you use Ajax or not.
Help those who have helped you... remember to "Mark as Answered"
I see one "bad" thing in approach with MVC right now -
I cannot use it on my WebForms website.
I am thinking about using MVC for parts of website while using WebForms for another part - for example I would use WebForms for simple forms that should postback, and use server side validation etc, while I would like to use MVC for AJAX calls and loading
dynamically parts of a webform page from MVC rendering engines.
What do you think ? is it wrong thought ? :)
P.S. I decided to add one more thought to one I supposed above.
Suppose I am starting new project - ok I am aware of some advantages of MCV And I really want to try it in my next project - I want to move to it. BUT like in any software company one of main important determinants of a successfull project - in my company
is spent time.
I have written a lot of controls - it's a whole library with my own implementation of powerful TabControl, TreeGrdi component, GroupBox, tooltips, and a bunch of AJAX extenders,
so what now ? How I should be encouraged to use MVC and how should I encourage my project manager to start using MVC? Will I be able to hit the same time limits, or will I be able to again create UI-s with the same level of complexity ?
May be I will be fired for my initiative :)
I mean there are a lot of things that are stopping me right now.
My blog: http://blog.devarchive.net
My samples: http://devarchive.net
WhatThe12
Contributor
3416 Points
984 Posts
Re: Why not support post-backs?
Apr 08, 2008 01:31 PM|LINK
If you don't like this thread, DON'T READ IT and DON'T REPLY TO IT. [:P]
paul.vencill
Contributor
6716 Points
1358 Posts
Re: Why not support post-backs?
Apr 08, 2008 03:21 PM|LINK
Like I said in my frist response; I'm probably splitting hairs too much. My point was simply that if you take a normally developed ASP.Net website where the developer doesn't specifically plan for browsers lacking javascript, and someone surfs there with a browser that is javascript *capable* but javascript *deactivated* then the postback functionality will not work properly. While that doesn't always matter, I've worked in domains where it does. What you're describing relies on detecting browser capabilities, not browser settings. I understand what you're saying, though, and I really wasn't trying to spawn a debate, merely make the point that javascript is prevalent in ASP.Net whether you use Ajax or not.
kirchi
Contributor
2422 Points
328 Posts
Re: Why not support post-backs?
Apr 27, 2008 10:16 AM|LINK
I see one "bad" thing in approach with MVC right now -
I cannot use it on my WebForms website.
I am thinking about using MVC for parts of website while using WebForms for another part - for example I would use WebForms for simple forms that should postback, and use server side validation etc, while I would like to use MVC for AJAX calls and loading dynamically parts of a webform page from MVC rendering engines.
What do you think ? is it wrong thought ? :)
P.S. I decided to add one more thought to one I supposed above.
Suppose I am starting new project - ok I am aware of some advantages of MCV And I really want to try it in my next project - I want to move to it. BUT like in any software company one of main important determinants of a successfull project - in my company is spent time.
I have written a lot of controls - it's a whole library with my own implementation of powerful TabControl, TreeGrdi component, GroupBox, tooltips, and a bunch of AJAX extenders,
so what now ? How I should be encouraged to use MVC and how should I encourage my project manager to start using MVC? Will I be able to hit the same time limits, or will I be able to again create UI-s with the same level of complexity ?
May be I will be fired for my initiative :)
I mean there are a lot of things that are stopping me right now.
My samples: http://devarchive.net