A question of design... to Refactor a webform or not.

Hello All,

   My normal coding for most web forms is to use perl-cgi stuff or PHP, however 
in forcing myself to learn new things I have been conducting a series of 
experiments duplicating various pages and web forms in ASP.Net for the sheer 
versatility and learning experience it can bring. One of my pages done without 
codebehind, just embedding the C# right into the form and doing most of the 
development with WebMatrix was code that read 7 entries at random from an XML 
file of 70+ entries. This fairly simple yet pitfall filled task was done in 
about 80 lines of code in just a single method, Page_Load.

  I was wondering what the general consensus is to refactoring this short of 
code into a series of smaller functions and if doing such would improve or 
degrade the actual performance of the page in terms of load time. The code 
itself is fairly straightforward proceedural stuff and in fact I suspect my 
method of accomplishing the whole thing is grossly inefficent. However since I 
haven't actually had formal programming courses I am not entirely sure.

  Does anyone here normally practice Refractoring on relatively non OOp code? 
Have you found it makes a difference or has it lead to further bugs and other 
issues?

--
Best regards,
 Robert                          mailto:robert-lists@xxxxxxxxxxxxxx
-------------------------------------------------------------
Today's Random Observation:

Foolproof operation:  All parameters are hard coded.

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com