Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "FAQ When do I need to write a plug-in install handler?"
m |
|||
| Line 1: | Line 1: | ||
| − | Writing a plug-in install handler is appropriate for most professional applications. | + | Writing a plug-in install handler is appropriate for most professional applications. Doing so is not only a comfort that most end users will expect but also allows you to perform custom installation, such as |
| − | Doing so is not only a comfort that most end users will expect but also allows | + | |
| − | you to perform custom installation, such as | + | |
| − | * Moving data to other locations in the file system outside the install | + | * Moving data to other locations in the file system outside the install directory. This allows data to be shared by multiple applications or by multiple versions of your application. |
| − | directory. This allows data to be shared by multiple applications or by multiple | + | * Reading or saving values in the Windows registry. |
| − | versions of your application. | + | * Asking the user to confirm licensing terms. |
| − | * Reading or saving values in the Windows registry. | + | * Searching for installed components, such as ActiveX or database drivers, that your application requires and installing them, if necessary. |
| − | * Asking the user to confirm licensing terms. | + | |
| − | * Searching for installed components, such as ActiveX or database drivers, | + | |
| − | that your application requires and | + | |
| − | installing them, if necessary. | + | |
| − | When creating a feature using the PDE wizard, you get the option to specify | + | When creating a feature using the PDE wizard, you get the option to specify an optional feature-specific install handler. |
| − | an optional feature-specific install handler. | + | |
== See Also: == | == See Also: == | ||
| + | *[[FAQ Can I use an installation program to distribute my Eclipse product?]] | ||
| − | + | {{Template:FAQ_Tagline}} | |
| − | + | ||
| − | + | ||
Latest revision as of 22:52, 1 June 2006
Writing a plug-in install handler is appropriate for most professional applications. Doing so is not only a comfort that most end users will expect but also allows you to perform custom installation, such as
- Moving data to other locations in the file system outside the install directory. This allows data to be shared by multiple applications or by multiple versions of your application.
- Reading or saving values in the Windows registry.
- Asking the user to confirm licensing terms.
- Searching for installed components, such as ActiveX or database drivers, that your application requires and installing them, if necessary.
When creating a feature using the PDE wizard, you get the option to specify an optional feature-specific install handler.
See Also:
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.