Re: [WiX-users] Avoid showing final "installation interrupted" (i.e. UserExit) dialog on Cancel

[chaiguy1337]

Thanks--I got it to work! For others interested, I posted more details here:
http://stackoverflow.com/questions/3304624/cancel-an-msi-without-showing-the-installation-interrupted-dialog

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Avoid-showing-final-installation-interrupted-i-e-UserExit-dialog-on-Cancel-tp5323855p5327841.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Avoid showing final "installation interrupted" (i.e. UserExit) dialog on Cancel

[chaiguy1337]

Hi all. I would like to avoid showing that last dialog when the user clicks
"Cancel" before installation has begun. I would still like the dialog to be
shown if the user cancels an installation that has been started, as this
tells them the cancellation was successful, but if no install is taking
place, I would like clicking Cancel to just terminate the installer
gracefully and silently.

I have gotten a couple "ideas" on how to do this from different people,
which is to define a property when the cancel button is clicked and then
make this a condition for the exit dialog, but I unfortunately don't know
how to do this. I've tried a couple things, namely declaring in my Cancel
button element:




1

...and then adding this to the Show element of the UserExit dialog:


NOT 
AbortInstall


...but that doesn't seem to do anything. :(

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Avoid-showing-final-installation-interrupted-i-e-UserExit-dialog-on-Cancel-tp5323855p5323855.html
Sent from the wix-users mailing list archive at Nabble.com.

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Rob, it's not like I haven't been putting my own time into solving this as
well. I spent the entire day today working on this problem, attempting to
find the solution by scouring the internet and coming up with my own test
cases. The question started as a simple query concerning the abilities of
WiX, but led to me running into a brick wall concerning existing version
removal. I read through all of the WiX documentation and (so I thought)
relevant MSI documentation as well. However, I didn't think to look up the
ProductVersion property, because out of everything involved in this, that
was the one thing I thought I understood.

How was I to know or even fathom that such a limitation might exist without
prior experience in this area? To me, this is precisely the benefit of
having a community of experienced users who can help to address this kind of
obscure thing.

I apologize for the number of emails. To be honest I'm not entirely used to
dealing with mailing lists, so perhaps I was a little out of line on
etiquette, but alas there was no option of an online forum. Nevertheless I'm
appreciative of all the help I received and hope it wasn't too much of a
burden. The first thing I did before asking any question was to thoroughly
search both the mailing list archive and google for the answer, and only
posted if I couldn't find it.

Somewhat relatedly, and to avoid this particular issue in the future,
perhaps WiX could issue a warning if a version number is supplied with more
than three components. Something to the effect that "any version components
beyond three will be ignored by Windows Installer, so you should not rely on
them to differentiate between versions". I know that definitely would have
helped me out in this case.

Again, sorry for the unintentional abuse of the mailing list.

Logan


Rob Mensching-2 wrote:
> 
> Was reading the MSI SDK out of the question?
> 
> Logan, I'm not trying to single you out but there have been a lot of
> questions lately that could be answered or asked better if the people
> asking the questions took the time to read the MSI SDK.  I don't know
> about others here but it feels a little disrespectful to me to ask
> questions that take up our time without spending some of your time up
> front to learn the technology.
> 
> The Windows Installer is a very deep and intricate technology.  It should
> be easier and there are probably still many things we can do to improve
> WiX to make learning the Windows Installer easier but we aren't going to
> get there by answering questions that are already answered in the existing
> documentation.
> 
> That said, if you learn something and have a suggestion how we can improve
> the WiX toolset to help the next person learn faster, I would be very
> interested in hearing those suggestions.
> 
> Thanks.
> 
> 
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 16:04
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Run CA on uninstall, but not when updating
> (RemovePreviousVersions)
> 
> 
> *facepalm*
> 
> Thanks :S
> 
> That seems to have done it. I probably never would have figured that out.
> 
> 
> Brian Rogers-3 wrote:
>>
>> Ah, I think you revealed the problem:
>>
>> http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx
>>
>> "Note that Windows Installer uses only the first three fields of the
>> product version. If you include a fourth field in your product version,
>> the installer ignores the fourth field."
>>
>> ##
>> $_='^#(/||/@[EMAIL PROTECTED]@:^[-['^";@@@\\>])@.".
>> "{)/];)^{";$,+=(++$,);$_.=">&$,";`$_`;
>>
>>
>> -Original Message-
>> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
>> Sent: Friday, October 24, 2008 3:38 PM
>> To: wix-users@lists.sourceforge.net
>> Subject: Re: [WiX-users] Run CA on uninstall, but not when updating
>> (RemovePreviousVersions)
>>
>>
>> Neither of the versions have ALLUSERS set at all, because I want them to
>> be
>> per-user. As I explained I worded that poorly. The installer with
>> ALLUSERS=2
>> was for another product altogether, unrelated to this one.
>>
>> Here's what I'm doing:
>>
>> 1. Build and install program with version 1.0.0.0 and ProductCode 'a'.
>> 2. Change version to 1.0.0.1 and ProductCode to 'b', and install again.
>>
>> At this point there are two entries in Add/Remove Programs, one for
>> 1.0.0.0
>> and one for 1.0.0.1, despite all my efforts to make the latter remove the
>> f

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

