Re: Source Control
- From: "Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 6 Sep 2007 11:28:38 -0400
Most of us do not modify the Public folders, so we don't run into that
issue. We don't do that becuase it creates the two problems that you are
discussing, plus the problem of the same CPU but no need for the changes.
As far as version control goes, this has been discussed before. Search for
Version Control in this newsgroup.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"Joe Welfeld" <jwelfeldnospam@xxxxxxxxxxxxx> wrote in message
news:%23EHkcCJ8HHA.3900@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Just looking for options, opinions, suggestions, on how to Source
Control WinCE 5.0 using Source Safe, what do people do ? do you put
the complete WINCE500 directory under source control ? (what about .lib
files and .dll's) how do you handle Microsoft updates, (especially if you
had to modify on of the files yourself, and now MS updates it) or
perhaps you just SourceSafe the files you changed and do a "new
platform" each time you need to re-create your system ?
One thing that has been done here is some of the public files have been
modified and now we need to support a different processor so how do
people handle this issue ? Multiple build machines ?
Looking for some heated discussions here ;)
Thanks,
Joe W.
.
- Follow-Ups:
- Re: Source Control
- From: Steve Maillet \(MVP\)
- Re: Source Control
- References:
- Source Control
- From: Joe Welfeld
- Source Control
- Prev by Date: OALPAtoVA
- Next by Date: Re: How can I send e-mail from my own app?
- Previous by thread: Source Control
- Next by thread: Re: Source Control
- Index(es):
Relevant Pages
|
