>>IMO, I wouldn't like this. It requires that you keep track of where the latest changes are. In my case, I work with a team of developers spread across the country and it would lead to more source control problems than we already have.
>
>Fogging.
>
>How is this different from managing code on any other platform ?
>
>Why does changing the "form" of the code representantion (ie. VCX/SCX) affect "source control".
Is the latest version in the VCX or the text file? What happens if I check in the text file instead of the VCX? What happens if one developer makes changes in the text file and forgets to put the changes in place, then another makes changes to the VCX or even a different text file of the same class library?
>
>In fact, VCX/SCXs (usually) require a "text convert" step in order to be properly managed by most "source control systems" (ie. SCCTEXT.PRG).
But that happens automatically.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer