How can I prevent subversion from updating without making any changes due to IIS recompiling the website?

For my staging site, I have a subversion repository that I update when I need to view changes on the staging server. Instead of manually updating the staging server's subversion folder every few minutes when I need to check something, I have a script that automatically checks for any subversion updates. My problem is that every time an update is checked, even if there is no change, I think the subversion might be modifying some files in the .svn folders on the site, and this forces IIS to recompile the website, which takes 40 seconds. If no code changes occur, then I don't want IIS to recompile the website. Does anyone know a good way to fix this so that the site only recompiles the code changes and not after every check for updates?

0


source to share


5 answers


You can modify your script to do the diff first (with --summarize) and then update if the relevant files are in the diff summary list (* .cs, etc.).



+2


source


You should have a script to check the current version number of the repository before doing the update. If the version number has not changed, do not update.



0


source


How about using this code in a post-commit instead, so it should only run after a correct commit?

0


source


Your solution is probably in your question: Don't let IIS browse the .svn folders. No idea here, but IIS should have a setting somewhere to exclude certain directories from being scanned for changed files. Maybe tag the .svn folders with a hidden file attribute?

Google provides this forum as a place to inquire about IIS configuration issues:

http://forums.iis.net/1034.aspx?PageIndex=18&forumoptions=0:1:11 ::

0


source


0


source







All Articles