Skip to content

Conversation

@CharliePoole
Copy link
Member

No description provided.

OsirisTerje and others added 30 commits April 3, 2024 12:35
Try to load assembly from trusted list, before to start using some complex logic and enumerate AdditinalFrameworkDirectories
Improve logging for assembly resolving process
(cherry picked from commit f642e99)
Loading of unmanaged assemblies suffers from the same issues as loading managed assemblies in that the wrong deps.json is used by default.  This updates the TestAssemblyLoadContext to use the exact same pattern for loading unmanaged assemblies as managed assemblies.
1. Use the default assembly loading logic (I'm unsure if we actually need this since, in both managed and unmanaged, the base AssemblyLoadContext logic is a no-op and it's actually the VM that has some logic for loading assemblies).
2. Use an AssemblyDependencyResolver for the test assembly.
3. Check in the same folder as the test assembly (in case the dependencies are not fully specified in deps.json).

Resolves #1253
…hich were added/merged after this PR was created.
Adding yml file for CI build
Integrate TestAssemblyLoadContext changes to version315
CharliePoole and others added 29 commits October 16, 2025 21:18
Fix crashing bug when trying to run an unmanaged test assembly.
Add unit tests of netcore3.1 driver
There is an indirect reference through Castle.Core to a non-existing version of System.ComponentModel.TypeConverter
If I add System.ComponentModel.TypeConverter locally, the compiler complains that it isn't used ...
Enhanced assembly resolution for windows and aspnetcore
Ignore .addins files in XML format
Handle prerelease dotnet runtimes correctly
Eliminate use of our custom AssemblyLoadContext
Fix problems in assembly loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.