Thank you Oleg for the quick answer and the workaround.
The real case from which the example was stripped, is an AutoCAD plugin which I'm developing which must be installed under the "Program Files/AutoDesk/ApplicationPlugins/" so that Autocad will find it and load it. The plugin is communicating with our own product which is installed under another program files subdirectory.
Initially I had made two separate installers, one for the plugin and one for our own product. But our PO wanted a single installer to run to make it easy for the user, which is quite understandable. So I combined the two installers into one, but apparently this is a bad approach as there is no common installdir folder.
What would be a good way of handling the above scenario? Should I use a bootstrapper that runs two separate msi:s?
The real case from which the example was stripped, is an AutoCAD plugin which I'm developing which must be installed under the "Program Files/AutoDesk/ApplicationPlugins/" so that Autocad will find it and load it. The plugin is communicating with our own product which is installed under another program files subdirectory.
Initially I had made two separate installers, one for the plugin and one for our own product. But our PO wanted a single installer to run to make it easy for the user, which is quite understandable. So I combined the two installers into one, but apparently this is a bad approach as there is no common installdir folder.
What would be a good way of handling the above scenario? Should I use a bootstrapper that runs two separate msi:s?