Is anyone using Team Foundation Server for source control of Visual FoxPro
projects? Any pros and cons on using it?
If not, what is an alternative with pros and cons?
Thanks
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/02dd01ce009d$ffc1a7b0$ff44f710$@com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2/1/2013 12:03 PM, Alan Lukachko wrote:
> Is anyone using Team Foundation Server for source control of Visual FoxPro
> projects? Any pros and cons on using it?
>
> If not, what is an alternative with pros and cons?
>
> Thanks
I'm using it here with my projects at the day gig. You can't see
history changes with SCX/VCX files, but of course it does the PRGs just
fine. Christof posted some comments on it. Check the archives.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510BF7CA.80103@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2/1/13 9:13 AM, MB Software Solutions, LLC wrote:
> On 2/1/2013 12:03 PM, Alan Lukachko wrote:
>> Is anyone using Team Foundation Server for source control of Visual FoxPro
>> projects? Any pros and cons on using it?
>>
>> If not, what is an alternative with pros and cons?
>>
>> Thanks
>
> I'm using it here with my projects at the day gig. You can't see history changes
> with SCX/VCX files, but of course it does the PRGs just fine. Christof posted some
> comments on it. Check the archives.
You'll be just fine as long as you remember to always put a cover page on your TFS
Report.
Paul
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510BF8FB.3090402@ulmcnett.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2/1/2013 12:18 PM, Paul McNett wrote:
> You'll be just fine as long as you remember to always put a cover page on your TFS
> Report.
LOL! Um, yeah....did you get the memo????
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510BF99C.7030201@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Fri, Feb 1, 2013 at 12:03 PM, Alan Lukachko <
al@software-strategies-na.com> wrote:
> Is anyone using Team Foundation Server for source control of Visual FoxPro
> projects? Any pros and cons on using it?
>
> If not, what is an alternative with pros and cons?
>
>
Rick Borup is a fan of Mercurial. He's done some presentations on it. You
ought to be able to find them on the Internets.
Any distributed version control system (DVCS) like Mercurial, bazaar or git
is superior to a client-server model like TFS, CVS or SourceSafe.
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4tgrhr=ydpZmuTQ8BgxVEw3a94VZFpoaZN22Jn_AtUVkw@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2/1/2013 2:32 PM, Ted Roche wrote:
> On Fri, Feb 1, 2013 at 12:03 PM, Alan Lukachko <
> al@software-strategies-na.com> wrote:
>
>> Is anyone using Team Foundation Server for source control of Visual FoxPro
>> projects? Any pros and cons on using it?
>>
>> If not, what is an alternative with pros and cons?
>>
>>
> Rick Borup is a fan of Mercurial. He's done some presentations on it. You
> ought to be able to find them on the Internets.
>
> Any distributed version control system (DVCS) like Mercurial, bazaar or git
> is superior to a client-server model like TFS, CVS or SourceSafe.
>
I'm betting the logic/code required/written for such systems is very
complex. Makes my head hurt just thinking of how to handle all the
merging! Flat-out replacements are easy, but those merges, ...<shudder>
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510C1D0D.3030700@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
> On 2/1/2013 2:32 PM, Ted Roche wrote:
>> Rick Borup is a fan of Mercurial. He's done some presentations on it. You
>> ought to be able to find them on the Internets.
>>
>> Any distributed version control system (DVCS) like Mercurial, bazaar
>> or git
>> is superior to a client-server model like TFS, CVS or SourceSafe.
>>
>
On 02/01/13 11:52 AM, MB Software Solutions, LLC wrote:>
> I'm betting the logic/code required/written for such systems is very
> complex. Makes my head hurt just thinking of how to handle all the
> merging! Flat-out replacements are easy, but those merges, ...<shudder>
>
Actually, it's not. Look up some of the Mercurial tutorials to see
exactly how they handle splits and merges. Ted is right.
I've never run Visual SourceSafe (thank god!) nor svn, but I did fire up
Mercurial with the Tortoise UI, and found it quite easy to get running.
(My understanding is that Mozilla uses Mercurial while the Linux folks
use Git.)
IMO, the great advantage of a distributed system like Mercurial or Git
is that you DON'T HAVE ANY 'Team Foundation Server' to administer!
Dan Covill
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510C5C7D.4060005@san.rr.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2/1/13 4:23 PM, Dan Covill wrote:
>> On 2/1/2013 2:32 PM, Ted Roche wrote:
>>> Rick Borup is a fan of Mercurial. He's done some presentations on it. You
>>> ought to be able to find them on the Internets.
>>>
>>> Any distributed version control system (DVCS) like Mercurial, bazaar
>>> or git
>>> is superior to a client-server model like TFS, CVS or SourceSafe.
>>>
>>
> On 02/01/13 11:52 AM, MB Software Solutions, LLC wrote:>
>> I'm betting the logic/code required/written for such systems is very
>> complex. Makes my head hurt just thinking of how to handle all the
>> merging! Flat-out replacements are easy, but those merges, ...<shudder>
>>
> Actually, it's not. Look up some of the Mercurial tutorials to see exactly how they
> handle splits and merges. Ted is right.
>
> I've never run Visual SourceSafe (thank god!) nor svn, but I did fire up Mercurial
> with the Tortoise UI, and found it quite easy to get running. (My understanding is
> that Mozilla uses Mercurial while the Linux folks use Git.)
>
> IMO, the great advantage of a distributed system like Mercurial or Git is that you
> DON'T HAVE ANY 'Team Foundation Server' to administer!
I've been meaning to try Mercurial for years, especially since it is Python-based. I
hear that it is super-easy. Having said that, I'm loving Git. Being able to do
everything locally is amazingly cool and blazing fast.
Paul
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/510C62A8.20201@ulmcnett.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Fri, Feb 1, 2013 at 6:23 PM, Dan Covill <dcovill@san.rr.com> wrote:
>
>> IMO, the great advantage of a distributed system like Mercurial or Git is
> that you DON'T HAVE ANY 'Team Foundation Server' to administer!
>
----------------
What are you talking about? Sorry but you have no idea what you are
talking about I think.
TFS = a Sharepoint Skin. Nothing more.
Source code is only a tiny part of this massive tool.
I manage a sharepoint system for about 40 sites within. No we do not have
TFS in this mix as of yet, but in our upgrade we well in a few weeks or
months.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAJidMYKD17U1atqPpmgFUumvfA31M7J7xH9seqj9MSrDrNRPDA@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
> Is anyone using Team Foundation Server for source control of Visual FoxPro
> projects? Any pros and cons on using it?
>
If you view TFS merely as a source control tool, it's not the best choice
for you. At the last FoxPro conference I met a team leader who finds TFS to
be a fantastic tool: They have three TFS admins, eight people doing the
merging and three dozen developers (.NET and VFP). For them TFS is the
right tool.
TFS is designed to get into the way of the individual developer. It's
designed to have separate roles for administration and developers. It's
designed to be used in a certain process. Source control is really just one
aspect of TFS. If that's not what you want, you'll spend the time fighting
TFS.
If you want source control that is similar to TFS (check out, work, check
in) get SourceGear Vault. It's stable, it's mature and it works very well.
It's a centralized system, quick to setup and administer and in general
very easy to learn for developers who haven't work with source code control.
If you are willing to learn the distributed way, there are more and cheaper
options. I use Git, many here use Mercurial. And more options become
available every day. However, you need to be aware that distributed source
control is a bit more complex to use than traditional server based
products. There are also more options, like branching that I'm using
extensively now, that require time to master them.
Distributed systems just like the CVS/SVN based predecessors only work well
with text documents which adds one more level of complexity for VFP
developers due to VCX/SCX conversion.
--
Christof
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAL4QJhgZbKxVVyrB3DGti2VvDtTQvwWd2jvjV0TQ7H=7bpJq4w@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.