assembly vs. code behind

[JimO]

I have two dotNet 2 vb code behind files each about 900 lines. One file
has three classes in it and supports three forms. The other file supports
one form. What is the best practice to organize these file? Should I leave
it alone, break up the on one into three files, or maybe create assemblies?
There is no inhertance or common procedures and functions among any of the
classes.

Thanks,
Jim

[Chris Fulstow]

Hi Jim,

For the sake of maintainability, I'd probably break your first file up
into 3 separate code-behind file so it's easier to find the code for a
particular page. Then complile all your code-behind page classes into
the same assembly to make it easier to deploy.

HTH,
Chris

[JimO]

Thanks
Jim

"Chris Fulstow" <ch**********@hotmail.com> wrote in message
news:11**********************@i39g2000cwa.googlegr oups.com...

Hi Jim,

For the sake of maintainability, I'd probably break your first file up
into 3 separate code-behind file so it's easier to find the code for a
particular page. Then complile all your code-behind page classes into
the same assembly to make it easier to deploy.

HTH,
Chris