Why use panels when you could use the Infragistics WebTab object? And all that work happens on the client side. Just a thought.

P.S. I love my WebTab, 7 pages in all, 2 of which are optional depending if I am in Edit or Add mode.

>Okay, I built a base class form that hides and shows a set of panels based on the a menu option, wizard effect.
>Based on page selection a panel would become visible.
>
>Well at runtime this would work perfect. On the form load I set a default panel as the one to be visible and the rest are not, very simple idea right!
>
>Well it has cost me at least 8 hours of work, because the designer would run the form load even though you are designing.
>
>So it would make the 3 out of the 4 pages invisible, so in the designer when I went to work on that page and pull it to front, the designer would show the drag handles but nothing would be in the panel?????
>
>So I went looking to see what I screwed up (being a newbie), and eventually when I compared my base form to my to a co-workers, they worked differently because he didn't receive the latest additions to the framework that I was working on.
>
>So what it came down to was the designer was making the panels invisible......there goes 8 hours I will never get back.....
>
>I hope this helps some one else.
>
>the trick to solving the problem is to put an "if (!this.DesignMode)" around the call to make the pages invisible.
>
>Go figure a designer running method code@!!@!