I am currently attempting to use spkl to work with my PCF controls. I have a solution where I am using a config entity with my PCF control and i would like to be able to quickly Extract the solution and update it. The problem is that when using a PCF build project the *.cdsproj file is locatedat the root of the extracted files. Additionally the Customization.xml file in the Other folder get's overwritten to include the PCF control which causes the pac command to fail.
I would like if there were a way to set these following settings for the Solution Packager on a solution.
/allowWrite:Yes /allowDelete:Yes /clobber
-AllowWrite would be nice to be able to test a solution extract
-AllowDelete would ensure that the .cdsproj does not get deleted when extracting
-Clobber being omitted would allow me to set the Customization.xml file to read-only so that it is not overwritten during extraction.
farisdewantoro
commented
3 years ago
I am currently attempting to use spkl to work with my PCF controls. I have a solution where I am using a config entity with my PCF control and i would like to be able to quickly Extract the solution and update it. The problem is that when using a PCF build project the *.cdsproj file is locatedat the root of the extracted files. Additionally the Customization.xml file in the Other folder get's overwritten to include the PCF control which causes the pac command to fail.
I would like if there were a way to set these following settings for the Solution Packager on a solution.
/allowWrite:Yes /allowDelete:Yes /clobber
-AllowWrite would be nice to be able to test a solution extract -AllowDelete would ensure that the .cdsproj does not get deleted when extracting -Clobber being omitted would allow me to set the Customization.xml file to read-only so that it is not overwritten during extraction.
Thanks,
Rick
SparkleXrm/spkl/SparkleXrm.Tasks/Tasks/SolutionPackagerTask.cs