|
Doug,
in the registration in position
"HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Installation Manager" you have the key
"location". This is the installation location of the installation manager.
In the installation location of the installation manager you find the
folder
"\eclipse\configuration". In this folder you find the file "config.ini". In
"config.ini" you find the key "cic.appDataLocation", which contains the
path
to the application data of the installation manager.
In the path of the application data of the installation manager you find
the
file "installed.xml". This file contains all the informations you need,
including the installation path and the version of a package.
Hope this helps.
Frank
-----Ursprüngliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] Im Auftrag von Doug Davie
Gesendet: Donnerstag, 29. Januar 2009 14:01
An: WDSC Plugin Developers
Betreff: Re: [Wdsc-Plugin-Dev] determination of RDi installation location
Frank,
I should have clarified...
I need to determine the install location from outside the RDi product.
We use a WISE installation routine to package the product, and the customer
just needs to execute the .exe to install.
With previous WDSc installs we could just read the registration entries to
determine what was installled and where.
On Thu, Jan 29, 2009 at 3:03 AM, Frank Hildebrandt <
frank.hildebrandt@xxxxxxxxxxxxxxx> wrote:
Sorry,--
this is better.
import org.eclipse.core.runtime.FileLocator;
import org.eclipse.core.runtime.Platform;
FileLocator.toFileURL(Platform.getInstallLocation().getURL()).getPath();
Frank
-----Ursprüngliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] Im Auftrag von Doug Davie
Gesendet: Mittwoch, 28. Januar 2009 21:54
An: WDSC Plugin Developers
Betreff: [Wdsc-Plugin-Dev] determination of RDi installation location
In WDSc 6.x, one could determine the installation location by examining
the
registration entries.
But since 7.0, the registration entries are not written.
Is there another way to programmatically determine the installation
location
(and version)?
I want to install a links file into the proper folder structure.
Thanks
-doug
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsc-plugin-dev.
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsc-plugin-dev.
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsc-plugin-dev.
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsc-plugin-dev.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.