One thing to bare in mind is that there will be two class created for each item. One will be a base class that you'll be adding your code to. The actual class you want to use outside the library will be inheriting from this class and is created by WAPL. Normally at runtime this would have been created in an asp namespace with an automated class name based its filename. Which isn't an ideal situation when you're trying to reference it your other websites.

You can avoid this by specify a name using the ClassName attribute in either the Control, Page or Master directive. I've been post-fixing my class names with Base and allowing me to use to an appropriate name in ClassName which seems to work quite elegantly.

Last edited Aug 9, 2006 at 9:40 AM by grahamdyson, version 1


No comments yet.