Re: [WiX-users] How to debug?

2013-11-07 Thread Nick Ramirez 
Some things to try:

* Is the MSI failing? There ought to be separate MSI log files in the same
directory, so check those for any errors.

* Check the bootstrapper's log file to see how far it gets, may give you a
clue about where it's failing
* If you want to step into your managed BA, put a thread sleep in the code
to give yourself enough time to attach a debugger to the process
* If all else fails, try popping up some MessageBoxes do debug
* Are you seeing your custom UI load at all? If you are, that's very good!
Then you know you're UI is at least getting loaded up by Burn. If not, then
double check everything (config files, bundle.wxs, your bootstrapper C#
file, etc.)



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-tp7590356p7590374.html
Sent from the wix-users mailing list archive at Nabble.com.

--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-09-06 Thread Rob Mensching 
I like to use the AssertSz(FALSE, "debug XxxCA here"); from dutil.h. The
resulting dialog gives lots of information to make it easy to attach.

On Wed, Aug 25, 2010 at 2:00 PM, gapearce  wrote:

>
> I found it pretty easy and straightforward using VS2008 to attach to a
> setup
> program awaiting user input from a message box.  It was very easy...
>
> This MSND article touches on it -
> http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx -
>
> just attach to the process that has your messagebox title in it.
>
> add a breakpoint in VS2008 on the line of code in the dll after the
> messagebox.
> Of course the code has to match the dll...
>
> Respond to the button in the messagebox.  It will close and stop on the
> line
> in the debugger.
>
> You do have to remember to remove / disable the message boxes as stated
> above...when you ship, or when they become so annoying that you can't take
> it any more.
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-CustomAction-DLL-tp5458781p5463104.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-08-25 Thread gapearce 

I found it pretty easy and straightforward using VS2008 to attach to a setup
program awaiting user input from a message box.  It was very easy...

This MSND article touches on it -
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx - 

just attach to the process that has your messagebox title in it.  

add a breakpoint in VS2008 on the line of code in the dll after the
messagebox.  
Of course the code has to match the dll...

Respond to the button in the messagebox.  It will close and stop on the line
in the debugger.

You do have to remember to remove / disable the message boxes as stated
above...when you ship, or when they become so annoying that you can't take
it any more.
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-CustomAction-DLL-tp5458781p5463104.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-08-25 Thread jhennessey 

I set the environment variable MsiBreak for native code (
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx ) and
MMsiBreak for managed code (
http://blog.torresdal.net/2008/10/26/WiXAndDTFDebugAManagedCustomActionAndHowToGenerateAnMSILog.aspx
http://blog.torresdal.net/2008/10/26/WiXAndDTFDebugAManagedCustomActionAndHowToGenerateAnMSILog.aspx
) to the name of the custom action to debug. This way you don't have to mess
with adding message boxes.

As was already mentioned, sometimes setting environment variables doesn't
work until you reboot so what I do is launch a command prompt, set the
variable (using the SET command), then launch the install from the command
prompt (this always works for me).
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-CustomAction-DLL-tp5458781p5462437.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-08-25 Thread Wilson, Phil 
You may be able to use the MSI logging if you want to trace data into the MSI 
log file. Another cheap trick I've used is to set interestingly named 
properties to whatever I want to see the values of. The setting of these 
properties and values is logged. 

Phil Wilson 

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: Tuesday, August 24, 2010 5:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug CustomAction DLL

I think I recall you sometimes have to reboot and/or restart the Msiexec 
service 
after setting MsiBreak because the Service Control Manager doesn't get the env 
update.  I haven't used it in a long time so I could be wrong.  on the C#/DTF 
side I tend to use MessageBox during intitial development and almost never need 
to debug a custom action later in it's life cycle.
 



- Original Message 
From: Tony Juricic 
To: General discussion for Windows Installer XML toolset. 

Sent: Tue, August 24, 2010 5:00:47 PM
Subject: Re: [WiX-users] How to debug CustomAction DLL

Good ole' MessageBox is the most reliable way to debug C/C++ CAs that I found. 
You may be able to set the breakpoint after the MessageBox and then attach to 
the running msiexec process. 


-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL

Dear Wix Experts:

We have a CustomAction DLL written in C. How to debug it?

