THX for the quick help.
I hopefully solved my problem.
Now i use one main msi, as some kind of chainer. (no nested msi ;))
I think that will work, and i have enough control over my un-/
installsequence.
Bob Arnson-6 wrote:
>
> volkmar wrote:
>> My problem is not the call of CA.
>> It is more
volkmar wrote:
> My problem is not the call of CA.
> It is more the problem of sequenced uninstall.
>
> The solution i am thinking about is:
> 1. uninstall component A
> 2. do CA
> 3. remove all
>
MSI lets you schedule actions relative to one another, so you can call a
custom action after the
My problem is not the call of CA.
It is more the problem of sequenced uninstall.
The solution i am thinking about is:
1. uninstall component A
2. do CA
3. remove all
But i have no idea how i could realize this.
Bob Arnson-6 wrote:
>
> volkmar wrote:
>> For uninstalling the msi, i need a spec
My problem is not the call of CA.
It is more the problem of sequenced uninstall.
The solution i am thinking about is:
1. uninstall component A
2. do CA
3. remove all
But i have no idea how i could realize this.
volkmar wrote:
>
> First, sorry for my bad english.
>
> my msi creates some re
volkmar wrote:
> For uninstalling the msi, i need a special sequence:
> 1. Remove Registry Entries
> 2. Start and Exit Visual Studio
> 3. Remove Assemblies
>
You can sequence a custom action after RemoveRegistryValues to achieve
that order. The WixVSExtension includes CAs to run 'devenv /setup
First, sorry for my bad english.
my msi creates some registry entries and installs some assemblies to the
GAC. After that it start and exit Visual Studio.
But now my problem:
For uninstalling the msi, i need a special sequence:
1. Remove Registry Entries
2. Start and Exit Visual Studio
3. Rem
6 matches
Mail list logo
