Base page VS Utility Class

[Jeff User]

Hi all

Developing C# web apps, .net1.1

I have gotten in habit of placing commonly used (interface) functions
in my base page. However, some apps I work on use a seperate "Utility"
class containing common utility functions.

Is there any benefit in doing it one way or the other?
For instance, does having to load up a seperate class cost more or
less than loading a base page?

Best practices / thoughts are wanted.

Thanks
Jeff

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

Jeff User wrote:

Hi all

Developing C# web apps, .net1.1

I have gotten in habit of placing commonly used (interface) functions
in my base page. However, some apps I work on use a seperate "Utility"
class containing common utility functions.

Is there any benefit in doing it one way or the other?
For instance, does having to load up a seperate class cost more or
less than loading a base page?

Best practices / thoughts are wanted.

Thanks
Jeff

The cost of course depends on what the constructor does in each case.
The actual creation of the object costs very little.

--
Göran Andersson
_____
http://www.guffa.com

[Ollie Riches]

check out the visitor pattern

http://en.wikipedia.org/wiki/Visitor_pattern

Ollie Riches

"Jeff User" <je*****@hotmai l.comwrote in message
news:hh******** *************** *********@4ax.c om...

Hi all

Developing C# web apps, .net1.1

I have gotten in habit of placing commonly used (interface) functions
in my base page. However, some apps I work on use a seperate "Utility"
class containing common utility functions.

Is there any benefit in doing it one way or the other?
For instance, does having to load up a seperate class cost more or
less than loading a base page?

Best practices / thoughts are wanted.

Thanks
Jeff

[PS]

"Jeff User" <je*****@hotmai l.comwrote in message
news:hh******** *************** *********@4ax.c om...

Hi all

Developing C# web apps, .net1.1

I have gotten in habit of placing commonly used (interface) functions
in my base page. However, some apps I work on use a seperate "Utility"
class containing common utility functions.

Is there any benefit in doing it one way or the other?
For instance, does having to load up a seperate class cost more or
less than loading a base page?

Best practices / thoughts are wanted.

2 best practices are

1) avoiding code duplication
2) avoiding a bloated base class

When you find that 2 base classes have identical methods then you can
extract this out to a common utility class. You can still keep your method
in the base class if you want but it does nothing but use the utility class.
The advantage of this is that it is easy to know what methods are available
for your class however this also tends to bloat your base classes with many
methods.

Most people use the code smell principle. When it smells a little off then
it probably is and you refactor.

PS

[Jeff User]

Thanks everyone for all the good advice

Jeff

On Sun, 11 Feb 2007 13:25:10 -0500, Jeff User <je*****@hotmai l.com>
wrote:

>Hi all

Developing C# web apps, .net1.1

I have gotten in habit of placing commonly used (interface) functions
in my base page. However, some apps I work on use a seperate "Utility"
class containing common utility functions.

Is there any benefit in doing it one way or the other?
For instance, does having to load up a seperate class cost more or
less than loading a base page?

Best practices / thoughts are wanted.

Thanks
Jeff