View Issue Details

IDProjectCategoryView StatusLast Update
0008872MMW v4Install/Configpublic2012-03-23 21:13
Reporterrusty Assigned To 
PriorityurgentSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.0.2 
Target Version4.0.4Fixed in Version4.0.4 
Summary0008872: Install framework: allow multiple branded versions to run simultaneously
DescriptionFor the mambo project (and this can apply to MM in general), it would be desirable for multiple branded versions of MM to be able to run concurrently.

This could work, however there are definitely some issues that would have to be resolved:
1. The apps would share the DB. This itself probably isn't an issue, but there might be a problem in the fact that it would mean sharing of some UI related things (mainly nodes). Most likely not an issue.
2. Sharing of configuration in registry (if not Portable install). We probably could give each brand its own Registry location, in the main application it should be rather easy (probably just one constant in sources), some plug-ins might probably just share configuration to make things easier. TBD.
3. Use separate app ids (internally), so that both apps could be started simultaneously. Note that due to the shared DB the performance possibly wouldn't be optimal, on the other hand I guess that hardly anyone would use both apps really simultaneously, we just shouldn't forbid start up of the second instance.
Tagsx-mambo unplanned
Fixed in build1480

Relationships

related to 0009102 new MMW v4 Can't run to separate Portable Install simultaneously 

Activities

petr

2011-12-16 18:04

developer   ~0029527

Add MicroPlayer to the list of problematic parts of the MM.

petr

2012-01-24 15:49

developer   ~0030044

Items 2 implemented in 1466

peke

2012-01-24 17:01

developer   ~0030045

4. We should test COM server sharing as it could posses issues like with Last.fm I'll open new bug related to Plugin Issues that should be fixed similarly to f_wave and other our plugins.

petr

2012-01-26 09:29

developer   ~0030090

Fixed in 1466

jiri

2012-02-21 14:34

administrator   ~0030490

Clarification: 2&3 is fixed, 1 is _not_ fixed, since it wasn't considered to be an issue.

jiri

2012-02-21 14:48

administrator   ~0030491

Further IM discussions revealed that 1. actually should be fixed because:
 a. MM.ini shouldn't be shared.
 b. MM.DB better wouldn't be shared as well (e.g. because of custom collection icons, etc.)

So we should use different sub-folder in appdata\roaming folder for each MM brand.

petr

2012-02-28 00:40

developer   ~0030587

Fixed in 1480