Re: [WiX-users] Wix bootstrapper issues

2011-06-20 Thread Vadym Verba
On this machine, both Headline.Agent and Headline.Player are installed.
However, only the features (and consequently package) for Headline.Player get
detected as present. What decides whether or not a package is detected?

 

Hey, Alexander.

I had the similar issue. Apparently Burn engine does not detect just
installed product without property ALLUSERS=1. I put
InstallScope=perMachine attribute into Package node and it helped.

 

Best regards,

Vadym.

 

 

/pre
BR style=font-size:4px;
a href = http://www.sdl.com/sdl-vision;img 
src=http://www.sdl.com/images/email_new_logo.png; alt=www.sdl.com/sdl-vision 
border=0//a
BR
font face=arial  size=2a href =http://www.sdl.com/sdl-vision; 
style=color:005740; font-weight: boldwww.sdl.com/sdl-vision/a/font
BR
BR
font face=arial  size=1 color=#736F6E
bSDL PLC confidential, all rights reserved./b
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.BR
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.BR
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.
/font
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix bootstrapper issues

2011-06-20 Thread Vadym Verba
On this machine, both Headline.Agent and Headline.Player are installed.
However, only the features (and consequently package) for Headline.Player get
detected as present. What decides whether or not a package is detected?

 

Hey, Alexander.

I had the similar issue. Apparently Burn engine does not detect just
installed product without property ALLUSERS=1. I put
InstallScope=perMachine attribute into Package node and it helped.

 

Best regards,

Vadym.

/pre
BR style=font-size:4px;
a href = http://www.sdl.com/sdl-vision;img 
src=http://www.sdl.com/images/email_new_logo.png; alt=www.sdl.com/sdl-vision 
border=0//a
BR
font face=arial  size=2a href =http://www.sdl.com/sdl-vision; 
style=color:005740; font-weight: boldwww.sdl.com/sdl-vision/a/font
BR
BR
font face=arial  size=1 color=#736F6E
bSDL PLC confidential, all rights reserved./b
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.BR
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.BR
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.
/font
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Component Request: null eventhough parentfeatureisinADDLOCAL

2011-06-20 Thread Tobberoth
I decided to go with your advice and build a simple installer to get that
working first... so I basically copied the Wix tutorial for building patches
and kept updating it until I now have the same installer and patch, only
that they work this time. I still have no idea why it didn't work before,
which annoys me, but at least the installer system is working and I can move
on to things that make more sense to me. ;)

Thanks for your help Peter.

Regards
/Tobias Dersén