*facepalm*

Thanks :S

That seems to have done it. I probably never would have figured that out.


Brian Rogers-3 wrote:
> 
> Ah, I think you revealed the problem:
> 
> http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx
> 
> "Note that Windows Installer uses only the first three fields of the
> product version. If you include a fourth field in your product version,
> the installer ignores the fourth field."
> 
> ##
> $_='^#(/||/@[EMAIL PROTECTED]@:^[-['^";@@@\\>])@.".
> "{)/];)^{";$,+=(++$,);$_.=">&$,";`$_`;
> 
> 
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 3:38 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Run CA on uninstall, but not when updating
> (RemovePreviousVersions)
> 
> 
> Neither of the versions have ALLUSERS set at all, because I want them to
> be
> per-user. As I explained I worded that poorly. The installer with
> ALLUSERS=2
> was for another product altogether, unrelated to this one.
> 
> Here's what I'm doing:
> 
> 1. Build and install program with version 1.0.0.0 and ProductCode 'a'.
> 2. Change version to 1.0.0.1 and ProductCode to 'b', and install again.
> 
> At this point there are two entries in Add/Remove Programs, one for
> 1.0.0.0
> and one for 1.0.0.1, despite all my efforts to make the latter remove the
> former. Bear in mind these installers are IDENTICAL except for those two
> tiny changes.
> 
> Logan
> 
> 
> Ian Elliott (Excell Data Corporation) wrote:
>>
>> It sounds like the two msi's don't have ALLUSERS set to the same value. I
>> don't believe you can perform a major upgrade on msi's that don't match.
>> They both have to be per-user or per-machine. You can't mix and match as
>> far as major upgrades go.
>>
>> -Original Message-
>> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
>> Sent: Friday, October 24, 2008 2:23 PM
>> To: wix-users@lists.sourceforge.net
>> Subject: Re: [WiX-users] Run CA on uninstall, but not when updating
>> (RemovePreviousVersions)
>>
>>
>> I logged the install and found this, but I can't make any sense of it:
>>
>> Action ended 17:16:57: InstallFinalize. Return value 1.
>> MSI (s) (B8:58) [17:16:57:583]: Doing action: RemoveExistingProducts
>> MSI (s) (B8:58) [17:16:57:583]: Note: 1: 2205 2:  3: ActionText
>> Action 17:16:57: RemoveExistingProducts. Removing applications
>> Action start 17:16:57: RemoveExistingProducts.
>> MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2205 2:  3: Error
>> MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2228 2:  3: Error 4: SELECT
>> `Message` FROM `Error` WHERE `Error` = 22
>> MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2205 2:  3: Error
>> MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2228 2:  3: Error 4: SELECT
>> `Message` FROM `Error` WHERE `Error` = 23
>> MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2205 2:  3: Error
>> MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2228 2:  3: Error 4: SELECT
>> `Message` FROM `Error` WHERE `Error` = 16
>> MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2205 2:  3: Error
>> MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2228 2:  3: Error 4: SELECT
>> `Message` FROM `Error` WHERE `Error` = 21
>> Action ended 17:16:57: RemoveExistingProducts. Return value 1.
>>
>> My WiX msi has no ALLUSERS property at all, wheras my original product
>> had
>> ALLUSERS=2. However, I want my new product to be per-user.
>>
>> Logan
>>
>>
>> cemiles wrote:
>>>
>>> Toss up a log if you can.
>>>
>>> I'd say check your ALLUSERS property between the 2 msis (see if
>>> they're different).
>>
>>
>> -
>> A. Logan Murray
>> http://pihole.org/
>> --
>> View this message in context:
>> http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373540.html
>> Sent from the wix-users mailing list archive at Nabble.com.
>>
>>
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> ___
>> WiX-users m

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Neither of the versions have ALLUSERS set at all, because I want them to be
per-user. As I explained I worded that poorly. The installer with ALLUSERS=2
was for another product altogether, unrelated to this one.

