René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"assemblymanager.cs: ResolveHandler finds assemblies based on StartsWith","articleBody":"### Environment\r\n\r\n-   Pythonnet version: All\r\n-   Python version: All\r\n-   Operating System: All\r\n\r\n### Details\r\n\r\n-   Describe what you were trying to get done.\r\nLoading an assembly called MyAssembly. Assembly did not exist, should have resulted in an error, but instead it loaded MyAssemblyTest.\r\nThis can be done using Assembly.Load(\"AssemblyName\").\r\n\r\nEffectively this changes the way .NET normally loads assemblies and it ignores things such as strong naming. This could cause all kinds of unexpected effects in larger systems. \r\n\r\n```cs\r\n static Assembly ResolveHandler(Object ob, ResolveEventArgs args){\r\n            string name = args.Name.ToLower();\r\n            for (int i = 0; i \u003c assemblies.Count; i++) {\r\n                Assembly a = (Assembly)assemblies[i];\r\n                string full = a.FullName.ToLower();\r\n                if (full.StartsWith(name)) { // this is a problem!\r\n                    return a;\r\n                }\r\n            }\r\n            return LoadAssemblyPath(args.Name);\r\n        }\r\n```\r\n\r\nThe FindAssembly method has obvious issues as well, but it only searches inside the python path, so the effect there is limited. The ResolveHandler searches through all currently loaded assemblies, which is a bigger problem.","author":{"url":"https://github.com/rmadsen-ks","@type":"Person","name":"rmadsen-ks"},"datePublished":"2017-08-30T12:08:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/533/pythonnet/issues/533"}