On Wed, Jun 15, 2011 at 10:55 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:

 That's a shame. We are currently struggling with a C#-based installation
 product written in-house by another team so we've seen how trading for
 short-term control yields long-term problems. Since we adopted Wix some
 years
 ago, which admittedly has a big learning curve mostly due to the underlying
 Windows Installer, the deployment side of our products has improved
 substantially. Getting the first version out is the hardest, but later
 versions get easier.


 Have a quick look at your build. We make our patches from admin
 installations
 rather than the full Wix-only method - if youre using the pure-Wix method
 then it'll differ somewhat. These are the command lines, taken from an
 MSBuild file used to build them. Maybe you can glean something from them.

 !-- Uses -ax (admin) instead of -xi (xml input) and add -xo when using
 -ax.
 --
 torch.exe -t patch -xo -ax $(WorkingDir)\Binaries -p
 $(WorkingDir)\Release\$(MSIName) $(WorkingDir)\Update\$(MSIName) -out
 $(WorkingDir)\Diff.Wixmst

 candle.exe $(MSBuildProjectDirectory)\Patch.wxs -out
 $(WorkingDir)\Patch.wixobj

 light.exe $(WorkingDir)\Patch.wixobj -out $(WorkingDir)\Patch.WixMsp

 pyro.exe $(WorkingDir)\Patch.WixMsp -out
 $(MSBuildProjectDirectory)\$(PatchName) -pdbout
 $(WorkingDir)\$(PatchName).wixpdb -t $(Baseline)
 $(WorkingDir)\Diff.wixmst

 ! Note that the $(BaseLine) value must be the same as PatchBaseLine/@Id
 value
 in the patch wxs file.

 After checking your build I'd suggest two things that help me: trying and
 make a simple 1 file installer and patch. If that doesn't work then you
 have
 narrowed your search down. If it does work then you've verified that you
 are
 doing the right thing and just have to find where you didn't do it in the
 product.
 The other thing is to look at other patch logs and see what a successful
 patch looks like and where your log differs. The answer is nearly always
 there if only you know what to look for. Perhaps someone on here with
 better
 knowledge of patching can suggest where to look in the log, given the
 information so far.

 -Original Message-
 From: Tobberoth [mailto:tobber...@gmail.com]
  Sent: 15 June 2011 09:01
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Component Request: null eventhough
 parentfeatureisinADDLOCAL

 I did indeed retain the code. Since nothing has changed except the
 internals
 of the two files, both heat-generated .wxs are identical.

 I'm glad to hear that it looks OK since I was worried I had made some
 obvious embaressing mistake... that said, it's quite unsettling that you
 can't find any problem. I've had SO many issues with Wix and I think my
 boss
 is getting less and less happy that I chose Wix for our development. While
 Major Upgrades are working well, I've been trying to get some form of MSP
 system to work for ages now and it just refuses to work. First I had major
 issues with the SqlExtension where SQL refused to run during MSPs. I never
 got that to work and I'm currently using a CAQuietExec to run sqlcmd
 instead. (At that point in time, the MSP actually did update files though).
 Now this.

 I'm on the verge of thinking that coding a whole installer myself in C#
 would have been easier and faster.

 On Tue, Jun 14, 2011 at 2:06 PM, Peter Shirtcliffe
 pshirtcli...@sdl.comwrote:

  Did you run heat twice, once each on the original and upgrade MSIs, or
 did
  you retain the same source code for both versions ? You should be
 retaining
  the code.
 
  Other than that, it seems OK.
 
  -Original Message-
  From: Tobberoth [mailto:tobber...@gmail.com]
   Sent: 14 June 2011 12:33
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Component Request: null eventhough parent
  featureisinADDLOCAL
 
  Absolutely, let me know what information is needed. Here's my patch file,
  which is basically straight up from the tutorial on the wix page:
 
 Patch
 AllowRemoval=yes
 Manufacturer=Syscase
 DisplayName=Test Patch
 Description=Small Update Patch
 Classification=Update
 
 
 Media Id=5000 Cabinet=Sample.cab
 PatchBaseline Id=Sample/
 /Media
 
 PatchFamilyRef Id=SamplePatchFamily/
 /Patch
 
 Fragment
 PatchFamily Id='SamplePatchFamily' Version='5.1.0.0'
  Supersede='yes'
 ComponentRef Id=cmp432C3967A6AA13C06D8D1E0E95348403/
 

[WiX-users] (no subject)

2011-06-20 Thread Christoph Goetz
Hi,
I try to create my wix Project with an wxi File.
In a wxi File i have packed all the Files which are installed.
How can i inlude the Folders in the wxi File in the main.wxs?

Code Sample :

?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  ?Include C:\test.wxi ?
...


  Feature Id=ProductFeature Title=Test Level=1  

  
  ComponentRef Id=comp_DB8F510181154B28B50928C7DA07A49A/

/Feature

In test.wxi is the Component: comp_DB8F510181154B28B50928C7DA07A.

  Fragment
ComponentGroup Id=Test1-Files
  ComponentRef Id=comp_DB8F510181154B28B50928C7DA07A49A /
...

Christoph



--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] logging

2011-06-20 Thread David Amey
Hello Martin,

Thank you for your assistance, unfortunately this is still not working.

If anyone has any solution to this problem, then I would love to hear it!! 

Thanks again,

Dave

David Amey
The Creative Engine Ltd
Almac House, Church Lane, Bisley, Surrey, GU24 9DR
T: +44 (0)1483 799200  F: +44 (0)1483 799111

-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net] 
Sent: 15 June 2011 15:54
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] logging

Hi David,

I am not expert in candle and light but I believe that redirection in DOS 
should happen at the end of the line:

RunWait($WIX_FOLDER  '\candle.exe -dmanufacturer='$MANUFACTURER_NAME'
-dproductName='$productName' -dcabName='$CABINET_NAME'.cab
-dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out 
'$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs  myfile.txt
',$BUILD_FOLDER,@SW_MAXIMIZE)

Martin Kulov

-Original Message-
From: David Amey [mailto:da...@creative-engine.co.uk]
Sent: Wednesday, June 15, 2011 12:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] logging

