date:20100401

The original error message is:

error LGHT0130 : The primary key 'regA2E5343F2EC34F3CCC232B9D03BB2A85'
is duplicated in table 'Registry'.
Please remove one of the entries or rename a part of the primary key to
avoid the collision.

I expect that this key is generated internally by LIGHT, since the .wxs
file does not include it.

Regards
Markus

 -Original Message-
 From: Bob Arnson [mailto:b...@joyofsetup.com]
 Sent: Donnerstag, 1. April 2010 02:26
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] WiX 3.0: Bug in LIGHT
 
 On 3/31/2010 8:55 AM, Markus Karg wrote:
  tried to link it using LIGHT. LIGHT says that there is a duplicate
in
  that fragment, so we checked the fragment. In fact, there is no
  duplicate:
 
 
 What's the exact error message?
 
 --
 sig://boB
 http://joyofsetup.com/
 
 

---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] stop the service before uninstall

Hi,

Thanks for your answer. I was thinking also that maybe I could just 
somehow call an external CA _before_ InstallValidate that will take 
care to just stop the service. This way the service will be stopped, it 
will stop the app and when the InstallValidate comes into action 
everything is already down. Would this be this also a way to go?

Thx,
Viv

On 3/31/2010 8:57 PM, Wilson, Phil wrote:
 There isn't a built-in way to tell the uninstall that the ServiceControl that 
 stops the service is going to shut down your app. That means you'll need to 
 use an uninstall custom action to close down the app - I think WiX has one 
 called CloseApp or something. You'd sequence this before InstallValidate, 
 which is where the in-use situations are detected.  You also need a way to 
 tell your service to switch off its monitoring, and use that in a custom 
 action at uninstall time. I've seen this kind of situation before. There are 
 times when these services need to be told to stop their monitoring, such as 
 upgrades, patches, uninstalls, and when to start again. The way I've seen 
 this done is that a registry entry is created/altered, and before the service 
 does whatever it's going to do it checks the registry entry, so in your case 
 the service wouldn't monitor the app. So your uninstall would, in this order.

 1. Have an uninstall custom action that writes a stop monitoring registry 
 item for the service.
 2. A uninstall custom action (CloseApp?) that shuts down your app.

 InstallValidate finds no files in use and proceeds to stop services, 
 uninstall files etc.

 3. Custom action to delete the stop monitoring registry item.


 Phil Wilson


 -Original Message-
 From: Viv Coco [mailto:vcotirl...@hotmail.com]
 Sent: Wednesday, March 31, 2010 3:34 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] stop the service before uninstall

 Forgot to mention: as my application is started by the service it runs
 in the service context which means they both don't run in the context of
 the current user, but as SYSTEM. Also my application doesn't have a
 window (it's a winmain application but with
 EntryPointSymbol=mainCRTStartup).

 I think the uninstaller checks at the beginning of the uninstalling
 process which binaries are in use and b/c MyApp.exe is at that point
 running I get the reboot message. If I could tell the installer to check
 the files in use at a later point, after the service was stopped (b/c at
 that point MyApp.exe is also not running anymore) I could get rid of
 this reboot-message. Can I schedule this check at a later point?

 Thx,
 Viv

 On 3/31/2010 10:25 AM, Viv Coco wrote:

   When, during the uninstall process, are you getting the error? Is it

 happening during the RemoveFiles action?

 If I have correctly read the log file, happens during the
 InstallValidate (I checked in the log file the Doing action: and
 InstallValidate  is the last one before the message is shown).

 But in the log file I noticed that it's not my service that actually
 produces the problem, but my application. I have an application
 (MyApp.exe) that runs endlessly and is babysit by a service
 (MyServiceWatchdog.exe): when the service is started my application is
 started, when the service is stopped my application is stopped (the
 service takes care of startig/stopiing my application) .
 So in the (un)installer I said that the service must be stopped when
 uninstalling which will actually stop also my application (b/c my
 service will also kill my app when stopping).

 I'm not sure if I understood correctly but what I think happens is:
 the uninstaller checks the files and sees that my application
 (MyApp.exe) is running and there is no event scheduled to stop it, so
 it shows the reboot message. But actually MyApp.exe will be stopped
 once the service is stopped.
 Is there a way to tell the uninstaller that? I can't kill MyApp.exe
 from the uninstaller b/c if the service is not yet stopped when
 MyApp.exe is killed, the service will restart again MyApp.exe.

  
   If so, you might try adding the Wait=yes attribute to your
 ServiceControl so that it waits for it to stop

 the service before moving on to remove files. It may be that the SCM is
 taking too long and the installer need to give it time to complete.
 Just a
 guess, though.

 I tried with the Wait attribute but didn't change the behavior.

  
   Could you provide a log?

 sure, see attached. I saved the log as soon as I got the reboot message.

 Thanks a lot!
 Viv



 On 3/30/2010 1:55 PM, Nick Ramirez wrote:
  
 When, during the uninstall process, are you getting the error? Is it
 happening during the RemoveFiles action? If so, you might try adding the
 Wait=yes attribute to your ServiceControl so that it waits for it
 to stop
 the service before moving on to remove files. It may be that the SCM is
 taking too long and the installer need to give it time to complete.

Re: [WiX-users] WiX 3.0: Bug in LIGHT

2010-04-01 Thread Ondrej Zarevucky

Hi Markus,
I had the same problem with one of our COM objects. I'm was told there 
problem in our COM object registration and I fixed it by moving the 
version independent class entry under the version dependent one using 
our custom built WiX post processing tool:

ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator.1 
Description=FEMeshGen2DGenerator Class
ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator 
Description=FEMeshGen2DGenerator Class /
/ProgId

More about this issue can be found in this bug report:
http://sourceforge.net/tracker/index.php?func=detailaid=2793966group_id=105970atid=642714
 
http://sourceforge.net/tracker/index.php?func=detailaid=2793966group_id=105970atid=642714

I hope it helps a bit

Ondřej Zarevúcky

On 1.4.2010 8:21, Markus Karg wrote:
 The original error message is:

 error LGHT0130 : The primary key 'regA2E5343F2EC34F3CCC232B9D03BB2A85'
 is duplicated in table 'Registry'.
 Please remove one of the entries or rename a part of the primary key to
 avoid the collision.

 I expect that this key is generated internally by LIGHT, since the .wxs
 file does not include it.

 Regards
 Markus


 -Original Message-
 From: Bob Arnson [mailto:b...@joyofsetup.com]
 Sent: Donnerstag, 1. April 2010 02:26
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] WiX 3.0: Bug in LIGHT

 On 3/31/2010 8:55 AM, Markus Karg wrote:
  
 tried to link it using LIGHT. LIGHT says that there is a duplicate

 in

 that fragment, so we checked the fragment. In fact, there is no
 duplicate:


 What's the exact error message?

 --
 sig://boB
 http://joyofsetup.com/



  
 ---

 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] CopyFile to be executed only on first install and removed only when a real uninstall

Hi all,

I install an aaa.ini file together with my binaries. I need a second ini 
file (bbb.ini) which is a copy of the first one, it just have a 
different name, and it's in the same directory. I was thinking about 
using the CopyFile but I need also the following:
1) the CopyFile, meaning the creation of the bbb.ini should happen only 
if the bbb.ini file doesn't already exist (from previous installations)
2) the bbb.ini file should be removed only on a real uninstall - not 
upgrades, repairs, modifies.

How could I accomplish this?

Thx,
Viv

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] CopyFile to be executed only on first install and removed only when a real uninstall

btw, I could also do a normal component with a File Id, smth like:

