Unfortunately, I would say no. You can certainly set the images to cache,
but the actual layout bits are implemented as a user control (simple
explanation: page called, has master page, master page called, master page
embeds in contents sections). Because of the nature of browsers today, and
the nature of the master page, I cannot see a means of caching all of the
master content. If someone has a brilliant way to accomplish this, I am all
ears.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***********************************************
Think Outside the Box!
***********************************************
"Keith Patrick" <ri*******************@nospam.hotmail.com> wrote in message
news:u5*************@TK2MSFTNGP10.phx.gbl...
I'd like to get some semblance of SmartNavigation-like behavior in a
MasterPage-based content navigation app (primarily the lack of "flicker")
I had it working in a version that used a MultiView instead of a true
MasterPage layout, but it wasn't conducive to the SiteMap that I use
throughout. The MasterPage paradigm is a good fit for the style of app,
and everything else works perfectly except I'd prefer to stop the
flickering. Since I can't enable SmartNav at the MasterPage level (in
addition to the attribute being marked as obsolete), is there some way to
programmatically render the page a bit more efficiently on the client if
the page-to-page nav uses the same MasterPage?