project versioning workflow

[=?Utf-8?B?cm9kY2hhcg==?=]

hey all,
i posted this in source safe newsgroup but didn't get a reply so i might try
here if it's ok. i apologize if this is considered duplicate.

here's my original post:

http://msdn.microsoft.com/newsgroups...b-24a2d1b88968

please let me know for next time if this was a duplicate effort?

thanks,
rodchar

[=?Utf-8?B?YnJ1Y2UgYmFya2Vy?=]

you should just create a dummy project and try stuff.

checkin with and without comments
do some labels
do more checks
play with pinning.
try a branch.
try a merge to branced code
view history after each of this steps.
try using compare.

after you understand vss, then you can desgin your application structure.
how are you handling mainline, releases, and patches to releases.
-- bruce (sqlwork.com)
"rodchar" wrote:

hey all,
i posted this in source safe newsgroup but didn't get a reply so i might try
here if it's ok. i apologize if this is considered duplicate.

here's my original post:

http://msdn.microsoft.com/newsgroups...b-24a2d1b88968

please let me know for next time if this was a duplicate effort?

thanks,
rodchar

[=?Utf-8?B?cm9kY2hhcg==?=]

how are you handling mainline, releases, and patches to releases.
i've never been introduced to a formal way of doing this.

"bruce barker" wrote:

you should just create a dummy project and try stuff.

checkin with and without comments
do some labels
do more checks
play with pinning.
try a branch.
try a merge to branced code
view history after each of this steps.
try using compare.

after you understand vss, then you can desgin your application structure.
how are you handling mainline, releases, and patches to releases.
-- bruce (sqlwork.com)
"rodchar" wrote:

hey all,
i posted this in source safe newsgroup but didn't get a reply so i might try
here if it's ok. i apologize if this is considered duplicate.

here's my original post:

http://msdn.microsoft.com/newsgroups...b-24a2d1b88968

please let me know for next time if this was a duplicate effort?

thanks,
rodchar