Improve ALC handling

[gautamdsheth]

Type

• Bug Fix
• New Feature
• Sample

Related Issues?

Fixes NA

What is in this Pull Request ?

1. The resolver only answers PnP's own requests. It's hooked into the whole process, so before this change it gave our bundled DLLs (Microsoft.Extensions.*, MSAL and others) to any module that failed to load an assembly we ship, such as Az or Graph. That mixes PnP's private versions into other modules. Now it only answers for assemblies PnP.PowerShell.dll references directly (s_referencedAssemblyNames) and returns null for everything else, so other modules fall back to their normal loading.
2. The import script doesn't leave variables behind. RegisterPnPAssemblyResolver.ps1 runs in the user's session, so $moduleRoot, $assembly and the others used to stay in the session after Import-Module. Its body now runs in a child scope (& { ... }), so those variables disappear.

[Copilot]

Copilot review overview

🟡 Changes recommended

The process-wide resolver still cannot distinguish PnP requests from identical assembly requests made by other modules.

Review effort: Balanced
Findings: 1

Open (1)

• Restrict MSAL resolution handler to PnP-specific requester context · New

What changed in this PR

This PR attempts to reduce cross-module assembly conflicts and prevent resolver variables leaking into user sessions.

Changes:

• Filters default-context resolution by PnP’s direct assembly references.
• Runs the resolver bootstrap script in a child scope.

File	Description
src/​Commands/​Base/​PnPPowerShellModuleInitializer.cs	Adds the assembly-name resolution filter.
resources/​RegisterPnPAssemblyResolver.ps1	Isolates bootstrap variables in child scope.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

Matching assembly name and version cannot guarantee that a process-wide resolution request originated from PnP.

Review effort: Balanced
Findings: 1

Open (1)

• Assembly resolver does not isolate PnP dependency loads · New

Resolved since last review (1)

• Restrict MSAL resolution handler to PnP-specific requester context