Sweden
In the MediaPortal.Configuration.Startup class you are registering for the AppDomain.CurrentDomain.AssemblyResolve event, and when that event is received, you instruct the user about the situation and terminate the application.
I think this behavior is incorrect.
This event tells anyone listening that the application failed to load a specific assembly. It however also lets the listeners to give a go at trying to resolve the assembly. I as a plugin developer wanted to use this event to load some plugin references saved as embedded resources instead of having the files on disk. But since Configuration is the first one to register for the event, and thus also be the first one receiving the event, it will make the assumption that the reference cannot be resolved before all listeners have had a go at resolving it. Because of this, I think the behavior is a bug.
I think this behavior is incorrect.
This event tells anyone listening that the application failed to load a specific assembly. It however also lets the listeners to give a go at trying to resolve the assembly. I as a plugin developer wanted to use this event to load some plugin references saved as embedded resources instead of having the files on disk. But since Configuration is the first one to register for the event, and thus also be the first one receiving the event, it will make the assumption that the reference cannot be resolved before all listeners have had a go at resolving it. Because of this, I think the behavior is a bug.