We distribute some commercial products and, customers being what they are, their components aren't always in sync with our distributions. Sometimes this is ok, other times it isn't, so we're thinking about versioning entire vcx's as well as their class components (as per your suggestion #2). Your #3 is more than we need since it'd pick up changes that should fall under our radar, so I'm thinking we should actually include a class, "vcx_version," in each lib.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roche Sent: Tuesday, September 19, 2006 1:07 PM To: [EMAIL PROTECTED] Subject: Re: VCX versioning... How to? On 9/19/06, Lew Schwartz <[EMAIL PROTECTED]> wrote: > At compile time.... I'm thinking include a class named "version" with > a property that'll be updated by a project hook... Other ideas? > 1. Version control software 2. A property named "version" for each class, incremented via projecthook? 3. Export the VCX to text (via SCCText, CursorToXML or Paul's ScX), diff and increment version if changed. I'd have more ideas if I knew what it was you were trying to accomplish. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