Here's what I'm doing:

1. Build and install program with version 1.0.0.0 and ProductCode 'a'.
2. Change version to 1.0.0.1 and ProductCode to 'b', and install again.

At this point there are two entries in Add/Remove Programs, one for 1.0.0.0
and one for 1.0.0.1, despite all my efforts to make the latter remove the
former. Bear in mind these installers are IDENTICAL except for those two
tiny changes.

Logan


Ian Elliott (Excell Data Corporation) wrote:
> 
> It sounds like the two msi's don't have ALLUSERS set to the same value. I
> don't believe you can perform a major upgrade on msi's that don't match.
> They both have to be per-user or per-machine. You can't mix and match as
> far as major upgrades go.
> 
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 2:23 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Run CA on uninstall, but not when updating
> (RemovePreviousVersions)
> 
> 
> I logged the install and found this, but I can't make any sense of it:
> 
> Action ended 17:16:57: InstallFinalize. Return value 1.
> MSI (s) (B8:58) [17:16:57:583]: Doing action: RemoveExistingProducts
> MSI (s) (B8:58) [17:16:57:583]: Note: 1: 2205 2:  3: ActionText
> Action 17:16:57: RemoveExistingProducts. Removing applications
> Action start 17:16:57: RemoveExistingProducts.
> MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2205 2:  3: Error
> MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 22
> MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2205 2:  3: Error
> MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 23
> MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2205 2:  3: Error
> MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 16
> MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2205 2:  3: Error
> MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 21
> Action ended 17:16:57: RemoveExistingProducts. Return value 1.
> 
> My WiX msi has no ALLUSERS property at all, wheras my original product had
> ALLUSERS=2. However, I want my new product to be per-user.
> 
> Logan
> 
> 
> cemiles wrote:
>>
>> Toss up a log if you can.
>>
>> I'd say check your ALLUSERS property between the 2 msis (see if
>> they're different).
> 
> 
> -
> A. Logan Murray
> http://pihole.org/
> --
> View this message in context:
> http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373540.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373774.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Sorry, by "original product" I merely meant my other program that has nothing
to do with this one (except that I'm using it as a basis for comparison).
All instances of my current program will be per-user.

I presume there is no problem doing a per-user major upgrade on a per-user
installation.


Bob Arnson-6 wrote:
> 
> chaiguy1337 wrote:
>> My WiX msi has no ALLUSERS property at all, wheras my original product
>> had
>> ALLUSERS=2. However, I want my new product to be per-user.
>>   
> 
> You can't do "cross-context" upgrades: A per-machine install can't 
> major-upgrade a per-user install and vice-versa.
> 
> -- 
> sig://boB
> http://joyofsetup.com/
> 
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373624.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

I logged the install and found this, but I can't make any sense of it:

Action ended 17:16:57: InstallFinalize. Return value 1.
MSI (s) (B8:58) [17:16:57:583]: Doing action: RemoveExistingProducts
MSI (s) (B8:58) [17:16:57:583]: Note: 1: 2205 2:  3: ActionText 
Action 17:16:57: RemoveExistingProducts. Removing applications
Action start 17:16:57: RemoveExistingProducts.
MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2205 2:  3: Error 
MSI (s) (B8:58) [17:16:57:598]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 22 
MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2205 2:  3: Error 
MSI (s) (B8:58) [17:16:57:600]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 23 
MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2205 2:  3: Error 
MSI (s) (B8:58) [17:16:57:613]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 16 
MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2205 2:  3: Error 
MSI (s) (B8:58) [17:16:57:617]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 21 
Action ended 17:16:57: RemoveExistingProducts. Return value 1.

My WiX msi has no ALLUSERS property at all, wheras my original product had
ALLUSERS=2. However, I want my new product to be per-user.

Logan


cemiles wrote:
> 
> Toss up a log if you can.
> 
> I'd say check your ALLUSERS property between the 2 msis (see if
> they're different).


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373540.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

I'm having a problem: turns out the removal is not taking place at all. I
guess I didn't notice this before. When I install my update overtop of an
existing installation and look at add/remove programs, there are two
entries: one for each version.

Can someone give me a clue as to what's wrong? I've compared the msi's for
both this and my old product that worked properly and they appear to be
similar. Here's what I have in product.wxs:






REBOOT = 1 AND UILevel = 5 AND NOT
Installed

UILevel < 5 AND NOT Installed 
AND NOT
REBOOT = 1
REMOVE = "ALL" AND NOT
UPGRADINGPRODUCTCODE







Anything obviously wrong or missing??

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373492.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Ideally I prefer the simplicity of a messagebox over a wizard for
uninstalling, since a yes/no answer is all that is needed, but I think I
might just move the data directory to the recycle bin and not bother the
user with a question at all, since this still gives them the ability to
restore it if need be.

I am of the opinion that treating a user's personal information (i.e. data
that cannot simply be "reinstalled") in the same manner as the application
itself can be dangerous. While it is true that uninstalling a program
generally also means remove all user data along with it, it's also possible
that the user might not realize that and decide to manually reinstall the
application by uninstalling and reinstalling it. It would be a shame if at
the end of this operation they realized all their data was gone (my program
stores all of the user's data in a database, so we are talking some
potentially important stuff here). At least if it's in the recycle bin, all
they have to do is click the directory and choose "Restore". Worst case (not
counting accidentally emptying the recycle bin :P) is that they panic, email
me, and I tell them to check their recycle bin, and they let out a big WHEW!
No big deal.

