Thanks to all who responded.
I was trying to think of a passive way to implement source control until we install a new source change control system.
This was more a mental exercise than anything :-)
From the responses so far and my own playing around there doesn't seem to be an easy way to do something like this as it would need to cover a mix of RDP or SEU style editing.
Actually installing my own incarnation of the SEU command could cover the green screen, but how would you do something similar in RDP without writing a plugin.
I think someone had a similar question a while back because they were trying to deal with rogue developers.
While that's not my intent, passive source backups would be nice.
I had a similar discussion the other day with my documentation team who told me SVN doesn't work for them because they move folders around too often in RoboHelp.
Can't ever win :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 9
date: Fri, 21 Oct 2011 08:43:37 +0200
from: "D*B" <dieter.bender@xxxxxxxxxxxx>
subject: Re:Tracking when source member opened for editing
@good way: use SVN or some other sufficent source controll and versioning system!
@journaling PF: the performance problem is the replace operation used by the editor, not the open/close
@journaling: there is no diffrence between open for edit without save and open for browse
@alternative: audit journal (but doesn't replace svn!!!)
D*B
midrange.com