There are a few posts about it:
Post1: 
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/


Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx 
Post3: http://msdn.microsoft.com/en-us/library/aa368264(VS.85).aspx 

I tried it in Windows 7. I did set MsiBreak, but that famous "message box" 
never 

showed up. So I tried it in XP, the "message box" showed up. It says "To debug 
your custom action, attach your debugger to process 5632(0x1600) and press OK". 
I opened Windbg.

Post1 says "attach the process", Post2 says "Open Executable...". I tried both, 
neither works for me. In both cases, I got "*** ERROR: Symbol file could not be 
found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll - 
ntdll!DbgBreakPoint: 7c90120e cc              int    3" in Windbg.

Questions:
1. What's the problem here?
2. Should I attach process? Or should I "Open Executable..."?
3. If I should attach process, why it doesn't work?
4. If I should "Open Executable...", what the "File name" and "Arguments" 
fields 

should be? For example, the "File name" should be "C:\Temp\MyApp.msi" or 
"C:\Windows\system32\msiexec.exe"? How about arguments? Should it be "/i 
C:\Temp\MyApp.msi"?
5. Why it doesn't work in Windows 7?

If you even debug DLL CustomAction, pls let me know.

Thanks!



TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is 
addressed and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please contact the 
sender and delete the material from any computer.

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___

Re: [WiX-users] How to debug CustomAction DLL

2010-08-25 Thread dB . 
If you're developing a custom action (or many), you might save yourself a lot 
of time in the future by investing a bit upfront into unit testing your CA. 
This would allow you to invoke it from CPPUNIT, assert conditions, and obvious 
debug it without message boxes.

There's a post about the approach here -  
http://code.dblock.org/ShowPost.aspx?id=7 - and it's fully implemented in 
AppSecInc. community MSI extensions - http://msiext.codeplex.com. 

I haven't had to stick a message box in a CA for a while to debug it "live" :)

dB. @ dblock.org 
Moscow|Geneva|Seattle|New York


-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL

Dear Wix Experts:

We have a CustomAction DLL written in C. How to debug it?

There are a few posts about it:
Post1: 
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/
 
Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx 
Post3: http://msdn.microsoft.com/en-us/library/aa368264(VS.85).aspx 

I tried it in Windows 7. I did set MsiBreak, but that famous "message box" 
never 
showed up. So I tried it in XP, the "message box" showed up. It says "To debug 
your custom action, attach your debugger to process 5632(0x1600) and press OK". 
I opened Windbg.

Post1 says "attach the process", Post2 says "Open Executable...". I tried both, 
neither works for me. In both cases, I got "*** ERROR: Symbol file could not be 
found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll - 
ntdll!DbgBreakPoint: 7c90120e cc  int 3" in Windbg.

Questions:
1. What's the problem here?
2. Should I attach process? Or should I "Open Executable..."?
3. If I should attach process, why it doesn't work?
4. If I should "Open Executable...", what the "File name" and "Arguments" 
fields 
should be? For example, the "File name" should be "C:\Temp\MyApp.msi" or 
"C:\Windows\system32\msiexec.exe"? How about arguments? Should it be "/i 
C:\Temp\MyApp.msi"?
5. Why it doesn't work in Windows 7?

If you even debug DLL CustomAction, pls let me know.

Thanks!

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-08-24 Thread Christopher Painter 
I think I recall you sometimes have to reboot and/or restart the Msiexec 
service 
after setting MsiBreak because the Service Control Manager doesn't get the env 
update.  I haven't used it in a long time so I could be wrong.  on the C#/DTF 
side I tend to use MessageBox during intitial development and almost never need 
to debug a custom action later in it's life cycle.
 



- Original Message 
From: Tony Juricic 
To: General discussion for Windows Installer XML toolset. 

Sent: Tue, August 24, 2010 5:00:47 PM
Subject: Re: [WiX-users] How to debug CustomAction DLL

Good ole' MessageBox is the most reliable way to debug C/C++ CAs that I found. 
You may be able to set the breakpoint after the MessageBox and then attach to 
the running msiexec process. 


-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL

Dear Wix Experts:

We have a CustomAction DLL written in C. How to debug it?

