Sit up and take notice. The following comes from an MSDN article on application architecture
"...Unlike ASP, writing business logic entirely using ASP.NET is often a good idea...." and after a paragraph worth of explanations of this statement the author cover his butt with the following "..... It's worth pointing out, however, that reuse is harder with code wrapped in an .aspx page, even one using code behind, than with a standard assembly. For example, accessing code in an .aspx page from a Windows Forms client is problematic......."
Yes no kidding! I wish these fellows would, rather than repeat the party line, look around and see that there are well defined and established ways to build N-tier apps. There is a reason for storing business logic outside the presentation layer! Yes the aspx.cs code behind file may in a pinch qualify as "outside"- but just barely. Putting too much shareable code into one of those just totally goes against the grain. Unfortunately there are thousands of script kiddies who read the above article and take its advise. We already have gone down this path with newbies putting all their code behind VB Forms. I suppose the more things change the more they stay the same.
8:12:27 PM 
|
