G
Guest
Hi,
Ok I was reading an old ASP 3.0 Book and I noticed that when designing web
applications. Everything that us windows form and vb programmers would do was
to put all functions relating to a certain area in one form. Like for example
I would have an employee timesheet that in a window form would do the
adding/updating/deleting etc. in one form. But from my reading of this ASP
book adding a timesheet would be put on one page, updating in another and
deleting in another. So my question to you guys is this the way I should be
design my apps in ASP.net? Should I brake out the different functionality
related to one particular task into different aspx pages? How do you guys
design your web apps?
Thanks,
JJ
Ok I was reading an old ASP 3.0 Book and I noticed that when designing web
applications. Everything that us windows form and vb programmers would do was
to put all functions relating to a certain area in one form. Like for example
I would have an employee timesheet that in a window form would do the
adding/updating/deleting etc. in one form. But from my reading of this ASP
book adding a timesheet would be put on one page, updating in another and
deleting in another. So my question to you guys is this the way I should be
design my apps in ASP.net? Should I brake out the different functionality
related to one particular task into different aspx pages? How do you guys
design your web apps?
Thanks,
JJ