There are a few posts about it:
Post1: 
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/


Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx 
Post3: http://msdn.microsoft.com/en-us/library/aa368264(VS.85).aspx 

I tried it in Windows 7. I did set MsiBreak, but that famous "message box" 
never 

showed up. So I tried it in XP, the "message box" showed up. It says "To debug 
your custom action, attach your debugger to process 5632(0x1600) and press OK". 
I opened Windbg.

Post1 says "attach the process", Post2 says "Open Executable...". I tried both, 
neither works for me. In both cases, I got "*** ERROR: Symbol file could not be 
found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll - 
ntdll!DbgBreakPoint: 7c90120e cc              int    3" in Windbg.

Questions:
1. What's the problem here?
2. Should I attach process? Or should I "Open Executable..."?
3. If I should attach process, why it doesn't work?
4. If I should "Open Executable...", what the "File name" and "Arguments" 
fields 

should be? For example, the "File name" should be "C:\Temp\MyApp.msi" or 
"C:\Windows\system32\msiexec.exe"? How about arguments? Should it be "/i 
C:\Temp\MyApp.msi"?
5. Why it doesn't work in Windows 7?

If you even debug DLL CustomAction, pls let me know.

Thanks!



TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is 
addressed and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please contact the 
sender and delete the material from any computer.

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug CustomAction DLL

2010-08-24 Thread Tony Juricic 
Good ole' MessageBox is the most reliable way to debug C/C++ CAs that I found. 
You may be able to set the breakpoint after the MessageBox and then attach to 
the running msiexec process. 

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL

Dear Wix Experts:

We have a CustomAction DLL written in C. How to debug it?

There are a few posts about it:
Post1: 
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/
 
Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx 
Post3: http://msdn.microsoft.com/en-us/library/aa368264(VS.85).aspx 

I tried it in Windows 7. I did set MsiBreak, but that famous "message box" 
never 
showed up. So I tried it in XP, the "message box" showed up. It says "To debug 
your custom action, attach your debugger to process 5632(0x1600) and press OK". 
I opened Windbg.

Post1 says "attach the process", Post2 says "Open Executable...". I tried both, 
neither works for me. In both cases, I got "*** ERROR: Symbol file could not be 
found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll - 
ntdll!DbgBreakPoint: 7c90120e cc  int 3" in Windbg.

Questions:
1. What's the problem here?
2. Should I attach process? Or should I "Open Executable..."?
3. If I should attach process, why it doesn't work?
4. If I should "Open Executable...", what the "File name" and "Arguments" 
fields 
should be? For example, the "File name" should be "C:\Temp\MyApp.msi" or 
"C:\Windows\system32\msiexec.exe"? How about arguments? Should it be "/i 
C:\Temp\MyApp.msi"?
5. Why it doesn't work in Windows 7?

If you even debug DLL CustomAction, pls let me know.

Thanks!



TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug upgrade problem

2009-11-19 Thread Tom Crozier 
For anyone interested what I was able to do was create a custom action to set 
the ALLUSERS property to 1 and schedule it after FindRelatedProducts. Doing 
this allowed the old version to be located as a per user install then switch 
the new install to be per machine.

-Original Message-
From: Tom Crozier [mailto:tcroz...@rackwise.com] 
Sent: Wednesday, November 18, 2009 8:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug upgrade problem

I didn't see it before but

FindRelatedProducts: current install is per-user.  Related install for product 
'{C1BAE517-464C-4B99-BE0A-660C8210DE33}' is per-machine.

So now my question becomes - Is there a way to perform a major upgrade on an 
install that was previously per-user to per-machine?
Background: The old installer required admin privileges, wrote to the Program 
Files folder but did not set the ALLUSERS property. Now I want to correct this 
during a major upgrade but I'm not sure how.

Thanks - Tom



-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com] 
Sent: Wednesday, November 18, 2009 12:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug upgrade problem

Doesn't the msi verbose log say anything? 

Best regards,
Sebastian Brand

Deployment consultant
E-Mail: sebast...@instyler.com

Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com

On 17.11.2009, at 22:55, Tom Crozier wrote:

