NeoOffice2.1 preferences during installation NeoOffice2.2.1

[chello]

Hi,

I work for Druide Informatique. We distribute the French spelling and
grammar checker "Antidote RX". We plan to integrate Antidote RX into NeoOffice 2.2.1 that we obtained under the Programme NeoOffice Early Access.

I developed a custom UNO Package Bundle. This bundle implements a UNO Component. The interaction between Antidote and Neoffice (2.1 and 2.2.1) is completed.

However, I found a problem with the following sequence:

1) Install NeoOffice 2.1 using the Wizzard.
2) Install my custom UNO Package Bundle in Neofffce 2.1. Tthis step install the package in the preference of NeoOffice 2.1.
3) Remove the application bundle of NeoOffice 2.1. This step does not remove the preference folder of NeoOffice 2.1.
4) Install NeoOffice 2.2.1 using the Wizzard. During this installation, a copy of the preferences of NeoOffice 2.1 are made into the preference of NeoOffice 2.2.1), so my conponent is copied into NeoOffice 2.2.1 preferences.

However, after this sequence, the installation of my custom UNO Package Bundle is incorrect : of all the files and folders inside my package bundle, only the empty folder «scripts» in copied. So, when launched, NeoOffice 2.2.1 displays errors messages about missing files. To correct the situation, I have to reinstall the costum UNO Package Bundle in NeoOffice 2.2.1.

Is it possible to tell NeoOffice installer not to copy my bundle from 2.1 to 2.2.1, or to tell to copy the bundle completely?

Best Regards,

Pierre

[Samwise]

FYI, I have removed the topic you posted in NeoOffice Testing, since it was identical. We have few regulars, and they visit both places, so there is really no need to post in the two sections (i.e. it won't improve your chances of getting an answer).

[pluby]

I think the answer is no. I will explain why.

We use the standard, unmodified OOo code to import Neo 2.1 preferences to Neo 2.2.1 preferences. In general, the OOo code will import as many preferences (including UNO components) as it possibly can and, in some cases, the OOo code does not do this completely as is probably the cause of your problem.

In your post, you are assuming that our installer does the copying of Neo 2.1 preferences to Neo 2.2.1 but that assumption is incorrect. Instead, NeoOffice's underlying OOo code does the copying the when you first run NeoOffice 2.2.1. The underlying OOo code detects that no Neo 2.2.1 preferences directory exists so it does the copying of preferences.

Patrick