Visual Source Safe & shares/link paths too long 2

[SpenBabe]

We are currently using Visual Studio 6.0 Enterprise (with Visual Source Safe 6.0 included) & have a lot of code shared between projects

We have used a long descriptive names for projects, eg:
$\Sales Order Processing\Standard\MSSQL\Main Application
$\Sales Order Processing\Standard\MYSQL\Main Application
$\Sales Order Processing\Joe Bloggs\MSSQL\Main Application
etc...

Sharing & Branching works fine, but when you use 'Properties' on a file to see which other projects are using it, we see '$\...\MSSQL\Main Application', etc...

We make hundreds of bespoke versions of our standard software & consequently have a lot of shared code, but it is not easy to tell where else it is used.

Does any suffer this or know a patch/hack to switch horizontal scroll bars on or resize the dialog ?

PS: The options to report to printer do the same !!!

 

[chiph]

I get the same thing, and haven't figured out a way around it yet.

What's really annoying is if your check-out directory structure matches your VSS structure. Then, when using the VB references dialog, it cuts off the right side of the path, so you have no idea what the reference is pointing to.

I can only hope they fix this in the .NET release of Source Safe

Chip H.

 

[SpenBabe]

Thanks for the info.

Glad to know I'm not alone

Have got a copy of .NET Studio on the way. I will try it out & let you know !!!

Spen.

 

[Cagliostro]

I believe, the best idea is to use a virtual drive, and all of users to use it.
If you have long path you can do followind:
subst x: onedrive:\oneVeryLongPath\MSSQL\Main Application
subst z: otherDrive:\otherVeryLongPath\MSSQL\Main Application
and in paths you'll use such paths as
x:\onefile
z:\otherfile John Fill

ivfmd@mail.md

 

[chiph]

That's a good idea, John. I've got plenty of unused drive letters!

Chip H.

 

[CiderMonster]

Just testing to see if i've joined correctly

 

[chiph]

Welcome, CiderMonster.

Chip H.