Working folder setting keeps getting lost

bpd · Post by **bpd** » Wed Mar 09, 2005 12:25 pm

My development team uses just one ROOT working folder for all projects, all other subdirectories are then inherited.

Recently I have had reports, and it has happened to me a couple of times today that the Working Folder setting at the ROOT of the source tree is being lost and needs to be re-entered.

I.e. you enter the SG client click on the ROOT and no working folder appears to be set, so you have to enter and select the Force Inherit On All SubFolders. The next day you might be experiencing IDE binding problems and discover its because the setting has become blank again?

The problem seems to occur after a failure to bind a project to Vault in the VS.NET IDE - but I cant guarantee that

P.S. We are using 3.0.2 Server/Client

gmagana · Post by **gmagana** » Wed Mar 09, 2005 1:01 pm

Are these web projects? VS.NET keeps changing the working folder to the local inetpub/wwwroot for these kinds of projects.

bpd · Post by **bpd** » Thu Mar 10, 2005 8:12 am

Well Web based projects do seem to be predominantly the worst affected, but we have seen the effect on non-web projects (or non-web DLL code where solutions contain web projects and DLL projects)

If this is a shortfall of the VS.NET IDE is there anyway that the IDE integration can be improved to counter it - we are having instance where code is being Undo CheckOut because the working folder has changed

dan · Post by **dan** » Thu Mar 10, 2005 9:09 am

As with any error, if you can reproduce it reliably and send us the steps, we might be able to work around it.

It might make sense that it happens related to errors in binding - binding is one of the ways to set working folders, so it might be unsetting it, but then failing to set it properly.