HOWTO: Creating and Organizing Reuseable or Common Methods and Functions for ASP.NET

[Don Wash]

Hi All!

I'm developing ASP.NET pages using VB.NET language. My background is VB6 and
ASP3. Right now, I'm evaluating strategies on creating reusable and common
functions and methods for ASP.NET. In ASP 3, it was nothing more than
functions and methods coded in #Include Files. Now ASP.NET offers features
such as Page Inheritance and full software development support.

So I'm just wondering, what should I do if I have 5 functions, that can be
reused (i.e called it) in 10 different ASPX pages, what do I do? Do I create
a model page which contains the classes and inherit them? Or do I just
create a VB file containing all the functions and I can call the functions
from other ASPX pages once I compile them? Or do I create ASCX web controls?
But right now, basically all I need to do is the code only reusable
component and no UI.

Please advice on the best method to create reusable functions and methods
segments for ASP.NET. Also URL pointers on explaining step-by-step
procedures on recommended method(s) will be greatly appreciated!!!

Thanks you all in advance!
Don

 

[Curt_C [MVP]]

Both methods will work for you. Inheritance may be the easiest to use and
the simplist but it will depend a bit on what you are doing. If these are
simple functions then the page is great. If they are larger it might be
easier to place them into a class and call it when needed. I tend to use a
combination. I have inherited pages, inherited classes and seperate files
sometimes all within the same app. I know that's not quite what you wanted
to hear but without specifically seeing your usage it's the best I can say.

 

[Don Wash]

Hi Curt,

Thanks for the quick reply! I have some functions which are logical enough
to put them into one class and some "ad-hoc" functions and variables that
many pages in my website (Not All) needed.

So any ideas? (Also any pointers to tutorials or step-by-step for the
recommended method?)

Cheers!
Don

 

[Curt_C [MVP]]

I'd probably go with page inheritance in your case.
Simple enough. Just put all these functions in the code on one master page
that derives from the standard page class.
Then on all your pages in the code add your "master" as the class you
inherit from instead of the Page class.


--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com

 

[Darren Clark]

You can also just create static functions

eg

public class ConstantFunctions
{
public static void SetSelectedItem(ref
System.Web.UI.WebControls.DropDownList oDrop, string val)

{

System.Web.UI.WebControls.ListItem li = oDrop.Items.FindByValue(val);

if (li == null)

{

oDrop.SelectedIndex = 0;

}

else

{

li.Selected = true;

}

}

}

 

[Lucas Tam]

Or do I just
create a VB file containing all the functions and I can call the
functions from other ASPX pages once I compile them?

This will probably be the easiest method. Create a VB Class which you can
use in other pages.

 

[One Handed Man \( OHM - Terry Burns \)]

Wait for VS2005 which has the master page concept with content placeholders,
and web parts for portal development.

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing