I want to disable page caching so that when a user presses the browser's back
button after submitting a form, he won't be able to re-edit the form.
How can I do that?
Thanks in advance.

I have a serious problem in .NET currently. I am hoping somebody out there
can help me.
I have a ASP.NET application written in VB.NET and requires the user to log
in. I authenticate user using LDAP, so if the user id is active in our

I have an asp.net site, with most of the pages having this statement at
the top to cache them for 10 minutes:
<%@ OutputCache Duration="600" VaryByParam="none" %>
Now, under certain circumstances, I want to be able to manually empty

I'm quite the newbie at ASP.NET so I hope that this question doesn't sound
too stupid.
I'm looking into how suitable ASP.NET would be for an application that has
to display a series of images quite rapidly after an initial (reasonable)

We run a web site where we currently have 10 web servers.
We have built a synchronized cache that works like this.
All servers store its own cache and gets the data from the data source. We
always set a absolute expiration date when we add the cache item. Along with

I have a frameset that has a asp treeview control that is bound to an
XMLDataSource.
I cannot get the page to stop caching. I can manually change the data and
have different users hit the page and the page seems to renderthe first one

exception inside lock before lock body
lock(foo()){bar();} what will happen if foo() throws an exception? will
there be a lock on the exception?

I m using session veriables of asp.net on two websites
www.net4professionals.com(job site) and www.net4matrimonials.com
(bride/groom service)
when i create a session on page A i use codeing

I have a question regarding keeping a username in the cache in order to
prevent multiple logins. I read 'Preventing Multiple Logins in ASP.NET' by
Peter Bormberg (great article
http://www.eggheadcafe.com/articles/20030418.asp) and everything works fine,

I was wondering if some of you guys know if the concept of "Control State"
made it to the final rel. of ASP.NET 2.0
Thanks!
  Daniel