View Single Post
  #2  
Old 12-16-2003, 03:05 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
That behavior is by design. If the action modifies a file, it leaves it writeable so that it's clear that it has been modified. Typically, you would want to commit the version change to a source control system as part of the automated build, which would also usually set the file back to read-only when checked in / committed.

You can set the file(s) back to read-only manually if necessary via a Run Program step like (this can be copied/pasted into VBP):

<step action='Run Program' type='0'>
<command>%DOSCMD% attrib +r *.rc /s</command>
<description>Recursively sets all .rc files to read-only in the current .bld project dir</description>
<indent type='3'>1</indent>
<name>reset read-only</name>
<outputfrom type='3'>1</outputfrom>
<startin>%PROJDIR%</startin>
</step>
Reply With Quote