Hi Dave,

Thank you for this link.

I have been trying to implement it into my calls, but sadly it does not seem to 
work.
I have tried the redirecting with a simple  cmd call and it works fine.

However I am creating an automation process using autoit, and im not sure if I 
would be using the redirection correctly.

Autoit script:
RunWait($WIX_FOLDER  '\candle.exe myfile.txt 
-dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName'
-dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode'
-dproductGUID='$productCode' -out '$BUILD_FOLDER'\
'$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE)

If anyone could point me in the right direction I would be incredibly grateful.

Thanks!

David Amey
The Creative Engine Ltd
Almac House, Church Lane, Bisley, Surrey, GU24 9DR
T: +44 (0)1483 799200  F: +44 (0)1483 799111

-Original Message-
From: Dave Andersen [mailto:d.ander...@gmail.com]
Sent: 14 June 2011 19:28
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] logging

Something like this may help:
http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri
pts/


David Amey wrote:
 
 Hello All
 
 Can someone please explain how I can turn logging on during the candle 
 and light calls, as I have errors that I need to correct.
 I am automating the calls, which causes the command prompt to close 
 very quickly after the code has been run.
 
 Thanks in advance.
 
 PS thank you Tonny Erjomin for the help on language support David Amey 
 The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 
 9DR
 T: +44 (0)1483 799200  F: +44 (0)1483 799111
 
 --
  EditLive Enterprise is the world's most technically advanced 
 content authoring tool. Experience the power of Track Changes, Inline 
 Image Editing and ensure content is compliant with Accessibility 
 Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 


--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474
846p6475377.html
Sent from the wix-users mailing list archive at Nabble.com.


--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's 

Re: [WiX-users] logging

2011-06-20 Thread Peter Shirtcliffe
Ive not used AutoIt but a quick look suggests it's using createprocess. To
get output redirection on a command line you need to be in a DOS box. 

Try ('cmd \c '  $WIX_FOLDER  '\candle.exe..

You might have to fiddle with quote marks if there are spaces in your path.
Better yet, replace cmd \c with %COMSPEC% \c if the function will expand
environment variables.

-Original Message-
From: David Amey [mailto:da...@creative-engine.co.uk] 
Sent: 20 June 2011 14:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] logging

Hello Martin,

Thank you for your assistance, unfortunately this is still not working.

If anyone has any solution to this problem, then I would love to hear it!! 

Thanks again,

Dave

David Amey
The Creative Engine Ltd
Almac House, Church Lane, Bisley, Surrey, GU24 9DR
T: +44 (0)1483 799200  F: +44 (0)1483 799111

-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net] 
Sent: 15 June 2011 15:54
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] logging

Hi David,

I am not expert in candle and light but I believe that redirection in DOS
should happen at the end of the line:

RunWait($WIX_FOLDER  '\candle.exe -dmanufacturer='$MANUFACTURER_NAME'
-dproductName='$productName' -dcabName='$CABINET_NAME'.cab
-dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out
'$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs  myfile.txt
',$BUILD_FOLDER,@SW_MAXIMIZE)

Martin Kulov

-Original Message-
From: David Amey [mailto:da...@creative-engine.co.uk]
Sent: Wednesday, June 15, 2011 12:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] logging

Hi Dave,

Thank you for this link.

I have been trying to implement it into my calls, but sadly it does not seem
to work.
I have tried the redirecting with a simple  cmd call and it works fine.

However I am creating an automation process using autoit, and im not sure if
I would be using the redirection correctly.

Autoit script:
RunWait($WIX_FOLDER  '\candle.exe myfile.txt
-dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName'
-dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode'
-dproductGUID='$productCode' -out '$BUILD_FOLDER'\
'$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE)

If anyone could point me in the right direction I would be incredibly
grateful.

Thanks!

David Amey
The Creative Engine Ltd
Almac House, Church Lane, Bisley, Surrey, GU24 9DR
T: +44 (0)1483 799200  F: +44 (0)1483 799111

-Original Message-
From: Dave Andersen [mailto:d.ander...@gmail.com]
Sent: 14 June 2011 19:28
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] logging

