microsoft / microsoft/powerplatform-vscode
[Bug]: pac solution sync does not support nuget assembly plugins
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 60
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 14
Description
Is this bug related to Code Apps?
No
Description
When I create a new .cdsproj and add a plugin project to it and register it, synchronizing the solution does not bring the plugin assembly nor the package to the local file system.
Extension Version
2.0.143
VS Code Version
1.119.0
VS Code Channel
Stable
Steps to Reproduce
- Create a solution using
pac solution init - Import the solution into an environment.
- Create a plugin using
pac plugin init - Write some simple logic in the plugin and build it.
- Register the plugin using PRT or XrmTools.
- Add the plugin project as a reference to the solution
- Sync the solution using
pac solution sync. - Build the
.cdsprojand it will fail saying that the plugin assembly registration configuration is missing.
If you check the local files you will notice that both the plugin assembly and the plugin package are both missing from the local files and just the SdkMessageStep is synchronized.
Expected Behavior
No response
Actual Behavior
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the implementation behind pac solution sync and reproduce the listed .cdsproj workflow with a registered plugin project. Verify which synchronized files are produced for the plugin assembly and package, then confirm the .cdsproj builds successfully and includes the required plugin registration configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100