Component Id=aaa.ini Guid=GUID
File Id=aaa.ini Name=aaa.ini Source=template.ini KeyPath=yes /
/Component

Component Id=bbb.ini Guid=GUID
File Id=bbb.ini Name=bbb.ini Source=template.ini KeyPath=yes /
/Component

that means that template.ini would be on the target machine as aaa.ini 
and as bbb.ini which is fine.

But how can I condition the bbb.ini component to be removed only on a 
real uninstall - not upgrades, repairs, modifies? Is this doable?

Thx,
Viv

On 4/1/2010 10:43 AM, Viv Coco wrote:
 Hi all,

 I install an aaa.ini file together with my binaries. I need a second ini
 file (bbb.ini) which is a copy of the first one, it just have a
 different name, and it's in the same directory. I was thinking about
 using the CopyFile but I need also the following:
 1) the CopyFile, meaning the creation of the bbb.ini should happen only
 if the bbb.ini file doesn't already exist (from previous installations)
 2) the bbb.ini file should be removed only on a real uninstall - not
 upgrades, repairs, modifies.

 How could I accomplish this?

 Thx,
 Viv

 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users





--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Getting MSI Error 1613

2010-04-01 Thread Sandeep Gautam (HCL Technologies Ltd)

HI All,

While doing installation I am getting error # 1613(This installation package 
cannot be installed by the Windows Installer service. you must install a 
Windows service pack that contains a newer version of the Windows Installer 
service.). I am using Windows (r) Installer. V 4.00.6001.0.

Note: Installer was working till yesterday. Suddenly it is throwing this 
error(1613)

Please do needful.

Regards
-Sandeep
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to create web app/service on IIS 7 with WiX 3.0

2010-04-01 Thread Igor Paniushkin

I think I still need one, I couldn't find these actions in standard IIS
extension. Currently my custom actions is:
1) AspMaxRequestEntityAllowed and AspAllowSessionState on created
website
2) Enable32bitAppOnWin64 (enables it) on application pools
3) Setting ManagedRuntimeVersion on created application pool

My CA was deferred (not commit) action in the beginning and I made it to
be executed after ConfigureIIs (in Wix 3.5 I changed to be after
ConfigureIIs7), but from log file I can see that website was not created
after ConfigureIIs7 action. Can you please specify name after which IIS
action I should execute mine custom action?


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Monday, March 29, 2010 8:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

Regarding those errors, you can ignore them. In fact, feel free to file
a bug so we can make those errors appear less scary, because they aren't
really of concern, it just means Wow64 API's aren't available on your
OS.

Regarding the custom action, do you really need one? Can you rely on
standard IIS extension functionality? Introducing your own custom action
is a classic way to drive up installation failure rates, break rollback
support, cause problems during uninstall, etc. If the functionality you
want doesn't exist but it is functionality that makes sense for the
community, a feature request would be nice.

To answer your scheduling question, the real IIS work occurs before
commit, during the install script (deferred). The commit CA is just to
delete a file used to rollback state. If you really do need a custom
action, you should run your CA deferred too, but after the IIS custom
action. 

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Friday, March 26, 2010 8:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

Oops. My mistake. I had a typo in my wxs project file. I got successful
installation with website created on both (2008 64bit and 32bit), but on
windows 2008 64 bit I still got some error messages in log file:

StartIIS7ConfigTransaction:  Error 0x80070001: Failed to disable WOW64.
CommitIIS7ConfigTransaction:  Error 0x80070001: Failed to disable WOW64.

But now I have another problem, I had custom action which rely on
created website (doing some modifications to website which is not
supported on iis wix extension) and on sequence it was after
ConfigureIIs custom action, but now as I understood website created in
commit custom action. What is the best approach now to execute my own
custom action? How to schedule it after creation of website?

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Friday, March 26, 2010 4:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

I already tried the same on new build 3.5.1526 and I still can't create
website (tried on Windows 2008 32 bit machine). Next error messages in
log file:

Action start 16:09:59: InstallFinalize.
StartIIS7ConfigTransaction: Error 0x80070001: Failed to disable WOW64.
WriteIIS7ConfigChanges: Error 0x80070002: IIS: site not found for create
VDir
WriteIIS7ConfigChanges: Error 0x80070002: Failed to configure IIS VDir.
WriteIIS7ConfigChanges: Error 0x80070002: WriteIIS7ConfigChanges Failed.
Action ended 16:10:00: InstallFinalize. Return value 3.
RollbackIIS7ConfigTransaction: Error 0x80070001: Failed to disable
WOW64.
Action ended 16:10:00: INSTALL. Return value 3.
Action ended 16:10:00: ExecuteAction. Return value 3.
Action ended 16:10:00: INSTALL. Return value 3.
=== Logging stopped: 3/26/2010 16:10:00 ===
MSI (c) (F8:44) [16:10:00:387]: Product: ConfigureIIs7Test --
Installation
failed.

MSI (c) (F8:44) [16:10:00:402]: Windows Installer installed the product.
Product Name: ConfigureIIs7Test. Product Version: 1.0.0.0. Product
Language: 1033. Installation success or error status: 1603.

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Friday, March 26, 2010 11:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

I added a bug couple of weeks before about the same thing:
http://sourceforge.net/tracker/?func=detailaid=2961215group_id=105970;
atid=642714
Is it the same as yours?

And Mike already fixed it in the latest Wix build which should be
available today.


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Thursday, March 25, 2010 8:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

I'd file a bug with the authoring you pasted below, and the answers

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread Sagar1111


the reason behind not using System.Windows.Forms is that i dont want my
message box the appear behind mywizard. 
basically, What i want is a functionality like cancel button.
I need to to popup a message from my custom action. Show it in front of the
wizard. This pop-up dialog box would have two buttons yes and no. If the
user presses yes wizard should navigate to next dialogbox and if the user
presses no the wizard should stay on same dialogbox.
This functionality is quite similar to cancel button.
How do i achieve this?

Sagar
-- 
View this message in context: 
http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836020.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Prevent deinstallation

We have to write a .msi to install modules into a preinstalled software.

 

The problem is that once the module is installed, it can never get
uninstalled, as it modifies some software-internal structures in a way
that makes it impossible to undo.

 

So, we have to prevent that somebody goes into the system control panel,
selects the module, and presses uninstall.

 

Can we do that using WiX?

 

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX 3.0: Bug in LIGHT

Thank you for posting the URL. Yes, we are suffering exactly from that bug, and 
the proposed solution is working. :-)

