Bob Arnson wrote:
That looks fine but the sequencing you give in an earlier message means
that any directory chosen by the user will be overwritten by your
DirectorySet custom action. You want to add a condition -- NOT TARGETDIR
-- so it doesn't run if the user has already specified one in the
Mailinglist wrote:
Even if the directory changed by the user is overwritten, why are only the
directorys of that one msm in user given path and all other files and dirs in
the overwritten one. If the custom action overwrites the directory, it should
overwrite it for all msm, shouldn' t it?
Mailinglist wrote:
The directory causing the error is the TARGETDIR. The root path of the
installation and yes, the main component has a CreateFolder tag for it.
Stop, I've just seen that I turned facts. The one MergeModule with the
IisExtension gets its folders createt in the right path,
Mailinglist wrote:
We use a complete custom UI, here is the InstallDirDlg:
That looks fine but the sequencing you give in an earlier message means
that any directory chosen by the user will be overwritten by your
DirectorySet custom action. You want to add a condition -- NOT TARGETDIR
--
Mailinglist wrote:
The directory causing the error is the TARGETDIR. The root path of the
installation and yes, the main component has a CreateFolder tag for it.
Stop, I've just seen that I turned facts. The one MergeModule with the
IisExtension gets its folders createt in the right path,
Hello Bob,
When we come to the InstallDirDlg, the directory is shown correctly, if the
DirectorySet ca is run early enough. If the user now wishes to customize this
path, I get an error 2707, that the path does not exist, when I start up the
BrowseDlg.
Error 2707 includes the directory
Hello Bob,
When we come to the InstallDirDlg, the directory is shown correctly, if the
DirectorySet ca is run early enough. If the user now wishes to customize this
path, I get an error 2707, that the path does not exist, when I start up the
BrowseDlg.
Error 2707 includes the directory
Hello again,
I now have the problem, that in our setup we first search if drive e: is
present and set the TARGETDIR-Property to a folder on e: otherwise c:.
This is done like this:
Property Id='NEWINSTALLDIR' Value='C:\'
DirectorySearch Id='MSEwsDefaultInstallRoot_Search' Path='E:\'
8 matches
Mail list logo
