Last post Jul 22, 2008 11:54 AM by hongping
Jul 08, 2008 10:43 AM|ThisBytes5|LINK
We have a number of web applications, all of the applications are developed in VS 2005, with SP1 and use the ASP.NET Web Application project type as opposed to the new
à web site option.
All of our applications are installed with MSI, all created from the VS 2005 Web Setup Project, (though we have seen this in the past with xcopy deployments)
From time to time when we uninstall than re-install the web application we don't see the changes that were made in the new code base (MSI). However, if we delete the Temporary ASP.NET
Files folder for the virtual directory than the changes take place.
We have to delete the folder, a simple IIS reset doesn’t always work.
I’ve tried searching Google for Temporary ASP.NET Files, but haven’t turned up any issues that sound like what we are seeing.
Any ideas as to why we would have to go and delete the temporary folder? Any suggestions of where to look for info?
Jul 08, 2008 01:36 PM|hongping|LINK
ASP.NET should detect changes and restart the appdomains. ASP.NET Application Life Cycle Overview:
Is file-change notifications turned on? It should be on by default, and it is required for detecting file changes. http://support.microsoft.com/kb/911272
Also, try creating just a simple web site, then publish and deploy it. Then make changes to the original web site and republish and redeploy. This will determine whether there is something peculiar about the particular web application y ou are trying to
Jul 08, 2008 01:59 PM|ThisBytes5|LINK
I will be sure to look at the links, but wanted to comment as I'm leaving for the day.
This doesn't happen all the time, it's random (which I should have said in the intial post). As such it's not re-produceable a 100% of the time, also it's not always the same project that this happens too.
Jul 09, 2008 07:32 AM|ThisBytes5|LINK
I've read through both links.
The first appears to be a hot fix for something that isn't the issue we are seeing. Our apps don't hang, nor appear to hang.
The second link seems to describe what I expect to happen, but does not really explain why we are seeing what we are seeing the issue.
Given that we've done IISResets and Machine Reboots (missed that in first post) and this doesn't always resolve the issue, due to that and the above comment about the hot fix, I'm wondering if the file notification is really an issue at all.
Other item of interest is that we don't tend to see this on our developer machines, only our integration thru production environments where the MSI's are used.
Jul 17, 2008 01:15 PM|hongping|LINK
Could you verify whether you have the registry key mentioned in the hotfix? If so, what value is it? ( HKLM\Software\Microsoft\ASP.NET\FCNMode )
What is the difference between production environment and your developer environment? Could it be due to differences in configuration?
Jul 18, 2008 09:56 PM|ThisBytes5|LINK
When I say developer machines, I mean the machines with VS 2005 installed on them. The fact is we tend to always see the changes we make to code and recompile/debug it. Going to the production environment we do so with MSI installs.
However, as far as differances, there would be many only because our machine has VS 2005 and other development tools installed on them, but we did ensure to run the same OS on our dev machines as what is on our prod machines, win 2k3.
Jul 22, 2008 11:54 AM|hongping|LINK
Did you check the link and whether the registry key for FCNMode is set to the correct value? I have seen a couple of other posts with the same problem last week and their problem was indeed this key. You might want to check it to rule it out as a possibility.