Copy a file from Installsource to a subdirectory of INSTALLDIR (File NOT in Package!!!)

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Copy a file from Installsource to a subdirectory of INSTALLDIR (File NOT in Package!!!)

Hello,

I intend to copy a file from the Installation Source Directory to a
subdirectory of INSTALLDIR, though this file is NOT included in my ISWI
project. The reason is, that we must create many Master-Copies of one
specific release, which we distribute to our Resellers. Building a different
release for each Master-Copy seems to be awesome. It also may happen that
this file is not available at all.

So how can I tell ISWI to copy my file (from SourcePath) if it's present,
and not to if it's not?

I tried the following successfully: Write an InstallScript!! But my
MSI-Package gets VERY LARGE with two lines of Installscript-Code (I suppose
Runtime-Engine?). Another alternative would surely be to create a custom
Action which calls a script file (VBScript, FSO etc.). Not the best solution
I suppose!?

Does there exist another solution, which I can implement in the ISWI-IDE
(Power Editor, Property Table....)?

Re: Copy a file from Installsource to a subdirectory of INSTALLDIR (File NOT in Package!!!)

Hello Murat,

It sounds like you may want to use the MoveFile table.
Take a look at the msi help files for this table.

Sincerely,

Olga K.
InstallShield Technical Support

"Murat Cakir" <muratc@smartstore.de> wrote in message
news:3949a6ca.0@208.30.171.38...
> Hello,
>
> I intend to copy a file from the Installation Source Directory to a
> subdirectory of INSTALLDIR, though this file is NOT included in my ISWI
> project. The reason is, that we must create many Master-Copies of one
> specific release, which we distribute to our Resellers. Building a
different
> release for each Master-Copy seems to be awesome. It also may happen that
> this file is not available at all.
>
> So how can I tell ISWI to copy my file (from SourcePath) if it's present,
> and not to if it's not?
>
> I tried the following successfully: Write an InstallScript!! But my
> MSI-Package gets VERY LARGE with two lines of Installscript-Code (I
suppose
> Runtime-Engine?). Another alternative would surely be to create a custom
> Action which calls a script file (VBScript, FSO etc.). Not the best
solution
> I suppose!?
>
> Does there exist another solution, which I can implement in the ISWI-IDE
> (Power Editor, Property Table....)?
>
> Any help would be greatly appreciated....
>
>
> Murat Cakir
>
>

re:Copy a file from Installsource to a subdirectory of INSTALLDIR (File NOT in Package!!!)

Thanks Olga,

but how can I access the SourcePath of my Install-Package? What is the
variable: SourceDir, SourcePath, SRCPATH?

Thanks for your response!

"Olga-InstallShield" <supportnews@installshield.com> schrieb im Newsbeitrag
news:394a296e.0@208.30.171.38...
> Hello Murat,
>
> It sounds like you may want to use the MoveFile table.
> Take a look at the msi help files for this table.
>
> Sincerely,
>
> Olga K.
> InstallShield Technical Support
>
> "Murat Cakir" <muratc@smartstore.de> wrote in message
> news:3949a6ca.0@208.30.171.38...
> > Hello,
> >
> > I intend to copy a file from the Installation Source Directory to a
> > subdirectory of INSTALLDIR, though this file is NOT included in my ISWI
> > project. The reason is, that we must create many Master-Copies of one
> > specific release, which we distribute to our Resellers. Building a
> different
> > release for each Master-Copy seems to be awesome. It also may happen
that
> > this file is not available at all.
> >
> > So how can I tell ISWI to copy my file (from SourcePath) if it's
present,
> > and not to if it's not?
> >
> > I tried the following successfully: Write an InstallScript!! But my
> > MSI-Package gets VERY LARGE with two lines of Installscript-Code (I
> suppose
> > Runtime-Engine?). Another alternative would surely be to create a custom
> > Action which calls a script file (VBScript, FSO etc.). Not the best
> solution
> > I suppose!?
> >
> > Does there exist another solution, which I can implement in the ISWI-IDE
> > (Power Editor, Property Table....)?
> >
> > Any help would be greatly appreciated....
> >
> >
> > Murat Cakir
> >
> >
>
>