BTW, I actually do not understand why the *unversioned* variant has to be 
*inside* the versioned one? I would understand if the semantics would be 
exchanged (There shall be a registry entry, and in particular, there shall be 
a versioned one.), but I don't get the idea of the actual encapsulation 
(There shall be a versioned registry entry, and hey, also there shall be an 
unversioned one.?!

Regards
Markus


 -Original Message-
 From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz]
 Sent: Donnerstag, 1. April 2010 10:41
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] WiX 3.0: Bug in LIGHT
 
 Hi Markus,
 I had the same problem with one of our COM objects. I'm was told there
 problem in our COM object registration and I fixed it by moving the
 version independent class entry under the version dependent one using
 our custom built WiX post processing tool:
 
 ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator.1
 Description=FEMeshGen2DGenerator Class
 ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator
 Description=FEMeshGen2DGenerator Class /
 /ProgId
 
 More about this issue can be found in this bug report:
 http://sourceforge.net/tracker/index.php?func=detailaid=2793966group_
 id=105970atid=642714
 http://sourceforge.net/tracker/index.php?func=detailaid=2793966group
 _id=105970atid=642714
 
 I hope it helps a bit
 
 Ondřej Zarevúcky
 
 On 1.4.2010 8:21, Markus Karg wrote:
  The original error message is:
 
  error LGHT0130 : The primary key
 'regA2E5343F2EC34F3CCC232B9D03BB2A85'
  is duplicated in table 'Registry'.
  Please remove one of the entries or rename a part of the primary key
 to
  avoid the collision.
 
  I expect that this key is generated internally by LIGHT, since the
 .wxs
  file does not include it.
 
  Regards
  Markus
 
 
  -Original Message-
  From: Bob Arnson [mailto:b...@joyofsetup.com]
  Sent: Donnerstag, 1. April 2010 02:26
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] WiX 3.0: Bug in LIGHT
 
  On 3/31/2010 8:55 AM, Markus Karg wrote:
 
  tried to link it using LIGHT. LIGHT says that there is a duplicate
 
  in
 
  that fragment, so we checked the fragment. In fact, there is no
  duplicate:
 
 
  What's the exact error message?
 
  --
  sig://boB
  http://joyofsetup.com/
 
 
 
 
  -
 --
 
  ---
  Download Intel#174; Parallel Studio Eval
  Try the new software tools for yourself. Speed compiling, find bugs
  proactively, and fine-tune applications for parallel performance.
  See why Intel Parallel Studio got high marks during beta.
  http://p.sf.net/sfu/intel-sw-dev
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
  -
 -
  Download Intel#174; Parallel Studio Eval
  Try the new software tools for yourself. Speed compiling, find bugs
  proactively, and fine-tune applications for parallel performance.
  See why Intel Parallel Studio got high marks during beta.
  http://p.sf.net/sfu/intel-sw-dev
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 ---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Show Dialog from Custom Action

for this you can set in the PROPERTY in your custom action. and create a
custom dialog as per you requirements... on clicking the next of you current
dialog... call C# CA first and then call this new customized dialog and set
a condition as per the PROPERTY value.

hope you ll reslove you issue like this..

On Thu, Apr 1, 2010 at 2:46 PM, Sagar sagarkavitak...@gmail.com wrote:


 the reason behind not using System.Windows.Forms is that i dont want my
 message box the appear behind mywizard.
 basically, What i want is a functionality like cancel button.
 I need to to popup a message from my custom action. Show it in front of the
 wizard. This pop-up dialog box would have two buttons yes and no. If
 the
 user presses yes wizard should navigate to next dialogbox and if the user
 presses no the wizard should stay on same dialogbox.
 This functionality is quite similar to cancel button.
 How do i achieve this?

 Sagar
 --
 View this message in context:
 http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836020.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
Cheers,
Akash
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting MSI Error 1613

have you validated your package using ORCA or MSIVal ?

On Thu, Apr 1, 2010 at 2:37 PM, Sandeep Gautam (HCL Technologies Ltd) 
v-sgo...@microsoft.com wrote:

 HI All,

 While doing installation I am getting error # 1613(This installation
 package cannot be installed by the Windows Installer service. you must
 install a Windows service pack that contains a newer version of the Windows
 Installer service.). I am using Windows (r) Installer. V 4.00.6001.0.

 Note: Installer was working till yesterday. Suddenly it is throwing this
 error(1613)

 Please do needful.

 Regards
 -Sandeep

 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
Cheers,
Akash
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley

Could you create an .msp to patch the original installer to add these files?

-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: 01 April 2010 10:30
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Prevent deinstallation

We have to write a .msi to install modules into a preinstalled software.

The problem is that once the module is installed, it can never get
uninstalled, as it modifies some software-internal structures in a way
that makes it impossible to undo.

So, we have to prevent that somebody goes into the system control panel,
selects the module, and presses uninstall.

Can we do that using WiX?

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 DISCLAIMER 

Please consider the environment before printing this e-mail.

This e-mail has been scanned for all known virus's but this is not a 
confirmation it is virus free.

This is an e-mail from EIC Limited (Company Reg: 1086295). The contents of this 
e-mail are confidential. EIC Limited do not accept responsibility for the 
accuracy or completeness of the contents of this e-mail as it has been 
transmitted over a public network. If you receive this e-mail in error please 
accept our apology. If this is the case we would be obliged if you would 
contact the sender and then delete this e-mail.

THIS E-MAIL AND / OR ANY REPLIES TO IT, AND ANY ATTACHMENTS MAY BE INTERCEPTED, 
COPIED OR MONITORED BY EIC LIMITED FOR THE PURPOSE OF MONITORING OR KEEPING 
RECORD OF ITS BUSINESS AND FOR THE PURPOSES SET OUT IN THE TELECOMMUNICATIONS 
(LAWFUL BUSINESS PRACTICES) (INTERCEPTION OF COMMUNICATIONS) REGULATIONS 2000.

All statements made in this e-mail are subject to contract. The contents are 
not to be regarded as a contractual offer or acceptance. The sender is not 
authorised to bind EIC Limited.

The views expressed in this e-mail are those of the sender and not necessarily 
those of EIC Limited.

 DISCLAIMER 

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Rob Hamflett

Are you aware that disabling installs will prevent major upgrades?

Rob

On 01/04/2010 10:29, Markus Karg wrote:
 We have to write a .msi to install modules into a preinstalled software.



 The problem is that once the module is installed, it can never get
 uninstalled, as it modifies some software-internal structures in a way
 that makes it impossible to undo.



 So, we have to prevent that somebody goes into the system control panel,
 selects the module, and presses uninstall.



 Can we do that using WiX?



 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

Yes, but on modules no major updates will happen -- due to the
technological solution, the major upgrade will replace the main product
completele, including all modules. So the idea of having modules as .msp
is actually fascinating us, as it would solve this issue, too.

 -Original Message-
 From: Rob Hamflett [mailto:r...@snsys.com]
 Sent: Donnerstag, 1. April 2010 11:52
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Prevent deinstallation

 Are you aware that disabling installs will prevent major upgrades?

 Rob

 On 01/04/2010 10:29, Markus Karg wrote:
  We have to write a .msi to install modules into a preinstalled
 software.

  The problem is that once the module is installed, it can never get
  uninstalled, as it modifies some software-internal structures in a
 way
  that makes it impossible to undo.

  So, we have to prevent that somebody goes into the system control
 panel,
  selects the module, and presses uninstall.

  Can we do that using WiX?

-
 -
  Download Intel#174; Parallel Studio Eval
  Try the new software tools for yourself. Speed compiling, find bugs
  proactively, and fine-tune applications for parallel performance.
  See why Intel Parallel Studio got high marks during beta.
  http://p.sf.net/sfu/intel-sw-dev

---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley

Theoretically yes, they will be able to remove the patch from Programs and 
Features if they click on View installed updates, however, if you create the 
patch correctly, removing it will not actually remove the patched files. I have 
a patch process that works in this way. It should be noted though, that if you 
create any further patches that rely on the original being installed first, the 
user will have to be aware of the upgrade path.

-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: 01 April 2010 10:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Prevent deinstallation

In theorey we could, but:

Will this solve the problem?

Will the user be able to see that the module was installed?

 -Original Message-
 From: Richard Horsley [mailto:richard.hors...@eicltd.com]
 Sent: Donnerstag, 1. April 2010 11:42
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Prevent deinstallation

 Could you create an .msp to patch the original installer to add these
 files?

 -Original Message-
 From: Markus Karg [mailto:k...@quipsy.de]
 Sent: 01 April 2010 10:30
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] Prevent deinstallation

 We have to write a .msi to install modules into a preinstalled
 software.



 The problem is that once the module is installed, it can never get
 uninstalled, as it modifies some software-internal structures in a way
 that makes it impossible to undo.



 So, we have to prevent that somebody goes into the system control
 panel,
 selects the module, and presses uninstall.



 Can we do that using WiX?




