This occurrence is minimized by decomposing each individually editable component or subcomponent into a distinct file. When there are multiple developers working on the same solution component a conflict might arise where changes from two developers result in changes to a single file. Use of the /allowWrite parameter with verbose logging is effective.Īfter the extract operation is completed with the minimal set of files checked out from source control, a developer may submit the changed files back into source control, as is done with any other type of source file. The /allowWrite parameter can be used to assess what impact an extract operation has without actually causing any files to be written or deleted. The /clobber parameter can be used to override and cause read-only files to be written or deleted. This enables the user to check out, from source control, the minimal set of files that are changing. In addition, the tool honors the read-only attribute on component files producing a warning in the console window that particular files were not written.
When the SolutionPackager tool extracts the component files it will not overwrite existing component files of the same name if the file contents are identical.
Except for the sections described in When to edit the customizations file, manual editing of extracted component files and.