My website utilizes ASP. I have a link to a PowerPoint file within my website's file structure. The file is replaced every day with an updated version, but when users click on the link, the browser displays the cached version if they have visited before. How can I ensure that the updated version is loaded without asking the user to clear his or her cache?
I assume you're using IIS. How you do it depends on exactly which version of IIS you're using, but let's assume version 6 (i.e. the one that comes with Windows Server 2003).
You open up the Internet Information Services Manager, and find the file you want to modify the caching settings for (or you can do it on the folder that contains the file - for example, if you want to do all files in a directory, which is pretty common). Right click the file (or folder) and select "Properties". Then, on the HTTP Headers tab, check the "Enable content expiration" checkbox and change the settings to "Expire after 1 Day" or whatever you think is appropriate (maybe after an hour makes more sense).
In newer versions of IIS (e.g. the one that comes with Windows Server 2008) it's a bit different, but hopefully you should be able to figure it out from the description above.
Related
Is it possible to regenerate all pages within Interwoven TeamSite 6.7.2?
Simply selecting a folder and click on Actions -> regenerate page doesn't work. It gets the error message: "Not a generated file".
So is there a trick to regenerate through the folder hierarchy?
TeamSite will process whatever you passed as a parameter, be it file or folder. If it is not template-based, you will see that error. There is no way to recursively regenerate pages throughout a workarea natively.
I have written Perl scripts to traverse the filesystem, test each files extended attributes to see if it was template-based and regenerate the page if so. This is probably the easiest way to achieve mass regeneration.
If you must have this through the GUI, you can create a custom menu item that calls the above script.
Not sure when this question was posted - it says Jan 25 but does not reveal the year, but TeamSite 6.7 has been EOL (end of life) for a few years by the vendor HP Autonomy.
As of this writing the latest version of the software is TeamSite 7.3.2, with version 7.4 right around the corner. The reason I mention about versions is because, the paradigm to create and render pages has undergone a complete change.
Pages are no longer "generated" and deployed. SitePublisher - now part of TeamSite allows pages to be authored using WYSIWYG tools.
That said, the old paradigm of "generating" pages is still backward compatible, but if you are planning to upgrade you may get more value from the system by using SitePublisher and LiveSite.
run this command from the unix command line:
find /your/folder/startpoint -exec /path/to/iwregen {} \;
The error message: "Not a generated file" that you are getting is because you are trying to select a folder since the contents of folders can be different some can be your actual pages while some can be a .pdf file, .txt file or any other extension files.
Please try to regenerate pages using these steps:
Double click on the folder to open in which your actual pages resides
After this try to select all the pages (not manually but there is option/checkbox on the UI as "select all" or "select").
Now, after selecting all just scroll down and see all the selected things whether they are actual pages and not something else. If they are not the pages then deselect only that particular file.
Now, click on "Actions" and regenerate the pages all at once. This will definitely work.
Please vote this solution if it is useful else please add your further issues/questions will try to help you with the best of my knowledge.
Thanks!
I'm new to Aptana 3. I recently switched from using an FTP (Filezilla) and text editor just to speed the file editing process up a bit.
I'm dealing mainly with Wordpress sites on a shared Godaddy hosting account, and am having some trouble uploading the files I have edited via Aptana to my live site.
i.e. I've edited several lines in my "main.css" file. I save it in my "Project Explorer" window in Aptana, have my FTP connection all set up and working, and click the "Upload" icon. I refresh my browser and nothing has changed, and I can see the website is still pulling in the old css. I've also tried "synchronizing" my files and hitting the "Publish" button, but that doesn't work either?
I've also tried just editing the file in a new Remote Connection tab, but no joy either.
I've hunted all over for simple walkthrough for deployment or file sync guides for Aptana, and watched a few video tutorials but nothing has worked so far.
Hold Control+F5 for a few seconds in your browser. You probably are just running a cached version of the CSS in your browser. That should prune it.
I had the same problem. What I found I had to do was an initial synchronization, I know you mention that you did this but it may be that it didn't fully sync as its not always clear what is going on with the Aptana sync.
What I did:
Make sure your Project has a connection in it and that it points to the server location that you want to sync with
Select the Remote tab and right-click on a file within the chosen connection, choose File Transfer...
This will open the sync window and it will initiate a compare, this is where confusion set in for me, if the folder structure is not identical it will propose to create and delete lots of files. I found I was deselecting items to be safe but meant that it did not correctly sync. Make sure you are syncing from the same root level and then let it do a full sync, this seems to register or record a link between the local and remote files.
Run the sync. when it is complete you will now be able to upload individual files successfully from the Project tab using the upload icon (before a successful sync this will not work - even though it looks like it is doing an upload).
Hope this helps.
I'm having a problem exactly like the one in this very short video.
http://www.youtube.com/watch?v=912c6sQAsH0
I do not feel comfortable running a downloaded .exe file from a third party unknown developer as suggested by the link from the youtube page.
Does anyone know how to manually solve this problem?
Thanks.
Another way to rebuild the icon cache in Windows 7 without a restart is to change momentarily the screen color depth to 16 bits, for example, and when Windows asks you whether you want to keep the changes or not, click "No" to restore the original settings. This will invalidate the icon cache and Windows will recreate it instantly.
The problem is something called icon cache. Windows saves all recent icons in one file so that it does not have to gather icons all over the disk. This speeds up the system start.
Googling with the term "windows 7 rebuild icon cache" (without quotes) I was able to determine that icon cache is stored in file %USERPROFILE%\AppData\Local\IconCache.db and that all you need to do is rename it and restart Windows, like it's described here. Explorer has a hold of that file so you can't just delete it. There is a .bat file that makes it easy to delete the cache. You can download the file from here.
In Visual Studio 2010 I've created a Silverlight app by choosing the "Silverlight Business Application" template.
I changed some code in Home.xaml.cs, closed Visual Studio, opened it again, and began making more changes.
But now the changes that I make to the code don't take effect at all. It's as if the entire application is cached. I can even delete the whole contents of the Home.xaml.cs file so it is blank, and pressing F5 shows me my original Silverlight app. This happens both in Firefox and Chrome. I've rebuilt, deleted the bin directory, but it keeps showing me the same old application.
What do I need to change in this template so that I can make changes to the code, and see them reflected in the application?
Addendum:
I created a new Silverlight Business App, copied all the code to it, and this caches after the first change as well.
So it occurred to me to go into BusinessApplicationTestPage.asp and chang the link to the .xap file:
<param name="source" value="ClientBin/BusinessApplication4.xap?id=111"/>
So i've "fixed" the problem in that I change the id each time I run the application. And I suppose I could put a random number generator in here so that it refreshes each time. But... is this the intent? Isn't there an easier way to develop without this caching, and then only when deploying to cache like this?
Update:
Ok, just by adding that ?id=111 once, it recognizes each change now. Perhaps...
Start by using Control-F5 in IE. This not only refreshes the page, it clears the browser cache so in theory you will download a new version.
If weirdness like this is still happening you need to delete the contents of these folders...
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
This is such a well known pain-point in older versions of Visual Studio that most web developers I know have batch files specifically for cleaning out those directories.
These folders exist so that you can alter ASP.NET applications while the application is still running. IIS will detect the changed files and copy them to the temp directory while it silently restarts your web site. Alas this doesn't always work correctly, especially when running under the IDE.
I know this isn't an ideal solution, but I have found that the IE9 Beta caches XAPs much less aggressively than other browsers, and I don't face this problem when running my Silverlight applications in it.
I am creating a clickonce installer using the deployment strategy of Install from the Web or network share, on one of my project. I am learning how to use click once installers. When i publish my project it gets succeeded. i gave the URL of my website that i had created through google so that anyone can install from that URL. After publish gets succeeded the URL should be launched automatically but it is not. Moreover. When i check my website and in it that page whose URL i had given, there is nothing there. No installer. Please help.
Right Click on Publishing Project
Click Properties
Click "Publish"
In "Publishing Folder Location" is anything set there?
Click the button with ellipsis (...) to the right of the combobox
Click "FTP Site" (not Remote site, as this needs FrontPage extensions)
Enter the Server information, Directory (that you have access to), keep it as passive mode, uncheck the Anonymous option and put in the valid FTP instructions.
Click Open, and Republish. All should work 100% with this.
If not, have a look in your wwwroot/ folder and find the application information (if it's there) and you will have to manually upload the files.
EDIT for comment:
The website that you are uploading to, does it have FTP access? Meaning a place that you would upload file to for display on the website, even like your html content? (index.html etc.)
If not, you will need to get these details from your website hosting provider and fill in the appropriate fields for the FTP upload.
It's a while since I did this, but I'm fairly sure that you have to upload the files manually.
The installer needs the location so it can build the web page etc. All the files should be in an output folder in your project.
EDIT: I've just checked and the output folder is the one you specify on the first step of the Publish Wizard. If you specify a local folder the files will be put there for you to FTP to your website later. You can also specify a remote address as and FTP or HTTP location (which I'd forgotten when I posted my original answer). You'll have to enter the user name and password for connecting to the remote location later in the process.
Are you using Visual Studio 2008? The default behaviour of deploying a "publish.htm" page has changed.
Bring up your project's properties and switch to the "Publish" tab. Click the "Options" button and switch to the "Deployment" section of the dialog. You'll see by default that the "Deployment web page" TextBox is empty. You'll need to give that a value and also check the "Automatically generate deployment web page after every publish" CheckBox.
I've taken to filling that in with "default.htm" so that whichever folder you deploy your app into will have the ClickOnce publish page as its default page.