[Mono-bugs] [Bug 490302] New: Updating addins with defaultEnabled="false" causes previously enabled addins to become disabled

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=490302


           Summary: Updating addins with defaultEnabled="false" causes
                    previously enabled addins to become disabled
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.0.x
          Platform: x86-64
        OS/Version: Ubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Mono.Addins
        AssignedTo: lluis at novell.com
        ReportedBy: alex.launi at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3)
Gecko/20090305 Firefox/3.1b3

public static void Initialize ()
{
        // Initialize Mono.Addins.
        AddinManager.Initialize (Paths.UserPluginsDirectory);

        // Initialize services before addins that may use them are loaded.
        Services.Initialize ();
        InterfaceManager.Initialize ();

        // Now allow loading of non-services.
        foreach (string path in ExtensionPaths)
                AddinManager.AddExtensionNodeHandler (path, OnPluginChanged);

        AddinManager.Registry.Update (null);

}

When AddinManager.Registry.Update is called, if a plugin with
defaultEnabled="true" is updated to a newer version, the plugin becomes
disabled regardless of its previous state with the older version. The registry
should maintain the state of the plugin, and keep it enabled across updates.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
The addin is disabled

Expected Results:  
the addin remains enabled

I have tested this in our app (GNOME Do), and also in Banshee.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.