It depends on the type of changes you're making to the presentation layer. No system is going to help you if you remove the textbox from the page - you're going to have to make not-insignificant code changes. All architectures like MVC do is _minimize_ the _number_ and _impact_ of changes. It doesn't prevent them.
On the other hand, if your UI guy decides to move some elements around, you can be fairly confident that your codebehind page won't have to change. > Personally, I'm not that impressed with the "codebehind" concept; > it's still > very tightly linked to the presentation code, such that if you > were to > change the presentation code by hand, you'd have to change the .cs > file to > reflect that. To my mind, that's a flimsy separation of logic at > best, and > the .cs file often really contains presentation logic anyway - > code that > affects what the user views. > > That said, I'm certainly no ASP.NET expert, so I could be wrong. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