Something like this may help:
http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri
pts/


David Amey wrote:
 
 Hello All
 
 Can someone please explain how I can turn logging on during the candle 
 and light calls, as I have errors that I need to correct.
 I am automating the calls, which causes the command prompt to close 
 very quickly after the code has been run.
 
 Thanks in advance.
 
 PS thank you Tonny Erjomin for the help on language support David Amey 
 The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 
 9DR
 T: +44 (0)1483 799200  F: +44 (0)1483 799111
 
 --
  EditLive Enterprise is the world's most technically advanced 
 content authoring tool. Experience the power of Track Changes, Inline 
 Image Editing and ensure content is compliant with Accessibility 
 Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 


--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474
846p6475377.html
Sent from the wix-users mailing list archive at Nabble.com.


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image Editing
and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image Editing
and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



[WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings
G'morning (or evening wherever you are):

Our software has a couple of Explorer extensions - a namespace and shell 
extension to be exact - which we've always installed and uninstalled by running 
regsvr32 commands.  Are there any helpful Wix tutorials circulating on the net 
that describe the Wix equivalent for doing this?

Thanks.

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Thom Leigh
Use heat http://wix.sourceforge.net/manual-wix3/heat.htm to harvest
your registration information and create a wix fragment that you can
include or copy/paste from...

It's actually very easy :)

-Original Message-
From: Brad Lemings [mailto:b...@rebit.com] 
Sent: 20 June 2011 17:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Replacing regsvr32 commands with Wix elements

G'morning (or evening wherever you are):

Our software has a couple of Explorer extensions - a namespace and shell
extension to be exact - which we've always installed and uninstalled by
running regsvr32 commands.  Are there any helpful Wix tutorials
circulating on the net that describe the Wix equivalent for doing this?

Thanks.


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings
Hmm.  How can I capture the effects of the regsvr32 command in a .reg file 
which is what Heat expects?

-Original Message-
From: Thom Leigh [mailto:t...@mondago.com] 
Sent: Monday, June 20, 2011 11:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

Use heat http://wix.sourceforge.net/manual-wix3/heat.htm to harvest your 
registration information and create a wix fragment that you can include or 
copy/paste from...

It's actually very easy :)

-Original Message-
From: Brad Lemings [mailto:b...@rebit.com]
Sent: 20 June 2011 17:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Replacing regsvr32 commands with Wix elements

G'morning (or evening wherever you are):

Our software has a couple of Explorer extensions - a namespace and shell 
extension to be exact - which we've always installed and uninstalled by running 
regsvr32 commands.  Are there any helpful Wix tutorials circulating on the net 
that describe the Wix equivalent for doing this?

Thanks.


--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings
Found a regdiff tool.  Hopefully this should do the trick.  :)

-Original Message-
From: Brad Lemings [mailto:b...@rebit.com] 
Sent: Monday, June 20, 2011 1:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

Hmm.  How can I capture the effects of the regsvr32 command in a .reg file 
which is what Heat expects?

-Original Message-
From: Thom Leigh [mailto:t...@mondago.com]
Sent: Monday, June 20, 2011 11:21 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

Use heat http://wix.sourceforge.net/manual-wix3/heat.htm to harvest your 
registration information and create a wix fragment that you can include or 
copy/paste from...

It's actually very easy :)

-Original Message-
From: Brad Lemings [mailto:b...@rebit.com]
Sent: 20 June 2011 17:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Replacing regsvr32 commands with Wix elements

G'morning (or evening wherever you are):

Our software has a couple of Explorer extensions - a namespace and shell 
extension to be exact - which we've always installed and uninstalled by running 
regsvr32 commands.  Are there any helpful Wix tutorials circulating on the net 
that describe the Wix equivalent for doing this?

Thanks.


--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Setting user privileges

2011-06-20 Thread Michael Stoll
Hi,

is there a wix extension which is capable of creating a user with 
specific privileges? I need a non admin user with SeCreateSymbolicLink 
privilege.

Michael


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Dave Brotherstone

 -Original Message-
 From: Brad Lemings [mailto:b...@rebit.com]
 Sent: Monday, June 20, 2011 1:19 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

 Hmm.  How can I capture the effects of the regsvr32 command in a .reg file
 which is what Heat expects?