---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

  DISCLAIMER 

 Please consider the environment before printing this e-mail.

 This e-mail has been scanned for all known virus's but this is not a
 confirmation it is virus free.

 This is an e-mail from EIC Limited (Company Reg: 1086295). The
contents
 of this e-mail are confidential. EIC Limited do not accept
 responsibility for the accuracy or completeness of the contents of
this
 e-mail as it has been transmitted over a public network. If you
receive
 this e-mail in error please accept our apology. If this is the case we
 would be obliged if you would contact the sender and then delete this
 e-mail.

 THIS E-MAIL AND / OR ANY REPLIES TO IT, AND ANY ATTACHMENTS MAY BE
 INTERCEPTED, COPIED OR MONITORED BY EIC LIMITED FOR THE PURPOSE OF
 MONITORING OR KEEPING RECORD OF ITS BUSINESS AND FOR THE PURPOSES SET
 OUT IN THE TELECOMMUNICATIONS (LAWFUL BUSINESS PRACTICES)
(INTERCEPTION
 OF COMMUNICATIONS) REGULATIONS 2000.

 All statements made in this e-mail are subject to contract. The
 contents are not to be regarded as a contractual offer or acceptance.
 The sender is not authorised to bind EIC Limited.

 The views expressed in this e-mail are those of the sender and not
 necessarily those of EIC Limited.

  DISCLAIMER 



---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 DISCLAIMER 

Please consider the environment before printing this e-mail.

This e-mail has been scanned for all known virus's but this is not a 
confirmation it is virus free.

This is an e-mail from EIC Limited (Company Reg: 1086295). The contents of this 
e-mail are confidential. EIC Limited do not accept responsibility for the 
accuracy or completeness of the contents of this e-mail as it has

Re: [WiX-users] how to use heat to harvest VS projects

2010-04-01 Thread Neil Sleightholm

I will double check again but no I don't think they are.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com 
 



From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Thu 01/04/2010 01:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects



On 3/31/2010 8:41 AM, Neil Sleightholm wrote:
 Afraid not that only gets the primary output not referenced assemblies.
   

Aren't they in the content output group?

--
sig://boB
http://joyofsetup.com/


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Show Dialog from Custom Action

2010-04-01 Thread Sagar1111


Thanks for the reply akash.
I tried your way. but it is not working.
I am not able to navigate to next dialog on the click of a button in child
Dialogbox.

Sagar
-- 
View this message in context: 
http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836192.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Crash in Votive project build

2010-04-01 Thread John Aldridge

I have a Votive(MSI) project in Visual Studio which sometimes crashes 
right at the end of the build with the traceback

 Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] 
 arguments, SignatureStruct sig, MethodAttributes methodAttributes, 
 RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] 
 arguments, Signature sig, MethodAttributes methodAttributes, 
 RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags 
 invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean 
 skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags 
 invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at 
 Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThread(Object
  parameters)

I'm running

   Microsoft Visual Studio 2008 (Version 9.0.30729.1 SP)
   Windows Installer XML Toolset 3.0.5419.0

and I'm at a bit of a loss to know how to produce a useful bug report, 
or even who to send it to.

Any advice?

-- 
Cheers,
John

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

2010-04-01 Thread Richard Horsley

If it needs to be independent and not part of an overall upgrade then no, msp 
is not the solution for you. Unfortunately im not entirely sure that there IS a 
way of doing what you want without there being a way of the user removing the 
msi using the control panel. The only other thing you could do is have the 
installer create shared files as well as the installed product and make one of 
these an .inf file that contains the installed information that your support 
desk can check to see if the product was EVER installed.

Richard Horsley

-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: 01 April 2010 11:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Prevent deinstallation

Well, the problem is actually less that we want to prevent *files* from
getting removed (the module itself is not a file but a once-run
proprietary script that removes itself as soon as it successfully
terminated) but that we want to prevent (a) the uninstall button
produces any kind of error message (e. g. it does not find the
self-erased file), and (b) our hotline falls into a trap when checking
for installed modules using the system control panel, not seeing the
module anymore there.

Also, the modules are only dependent of the main product, but must be
independent of other modules.

So this sounds as if .msp is *not* the solution then?

 -Original Message-
 From: Richard Horsley [mailto:richard.hors...@eicltd.com]
 Sent: Donnerstag, 1. April 2010 12:05
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Prevent deinstallation

 Theoretically yes, they will be able to remove the patch from
Programs
 and Features if they click on View installed updates, however, if
 you create the patch correctly, removing it will not actually remove
 the patched files. I have a patch process that works in this way. It
 should be noted though, that if you create any further patches that
 rely on the original being installed first, the user will have to be
 aware of the upgrade path.

 -Original Message-
 From: Markus Karg [mailto:k...@quipsy.de]
 Sent: 01 April 2010 10:58
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Prevent deinstallation

 In theorey we could, but:

 Will this solve the problem?

 Will the user be able to see that the module was installed?

  -Original Message-
  From: Richard Horsley [mailto:richard.hors...@eicltd.com]
  Sent: Donnerstag, 1. April 2010 11:42
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Prevent deinstallation
 
  Could you create an .msp to patch the original installer to add
these
  files?
 
  -Original Message-
  From: Markus Karg [mailto:k...@quipsy.de]
  Sent: 01 April 2010 10:30
  To: General discussion for Windows Installer XML toolset.
  Subject: [WiX-users] Prevent deinstallation
 
  We have to write a .msi to install modules into a preinstalled
  software.
 
 
 
  The problem is that once the module is installed, it can never get
  uninstalled, as it modifies some software-internal structures in a
 way
  that makes it impossible to undo.
 
 
 
  So, we have to prevent that somebody goes into the system control
  panel,
  selects the module, and presses uninstall.
 
 
 
  Can we do that using WiX?
 
 
 
 

---
  ---
  Download Intel#174; Parallel Studio Eval
  Try the new software tools for yourself. Speed compiling, find bugs
  proactively, and fine-tune applications for parallel performance.
  See why Intel Parallel Studio got high marks during beta.
  http://p.sf.net/sfu/intel-sw-dev
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
   DISCLAIMER 
 
  Please consider the environment before printing this e-mail.
 
  This e-mail has been scanned for all known virus's but this is not a
  confirmation it is virus free.
 
  This is an e-mail from EIC Limited (Company Reg: 1086295). The
 contents
  of this e-mail are confidential. EIC Limited do not accept
  responsibility for the accuracy or completeness of the contents of
 this
  e-mail as it has been transmitted over a public network. If you
 receive
  this e-mail in error please accept our apology. If this is the case
 we
  would be obliged if you would contact the sender and then delete
this
  e-mail.
 
  THIS E-MAIL AND / OR ANY REPLIES TO IT, AND ANY ATTACHMENTS MAY BE
  INTERCEPTED, COPIED OR MONITORED BY EIC LIMITED FOR THE PURPOSE OF
  MONITORING OR KEEPING RECORD OF ITS BUSINESS AND FOR THE PURPOSES
SET
  OUT IN THE TELECOMMUNICATIONS (LAWFUL BUSINESS PRACTICES)
 (INTERCEPTION
  OF COMMUNICATIONS) REGULATIONS 2000.
 
  All statements made in this e-mail are subject to contract. The
  contents are not to be

