microsoft / microsoft/powerplatform-vscode

[Bug]: pac solution sync does not support nuget assembly plugins

Open
#1,587 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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
  1. Create a solution using pac solution init
  2. Import the solution into an environment.
  3. Create a plugin using pac plugin init
  4. Write some simple logic in the plugin and build it.
  5. Register the plugin using PRT or XrmTools.
  6. Add the plugin project as a reference to the solution
  7. Sync the solution using pac solution sync.
  8. Build the .cdsproj and 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.