PowerShell / PowerShell/PowerShell
Global Assembly Minimum Version
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 55.5k
- Forks
- 8.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 88
Description
Summary of the new feature / enhancement
I want to load a newer version of an assembly that is not vulnerable.
Set-AssemblyVersion -LiteralPath '.../System.Text.Json.dll' -Version '9.0.1' -Scope System
Proposed technical implementation details (optional)
To modify the loading behavior: a config defines the version and a ResolveAssembly EventHandler will handle this.
This might also allow to define 3 configs: System, User, Process.
This could be a module that is loaded after the start, but this means powershell own dependencies can only be updated by installing a patched version.
The alternative might be to modifiy the .deps.json (or .config config / runtime / assemblyBinding), but it seams this is out of my league.
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
The issue names no repository files or tests. Start by researching PowerShell's assembly-loading path and the ResolveAssembly EventHandler, then compare the proposed .deps.json, config/runtime/assemblyBinding, and module approaches. Done means defining the configuration scopes and making Set-AssemblyVersion load the requested assembly version safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100