However if that data really IS gone, that IS a big deal, and I want to avoid
that at all costs.

So that said, do I really have to worry about patching/upgrading/rolling
back? My program is simple (and small) enough that I have no plans to ever
patch pieces of an install. The major upgrade suits me just fine for now. As
for rolling back, if some error occurs during uninstall, the worst case
scenario is that the custom action executes and the user's data ends up in
the recycle bin, however I don't even think this will happen because the
custom action is scheduled at the very end, after InstallFinalize, which
means that if an error occurs, the rollback will take place before the
custom action is even executed. Is this not correct?

Thanks for the tips and pointers. I've run through some tests and it appears
to be working (executing the CA on full uninstall but not on an upgrade) so
I thank you all for your help!

Logan


Rob Mensching-2 wrote:
> 
> 1.  Windows Installer can remove files based off a property.  So you can
> prompt and set a property appropriately to remove the files or not.
> 
> 2.  I don't think files go into the recycle bin.  So you may have to have
> a CustomAction for that.  Too bad, since it means you'll have to think
> through all the install/uninstall/patching/upgrade/rollback for all that
> semantics.
> 
> I've never heard someone say, "Oh, it'll be easier to write a CustomAction
> than use the built in Windows Installer functionality after shipping a
> CustomAction."  
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1373156.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Aha! Thanks for the warning; that would have surely caused headaches as
currently my custom action is scheduled before RemoveExistingProducts.

Do I need to also schedule FindRelatedProducts in order for
RemoveExistingProducts to work?


