<dbu1997@gmail.com> wrote in message
news:1179328238.476784.85720@n59g2000hsh.googlegroups.com...
>I am new to creating Setup projects in VStudio. I am using 2005. My
> experience is with C++.
>
> My problem is that I am using a custom build steps to call an
> executable that
>
> (1) Writes an encrypted string to a registry value,
> (2) Edits an installed *.ini file.
>
> The custom build step calls my executable from the application folder.
> What I don't like is that the exe's are left in the target directory
> when the install is finished.
>
> Is there a way to remove the exe after installation, or is they a more
> elegant solution? I am sure this is easy, but I am a stuck. Is is
> possible to have a custom build step do system calls?
>

On May 17, 10:58 am, "Phil Wilson" <pdjwil...@nospam.cox.net> wrote:
> In the solution explorer view where it shows your executable, see if you can
> set the Exclude property to True (F4 for preoperties works for me). Some
> executables and Dlls can be excluded, meaning they're not installed but
> instead stored in the Binary table of the MSI file and streamed out into a
> temp folder to run (which means your working directory won't be your app
> folder).
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]<dbu1...@gmail.com> wrote in message
>
> news:1179328238.476784.85720@n59g2000hsh.googlegroups.com...
>
> >I am new to creating Setup projects in VStudio. I am using 2005. My
> > experience is with C++.
>
> > My problem is that I am using a custom build steps to call an
> > executable that
>
> > (1) Writes an encrypted string to a registry value,
> > (2) Edits an installed *.ini file.
>
> > The custom build step calls my executable from the application folder.
> > What I don't like is that the exe's are left in the target directory
> > when the install is finished.
>
> > Is there a way to remove the exe after installation, or is they a more
> > elegant solution? I am sure this is easy, but I am a stuck. Is is
> > possible to have a custom build step do system calls?

<dbu1997@gmail.com> wrote in message
news:1179426075.741728.217200@l77g2000hsb.googlegroups.com...
> On May 17, 10:58 am, "Phil Wilson" <pdjwil...@nospam.cox.net> wrote:
>> In the solution explorer view where it shows your executable, see if you
>> can
>> set the Exclude property to True (F4 for preoperties works for me). Some
>> executables and Dlls can be excluded, meaning they're not installed but
>> instead stored in the Binary table of the MSI file and streamed out into
>> a
>> temp folder to run (which means your working directory won't be your app
>> folder).
>> --
>> Phil Wilson
>> [Microsoft MVP-Windows Installer]<dbu1...@gmail.com> wrote in message
>>
>> news:1179328238.476784.85720@n59g2000hsh.googlegroups.com...
>>
>> >I am new to creating Setup projects in VStudio. I am using 2005. My
>> > experience is with C++.
>>
>> > My problem is that I am using a custom build steps to call an
>> > executable that
>>
>> > (1) Writes an encrypted string to a registry value,
>> > (2) Edits an installed *.ini file.
>>
>> > The custom build step calls my executable from the application folder.
>> > What I don't like is that the exe's are left in the target directory
>> > when the install is finished.
>>
>> > Is there a way to remove the exe after installation, or is they a more
>> > elegant solution? I am sure this is easy, but I am a stuck. Is is
>> > possible to have a custom build step do system calls?
>
> This worked fine - I wrongly assumed that excluding the exe would
> prevent the custom action from working - I guess people smarter than I
> thought about this already.
>