Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily.
X
Creating a Build Sandbox used to populate with writable files in past versions of Integrity
Does anyone know when PTC or MKS changed the way a Build Sandbox populates your local drive with "read-only" files instead of "writable" files or whatever you had the file set to when you checked it in? Is there an option to set the "read-only" parameter to whatever the file was initially checked in as? Note: I'm using Integrity 12.2.1 and in the past have used MKS 2005-2009.
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.
First of all is this Laurent? If so hello, from the past.
Your solution is fine as there are many ways to make the build sandbox files writable, but I'm wondering why it changed. When you create a build sandbox of source files, you often want them writable as the compiler generally needs them writable to even generate an executable or object code. Integrity only made regular sandbox files read-only to provide some indication that they weren't checked out and ready for editing. Now it seems they took the same approach with a build sandbox which is not the original intent of a build sandbox.