You don't need to - heat file yourfile.dll  -o install_actions.wxs
will capture everything that regsvr32 does (or actually what your
DllRegisterServer call in the DLL does).

It really is that easy :)
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings

What does Unable to load file: error 93 mean?

Here's the entire warning message:

heat.exe : warning HEAT5150 : Could not harvest data from a file that 
was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If this file does 
not support SelfReg you can ignore this warning. Otherwise, this error detail 
may be helpful to diagnose the failure: Unable to load file: 
C:\Builds\MyNSE\MyNSE.dll, error: 193

When I run the command regsvr32 MyNSE.dll, the command executes successfully. 
 Safe to ignore this warning?

-Original Message-
From: Dave Brotherstone [mailto:dav...@pobox.com] 
Sent: Monday, June 20, 2011 1:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements


 -Original Message-
 From: Brad Lemings [mailto:b...@rebit.com]
 Sent: Monday, June 20, 2011 1:19 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

 Hmm.  How can I capture the effects of the regsvr32 command in a .reg 
 file which is what Heat expects?


You don't need to - heat file yourfile.dll  -o install_actions.wxs will capture 
everything that regsvr32 does (or actually what your DllRegisterServer call in 
the DLL does).

It really is that easy :)
--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings
My guess is it is not safe to ignore this warning.  The generated Wix source 
contains nothing but a DirectoryRef, a Component, and File element.  I know 
more is required to register a COM server than that.  So heat does not work.  
Question now is, why not?

-Original Message-
From: Brad Lemings 
Sent: Monday, June 20, 2011 3:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements


What does Unable to load file: error 93 mean?

Here's the entire warning message:

heat.exe : warning HEAT5150 : Could not harvest data from a file that 
was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If this file does 
not support SelfReg you can ignore this warning. Otherwise, this error detail 
may be helpful to diagnose the failure: Unable to load file: 
C:\Builds\MyNSE\MyNSE.dll, error: 193

When I run the command regsvr32 MyNSE.dll, the command executes successfully. 
 Safe to ignore this warning?

-Original Message-
From: Dave Brotherstone [mailto:dav...@pobox.com]
Sent: Monday, June 20, 2011 1:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements


 -Original Message-
 From: Brad Lemings [mailto:b...@rebit.com]
 Sent: Monday, June 20, 2011 1:19 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

 Hmm.  How can I capture the effects of the regsvr32 command in a .reg 
 file which is what Heat expects?


You don't need to - heat file yourfile.dll  -o install_actions.wxs will capture 
everything that regsvr32 does (or actually what your DllRegisterServer call in 
the DLL does).

It really is that easy :)
--
EditLive Enterprise is the world's most technically advanced content authoring 
tool. Experience the power of Track Changes, Inline Image Editing and ensure 
content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Hoover, Jacob

  If I had to guess, this component may rely on other components. I
swear I saw something along the lines of this with an ATL component.
When the registry redirection occurs inside of Heat, it makes the
registry look empty. As such, if your component required ATL it would
fail inside its regsvr32 procedure.

  I had pondered making a patch myself, where heat would allow for a reg
script to be passed as a parameter (basically reg script being another
heat fragment).  With that, you could create an ATL.reg using heat
against the ATL DLL, and then pass it as a parameter to the Heat call
for your component.

  The only problem would be writing the logic to identify which
attributes were changed by your DLL compared to your reg script.  

  I could be way off base, but I think I could generate a reproducible
test case.

-Original Message-
From: Brad Lemings [mailto:b...@rebit.com] 
Sent: Monday, June 20, 2011 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

My guess is it is not safe to ignore this warning.  The generated Wix
source contains nothing but a DirectoryRef, a Component, and File
element.  I know more is required to register a COM server than that.
So heat does not work.  Question now is, why not?

-Original Message-
From: Brad Lemings 
Sent: Monday, June 20, 2011 3:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements


What does Unable to load file: error 93 mean?

Here's the entire warning message:

heat.exe : warning HEAT5150 : Could not harvest data from a file
that was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If
this file does not support SelfReg you can ignore this warning.
Otherwise, this error detail may be helpful to diagnose the failure:
Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193