> I created an installer that contains 2 Upgrade sections for 2 different 
> products that are installed however when I run the installer it only locates 
> one of them. How do I go about debugging this to find out why the 2nd is not 
> detected by FindRelatedProducts? I did a small test app and this seemed to 
> work fine.
> 
> Thanks
> 
> -  Tom
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.425 / Virus Database: 270.14.67/2506 - Release Date: 11/17/09 
19:26:00

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.425 / Virus Database: 270.14.67/2506 - Release Date: 11/17/09 
19:26:00

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug upgrade problem

2009-11-18 Thread Tom Crozier 
I didn't see it before but

FindRelatedProducts: current install is per-user.  Related install for product 
'{C1BAE517-464C-4B99-BE0A-660C8210DE33}' is per-machine.

So now my question becomes - Is there a way to perform a major upgrade on an 
install that was previously per-user to per-machine?
Background: The old installer required admin privileges, wrote to the Program 
Files folder but did not set the ALLUSERS property. Now I want to correct this 
during a major upgrade but I'm not sure how.

Thanks - Tom



-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com] 
Sent: Wednesday, November 18, 2009 12:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug upgrade problem

Doesn't the msi verbose log say anything? 

Best regards,
Sebastian Brand

Deployment consultant
E-Mail: sebast...@instyler.com

Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com

On 17.11.2009, at 22:55, Tom Crozier wrote:

> I created an installer that contains 2 Upgrade sections for 2 different 
> products that are installed however when I run the installer it only locates 
> one of them. How do I go about debugging this to find out why the 2nd is not 
> detected by FindRelatedProducts? I did a small test app and this seemed to 
> work fine.
> 
> Thanks
> 
> -  Tom
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.425 / Virus Database: 270.14.67/2506 - Release Date: 11/17/09 
19:26:00

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug upgrade problem

2009-11-17 Thread Sebastian Brand (Instyler Software) 
Doesn't the msi verbose log say anything? 

Best regards,
Sebastian Brand

Deployment consultant
E-Mail: sebast...@instyler.com

Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com

On 17.11.2009, at 22:55, Tom Crozier wrote:

> I created an installer that contains 2 Upgrade sections for 2 different 
> products that are installed however when I run the installer it only locates 
> one of them. How do I go about debugging this to find out why the 2nd is not 
> detected by FindRelatedProducts? I did a small test app and this seemed to 
> work fine.
> 
> Thanks
> 
> -  Tom
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug MSI properties?

2008-10-30 Thread Richard 

In article <[EMAIL PROTECTED]>,
Rob Mensching <[EMAIL PROTECTED]>  writes:

> Verbose log file gives you that and with recent Windows Installers
> (v3+?) it' ll even show you when properties change value.

A trick I've employed is to add a "debug" dialog to the UI.  Setting a
property from the command-line enabled a Debug... button on all
dialogs that spawns the debug dialog.  There you can enter formatted
text and have it evaluated as well as scroll through a listbox of
properties to see their values.  Its come in handy on a number of
occasions because your formatted strings are evaluated during the
install session, giving you the ability to prototype Formatted values
and the like.  I don't know if this is something that people would
like to see in the WiX UI templates, but I can see about creating one
if there's interest.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
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] How to debug MSI properties?

2008-10-30 Thread Rob Mensching 
Verbose log file gives you that and with recent Windows Installers (v3+?) it'll 
even show you when properties change value.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 13:43
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug MSI properties?

Our kit has a feature that's depending on
VS90_IDE_VC_PROJECTSYSTEM_INSTALLED being defined.  I'm installing onto a
VMWare image with VS2008 and (only) Visual C++ installed, and the feature
fails to install.  The feature that depends on VS2005 seems to install
properly onto a similarly configured VMWare image with VS2005 and (only)
VC++.

Is there any way I can get a dump of the MSI properties that are defined
during an installation?

Thanks.

 - Barry Tannenbaum
-
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

Re: [WiX-users] How to debug a CustomAction 1723 error ondll invocation?

2007-07-11 Thread Carter Sanders 

I fixed the problem by adding the dll entry method name in a .def file for
the project.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug a CustomAction 1723 error ondll invocation?

2007-07-05 Thread Carter Sanders 

Thanks for your help, Rob.


On 7/5/07, Rob Mensching <[EMAIL PROTECTED]> wrote:


 Please keep the mailing list on the line…