Re: [WiX-users] Show Dialog from Custom Action

i was not saying anythin about child dialog..

you custom dialog will be another andependent dialog...

1. lets say that you have a dialogA on click on next you are callin c# CA
2. no need to call any C# CA instead call another Dialog..say DialogB on
NEXT of it (which is your custom dialog) with OK and CANCEL buttons on it.
3. if some one clicks on the OK button then you can navigate to the next
dialog..say DialogC
4. if some one click CANCEL.. then you can navigate back to the DialogA.


dint u tried this way ? ...

or in place of new Dialog... you can use SPAWN DIALOG as well. as per ur
business needs



On Thu, Apr 1, 2010 at 3:43 PM, Sagar sagarkavitak...@gmail.com wrote:


 Thanks for the reply akash.
 I tried your way. but it is not working.
 I am not able to navigate to next dialog on the click of a button in child
 Dialogbox.

 Sagar
 --
 View this message in context:
 http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836192.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
Cheers,
Akash
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Show Dialog from Custom Action

if you need help about how to use the spawn dialog..then you have to look
into my blog here http://akash-bhatia.blogspot.com/.
i have used the spawn dialog to populate the list of SQL servers on the
network...



On Thu, Apr 1, 2010 at 5:25 PM, akash bhatia 911ak...@gmail.com wrote:

 i was not saying anythin about child dialog..

 you custom dialog will be another andependent dialog...

 1. lets say that you have a dialogA on click on next you are callin c# CA
 2. no need to call any C# CA instead call another Dialog..say DialogB
 on NEXT of it (which is your custom dialog) with OK and CANCEL buttons on
 it.
 3. if some one clicks on the OK button then you can navigate to the next
 dialog..say DialogC
 4. if some one click CANCEL.. then you can navigate back to the DialogA.


 dint u tried this way ? ...

 or in place of new Dialog... you can use SPAWN DIALOG as well. as per
 ur business needs



 On Thu, Apr 1, 2010 at 3:43 PM, Sagar sagarkavitak...@gmail.comwrote:


 Thanks for the reply akash.
 I tried your way. but it is not working.
 I am not able to navigate to next dialog on the click of a button in child
 Dialogbox.

 Sagar
 --
 View this message in context:
 http://n2.nabble.com/Show-Dialog-from-C-Custom-Action-tp4823643p4836192.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




 --
 Cheers,
 Akash




-- 
Cheers,
Akash
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] First run notepad with my.cfg and only then start the service

Hi all,

I install along with my application:
1) a service that starts and stops my application as needed
2) a conf file that contains actually the user data and that will be 
shown to the user to modify as needed (I give the user the chance to 
change it by running notepad.exe with my conf file during installing)

The problem is that in my code the service I install starts _before_ the 
user had the chance to modify the conf file. What I would like is:
1) first the user gets the chance to change the conf file (run 
notepad.exe with the conf file)
2) only afterward start the service


[code]
Component Id=MyService.exe Guid=GUID
File Id=MyService.exe Source=MyService.exe Name=MyService.exe 
KeyPath=yes Checksum=yes /
ServiceInstall Id='ServiceInstall' DisplayName='MyService' 
Name='MyService' ErrorControl='normal' Start='auto' Type='ownProcess' 
Vital='yes'/
ServiceControl Id='ServiceControl' Name='MyService' Start='install' 
Stop='both' Remove='uninstall'/
/Component

Component Id=my.conf Guid= NeverOverwrite=yes
File Id=my.cfg Source=my.cfg_template Name=my.cfg KeyPath=yes /
/Component

[...]

Property Id=NOTEPADNotepad.exe/Property
CustomAction Id=LaunchConfFile Property=NOTEPAD 
ExeCommand=[INSTALLDIR]my.cfg Return=ignore Impersonate=no 
Execute=deferred/
!--Run only on installs--
InstallExecuteSequence
Custom Action='LaunchConfFile' Before='InstallFinalize'(NOT Installed) 
AND (NOT UPGRADINGPRODUCTCODE)/Custom
/InstallExecuteSequence
[/code]

What am I doing wrong in the above code and how could I change it in 
order to achieve what I need? (first run notepad with my conf file and 
then start the service).

TIA,
Viv

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] read a file + advertise

2010-04-01 Thread Castro, Edwin G. (Hillsboro)

Thinking out loud:

I would probably use a RegistrySearch to set the properties in question from 
the registry. I think these execute prior to LaunchConditions and will leave 
the properties blank *if* the values _do not_ exist in the registry.

I would then code a custom action that reads the xml file and sets properties 
that still do not have values. (Always prefer what is already in the registry.) 
I would schedule this custom action prior to LaunchConditions and add a few 
LaunchConditions that check the properties to have values. (Fail the installer 
if the properties do not have values either from the registry or the xml file.)

I would then have a component for each registry value that sets the property 
values in the registry.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


 -Original Message-
 From: lewisv [mailto:le...@nitorco.com]
 Sent: Wednesday, March 31, 2010 7:38 PM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] read a file + advertise
 
 
 Ok, i can save the data that is in my xml in the registry. But i will
 need to
 do that only the first time.
 How do i determine, if this is a first time install ( where i need to
 read
 the xml file) for an advertise install where i need to read the
 registry.
 
 Should i just have my custom action check the registry first? If i do
 that,
 what will happen on an uninstall/re-install. I need to to re-read the
 xml
 file then.
 
 Should i always write to the registry also, even if the values are
 already
 there?
 
 --
 View this message in context: http://n2.nabble.com/read-a-file-
 advertise-tp4834153p4834819.html
 Sent from the wix-users mailing list archive at Nabble.com.
 
 ---
 ---
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting MSI Error 1613

My first reaction would be to assume that the error message might actually be 
correct, and the MSI requires MSI version 4.5 or above.  That's in the schema 
of your package (or page count in the MSI file summary info). 

Phil Wilson 

-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:v-sgo...@microsoft.com] 
Sent: Thursday, April 01, 2010 2:07 AM
To: wix-users@lists.sourceforge.net
Cc: Roopendra Gowlikar (HCL Technologies Ltd)
Subject: [WiX-users] Getting MSI Error 1613

HI All,

While doing installation I am getting error # 1613(This installation package 
cannot be installed by the Windows Installer service. you must install a 
Windows service pack that contains a newer version of the Windows Installer 
service.). I am using Windows (r) Installer. V 4.00.6001.0.

Note: Installer was working till yesterday. Suddenly it is throwing this 
error(1613)

Please do needful.

Regards
-Sandeep
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prevent deinstallation

What does this mean: (e. g. it does not find the self-erased file) in 
reference to the uninstall? If the only problem here is that you've installed a 
file, removed it, and now you want to prevent repair then make the Component 
guid null and you can remove it with impunity.

Phil Wilson 



-Original Message-
From: Markus Karg [mailto:k...@quipsy.de] 
Sent: Thursday, April 01, 2010 4:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Prevent deinstallation

Thanks for the tip, but what we are seeking for is a 100% pure MSI
way. :-)

 -Original Message-
 From: Richard Horsley [mailto:richard.hors...@eicltd.com]
 Sent: Donnerstag, 1. April 2010 12:57
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Prevent deinstallation
 
 If it needs to be independent and not part of an overall upgrade then
 no, msp is not the solution for you. Unfortunately im not entirely
sure
 that there IS a way of doing what you want without there being a way
of
 the user removing the msi using the control panel. The only other
