Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Wed, 30 Apr 2008 15:46:09 GMT,    group: microsoft.public.vstudio.sourcesafe        back       


VSS 2005 (v8.0) - Setting working folders in subprojects   
How do I guarantee that changing the working folder of a project with
subprojects also changes the working folders of subprojects? In my case
subprojects reflect the subfolders on the hard drive that contain the source
files. 

VSS is a bit strange in the way all this is handled.  For example say we have

Project1
Project1\subproject1
Project1\subproject2

On the hard-drive say we have

C:\Project1-V1.0
C:\Project1-V1.0\subproject1
C:\Project1-V1.0\subproject2

and

C:\Project1-V1.1
C:\Project1-V1.1\subproject1
C:\Project1-V1.1\subproject2

If I change the working folder from C:\Project1-V1.0 to C:\Project1-V1.1, I
usually have to change the working folder of subproject1 and subproject2
individually, at which point subprojects of subproject1 and subproject2 *are"
changed automatically; I don't have to go through the entire heirarchy and
modify all the working folders of every subproject, only the second level of
the hierarchy.

I can live with that, but the kicker is that if you ever inidvidually change
a lower subproject to "break away" to a folder somewhere else on the hard
drive, that information is retained and is not changed when upper projects
are later given a new working folder. This is very dangerous if the
assumption is made that changing a project working folder changes subproject
working folders.

In Options > General, "Act on projects recursively" is *checked*.

So the question is

1.  How to either (a) check whether or (b) gurantee that subproject working
folders follow higher project working folders. Any other options or
procedures I should know  about ?

2.  What are the rules on how subproject working folders get assigned
automatically?
date: Wed, 30 Apr 2008 15:46:09 GMT   author:   GCB-atWork-Toronto u43302@uwe

Re: VSS 2005 (v8.0) - Setting working folders in subprojects   
"GCB-atWork-Toronto" <u43302@uwe> wrote in message news:837538593cfb6@uwe...
> How do I guarantee that changing the working folder of a project with
> subprojects also changes the working folders of subprojects? In my case
> subprojects reflect the subfolders on the hard drive that contain the 
> source
> files.
>
> VSS is a bit strange in the way all this is handled.  For example say we 
> have
>
> Project1
> Project1\subproject1
> Project1\subproject2
>
> On the hard-drive say we have
>
> C:\Project1-V1.0
> C:\Project1-V1.0\subproject1
> C:\Project1-V1.0\subproject2
>
> and
>
> C:\Project1-V1.1
> C:\Project1-V1.1\subproject1
> C:\Project1-V1.1\subproject2
>
> If I change the working folder from C:\Project1-V1.0 to C:\Project1-V1.1, 
> I
> usually have to change the working folder of subproject1 and subproject2
> individually, at which point subprojects of subproject1 and subproject2 
> *are"
> changed automatically; I don't have to go through the entire heirarchy and
> modify all the working folders of every subproject, only the second level 
> of
> the hierarchy.
>
> I can live with that, but the kicker is that if you ever inidvidually 
> change
> a lower subproject to "break away" to a folder somewhere else on the hard
> drive, that information is retained and is not changed when upper projects
> are later given a new working folder. This is very dangerous if the
> assumption is made that changing a project working folder changes 
> subproject
> working folders.
>
> In Options > General, "Act on projects recursively" is *checked*.
>
> So the question is
>
> 1.  How to either (a) check whether or (b) gurantee that subproject 
> working
> folders follow higher project working folders. Any other options or
> procedures I should know  about ?
>

In VSS 6.0d, you could select projects that had working folders, click the 
"set working folder" button, and clear the dialog.  That would make it 
inherit the working folder from higher in the project tree.  Unfortunately 
VSS 2005 no long allows this.  But, in your database's database folder, 
there will be a "users/<username>/ss.ini" file.  This file has the mappings 
for all your working folders and you can manually delete any you don't want 
set.

Also, when you get a project recursively, you can select "build tree, 
override working folders" and all subprojects that have specific working 
folders set will be ignored.

> 2.  What are the rules on how subproject working folders get assigned
> automatically?

They are set automatically if they don't have a specific folder set, and a 
higher level project has one set.  Again, the settings are in the user's 
SS.INI file and you can manually edit the file and remove the ones you don't 
want.

FYI:  working folders are set on a per user *and* per computer basis.  You 
will see the names of the workstations in the SS.INI file qualifying each 
setting.

-Mark
date: Wed, 30 Apr 2008 20:44:38 -0700   author:   Mark Tolonen

Re: VSS 2005 (v8.0) - Setting working folders in subprojects   
Mark, thanks once again, your remarks were spot on and exactly what I needed
to know.

Gerry

Mark Tolonen wrote:
>> How do I guarantee that changing the working folder of a project with
>> subprojects also changes the working folders of subprojects? In my case
>[quoted text clipped - 48 lines]
>> folders follow higher project working folders. Any other options or
>> procedures I should know  about ?
>
>In VSS 6.0d, you could select projects that had working folders, click the 
>"set working folder" button, and clear the dialog.  That would make it 
>inherit the working folder from higher in the project tree.  Unfortunately 
>VSS 2005 no long allows this.  But, in your database's database folder, 
>there will be a "users/<username>/ss.ini" file.  This file has the mappings 
>for all your working folders and you can manually delete any you don't want 
>set.
>
>Also, when you get a project recursively, you can select "build tree, 
>override working folders" and all subprojects that have specific working 
>folders set will be ignored.
>
>> 2.  What are the rules on how subproject working folders get assigned
>> automatically?
>
>They are set automatically if they don't have a specific folder set, and a 
>higher level project has one set.  Again, the settings are in the user's 
>SS.INI file and you can manually edit the file and remove the ones you don't 
>want.
>
>FYI:  working folders are set on a per user *and* per computer basis.  You 
>will see the names of the workstations in the SS.INI file qualifying each 
>setting.
>
>-Mark

-- 
Message posted via DotNetMonster.com
http://www.dotnetmonster.com/Uwe/Forums.aspx/mvs-vss/200805/1
date: Thu, 01 May 2008 10:18:33 GMT   author:   GCB-atWork-Toronto via DotNetMonster.com u43302@uwe

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us