Emmanuel Bellas
Emmanuel Bellas
Calling `pac solution pack` (version: 1.19.4+gfbe2fd6) with mapping file does not map pluginpackages. To reproduce: 1. `pack plugin init` a new plugin and build it 2. open plugin registration tool...
E.g. running `pac solution version -s Solution' changes the solution.xml in the following way:  (whereas `pac solution sync` preserves xml formatting). Bug: `pac solution version` should not change formatting...
To reproduce (following the steps here https://learn.microsoft.com/en-us/power-apps/developer/component-framework/import-custom-controls#create-a-plug-in-project-and-add-a-reference-to-it-in-your-solution): \> `pac solution init -pn xxx -pp xxx ` \> `pac plugin init -o Plugin` \> `pac solution add-reference -p Plugin` \> `msbuild`...
**Describe the bug** (note, this issue is also described here: https://github.com/microsoft/powerplatform-build-tools/discussions/971) Whe trying to upload a Power Pages site (modelVersion 2), we get the following error (as shown in pac-log.txt)...
**Describe the bug** When a Power Pages site has a cloud flow integration (https://learn.microsoft.com/en-us/power-pages/configure/cloud-flow-integration), the downloaded yaml does not correctly include the web roles that were assigned to this cloud...