Hi,
I want to apply source control on a shared folder sitting on one of our servers. I used shadow folders to reflect the changes whenever somebody checks in, and it works fine.
However we have templates (.ascx) files in this shadow folder and when we try to load these templates from ASP.NEt we get permission errors.
Is there any other way to reflect the changes to a shared folder
Thanks

VSS shadow folder permission problem
Deffiant
Hi Alin,
Thanks for your prompt reply.
What I am facing is the opposite of your last post:
There is no problem for VSS in updating the shadow folder, it works perfectly.
The files under the shadow folder can never be accessed by .net code (the code tries to load the ascx file sitting in shadow folder using loadobject method)
The weird thing is I can access the files in shadow folder using file system, I can even delete them, so I assume it is not a file system lock.
I even tried to replicate the shadow folder to another folder and tried to access the ascx files from the new location, I still get IO error. This makes me think that VSS changes the files in some way when it is copying them to shadow folders upon check in.
I really have to put versioning on this shared folder, so do you think vss automation will be any good Or is there other things I can try to solve the IO issue
Regards
Gizem
angela221
> This makes me think that VSS changes the files in some way when it is copying them to shadow folders upon check in.
No, VSS does not change the files in a weird way that will prevent the files to be loaded by .net. The proof As you say, from the file system you can access the files, you can even delete them, etc.
I have no idea what's preventing .net to load the files from the shared location, but it may simply be a policy (like when you're trying to execute a .net binary from a remote share) or access permission you need to set for asp.net to access the location.
It seems to me you have a problem with asp.net configuration, in which case you should probably post the question on asp.net forums.
Alin
jali
Yes, as far as I know Asp.net (and in fact .net frameworks) locks the files when you open them with Stream reader/writer classes. If you have a .net application that uses the files from the shadow folder, that would explain why VSS fails to update the shadow folders.
Alin
Gokop Goteng
Thanks Alin,
I have to update the shadow folder every time a file in the project is checked in so manually getting the project won't work for me.
It seems to work i.e. i can see the latest version in the shadow folder but this shadow folder includes some template files used by asp.net applications. These applications throw IO exceptions when they try to load these templates with loadobject. So I assume shadowing changes the files in some way or constantly locks them
Frank Melvin
Hi Nimrodel,
The easiest way to synchronize VSS structure with the shadow folder content (if for some reasons the shadow folder was not automatically updated) is to do a recursive Get from the project that's shadowed into the shadow location.
Alin