Move PackageManager UI to DynamoPackagesWPF view extension

[Copilot]

DynamoPackageManager UI was incorrectly housed in DynamoCoreWpf instead of its corresponding view extension project, violating the OOTB view extension pattern.

Changes

File Migration

• Moved 50+ files from DynamoCoreWpf to DynamoPackagesWPF:
  • ViewModels: PackageManagerViewModel, PackageViewModel, InstalledPackagesViewModel, etc.
  • Views: PackageManagerView, PublishPackageView, PackageManagerSearchView, etc.
  • Controls: 11 UI controls (SearchBoxControl, FilterTagControl, etc.)
  • Pages: 4 publish wizard pages
  • Resources: Localized documentation, PackageManagerWizard npm bundle

Architecture

Before:

// DynamoView.xaml.cs directly managed PackageManager UI
private PackageManagerView packageManagerWindow;

private void DynamoViewModelRequestShowPackageManager(object s, EventArgs e)
{
    packageManagerWindow = new PackageManagerView(this, _pkgVM);
    packageManagerWindow.Show();
}

After:

// PackageManagerViewExtension.cs handles UI lifecycle
public void Loaded(ViewLoadedParams p)
{
    dynamoViewModel.RequestPackageManagerDialog += OnRequestPackageManagerDialog;
}

private void OnRequestPackageManagerDialog(object sender, EventArgs e)
{
    packageManagerWindow = new PackageManagerView(viewLoadedParams.DynamoWindow, pkgVM);
    packageManagerWindow.Show();
}

Key Decisions

• EventArgs classes (PackageManagerSizeEventArgs, OpenPackageManagerEventArgs) moved to DynamoViewModelEvents.cs - they're part of the event contract, not UI implementation
• PublishPackageViewModel kept in DynamoCoreWpf - used as event parameter, moving it would create circular dependency DynamoCoreWpf → DynamoPackagesWPF → DynamoCoreWpf

Project Files

• Fixed 95 malformed XML elements in DynamoCoreWpf.csproj (orphaned tags, misplaced closing elements)
• Updated DynamoPackagesWPF.csproj with all migrated files and npm build targets

Result

PackageManager UI now follows the same pattern as other OOTB view extensions (DocumentationBrowser, GraphNodeManager, etc.) with proper separation between core framework and extension UI.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[sonarqubecloud]

Quality Gate failed

Failed conditions
5 Security Hotspots
4.4% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE