Bug 28876 - Satellite assembly finder fails for memory-loaded assemblies with GetDirectoryName(): Invalid path
Summary: Satellite assembly finder fails for memory-loaded assemblies with GetDirector...
Alias: None
Product: Runtime
Classification: Mono
Component: Reflection ()
Version: unspecified
Hardware: PC Linux
: High major
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2015-04-08 00:19 UTC by Gabriel Garcia
Modified: 2015-04-15 04:51 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Test case from the previous github url, so we can keep the test case here (16.38 KB, application/octet-stream)
2015-04-10 22:08 UTC, Miguel de Icaza [MSFT]

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Gabriel Garcia 2015-04-08 00:19:25 UTC
Assembly.get_location() returns an empty string for assemblies loaded from memory.

Assembly.InternalGetSatelliteAssembly uses that location string directly in a call to Path.GetDirectoryName, which then fails with: System.ArgumentException: Invalid path

This is unexpected behavior.

** Test case **

Comment 1 Miguel de Icaza [MSFT] 2015-04-10 22:08:38 UTC
Created attachment 10722 [details]
Test case from the previous github url, so we can keep the test case here
Comment 2 Miguel de Icaza [MSFT] 2015-04-10 22:13:25 UTC
At least my Mono version d86446f from April 2nd has this problem.

It is more likely caused by a recent change in resource lookup:


From March 23rd
Comment 3 Gabriel Garcia 2015-04-11 07:52:59 UTC
I sent a PR that fixes this bug (I forgot to link it here): https://github.com/mono/mono/pull/1693

As stated in the PR description, I'm not sure if this is a sensible solution to the problem. I.e. if it follows reference .NET behavior.
Comment 4 Marek Safar 2015-04-15 04:51:17 UTC
Fixed in master