PrismLibrary / PrismLibrary/Prism
DirectoryModuleCatalog contains a large number of outdated APIs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.8k
- Forks
- 1.6k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
Summary
assembly.ReflectionOnlyLoadFrom(dependentAssemblyFilename);
API Changes
assembly.load(dependentAssemblyFilename);
The recommended method for loading DLLs in. net core is AssemblyContextLoad. Would you like to consider changing AppDomain to AssemblyContextLoad in the future?
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 with src/Wpf/Prism.Wpf/Modularity/DirectoryModuleCatalog.netcore.cs at the referenced line and review how dependent assemblies are loaded. Compare the current ReflectionOnlyLoadFrom/AppDomain-related APIs with the issue's proposed AssemblyContextLoad approach, then verify the catalog's assembly-loading behavior with the relevant existing tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100