Custom Query (2734 matches)

Currently the plugin version is linked to the assembly version of the assembly declaring the plugin class.

Assembly build and revision numbers will set to constant zero and AssemblyFileVersion will be used to link the assembly to a subversion revision number. In the same way the plugin version will reference the subversion revision number (via subwcref). Major, minor and build number are set manually. The version appendix should be removed from the plugin name.

The change also has an effect on the specification of plugin dependencies. For the dependency a version has to be declared as well. The plugin infrastructure must check if a plugin with the same major and minor and larger or equal build and revision number is available.

Persistence depends on ZIP compression. If this library is not declared as dependency of Persistence, a different version might be loaded from the GAC and cause problems during serialization. As this is also a dependency of the PluginInfrastructure the file inclusion requirement should probably go here?

Exception message: 'asm.Location' threw an exception of type 'System.NotSupportedException'

    internal static IEnumerable<Type> GetTypes(Type type, IPluginDescription pluginDescription, bool onlyInstantiable) {
      PluginDescription pluginDesc = (PluginDescription)pluginDescription;
      return from asm in AppDomain.CurrentDomain.GetAssemblies()
             where !string.IsNullOrEmpty(asm.Location) // ignore dynamically generated assemblies
             where pluginDesc.AssemblyLocations.Any(location => location.Equals(Path.GetFullPath(asm.Location), StringComparison.CurrentCultureIgnoreCase))
             from t in GetTypes(type, asm, onlyInstantiable)
             select t;
    }