Sorry about that - switched accounts and dropped the CC accidentally.

You have to call it before RemoveFiles executes.  Or you have to remove the

dependency.


I recommend the latter whenever possible.




I'm not sure how to remove the dependency. My issue is that I need to clear
out a directory of plugins at uninstall time, and the contents of this
directory are a mix of installed files and an unpredictable and arbitrarily
deep set of files and directories that were downloaded using an update
manager built into the product.

If you know of a better way to do this, I'd love to hear about it.

The custom dll reads the INSTALLDIR from the registry and does a recursive
delete of INSTALLDIR/plugins. I couldn't find some easy built in way to do
this in WiX, so I tried resorting to the custom dll.

To place the CA before RemoveFiles, I placed it before
"RemoveRegistryValues", but I'm still seeing the same issue.

Thanks-
 Carter




*From:* Carter Sanders [mailto:[EMAIL PROTECTED]

*Sent:* Thursday, July 05, 2007 10:50 AM
*To:* Rob Mensching; Carter Sanders
*Subject:* RE: [WiX-users] How to debug a CustomAction 1723 error ondll
invocation?



Yes. The dll that is invoked is installed by the installer. Given that,
can you advise what would be the proper point in the install execute
sequence to call the action?



Thanks-

Carter



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to debug a CustomAction 1723 error on dll invocation?

2007-07-03 Thread Rob Mensching 
Does your CustomAction have dependencies on the machine that get removed during 
uninstall?

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carter Sanders
Sent: Tuesday, July 03, 2007 12:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug a CustomAction 1723 error on dll invocation?

Hi-
  I have a custom action I execute on uninstall, and it fails popping a dialog 
saying "A DLL required for this install to complete could not be run"

(from msiexec log)-
MSI (s) (F8:18) [15:35:49:202]: Creating MSIHANDLE (2) of type 790542 for 
thread 1560
MSI (s) (F8:2C) [15:35:49:202]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSI6.tmp, Entrypoint: CleanupPluginsDirEntry
MSI (s) (F8:F0) [15:35:49:202]: Generating random cookie.
MSI (s) (F8:F0) [15:35:49:265]: Created Custom Action Server with PID 1072 
(0x430).
MSI (s) (F8:F4) [15:35:49:765]: Running as a service.
MSI (s) (F8:A8) [15:35:49:765]: Hello, I'm your 32bit Impersonated custom 
action server.
MSI (s) (F8:2C) [15:35:49:858]: Closing MSIHANDLE (2) of type 790542 for thread 
1560
MSI (s) (F8:18) [15:35:49:874]: Note: 1: 1723 2: CleanupPluginsDir 3: 
CleanupPluginsDirEntry 4: C:\WINDOWS\Installer\MSI6.tmp Action start 15:35:49: 
CleanupPluginsDir.
MSI (s) (F8:18) [15:36:03:858]: Product: Aptana IDE -- Error 1723. There is a 
problem with this Windows Installer package. A DLL required for this install to 
complete could not be run. Contact your support personnel or package vendor. 
Action CleanupPluginsDir, entry: CleanupPluginsDirEntry, library: 
C:\WINDOWS\Installer\MSI6.tmp MSI (c) (A0:94) [15:35:49:874]: Font created.  
Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Action ended 15:36:03: CleanupPluginsDir. Return value 3.
Action ended 15:36:03: INSTALL. Return value 3.

As you can see, I'm trying to call the custom action from uninstall, and it 
fails. I've tested this dll with a test app on the machine where it's supposed 
to run, and it succeeds.

If I change the custom action to ignore the return code, the uninstall 
succeeds, but the code doesn't do what it's supposed to (clean out the plugins 
directory).

My entry in the binary table is -


And my custom action looks like -


I've added the action to the install execute sequence like this -

(GenericRegistrySettings is a feature that's always installed)

I've tried this with and without a file entry for the dll-


I've tried creating a trivial entry function which returns zero, but that also 
fails. I also tried using a persistant dll on the target machine, but that 
didn't help either.

I'm kind of at a loss as to how to further debug this. Can anybody give me some 
pointers? Any help would be greatly appreciated.

Thanks-
   Carter
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users