The only thing I am hung up on is why you need to have 2 Page_Load events.

Wouldnt it be just as easy to do:

protected void Page_Load(object sender, EventArgs e)
{
  if(!Page.IsPostBack)
  {
     doLoginStuff();
     doFeaturedProducts();
  }
}

I don't know. I am glad you got your issue resolved though.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET

Professional IIS 7 and ASP.NET Integrated Programming

================================================== =========

I was just talking to a guy in the HTML forum with a similar problem. I was under the impression that in ASP.NET you only need one handler.

Then no matter how much you need to do on page load, you keep writing code for all you need to do inside the event handler until it does all the actions you need to do.

So you have one handler, but all the different actions it needs to take are collected inside (hence the more urgent need for clean coding). Is this wrong?

-------------------------

Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe

When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper

Chroniclemaster1, Founder of www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.

You only need one handler (I am assuming you are refering to Page_Load) but, as Imar demonstrated, you can have as many as you want.

Depending on the Programmer, the Page_Load event may only ever execute an Action one time (like binding a control to a datasource for example) and all subsequent post backs could be handled by different control events.


================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET

Professional IIS 7 and ASP.NET Integrated Programming

================================================== =========

Yes, I was referring to Page_Load, though I assume (always dangerous) that the principle extends to any event handler.

And just to clarify, you CAN use different post backs, but those are functionality related issues for your application. You don't NEED to do it just to effect multiple actions, you can run multiple actions inside one event handler (Page_Load or anything else).

-------------------------

Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe

When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper

Chroniclemaster1, Founder of www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.

Not al all....

As Doug suggested, you can have something like:

doLoginStuff();
doFeaturedProducts();

in your Page_load. You can call as many other methods as you see fit. The good thing about using separate methods is that you can reuse them from other events as well. E.g. when !Page.IsPostBack you call GetData() and from some event triggered by some data bound control you can call the same method again.....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004