Alexander Shevchuk wrote:
> 
> Remember that UPGRADINGPRODUCTCODE is set by RemoveExistingProducts
> action. For your condition for UninstallCA to work properly,
> RemoveExistingProducts must be scheduled before your custom action.
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1372992.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Rob Mensching-2 wrote:
> 
> Can you just use the native MSI functionality to remove the application
> data?
> 

No, the path is determined at runtime based on the user's AppData directory
(and is theoretically customizable, though I haven't added ui to do that)
and moreover I want to either:

a) provide the option via a messagebox whether the data should be removed on
uninstall, or
b) move it to the recycle bin so it can be recollected if the user is
performing a manual reinstall

Since it is my understanding MSI can do neither of these things (easily), a
custom action seems apt.

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1372976.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Excellent. So I should be able to set the condition for my uninstall CA to
something like this:

REMOVE = "ALL" AND NOT
UPGRADINGPRODUCTCODE

...and it will only run when an explicit uninstall (and not a major upgrade)
is performed?

One more thing, could you explain what REMOVE="ALL" actually means, and does
it belong in the above context? I just copied that from an example but
couldn't find it explained anywhere except that it will contain a list of
the components to remove or the string "ALL". Presumably, this means that
the CA will only run if ALL of the components are being removed (which I
assume is the case in an explicit uninstall), which makes sense. Is this
correct?


Ian Elliott (Excell Data Corporation) wrote:
> 
> This should get you started:
> http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
> 
> Also, when a major upgrade runs the UPGRADINGPRODUCTCODE property is
> passed into the version being uninstalled.
> 
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 8:52 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Run CA on uninstall, but not when updating
> (RemovePreviousVersions)
> 
> 
> Back when I wrote my installer using Visual Studio's setup project, there
> was
> a flag RemovePreviousVersions that would allow future versions of my
> program
> to update previous versions simply by removing the previous version and
> installing the new one overtop of them.
> 
> My first question is how to do this with WiX.
> 
> But more importantly, there was a custom action in my old setup (via
> System.Configuration.Install) that added a custom action to the
> BeforeUninstall event:
> 
> this.BeforeUninstall += new InstallEventHandler(
> InstallHelper_BeforeUninstall );
> 
> Which removed the data files generated by the application at runtime.
> 
> Anyhow, the point is that this custom action would only occur when the
> product was actually manually uninstalled, and I want to make sure my WiX
> installer has the same behavior. In other words, I want to call my custom
> action only when the user explicitly selects to uninstall the program, not
> when it is removed when a new version is installed overtop it (assuming
> this
> is possible with WiX).
> 
> Can someone help me with this?
> 
> -
> A. Logan Murray
> http://pihole.org/
> --
> View this message in context:
> http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1372539.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1372883.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Run CA on uninstall, but not when updating (RemovePreviousVersions)

[chaiguy1337]

Back when I wrote my installer using Visual Studio's setup project, there was
a flag RemovePreviousVersions that would allow future versions of my program
to update previous versions simply by removing the previous version and
installing the new one overtop of them.

My first question is how to do this with WiX.

But more importantly, there was a custom action in my old setup (via
System.Configuration.Install) that added a custom action to the
BeforeUninstall event:

this.BeforeUninstall += new InstallEventHandler(
InstallHelper_BeforeUninstall );

Which removed the data files generated by the application at runtime.

Anyhow, the point is that this custom action would only occur when the
product was actually manually uninstalled, and I want to make sure my WiX
installer has the same behavior. In other words, I want to call my custom
action only when the user explicitly selects to uninstall the program, not
when it is removed when a new version is installed overtop it (assuming this
is possible with WiX).

Can someone help me with this?

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Run-CA-on-uninstall%2C-but-not-when-updating-%28RemovePreviousVersions%29-tp1372539p1372539.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Thanks! Got it working.


Bob Arnson-6 wrote:
> 
> chaiguy1337 wrote:
>> Is there a particular reason the example in the help file didn't use
>> "normal"
>> exe custom actions? I don't want to do something that might cause
>> problems
>> later.
>>   
> 
> Because a more typical use case is to launch a document (like a 
> readme.html or .pdf). WixShellExec was designed just for that purpose. 
> Most users won't expect another install to launch after "finishing" one.
> 
> -- 
> sig://boB
> http://joyofsetup.com/
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366796.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

