Update

[vaibhavopkey]

How can I achieve this? Suppose a user installs my software, which includes plugins:
Both in single folder name plugins.
1) Default Plugins
2) User-Installed Plugins.

When the user updates the app using the installer first it uninstall the app, all plugins are removed.
I want to ensure that user-installed plugins are not removed during the update — only the default ones should be replaced.
This way, when the user updates the app again, their previously installed plugins remain intact.

Is my approach standard? First, I copy all the existing plugins to a different location. After the user updates the app, I copy them back to the default location.
However, there's one issue: how can I identify and copy only the user-installed plugins to that separate location?
Is there any feature available ,so i give name and it copy only that plugin.

[JohnGaver]

This topic applies to InstallAware Multi Platform as well.

Unless you're forcibly deleting all files in your plug-in folder, your setup wouldn't remove files it hasn't installed itself when you call Apply Uninstall - either for your own setup's installation log (just like uninstalling it), or for the installation log of a different version (just like removing your own old version before installing an updated version).

By assigning the $NATIVE_LOGGING$ variable to the $NATIVE_OLDLOG$ variable, default template and wizard generated setup scripts facilitate the removal of an older (or newer, as the case may be) product version; as identified by a Product Code GUID that matches the existing setup you are running.

[vaibhavopkey]

I am using an Application Bundle for Mac. As we know, a Mac application bundle contains all files within it.
I'm installing the application bundle directly. So, when I uninstall it, the entire bundle—including the plugins—gets deleted.
In this scenario, Native_log may not work.
Is it a good practice to copy all plugins to another location before uninstallation and then restore them after installation, or is there a better approach?

For reference, if you're not familiar with an application bundle:
An application bundle on macOS is a special type of directory that appears as a single file in Finder but actually contains all the files and resources needed for an app to run. It follows a specific structure and uses the .app extension.

[JohnGaver]

Unfortunately, your latest post doesn't relate to any of the points I've made at all.

As far as the installation is concerned, there's absolutely nothing special about an application bundle whatsoever.

Indeed, the macOS installer built by InstallAware Multi Platform itself is an application bundle.