tag:blogger.com,1999:blog-8425265434515353560.post732827131407772869..comments2010-06-21T13:32:34.788-04:00Matt Passellhttp://www.blogger.com/profile/08333337257678227054noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8425265434515353560.post-67048243421842103652010-06-21T13:32:34.777-04:002010-06-21T13:32:34.777-04:00Hmm. That's interesting. We never explicitly changed the permissions for the files or directories, but it's possible that moving the file out and then back in caused a change as a side effect. I'll have to read up on that sometime.Matt Passellhttp://www.blogger.com/profile/11172160863136806601noreply@blogger.comtag:blogger.com,1999:blog-8425265434515353560.post-60727397321913008932010-06-21T12:31:13.644-04:002010-06-21T12:31:13.644-04:00I had this problem as well. To fix it for me I had to give my user full control of the parent folder of directory I wanted to update. Which I imagine was the case for you too, since by default users can't create files on C:\ on vista and beyond.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8425265434515353560.post-91173471520148724742009-09-17T22:13:55.548-04:002009-09-17T22:13:55.548-04:00I have had annoying cases happen like that as well. What I do is export all of my changes to a temporary directory, blow away the working copy directory, re-import it and apply the changes I had set aside. It sucks, but it works.Karnalhttp://www.blogger.com/profile/08002847790182260939noreply@blogger.com