When I run the command regsvr32 MyNSE.dll, the command executes
successfully.  Safe to ignore this warning?

-Original Message-
From: Dave Brotherstone [mailto:dav...@pobox.com]
Sent: Monday, June 20, 2011 1:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements


 -Original Message-
 From: Brad Lemings [mailto:b...@rebit.com]
 Sent: Monday, June 20, 2011 1:19 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements

 Hmm.  How can I capture the effects of the regsvr32 command in a .reg 
 file which is what Heat expects?


You don't need to - heat file yourfile.dll  -o install_actions.wxs will
capture everything that regsvr32 does (or actually what your
DllRegisterServer call in the DLL does).

It really is that easy :)

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Replacing regsvr32 commands with Wix elements

2011-06-20 Thread Brad Lemings
No, I think you're right on the money.  The NSE DLL that I'm testing requires 
MFC, Qt, and a host of other dependencies.  Being that I had to rebuild my 
Service so that it is statically linked just so Windows Installer could start 
it at the expected time, the MFC/ATL dependency is no surprise.  :P

 -Original Message-
 From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
 Sent: Monday, June 20, 2011 4:07 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements
 
 
   If I had to guess, this component may rely on other components. I swear I
 saw something along the lines of this with an ATL component.
 When the registry redirection occurs inside of Heat, it makes the registry 
 look
 empty. As such, if your component required ATL it would fail inside its
 regsvr32 procedure.
 
   I had pondered making a patch myself, where heat would allow for a reg
 script to be passed as a parameter (basically reg script being another heat
 fragment).  With that, you could create an ATL.reg using heat against the ATL
 DLL, and then pass it as a parameter to the Heat call for your component.
 
   The only problem would be writing the logic to identify which attributes
 were changed by your DLL compared to your reg script.
 
   I could be way off base, but I think I could generate a reproducible test 
 case.
 
 -Original Message-
 From: Brad Lemings [mailto:b...@rebit.com]
 Sent: Monday, June 20, 2011 4:47 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements
 
 My guess is it is not safe to ignore this warning.  The generated Wix source
 contains nothing but a DirectoryRef, a Component, and File element.  I know
 more is required to register a COM server than that.
 So heat does not work.  Question now is, why not?
 
 -Original Message-
 From: Brad Lemings
 Sent: Monday, June 20, 2011 3:42 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: RE: [WiX-users] Replacing regsvr32 commands with Wix elements
 
 
 What does Unable to load file: error 93 mean?
 
 Here's the entire warning message:
 
   heat.exe : warning HEAT5150 : Could not harvest data from a file
 that was expected to be a SelfReg DLL: C:\ Builds\MyNSE\MyNSE.dll. If
 this file does not support SelfReg you can ignore this warning.
 Otherwise, this error detail may be helpful to diagnose the failure:
 Unable to load file: C:\Builds\MyNSE\MyNSE.dll, error: 193
 
 When I run the command regsvr32 MyNSE.dll, the command executes
 successfully.  Safe to ignore this warning?
 
 -Original Message-
 From: Dave Brotherstone [mailto:dav...@pobox.com]
 Sent: Monday, June 20, 2011 1:58 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements
 
 
  -Original Message-
  From: Brad Lemings [mailto:b...@rebit.com]
  Sent: Monday, June 20, 2011 1:19 PM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Replacing regsvr32 commands with Wix elements
 
  Hmm.  How can I capture the effects of the regsvr32 command in a .reg
  file which is what Heat expects?
 
 
 You don't need to - heat file yourfile.dll  -o install_actions.wxs will
 capture everything that regsvr32 does (or actually what your
 DllRegisterServer call in the DLL does).
 
 It really is that easy :)
 
 --
 EditLive Enterprise is the world's most technically advanced content
 authoring tool. Experience the power of Track Changes, Inline Image
 Editing and ensure content is compliant with Accessibility Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 --
 EditLive Enterprise is the world's most technically advanced content
 authoring tool. Experience the power of Track Changes, Inline Image
 Editing and ensure content is compliant with Accessibility Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 EditLive Enterprise is the world's most technically advanced content
 authoring tool. Experience the power of Track Changes, Inline Image
 Editing and ensure content is compliant with Accessibility Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users