Visual SourceSafe Forum

[JDurbin]

Hey Roberrrt! How bout a VSS Forum? I couldn't find one here. Can you ask? I don't see the "Suggestion Box" link anywhere.

It is part of Studio like VFP, VB, VC++, VID.
It is picking up idiot users like me to screw their project up with.
It is part of the M$ MCP exams though small.
It is not a forum here yet. [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[TomasDill]

Hi, John!

I suppose its because different tools (VB, VFP, VC++ etc.) use different interface to work with VSS. So, when you work with VSS from VFP, you should ask your questions in the VFP forums.

[sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[JDurbin]

Oh didn't know that. I just finally figured out you have to use FILE/Join Source Control Project

Its pretty cool. The merge screen is nice too showing changes by different people if you have allow multiple checkouts enabled and the same file changed by more than 1 person. cool [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[JDurbin]

Vlad have you used SourceSafe from VB or elsewhere? How is interface different? It seems to me SS is SS. You still have to set it up which I'm finding isnt too hard. I know from VFP you join it but what all is so different from VB ot VFP,etc? [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[TomasDill]

I meant use of SS from VFP or VB. Of course, when you run native VSS interface, this is common. However, VFP ways of storing project files and sources in VSS is MUCH more different than in VB. [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[jonscott8]

John, I made your recommendation to Dave and he had no idea what VSS was. LOL

I'll post back when I find out if its a go.

PS.
I think Rob's on vactation, he hasnt been in since Wednesday. [sig]<p>Jon Hawkins<br><a href=mailto: jonscott8@yahoo.com> jonscott8@yahoo.com</a><br><a href= > </a><br>The World Is Headed For Mutiny.....When All We Want Is Unity. - Creed[/sig]

 

[JDurbin]

Thanks Vlad and Jon [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[jonscott8]

Visual SourceSafe forum has been added. [sig]<p>Jon Hawkins<br><a href=mailto: jonscott8@yahoo.com> jonscott8@yahoo.com</a><br><a href= > </a><br>The World Is Headed For Mutiny.....When All We Want Is Unity. - Creed[/sig]

 

[foxdev]

From my checkered past experience with VSS, I'd recommend NOT using VSS with the VFP Project Manager interface. I'm not saying it can't be done, and I'm not saying it isn't handy at times. But in my experience:

* opening a project is quite slow on a large VFP application

* the default behavior is to checkout a file if you open it from the Project Manager; this means that when people go to simply look at code from within the PM, they automatically check the file out; often, the user is unaware of this, and they go and make &quot;test changes&quot; to the file, then inadvertently check it back in, even though it wasn't their intention.

* allowing multiple checkouts is risky. From a technical standpoint, it exponentially increases the chances of corruption, as VSS must assemble and resolve changes made by multiple poeple at the same time. From a management standpoint, you don't want developer &quot;A&quot; making changes to a class or form independant of developer &quot;B&quot; when the changes by both could impact the other.

So there.

The opinions expressed above are not intended to imply that I do not love Microsoft products and believe in their interoptibility. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br> [/sig]

 

[TomasDill]

Robert, we work with VFP-VSS in our VFP team already 2 years and I can say that VSS for VFP is reliable and useful enough. There are some things that you should avoud, of course.
In addition, to speed up working with VSS, we made our local (team) server in our segment of network, that speed up working with VSS from VFP ~8 times. So problem is not in VFP or VSS or MS products. It is just in organization. [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[JDurbin]

I resumed this thread in the new VSS Forum forum722 in the style of Siskel and Ebert to Robert's comments. Just good fun but facts from the other view point nonetheless. Way to go TT for opening the new VSS forum.

[sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]