Shared Resource and Shadowed Folder Issue

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Leviathan2006
Posts: 6
Joined: Mon Mar 20, 2006 12:25 pm

Shared Resource and Shadowed Folder Issue

Post by Leviathan2006 » Thu Jun 15, 2006 10:44 am

Our application and setup requires our developers to check in DLL files as part of the development process. In the application, we have shared DLL files with other folders in the application to maintain the required functionality and overcome a limitation of VS.Net.

For example, I have the following setup.

$/Folder1/bin/debug/file.dll

This DLL is shared to the following locations.

$/Folder2/bin/debug/file.dll
$/Folder3/bin/debug/file.dll
$/Folder4/bin/debug/file.dll

When a developer checks out a project, and rebuilds the DLL, and checks the item back in, the original DLL in Folder1 is updated, and the shares are all updated as well.

As part of the configuration, I have Shadow Folders setup on the Vault server to shadow out to C:\Inetpub\wwwroot\application\.

When a change is committed back to the Vault, and shadowed out I am having a problem with the original DLL not being updated. For example,

c:\inetpub\wwwroot\application\Folder1\bin\debug\file.dll DOES NOT UPDATE

c:\inetpub\wwwroot\application\Folder2\bin\debug\file.dll DOES GET UPDATED
c:\inetpub\wwwroot\application\Folder3\bin\debug\file.dll DOES GET UPDATED
c:\inetpub\wwwroot\application\Folder4\bin\debug\file.dll DOES GET UPDATED

Anyone have any ideas on what to look for? Is this a bug?

Thanks in advance.

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Thu Jun 15, 2006 10:56 am

Is there a web application running files in c:\inetpub\wwwroot\application\Folder1\bin\debug ?

If so, then it is probably a good bet IIS has a lock on the file.dll, and it cannot be overwritten until IIS releases the lock on the file.
Jeff Clausius
SourceGear

Leviathan2006
Posts: 6
Joined: Mon Mar 20, 2006 12:25 pm

Post by Leviathan2006 » Thu Jun 15, 2006 11:59 am

Looks like a complete reboot on the server corrected the problem.
Thanks.

Post Reply