Rank: Advanced Member
Groups: Member
Joined: 10/15/2008
Posts: 45
|
Hi,
I guess the reason is obvious.
At present, my entire Master reloads when loading a page that targets its ContentPlaceHolder. Therefore, I'm thinking of replacing the ContentPlaceHolder with a CallbackPanel, since I'm still on VS2005 and .NET 2.0, thus, don't have UpdatePanel. This way, when loaded page fires a postback, only what is enclosed withing the CallbackPanel gets reloaded.
In other words, I'm trying to simulate iFrames via CallbackPanels.
Is this approach applicable?
Thanks.
Regards,
Saed Hamdan
"Man may be destroyed but not defeated" -Hemmingway
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,088
|
You can use CallbackPanel to resolve the typical master page scenario you described, however that requires you to make significant structural change to your application. The fundamental difference at here is, with MasterPage, you have many .aspx pages. With CallbackPanel, everything is in the same page. Our sample project uses exactly this approach. So you can take a look of that.
This has nothing to do with iframe though. CallbackPanel can never be used to replace iframe because CallbackPanel works within the same page and the exact purpose of iframe is to load another page.
Thanks
|