Last post Jan 10, 2009 10:46 PM by marksnell
Jan 05, 2009 07:42 PM|marksnell|LINK
I am editor of a community newspaper and have written an ASP.NET website which contains the archive of more than 12,000 articles.
I need to edit this site from different computers in different locations at different times. When I make changes to existing pages and then go to a different computer to do more work on the site, it can take an hour or two to update the cache (even though
I may only have made a change to one page on the other computer).
This update ties up VWD and it will not allow me to continue with other changes. There does not appear to be any way to disable the cache, and the update process seems only to be able to be interrupted on a file by file basis (ie pressing ESC then OK in a dialog
box) - not feasible when there are 12,000 files.
Is there any way around this? Or is VWD just not the right tool for this job? What are the alternatives?
All the best
Jan 06, 2009 11:09 AMemail@example.com|LINK
By "make changes" do you mean you open the site in VWD, change something in a file and then republish the application? If so, it has nothing to do with caching. Stop publishing the entire site for a single change in a single file.
To go further, use a content management system, not thousands of individual files.
Jan 06, 2009 11:34 AM|Danny117|LINK
Wow you've made your own site thats great. I'd say you want to make a page that loads an article from a database and then displays it. Or a content management system of sorts like the other guy said.
http://www.asp.net/downloads/starter-kits/the-beer-house/ the beer house has some article support in it although its not specifically designed for news papers.
http://www.asp.net/downloads/starter-kits/Kigg/ Your readership will love you it lets your users rank the articles in real time.
Jan 10, 2009 10:46 PM|marksnell|LINK
Jeff and Danny, thanks for your suggestions.
To provide a little further information:
The site uses one master page per year, and one aspx page per issue. A querystring is used to load one of up to around 50-80 articles per issue, each stored as an XML file.
The page provides a menu which gives access to all the other articles in the issue or to any of the previous issues.
The articles are stored as individual files because of the nature of the production process of the newsprint version of the newspaper.
Articles are sourced in a variety of ways, but are often received as emails or email attachments (Word documents). I do not work in the newspaper office, so they are sent on to me for editing by email and returned to the production department by email. When
the internet is down, the articles can be put onto flashdrive and I can pick them up from the office.
They are edited in Word because the newspaper publishing software readily accepts Word styles. Word is also used because, in the process of editing, Word macros are easily used to create the XML files of the web articles, as well as the XML file for the contents
menu (which is also used for page placement in the newsprint version).
After the newsprint version is "put to bed", the XML files are loaded onto the web by FTP. A new aspx page is created for the new issue, based on an existing template. In five minutes, the latest version is available on the website.
I have not come across an affordable content management system which:
* provides access to any of 12,000 articles within two or three clicks
* provides the ability for bulk upload of articles via FTP
* can create a new issue online within five minutes
* integrates well with the production of a newsprint newspaper.
The database option has appeal, but it seems a major exercise to design and program a way to bulk upload the articles.
Most CMS and database systems assume a web interface as the primary data input method. This is not only cumbersome but means our primary data is not available locally when the internet is down, and we are relying on it for our newsprint version.
The website is maintained on the web host, because I am not always in the one location with access to the one computer. It is not one local site which is then published to the website, but essentially the reverse.
It is this use of multiple computers which leads me to believe that it is a caching issue.
For example, when I have loaded files by FTP, the next time I load VWD I get messages like:
Getting [filename] from the Web ... press ESC to cancel
Often this ties up the machine and, even though there seems to be a little bit of time-slicing, makes effective use of VWD impossible.
This same sort of thing occurs when I add files through VWD or "make changes" to a single existing file on another machine. Often the number of files retrieved from "the Web" is much greater than the numbers that were actually changed.
Often, I will be challenged with a whole series of "a newer version exists on the server" messages, which require me to say yes or no to each individual file.
Deleting the cache and allowing it to reload from the server wastes a lot less of my time, because it allows me to do other things in the meantime (and not sit answering yes/no).
So, my original question remains: Is there a way to disable or suspend the caching process, so that I can schedule it at times of my choosing, ... or to configure VWD in another way so that it will work more effectively in a multi-location scenario, where large
numbers of files are involved?
Is there another editor that provides IDE support for ASP.NET that does not have this caching issue?
All the best