I wasn't talking about launching another install, I was talking about
launching the application that was just installed. I guess that makes sense
as to why ShellExec was chosen for the example. I will fiddle around with
normal custom actions and see if I can get it working.


Bob Arnson-6 wrote:
> 
> chaiguy1337 wrote:
>> Is there a particular reason the example in the help file didn't use
>> "normal"
>> exe custom actions? I don't want to do something that might cause
>> problems
>> later.
>>   
> 
> Because a more typical use case is to launch a document (like a 
> readme.html or .pdf). WixShellExec was designed just for that purpose. 
> Most users won't expect another install to launch after "finishing" one.
> 
> -- 
> sig://boB
> http://joyofsetup.com/
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366725.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Is there a particular reason the example in the help file didn't use "normal"
exe custom actions? I don't want to do something that might cause problems
later.


Bob Arnson-6 wrote:
> 
> chaiguy1337 wrote:
>> Hi all. I'm looking for a way to pass command line arguments to my app
>> launched when the installation is complete, so that my app knows it was
>> launched by the installer.
>>
>> I basically copied the example from the help file:
>>
>> >  Value="[#OrangeNote.exe]" />
>> >  BinaryKey="WixCA"
>>  DllEntry="WixShellExec"
>>  Impersonate="yes" />
>>
>> Where might I add my "-installer" switch? I tried changing the Value of
>> the
>> property to "[#OrangeNote.exe] -installer" but that didn't work at all,
>> and
>> the app never launched.
>>   
> 
> WixShellExecTarget must be only the path of the executable/document. 
> There's no support to add arguments. For that, use a "normal" exe custom 
> action instead of WixShellExec.
> 
> -- 
> sig://boB
> http://joyofsetup.com/
> 
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366652.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Passing command line arguments to an app launched after setup

[chaiguy1337]

Hi all. I'm looking for a way to pass command line arguments to my app
launched when the installation is complete, so that my app knows it was
launched by the installer.

I basically copied the example from the help file:




Where might I add my "-installer" switch? I tried changing the Value of the
property to "[#OrangeNote.exe] -installer" but that didn't work at all, and
the app never launched.

Logan

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Passing-command-line-arguments-to-an-app-launched-after-setup-tp1366362p1366362.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET Bootstrapper, Self-Extracting Executables

[chaiguy1337]

Wow, AutoIt is really great! I'm totally loving it. It's a simple, easy to
use syntax and it's quite sophisticated. Compiles to a native app, very
small footprint. I've got a nice little custom bootstrapper now, combined
with my WinRAR self-extractor and WiX installer, and this is shaping up to
be one heck of an installation! :D


DEÁK JAHN, Gábor-2 wrote:
> 
> 
> Hello,
> 
> as I had to face the same problem just a couple of weeks ago, the final
> approach I took was putting together a very simple bootstrapper in the
> AutoIt scripting language. Nothing fancy, it is a Setup.exe that checks
> for .NET 2.0 and SP1 in my case, downloads and executes them from a known
> location, then downloads the actual MSI and launches it. In a distributed
> media scenario (eg. all files on a CD) it is even simpler because there is
> no need to download anything.
> 
> Bye,
>Gábor
> 
> ---
> DEÁK JAHN, Gábor -- Budapest, Hungary
> E-mail: [EMAIL PROTECTED]
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 


-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/.NET-Bootstrapper%2C-Self-Extracting-Executables-tp1351845p1362530.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Found the perfect self-extracting executable maker

[chaiguy1337]

WinRAR! I've been using WinRAR for years as my main compressed archive
viewer, but only just recently discovered it has support for creating
self-extracting archives (SFX it calls them) as well! Not only that but it's
by far the best out of all of the ones I've tried.

Namely, it does everything I want, including:

