I'm currently involved with a classic ASP project that consumes an in-house
developed webservice written in VB.NET. The webservice is approaching 50K
lines of code with no end in site. Presently, it takes about 30-seconds for
the webservice to load before an interface is displayed. Some of the methods
are specific for a particular module of the app and aren't used anywhere
else w/in the app. My question is... would be a better practice to break up
some of the w/s code into different classes, then load those classes as
they're needed. Currently *all* the code is in one class. What are the
advantages and disadvantages of taking this approach? We're about to
starting two new modules to the webapp and now would be the time to start
employing this methodology if it's advantageous to do so.

Thanks!