Command line option to prevent setting files to a read-only status during a build

[julio]

As I explained on this post (https://helpman.it-authoring.com/viewto ... 34&t=16170), we would like to ask for a way of creating a build without locking all files in a read-only status. We are now using server machines with multiple cores and we would like to take advantage of these cores, thus decreasing the build time.
In TFS, which we use in our company, there is no need to worry about changes in files during a build process, because all files needed for a build are downloaded and used for that build without any changes. I think a new command line option would be enough for this situation.

Thank you.

[Tim Green]

Hi Julio,

Thanks for posting this. I can't make any promises at the moment, but it is definitely on the list for consideration.

[markusflow]

+1. This would be very helpful.

[Tim Green]

Looking at this now, I'm really not so sure what the problem is: There's nothing to stop you from starting multiple instances of Help+Manual to execute multiple builds at the same time. HM only needs to read the project it is publishing, and if it is stored as uncompressed HMXP it is not locked anyway. Where is the issue here?