If a plugin added to a mpei package was created by another version of the .net framework than 3.5 (version 4 for example), MpeMaker will not add any plugin dependency for the assembly when saving the project. No error message is presented to the user.
If this "corrupted" package is then tried to be installed with MpeInstaller, it will at first show up as compatible but later fail due to the missing dependencies.

h4. Steps to Reproduce
1. Have a .dll plugin made with .NET Framework version 4 with a target in the %Plugins% folder in a Mpemaker project.
2. Save project.
3. Dependencies for the plugin will be missing in the xmp2 file.

h4. Additional Information
This issue is due to the incorrect handling of the BadImageFormatException exception when loading the assembly to determine if it's a valid MP plugin. Currently, if this exception is encountered, MpeMaker will stop trying to determine validity. Instead, it should continue on, having the same behavior that MP config does when loading plugins.

Furthermore, no attempts to catch other types of exception are currently done, and user is never notified if plugin determination fails. This will also be remedied as part of this issue.