thing
 you could do is have the installer create shared files as well as the
 installed product and make one of these an .inf file that contains the
 installed information that your support desk can check to see if the
 product was EVER installed.
 
 Richard Horsley
 
 -Original Message-
 From: Markus Karg [mailto:k...@quipsy.de]
 Sent: 01 April 2010 11:20
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Prevent deinstallation
 
 Well, the problem is actually less that we want to prevent *files*
from
 getting removed (the module itself is not a file but a once-run
 proprietary script that removes itself as soon as it successfully
 terminated) but that we want to prevent (a) the uninstall button
 produces any kind of error message (e. g. it does not find the
 self-erased file), and (b) our hotline falls into a trap when checking
 for installed modules using the system control panel, not seeing the
 module anymore there.
 
 Also, the modules are only dependent of the main product, but must be
 independent of other modules.
 
 So this sounds as if .msp is *not* the solution then?
 
  -Original Message-
  From: Richard Horsley [mailto:richard.hors...@eicltd.com]
  Sent: Donnerstag, 1. April 2010 12:05
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Prevent deinstallation
 
  Theoretically yes, they will be able to remove the patch from
 Programs
  and Features if they click on View installed updates, however, if
  you create the patch correctly, removing it will not actually remove
  the patched files. I have a patch process that works in this way. It
  should be noted though, that if you create any further patches that
  rely on the original being installed first, the user will have to be
  aware of the upgrade path.
 
  -Original Message-
  From: Markus Karg [mailto:k...@quipsy.de]
  Sent: 01 April 2010 10:58
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Prevent deinstallation
 
  In theorey we could, but:
 
  Will this solve the problem?
 
  Will the user be able to see that the module was installed?
 
   -Original Message-
   From: Richard Horsley [mailto:richard.hors...@eicltd.com]
   Sent: Donnerstag, 1. April 2010 11:42
   To: General discussion for Windows Installer XML toolset.
   Subject: Re: [WiX-users] Prevent deinstallation
  
   Could you create an .msp to patch the original installer to add
 these
   files?
  
   -Original Message-
   From: Markus Karg [mailto:k...@quipsy.de]
   Sent: 01 April 2010 10:30
   To: General discussion for Windows Installer XML toolset.
   Subject: [WiX-users] Prevent deinstallation
  
   We have to write a .msi to install modules into a preinstalled
   software.
  
  
  
   The problem is that once the module is installed, it can never get
   uninstalled, as it modifies some software-internal structures in a
  way
   that makes it impossible to undo.
  
  
  
   So, we have to prevent that somebody goes into the system control
   panel,
   selects the module, and presses uninstall.
  
  
  
   Can we do that using WiX?
  
  
  
  
 

---
   ---
   Download Intel#174; Parallel Studio Eval
   Try the new software tools for yourself. Speed compiling, find
bugs
   proactively, and fine-tune applications for parallel performance.
   See why Intel Parallel Studio got high marks during beta.
   http://p.sf.net/sfu/intel-sw-dev
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
  
    DISCLAIMER 
  
   Please consider the environment before printing this e-mail.
  
   This e-mail has been scanned for all

[WiX-users] MSI fails when compiled on a different machine

2010-04-01 Thread Kevin Garman

Hi,

I've got a strange one today. When I compile our app/installer and run
the resulting msi everything works great. When a coworker compiles it
on his machine, the msi he produces fails in my test environment--there
doesn't seem to be any significant differences between our build
environments. Most notable in the install log is:

Action 13:06:22: ConfigureIIsExec. Executing IIS Configuration
MSI (s) (48:64) [13:06:22:133]: Executing op:
CustomActionSchedule(Action=ConfigureIIsExec,ActionType=3073,Source=BinaryData,Target=ConfigureIIsExec,CustomActionData=ConfigureIIs1002100210021002100210021152DirProperties1Access2Authorization2AnonymousUser_1IIsControlledPassword2LogVisits2Index2DefaultDoc1AspDetailedError2HttpExpires1CacheControlMaxAge2CacheControlCustom1NoCustomError2AccessSSLFlags2AuthenticationProviders13webpropGeneral513-21474836480-2147483648-2147483648-2147483648-2147483648-2147483648-214748364843vdpropsStatusWatchWebpage-2147483648-21474836480-2147483648-2147483648statuswatch.aspx-2147483648-2147483648-2147483648-214748364842100210021122Name1Isolation2AllowSessions2SessionTimeout2Buffer2ParentPaths2DefaultScript1ScriptTimeout2ServerDebugging2ClientDebugging2AppPool_1Application13StatusWatch_WebApp_SW2_L3Server0-2147483648-2147483648-2147483648-2147483648-2147483648-2147483648-2147483648webappStatusWatch43StatusWatch_SW2_
MSI (s) (48:98) [13:06:22:149]: Invoking remote custom action. DLL: C:
\WINNT\Installer\MSID7.tmp, Entrypoint: ConfigureIIsExec
ConfigureIIsExec: Error 0x80070006: Failed to format string
ConfigureIIsExec: Error 0x80070006: Failed to get Description for Web
ConfigureIIsExec: Error 0x80070006: failed while processing WebSites
Error 26002. Failed while processing WebSites. (-2147024890 )
MSI (s) (48!60) [13:08:02:964]: Product: StatusWatch Server 1.0.4.0
(SW2_L3Server) -- Error 26002. Failed while processing WebSites.
(-2147024890 )

I know this isn't much information, but I'm hoping someone can perhaps
ask some questions that may get me looking in the right place.

Thanks much,
Kevin

Re: [WiX-users] MSI fails when compiled on a different machine

2010-04-01 Thread Kevin Garman

Sorry, I spoke too soon. We have different wix versions.

On Thu, 2010-04-01 at 11:52 -0500, Kevin Garman wrote:

Hi,

I know this isn't much information, but I'm hoping someone can perhaps
ask some questions that may get me looking in the right place.

Thanks much,
Kevin

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to create web app/service on IIS 7 with WiX 3.0

2010-04-01 Thread Mike Carlson (DEV DIV)

If you schedule your deferred custom action after both ConfigureIIs and 
ConfigureIIs7, and it is deferred, then at the time it's run, it should be run 
after the websites are created.

Note the log can be somewhat confusing at first when dealing with deferred 
custom actions because deferred custom actions' actual execution is deferred to 
the InstallExecute, InstallExecuteAgain, or InstallFinalize sequences. I 
don't know if this could be causing some of the confusion about when the custom 
actions are executed.

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Thursday, April 01, 2010 2:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX 3.0

I think I still need one, I couldn't find these actions in standard IIS
extension. Currently my custom actions is:
1) AspMaxRequestEntityAllowed and AspAllowSessionState on created
website
2) Enable32bitAppOnWin64 (enables it) on application pools
3) Setting ManagedRuntimeVersion on created application pool

My CA was deferred (not commit) action in the beginning and I made it to
be executed after ConfigureIIs (in Wix 3.5 I changed to be after
ConfigureIIs7), but from log file I can see that website was not created
after ConfigureIIs7 action. Can you please specify name after which IIS
action I should execute mine custom action?


-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com] 
Sent: Monday, March 29, 2010 8:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

Regarding those errors, you can ignore them. In fact, feel free to file
a bug so we can make those errors appear less scary, because they aren't
really of concern, it just means Wow64 API's aren't available on your
OS.

Regarding the custom action, do you really need one? Can you rely on
standard IIS extension functionality? Introducing your own custom action
is a classic way to drive up installation failure rates, break rollback
support, cause problems during uninstall, etc. If the functionality you
want doesn't exist but it is functionality that makes sense for the
community, a feature request would be nice.

