#include equivalent for aspnet

[dee]

Several pages in our site use the same code. Is there a way to use the same
idea as the old C #include technique in an aspnet application.
Thanks.
Dee

 

[Lucas Tam]

Several pages in our site use the same code. Is there a way to use the
same idea as the old C #include technique in an aspnet application.

Couple ways of doing this... depending on the type of code:

1. Build a User Control / Custom Control
2. Build a shared DLL
3. Use MasterPages to build a template system

 

[Jon Paal]

You can do as Lucas suggested or use server side includes which are still
supported

 

[dee]

Thanks

You can do as Lucas suggested or use server side includes which are still
supported

 

[dee]

Thanks.

Couple ways of doing this... depending on the type of code:

1. Build a User Control / Custom Control
2. Build a shared DLL
3. Use MasterPages to build a template system

 

[Steve C. Orr [MVP, MCSD]]

Include files are old fashioned.
User controls are a better approach. Yes, they can contain any kind of
controls you'd like. You can create public properties, methods, and events
to facilitate communication between the user control and the page.
Even better is the "Master Pages" functionality that will be included with
ASP.NET 2.0.

Here's more info:
http://SteveOrr.net/faq/UserCustom.aspx
http://aspnet.4guysfromrolla.com/articles/010505-1.aspx

 

[dee]

Thanks

Include files are old fashioned.
User controls are a better approach. Yes, they can contain any kind of
controls you'd like. You can create public properties, methods, and
events
to facilitate communication between the user control and the page.
Even better is the "Master Pages" functionality that will be included with
ASP.NET 2.0.

Here's more info:
http://SteveOrr.net/faq/UserCustom.aspx
http://aspnet.4guysfromrolla.com/articles/010505-1.aspx