Well, as Jimi Hendrix once said "You can't believe everything you see and
hear, can you?"
FrameSets are problematic. Of course, everything is problematic to a degree.
FrameSets with ASP or ASP.Net can be a bit more problematic, mostly for 2
reasons:
1. Search Engine behavior - Search Engines have a hard time with FrameSets.
2. Frame coordination - As each frame is a separate browser instance,
Session is unreliable in the context of FrameSets, and communication between
frames has to occur on the client.
That said, FrameSets are a tool. Anything else you have heard is
characterization, not fact. The fact is, FrameSets are a tool that can be
useful under the right circumstances. For less-experienced developers, I
would have to agree with Steve to steer clear of them.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
"Michael" <st******@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
I'm new to ASP.Net but been a programmer for decades.
I'm doing a new App and am intending to use an Item Listing Frame
alongside
a Data Input Frame (I hate in-Grid editing). I figure when I hit Save on
the
Input Frame the List will update (and who cares how long it takes) while
the
Entry Frame presents you with a blank form ready to go almost immediately.
I've looked around for information/tutorials on Frames in .Net and it's
pretty scarce. I remember a few years ago everyone hated Frames due to
some
browsers not supporting them.
Is this still the case? Or is it just an old prejudice?
Regards