To answer your scheduling question, the real IIS work occurs before
commit, during the install script (deferred). The commit CA is just to
delete a file used to rollback state. If you really do need a custom
action, you should run your CA deferred too, but after the IIS custom
action. 

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Friday, March 26, 2010 8:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

Oops. My mistake. I had a typo in my wxs project file. I got successful
installation with website created on both (2008 64bit and 32bit), but on
windows 2008 64 bit I still got some error messages in log file:

StartIIS7ConfigTransaction:  Error 0x80070001: Failed to disable WOW64.
CommitIIS7ConfigTransaction:  Error 0x80070001: Failed to disable WOW64.

But now I have another problem, I had custom action which rely on
created website (doing some modifications to website which is not
supported on iis wix extension) and on sequence it was after
ConfigureIIs custom action, but now as I understood website created in
commit custom action. What is the best approach now to execute my own
custom action? How to schedule it after creation of website?

-Original Message-
From: Igor Paniushkin [mailto:ipaniush...@sdl.com] 
Sent: Friday, March 26, 2010 4:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to create web app/service on IIS 7 with WiX
3.0

I already tried the same on new build 3.5.1526 and I still can't create
website (tried on Windows 2008 32 bit machine). Next error messages in
log file:

Action start 16:09:59: InstallFinalize.
StartIIS7ConfigTransaction: Error 0x80070001: Failed to disable WOW64.
WriteIIS7ConfigChanges: Error 0x80070002: IIS: site not found for create
VDir
WriteIIS7ConfigChanges: Error 0x80070002: Failed to configure IIS VDir.
WriteIIS7ConfigChanges: Error 0x80070002: WriteIIS7ConfigChanges Failed.
Action ended 16:10:00: InstallFinalize. Return value 3.
RollbackIIS7ConfigTransaction: Error 0x80070001: Failed to disable
WOW64.
Action ended 16:10:00: INSTALL. Return value 3.
Action ended 16:10:00: ExecuteAction. Return value 3.
Action ended 16:10:00: INSTALL. Return value 3.
=== Logging stopped: 3/26/2010 16:10:00 ===
MSI (c) (F8:44) [16:10:00:387]: Product: ConfigureIIs7Test --
Installation
failed.

MSI (c) (F8:44) [16:10:00:402]: Windows Installer installed the product.
Product Name: ConfigureIIs7Test. Product Version: 1.0.0.0. Product
Language: 1033. Installation success or error status: 1603.

-Original Message-
From: Igor Paniushkin

[WiX-users] Error code:0xC00E5201 - Failed to create patch.

2010-04-01 Thread Carolina Zuqueto Amaral

Hi,

I used the example from this site 
(http://wix.sourceforge.net/manual-wix3/patch_building.htm) to create the 
patch. But when I generated the MSP the following error occurred: Failed to 
create patch. Error code: 0xC00E5201.
How can I resolve it?


Log:

* Log starting: 2010-04-01 15:53:23 *

  INFO: Using Pcp Path: C:\Dev\usr\carolina.amaral\Patch 
-PatchCreation\Patch\Patch.pcp.
  INFO: Using Temporary Directory: 
C:\Users\CAROLI~1.AMA\AppData\Local\Temp\~pcw_tmp.tmp.
  INFO: Passed all of the main control parameter validation to PatchWiz, now 
calling the next 5 phases.
  INFO: Phase I: Entered validation and processing phase.
  INFO:  Validation of Pcp.
  INFO:  MinimumRequiredMsiVersion is 100.
  INFO:  SEQUENCE_DATA_GENERATION_DISABLED is 0.
  INFO:  ListOfPatchGUIDsToReplace is .
  INFO:  ListOfTargetProductCodes is .
  INFO:  MsiFileToUseToCreatePatchTables is .
  INFO:  PatchGUID is {224C316C-5894-4771-BABF-21A3AC1F75FF}.
  INFO:  PatchOutputPath is C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log.
  INFO:  PatchSourceList is .
  INFO:  PATCH_CACHE_DIR is .
  INFO:  AllowDualPatch is 0.
  INFO:  AllowProductCodeMismatches is 0.
  INFO:  AllowProductVersionMajorMismatches is 0.
  INFO:  ApiPatchingSymbolFlags is 0.
  INFO:  DontRemoveTempFolderWhenFinished is 0.
  INFO:  IncludeWholeFilesOnly is 1.
  INFO:  PATCH_CACHE_ENABLED is 0.
  INFO:  OptimizePatchSizeForLargeFiles is 0.
  INFO:  META_DATA_GENERATION_DISABLED is 0.
  INFO:  TrustMsi is 0.
  INFO:  AllowLaxValidationFlags is 0.
  INFO: Phase III:  Entering Prepare Files.
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\Sample.txt C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\Sample.txt...
INFO Comparing bytes...
INFO Different content...
INFO File Key: SampleFile is modified
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\WpfControlLibrary.dll C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\WpfControlLibrary.dll...
INFO Comparing bytes...
  WARNING: File versions for target file: C:\Sample\1.0\admin\PFiles\Patch 
Sample Directory\WpfControlLibrary.dll and upgrade file: 
C:\Sample\1.1\admin\PFiles\Patch Sample Directory\WpfControlLibrary.dll are 
same, while the files itself are different.
INFO Different content...
INFO File Key: WpfControlLibraryDLL is modified
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\WpfUpdatableApp.exe C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\WpfUpdatableApp.exe...
INFO Comparing bytes...
  WARNING: File versions for target file: C:\Sample\1.0\admin\PFiles\Patch 
Sample Directory\WpfUpdatableApp.exe and upgrade file: 
C:\Sample\1.1\admin\PFiles\Patch Sample Directory\WpfUpdatableApp.exe are same, 
while the files itself are different.
INFO Different content...
INFO File Key: WpfUpdatableAppEXE is modified
  INFO: Phase IV: Entering Generate Payload.
  INFO: Phase V:   Entering Generate MSP.
  ERROR: Unable to create patch 'C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log'.
  ERROR:  The Last Error Received is: 1631
  ERROR:  The Last Error Received is: 1: 2203 2: C:\Program 
Files\Microsoft SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log 3: 
-2147287037
  INFO: Temporary folder is about to be cleaned out and deleted: 
C:\Users\CAROLI~1.AMA\AppData\Local\Temp\~pcw_tmp.tmp
  ERROR: Internal PatchWiz Error occurred.
  ERROR:  The Last Error Received is: -1072803578



Thanks,

Carolina Zuqueto Amaral
carolina.ama...@conv.com.brmailto:carolina.ama...@conv.com.br
tel +55 21 2494-5476
cel +55 21 9524-7186




Confidencialidade: A informa??o contida nesta mensagem de e-mail, incluindo 
quaisquer anexos, ? confidencial e est? reservada apenas ? pessoa ou entidade 
para a qual foi endere?ada. Se voc? n?o ? o destinat?rio ou a pessoa 
respons?vel por encaminhar esta mensagem ao destinat?rio, voc? est?, por meio 
desta, notificado que n?o dever? rever, retransmitir, imprimir, copiar, usar ou 
distribuir esta mensagem de e-mail ou quaisquer anexos. Caso voc? tenha 
recebido esta mensagem por engano, por favor, contate o remetente imediatamente 
e apague esta mensagem de seu computador ou de qualquer outro banco de dados. 
Grato.

Confidentiality Notice: The information contained in this email message, 
including any attachment, is confidential and is intended only for the person 
or entity to which it is addressed. If you are neither the intended recipient 
nor the employee or agent responsible for delivering this message to the

Re: [WiX-users] Conditions for Uninstall/Remove Only

2010-04-01 Thread little.forest

Thanks Sanjay.


This is great. Especially there is a table - much clearer.




From: Sanjay Rao s...@noida.interrasystems.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Wed, March 31, 2010 11:02:18 PM
Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only

try out this one.
(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL)

for more details u can see
http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi

-Sanjay


little.forest wrote:
 How can I create conditions for a custom action to run for Uninstall/Remove 
 only?


 If I use condition 'Installed' then the CA runs in Repair mode.
 If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it 
 doesn't run in Uninstall/Remove either.

 Thanks.


   __
 Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
 favourite sites. Download it now
 http://ca.toolbar.yahoo.com.
 --
 Download Intel® Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



  




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  __
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
favourite sites. Download it now
http://ca.toolbar.yahoo.com.
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode

2010-04-01 Thread little.forest

Thanks Bob,


You're right. They don't support MSI.




From: Bob Arnson b...@joyofsetup.com
To: wix-users@lists.sourceforge.net
Sent: Wed, March 31, 2010 5:22:35 PM
Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get  
Error 2836 in Repair mode

On 3/31/2010 2:31 PM, little.forest wrote:
 Actually we asked the vendor first, but they told us sorry, we don't support 
 Wix...


They don't have to support WiX, just MSI.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  __
Make your browsing faster, safer, and easier with the new Internet Explorer® 8. 
Optimized for Yahoo! Get it Now for Free! at 
http://downloads.yahoo.com/ca/internetexplorer/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error code:0xC00E5201 - Failed to create patch.

I'm wondering if there's a parameter problem in there somewhere. You have a 
-PatchCreation parameter, and that -P is turning into the MsiMsp equivalent of 
-p path and you're getting folders called \atchCreation and errors in there 
like -2147287037, which is 0x80030003 The path %1 could not be found. 

Phil Wilson 


-Original Message-
From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br] 
Sent: Thursday, April 01, 2010 12:07 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] Error code:0xC00E5201 - Failed to create patch.

