Comments on: ASP.NET Tip/Trick: Use a Base Page Class for All Application Pages

By: jyest

jyest — Mon, 19 Oct 2009 10:38:56 +0000

Hi, it’s a really helpful article to me,

Just 1 question, I use vb.net, and when I try to use following code in my code, I got a dead loop

‘If the URL is modified
Private Sub Page_Init(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Init
‘mybase.OnInit(e) will invoke Page_Init
MyBase.OnInit(e)
End Sub

Any ideas or suggestions? thanks

By: Ram Chandra Nagar

Ram Chandra Nagar — Tue, 14 Jul 2009 07:14:57 +0000

Hi this is use full if you are working on web based application realy its reduse code redudency
thanks

By: DevExpert

DevExpert — Thu, 25 Jun 2009 19:22:33 +0000

Hilton, very interesting. I hadn’t even considered page adapters for this. I’ll definitely keep it in mind for future projects. Thank you!

By: DevExpert

DevExpert — Thu, 25 Jun 2009 19:20:32 +0000

Good stuff — thanks for the info!!

By: Thomas Haggren

Thomas Haggren — Wed, 24 Jun 2009 16:05:16 +0000

Great article

Here is a good article about the “Response.Redirect(url) ThreadAbortException” http://www.c6software.com/CodeSolutions/dotnet/ThreadAbortException.aspx

By: Hilton Giesenow

Hilton Giesenow — Thu, 11 Jun 2009 10:08:37 +0000

Nice post, some great tips! My only problem with a new base class is that developers can forget to do it. Some other possible solutions are overriding the default Visual Studio templates, and using Extension Methods. I’ve got a complimentary idea on using PageAdapters to do some similar things that might be of interest.

By: Mike Ohlsen

Mike Ohlsen — Tue, 02 Jun 2009 15:06:11 +0000

DevExpert, you just have to be careful. using Response.Redirect(url, false) means execution continues. Any code after Response.Redirect (which you dont have any in your example) and in later page events will still fire. So you have to be aware.

By: DevExpert

DevExpert — Tue, 02 Jun 2009 14:29:02 +0000

Mike — why didn’t I use that? Because I didn’t know it existed! *Insert newbie comment here*

Thanks a million for pointing this out!!

By: Mike Ohlsen

Mike Ohlsen — Tue, 02 Jun 2009 14:13:38 +0000

Why not use Response.Redirect(url, false)? This will prevent the ThreadAbortException from being thrown and allow processing to continue with calling Response.End.

http://msdn.microsoft.com/en-us/library/a8wa7sdt(VS.80).aspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;312629

By: DevExpert

DevExpert — Tue, 02 Jun 2009 13:02:10 +0000

Shail,
1. This will work fine, as long as you don’t inherit your master page class from this class — they’re 2 different types of classes. This will only work for ASPX application pages. As long as you inherit only your ASPX pages, it shouldn’t break anything.
2. Nope, this approach doesn’t do anything to break event handlers. Keep in mind that you’re already using inheritance and using a base page class (the System.Web.UI.Page) when you’re creating ASPX pages. The only difference here is you’re adding another layer between that class and your ASPX pages. Ultimately though, every page will still inherit from System.Web.UI.Page.
3. Yep, IntelliSense will pick these methods up.

Good luck!