Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2017-03-28 | return TPA assembly if loadfrom is passed a path to assembly with same identity | Rahul Kumar | 1 | -2/+2 | |
2017-02-12 | Remove always defined FEATURE_HOST_ASSEMBLY_RESOLVER | danmosemsft | 1 | -4/+4 | |
2016-05-20 | Enable overriding of TPA assemblies | Gaurav Khanna | 1 | -1/+2 | |
2016-05-17 | Revert "Enable overriding assemblies from TPA" | Gaurav Khanna | 1 | -2/+1 | |
2016-05-15 | Enable overriding assemblies from TPA | Gaurav Khanna | 1 | -1/+2 | |
2016-03-09 | Delete dead code | Jan Kotas | 1 | -4/+4 | |
- Delete BINDER, STANDALONE_BINDER and MDIL ifdefs | |||||
2016-01-27 | Update license headers | dotnet-bot | 1 | -4/+3 | |
2016-01-21 | Add support for AssemblyResolution when an assembly is not found in a given ↵ | Gaurav Khanna (CLR) | 1 | -1/+35 | |
Load Context. 1) Expose AssemblyResolve event off AssemblyLoadContext 2) Invoke the event if the abstract Load implementation does not return an assembly. | |||||
2016-01-12 | Fix arm specific build break pertaining to AssemblyLoadContext changes. | Gaurav Khanna | 1 | -2/+2 | |
[tfs-changeset: 1564035] | |||||
2016-01-12 | Add support Load assemblies from explicit path/streams into default load context | Gaurav Khanna (CLR) | 1 | -0/+74 | |
2015-11-11 | Fix a couple of issues involving assembly loading | Koundinya Veluri | 1 | -2/+5 | |
Fixes #1740 - After an assembly is loaded through a custom load context, when its dependencies are being loaded and the dependencies are in an app folder but not on the TPA list, don't search app paths when using the TPA binder, and instead use the default binder for the dependent assembly to load dependencies through the same custom AssemblyLoadContext. Fixes #1187 - In the AssemblyName created by AssemblyLoadContext.GetAssemblyName(), don't initialize the CodeBase property since it's not in the exposed surface area for .NET Core. If the AssemblyName is passed to Assembly.Load(), note that regardless of the path sent to GetAssemblyName(), default search orders are still used to load the assembly by name. A custom AssemblyLoadContext would need to be used to control where an assembly is loaded from. - Fixed a couple of error messages that mentioned phone | |||||
2015-01-30 | Initial commit to populate CoreCLR repo | dotnet-bot | 1 | -0/+198 | |
[tfs-changeset: 1407945] |