Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Caching / August 2005

Tip: Looking for answers? Try searching our database.

Republishing a ASP.NET page

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ehsan - 10 Aug 2005 11:19 GMT
Dear All,

We have constructed a web site with about 110 pages using ASP.NET with
Visual Basic server code. First time that we published our site (including
all pages)  everythings were working correctly and each page was read form
server as it was supposed,
but the problem is that when we change a VB codes of a page and republish it
agian, the server still shows the perviously published page!!! and new page
is not readed by server. It seems that a cached version of pages is being
displayed by our server not the changes one. How the cached files may be
deleted from the server? our is there any other reasons we may have note been
noticed for this problem?
Should we add any caching related codes into each pages?

We would really appreciate your assistant as we have tried so many sources
till now to resolv the problem but we were unsuccessfull. We are extremely
awaiting your advice.

Thanks again.

Regards,

Ehsan Rad
Joerg Jooss - 17 Aug 2005 20:43 GMT
> Dear All,
>
[quoted text clipped - 7 lines]
> version of pages is being displayed by our server not the changes
> one. How the cached files may be deleted from the server?

Cached pages usually don't live on the server, but on the client or
downstream proxies. You can use pure server-side caching in ASP.NET,
but this is not likely to be your problem.

> our is
> there any other reasons we may have note been noticed for this
> problem?  Should we add any caching related codes into each pages?

Yes, you should mark your pages as non-cacheable. This is usually the
best initial approach for dynamically created web pages:

Response.Cache.SetCacheability(HttpCacheability.NoCache);

Cheers,
Signature

http://www.joergjooss.de
mailto:news-reply@joergjooss.de


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.