Hi,

I used the example from this site 
(http://wix.sourceforge.net/manual-wix3/patch_building.htm) to create the 
patch. But when I generated the MSP the following error occurred: Failed to 
create patch. Error code: 0xC00E5201.
How can I resolve it?


Log:

* Log starting: 2010-04-01 15:53:23 *

  INFO: Using Pcp Path: C:\Dev\usr\carolina.amaral\Patch 
-PatchCreation\Patch\Patch.pcp.
  INFO: Using Temporary Directory: 
C:\Users\CAROLI~1.AMA\AppData\Local\Temp\~pcw_tmp.tmp.
  INFO: Passed all of the main control parameter validation to PatchWiz, now 
calling the next 5 phases.
  INFO: Phase I: Entered validation and processing phase.
  INFO:  Validation of Pcp.
  INFO:  MinimumRequiredMsiVersion is 100.
  INFO:  SEQUENCE_DATA_GENERATION_DISABLED is 0.
  INFO:  ListOfPatchGUIDsToReplace is .
  INFO:  ListOfTargetProductCodes is .
  INFO:  MsiFileToUseToCreatePatchTables is .
  INFO:  PatchGUID is {224C316C-5894-4771-BABF-21A3AC1F75FF}.
  INFO:  PatchOutputPath is C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log.
  INFO:  PatchSourceList is .
  INFO:  PATCH_CACHE_DIR is .
  INFO:  AllowDualPatch is 0.
  INFO:  AllowProductCodeMismatches is 0.
  INFO:  AllowProductVersionMajorMismatches is 0.
  INFO:  ApiPatchingSymbolFlags is 0.
  INFO:  DontRemoveTempFolderWhenFinished is 0.
  INFO:  IncludeWholeFilesOnly is 1.
  INFO:  PATCH_CACHE_ENABLED is 0.
  INFO:  OptimizePatchSizeForLargeFiles is 0.
  INFO:  META_DATA_GENERATION_DISABLED is 0.
  INFO:  TrustMsi is 0.
  INFO:  AllowLaxValidationFlags is 0.
  INFO: Phase III:  Entering Prepare Files.
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\Sample.txt C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\Sample.txt...
INFO Comparing bytes...
INFO Different content...
INFO File Key: SampleFile is modified
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\WpfControlLibrary.dll C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\WpfControlLibrary.dll...
INFO Comparing bytes...
  WARNING: File versions for target file: C:\Sample\1.0\admin\PFiles\Patch 
Sample Directory\WpfControlLibrary.dll and upgrade file: 
C:\Sample\1.1\admin\PFiles\Patch Sample Directory\WpfControlLibrary.dll are 
same, while the files itself are different.
INFO Different content...
INFO File Key: WpfControlLibraryDLL is modified
INFO Comparing Files: C:\Sample\1.0\admin\PFiles\Patch Sample 
Directory\WpfUpdatableApp.exe C:\Sample\1.1\admin\PFiles\Patch Sample 
Directory\WpfUpdatableApp.exe...
INFO Comparing bytes...
  WARNING: File versions for target file: C:\Sample\1.0\admin\PFiles\Patch 
Sample Directory\WpfUpdatableApp.exe and upgrade file: 
C:\Sample\1.1\admin\PFiles\Patch Sample Directory\WpfUpdatableApp.exe are same, 
while the files itself are different.
INFO Different content...
INFO File Key: WpfUpdatableAppEXE is modified
  INFO: Phase IV: Entering Generate Payload.
  INFO: Phase V:   Entering Generate MSP.
  ERROR: Unable to create patch 'C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log'.
  ERROR:  The Last Error Received is: 1631
  ERROR:  The Last Error Received is: 1: 2203 2: C:\Program 
Files\Microsoft SDKs\Windows\v6.0A\Bin\atchCreation\Patch\Patch.log 3: 
-2147287037
  INFO: Temporary folder is about to be cleaned out and deleted: 
C:\Users\CAROLI~1.AMA\AppData\Local\Temp\~pcw_tmp.tmp
  ERROR: Internal PatchWiz Error occurred.
  ERROR:  The Last Error Received is: -1072803578



Thanks,

Carolina Zuqueto Amaral
carolina.ama...@conv.com.brmailto:carolina.ama...@conv.com.br
tel +55 21 2494-5476
cel +55 21 9524-7186




Confidencialidade: A informa??o contida nesta mensagem de e-mail, incluindo 
quaisquer anexos, ? confidencial e est? reservada apenas ? pessoa ou entidade 
para a qual foi endere?ada. Se voc? n?o ? o destinat?rio ou a pessoa 
respons?vel por encaminhar esta mensagem ao destinat?rio, voc? est?, por meio 
desta, notificado que n?o dever? rever, retransmitir,

[WiX-users] MSI error 1935 (0x80070003) installing shared Win32 assembly - but only when installer includes DifxApp driver component

2010-04-01 Thread Stephen Paterson

I'm using WiX 3.0.5419.0 to generate an MSI that installs ...
1)  an MFC app
2)  the required VC9 merge modules
3)   a Win32 shared SxS assembly
4)  a DifxApp driver package.

I can build an installer that will successfully install and uninstall
the app and the driver
I can build an installer that will successfully install and uninstall
the app and the assembly.

However, when both the assembly and the driver are included the
installer fails shortly after the driver update completes and rolls
back.

 MSI (s) (60:80) [23:30:06:551]: Assembly Error:The system cannot find
the path specified.

I have MSI logs and source... If this sounds like something you might
know about let me know what you'd like to see, I'd really appreciate the
help.

Cheers,
Steve

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MSI error 1935 (0x80070003) installing shared Win32 assembly - but only when installer includes DifxApp driver component