-silent execution (no dialogs)
-ability to execute a file after extraction
-ability to extract to the temp directory and clean up when done
-customizable icon, and customizable dialogs if you do want them shown
-choose whether the final exe requests elevation (specifically I wanted the
ability to NOT request elevation, since most tools I used did this and I
don't like it)

...and tons more. It has seven tabs of customization options for SFX's
alone.

All for a single-dev license of $29. I highly recommend it. The fee is well
worth the self-extraction capabilities alone.

Disclaimer: I don't work for, nor am I affiliated in any way with the WinRAR
guys--I'm just so delighted I found it that I wanted to spread the word.

Cheers,
Logan

-
A. Logan Murray
http://pihole.org/
-- 
View this message in context: 
http://n2.nabble.com/Found-the-perfect-self-extracting-executable-maker-tp1360679p1360679.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET Bootstrapper, Self-Extracting Executables

[chaiguy1337]

Thanks for the tip! I will look into the AutoIt language. To get me started,
could you provide me with a sample piece of your script that checks the .NET
version and downloads/launches the installer?

Logan


DEÁK JAHN, Gábor-2 wrote:
> 
> On Sun, 19 Oct 2008 10:41:05 -0700, Rob Mensching wrote:
> 
> Hello,
> 
> as I had to face the same problem just a couple of weeks ago, the final
> approach I took was putting together a very simple bootstrapper in the
> AutoIt scripting language. Nothing fancy, it is a Setup.exe that checks
> for .NET 2.0 and SP1 in my case, downloads and executes them from a known
> location, then downloads the actual MSI and launches it. In a distributed
> media scenario (eg. all files on a CD) it is even simpler because there is
> no need to download anything.
> 
> Bye,
>Gábor
> 
> ---
> DEÁK JAHN, Gábor -- Budapest, Hungary
> E-mail: [EMAIL PROTECTED]
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/.NET-Bootstrapper%2C-Self-Extracting-Executables-tp1351845p1355907.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET Bootstrapper, Self-Extracting Executables

[chaiguy1337]

Well the problem was that the bootstrapper was not working properly, in a
number of ways. (I'm attempting to use the NetFx35ClientSetup.exe
bootstrapper)

First of all it was always running, even if the user has the framework
installed, which I don't like because it detracts from my app's setup
experience and is unnecessary. And secondly, it is not even able to "find"
my application installer to continue the installation after it completes
anyway.

Here's what I'm doing:


  
.NET Framework Client Profile
  




  


Which is basically right out of the wix.chm file. Yet for some reason,
$(TargetPath) doesn't seem to work. I wonder, can this be relative? It seem
to me that this will end up hard-coding my current path to the installer,
which won't work on end-user machines.

Furthermore, if I do get this to work, I would end up packing things into a
self-extracting executable to unpack to a temp directory, meaning that the
actual path to the installer will be random, and will therefore either need
to be supplied relative to the bootstrapper, or passed-in as a command line
argument, which leads to my other question...

How can I change the command line parameters the bootstrapper is invoked
with?


metaman wrote:
> 
> Could you not use the MSBuild GenerateBootstrapper task to accomplish what
> you need to do?
>  http://msdn.microsoft.com/en-us/library/ms164294.aspx
> 
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/.NET-Bootstrapper%2C-Self-Extracting-Executables-tp1351845p1355254.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] digitally signing (authenticode) with wix?

[chaiguy1337]

I'm able to successfully sign my msi post-build, but when the installer runs,
although the Vista UAC shows that it is signed and verified as coming from
my organization, the name of the file is some random a29fc82b.msi type of
thing. I was wondering if there's any way at all to change the (apparently
auto-generated) name of the msi so that the UAC shows the name of my product
instead of this gibberish?


Rob Mensching-4 wrote:
> 
> More specifically, signing is a build task (think MSBuild or NAnt) not a 
> "build setup" task (aka: WiX).
> 
> Bob Arnson wrote:
>> Craig Miller wrote:
>>   
>>> Is there an easy way to digitally sign the msi w/ the WIX toolkit or
>>> should
>>> I use signtool by hand?
>>>   
>>> 
>>
>> WiX doesn't sign.
>>
>>   
> 
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/digitally-signing-%28authenticode%29-with-wix--tp707163p1352830.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users