Re: [WiX-users] Getting started using WiX 3.6

2012-07-12 Thread Nick Ramirez
The setup template did change a bit in 3.6. They put the directories and
components into separate fragments. And they added the MediaTemplate element
and added the Directory attribute to the ComponentGroup. But for the most
part, it's mostly like version 3.5, or version 3.0 for that matter. 

Fragments are just a way of making those pieces more modular. You could, for
example, move those fragments into their own .wxs files and it would still
work. Or you could remove the fragment elements altogether and it would be
fine.

I'm starting an update to the book to try to cover the changes in 3.6.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Getting-started-using-WiX-3-6-tp7579415p7579416.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Getting started using WiX 3.6

2012-07-12 Thread Daniel Lang
Hello everyone,

I'm just getting started using version 3.6 (latest build) and I'm having a hard 
time understanding the basics. The main reason is, that it seems that there's 
very few to none documentation available. I've started reading the book and 
also the tutorial, but they are very different from what I have in the VS2012 
template for the Product.wxs file, and don't really help getting me started.

Is there any more up-to-date documentation available? Even a blog post that 
outlines the differences in the XML-Format between 3.5 and 3.6 would be 
helpful? Anyone knows a good place to start with?

Thanks,
Daniel
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Install multiple services using single ServiceHost.exe?

2012-07-12 Thread Nick Ramirez
Looking at the definition for ServiceInstall, you have to have the File
element in the same component. So, that limits you. Otherwise you'd be able
to put the File in one component and maybe reference it by two different
ServiceInstalls. Alas.

I've done something that may be similar to what you're doing. I've used the
same file for two different services by adding a post-build step to my
Visual Studio project. I copied the .exe to the output folder twice, with
two different names. That way I could deploy it as if it was two different
files, but both using the same code base.  


--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-multiple-services-using-single-ServiceHost-exe-tp7579407p7579414.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] MediaTemplate - what's DiskPrompt/VolumeLabel mean in this context?

2012-07-12 Thread Nick Ramirez
What does DiskPrompt and VolumeLabel mean when used on a MediaTemplate
element? On the old Media element, it made sense because each Media element
corresponded to a unique CAB file:




But the MediaTemplate makes the cabinets for us and there's only one
element. What does it do with to have these attributes on it? 



It seems like it would need to use variables or something for the
attributes?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MediaTemplate-what-s-DiskPrompt-VolumeLabel-mean-in-this-context-tp7579413.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] BalExtension and the Common Public License

2012-07-12 Thread Bruce Cran
On 12/07/2012 23:40, Darwin Baines wrote:
> So having done this, and gotten it to work I'm at the stage of wondering what 
> would be the ramification if we were to distribute it with our product and if 
> it will be a common problem with others.

I think this is something you'd need to ask a lawyer, not the mailing 
list :)

My impression is that licensing issues haven't really been thought about 
for a while, since for example 
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm 
recommends copying the code for WixUI_InstallDir and customising it - 
yet the file is clearly under the CPL, and so by doing so you'd create a 
derivative product and need to distribute your changes - is this what 
was intended?

-- 
Bruce Cran

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] BalExtension and the Common Public License

2012-07-12 Thread John Robbins
Thanks for answering! If a quiet bootstrapper is what you want, take a look at 
writing a custom one. You have total control over every aspect of the UI so you 
can show as little or as much as you like.

There's not a lot of documentation, but the WiX bootstrapper itself is very 
well done and was what I used to get started. Over a year ago I did a custom 
bootstapper with Burn that had all sorts of crazy UI logic because the 
installer did six web sites, seven services, and all pieces could be installed 
in any number of machines.

John
Co-founder - Wintellect
@JohnWintellect | 
Blog
+1-206-321-7341

On Jul 12, 2012, at 3:40 PM, Darwin Baines wrote:

I may have taken the wrong approach and this may become a non-issue once the 
documentation comes out and clears things up, but I was looking to make a quiet 
bootstrapper whose only dialog was the “usage” help page; kind of an 
incremental step from a straight MSI to a bootstrapper, where the MSI dialogs 
are still used but I can at least take advantage of the pre-req functionality 
and launch conditions available in the unmanaged bootstrapper.

I fiddled around with the “Foundation” variant of the standard bootstrapper, 
but it still seemed to need EULA dialogs, Success/Failure dialogs etc. Maybe I 
gave up too early on this.

So my next step was to go look at the WixStdBA source code. It seemed like it 
would be pretty easy to rip out all the dialogs (pages) except the help page 
and manipulate it all to step through everything without the user interaction.

So having done this, and gotten it to work I’m at the stage of wondering what 
would be the ramification if we were to distribute it with our product and if 
it will be a common problem with others.

Thanks for your interest.

Darwin



From: John Robbins [mailto:j...@wintellect.com]
Sent: Thursday, July 12, 2012 3:44 PM
To: General discussion for Windows Installer XML toolset.
Cc: Darwin Baines
Subject: RE: BalExtension and the Common Public License
Sensitivity: Personal

Out of pure curiosity, why would you need to do your own custom bootstrapper? 
The WiX Burn bootstrapper is incredibly flexible and allows you to completely 
control everything I can imagine anyone would need. What does Burn not do that 
you need?

Thanks for satisfying my curiosity.

John
Co-founder – Wintellect
@JohnWintellect | 
Blog
+1-206-321-7341
-Original Message-
From: Darwin Baines 
[mailto:da...@microsoft.com]
Sent: Thursday, July 12, 2012 1:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] BalExtension and the Common Public License
Sensitivity: Personal

I am looking into possibility of creating my own bootstrapper that tweaks the 
standard bootstrapper.

I assume that if I write my bootstrapper from scratch, I shouldn't run into 
complications, but if I start with the standard bootstrapper code and make some 
changes that fits my situation, I've created a derivative work and therefore 
would be required to make the source code publicly available. (At least 
according to Wikipedia)

I imagine there will be people looking to have a place to start with, and the 
standard bootstrapper source code is where they will probably go.

Has this been discussed? Are there any plans to address this? Perhaps a 
bootstrapper template that is released under less restrictive terms where 
derivative source code isn't required to be made public availability. Or 
perhaps a more configurable bootstrapper where dialogs can be suppressed and 
custom dialogs can be added.

Thanks

Darwin
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware 
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/

Re: [WiX-users] BalExtension and the Common Public License

2012-07-12 Thread Darwin Baines
I may have taken the wrong approach and this may become a non-issue once the 
documentation comes out and clears things up, but I was looking to make a quiet 
bootstrapper whose only dialog was the "usage" help page; kind of an 
incremental step from a straight MSI to a bootstrapper, where the MSI dialogs 
are still used but I can at least take advantage of the pre-req functionality 
and launch conditions available in the unmanaged bootstrapper.

I fiddled around with the "Foundation" variant of the standard bootstrapper, 
but it still seemed to need EULA dialogs, Success/Failure dialogs etc. Maybe I 
gave up too early on this.

So my next step was to go look at the WixStdBA source code. It seemed like it 
would be pretty easy to rip out all the dialogs (pages) except the help page 
and manipulate it all to step through everything without the user interaction.

So having done this, and gotten it to work I'm at the stage of wondering what 
would be the ramification if we were to distribute it with our product and if 
it will be a common problem with others.

Thanks for your interest.

Darwin



From: John Robbins [mailto:j...@wintellect.com]
Sent: Thursday, July 12, 2012 3:44 PM
To: General discussion for Windows Installer XML toolset.
Cc: Darwin Baines
Subject: RE: BalExtension and the Common Public License
Sensitivity: Personal


Out of pure curiosity, why would you need to do your own custom bootstrapper? 
The WiX Burn bootstrapper is incredibly flexible and allows you to completely 
control everything I can imagine anyone would need. What does Burn not do that 
you need?



Thanks for satisfying my curiosity.


John
Co-founder - Wintellect
@JohnWintellect | 
Blog
+1-206-321-7341

-Original Message-
From: Darwin Baines 
[mailto:da...@microsoft.com]
Sent: Thursday, July 12, 2012 1:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] BalExtension and the Common Public License
Sensitivity: Personal



I am looking into possibility of creating my own bootstrapper that tweaks the 
standard bootstrapper.



I assume that if I write my bootstrapper from scratch, I shouldn't run into 
complications, but if I start with the standard bootstrapper code and make some 
changes that fits my situation, I've created a derivative work and therefore 
would be required to make the source code publicly available. (At least 
according to Wikipedia)



I imagine there will be people looking to have a place to start with, and the 
standard bootstrapper source code is where they will probably go.



Has this been discussed? Are there any plans to address this? Perhaps a 
bootstrapper template that is released under less restrictive terms where 
derivative source code isn't required to be made public availability. Or 
perhaps a more configurable bootstrapper where dialogs can be suppressed and 
custom dialogs can be added.



Thanks



Darwin

--

Live Security Virtual Conference

Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

___

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] BalExtension and the Common Public License

2012-07-12 Thread John Robbins
Out of pure curiosity, why would you need to do your own custom bootstrapper? 
The WiX Burn bootstrapper is incredibly flexible and allows you to completely 
control everything I can imagine anyone would need. What does Burn not do that 
you need?



Thanks for satisfying my curiosity.


John
Co-founder - Wintellect
@JohnWintellect | 
Blog
+1-206-321-7341

-Original Message-
From: Darwin Baines [mailto:da...@microsoft.com]
Sent: Thursday, July 12, 2012 1:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] BalExtension and the Common Public License
Sensitivity: Personal



I am looking into possibility of creating my own bootstrapper that tweaks the 
standard bootstrapper.



I assume that if I write my bootstrapper from scratch, I shouldn't run into 
complications, but if I start with the standard bootstrapper code and make some 
changes that fits my situation, I've created a derivative work and therefore 
would be required to make the source code publicly available. (At least 
according to Wikipedia)



I imagine there will be people looking to have a place to start with, and the 
standard bootstrapper source code is where they will probably go.



Has this been discussed? Are there any plans to address this? Perhaps a 
bootstrapper template that is released under less restrictive terms where 
derivative source code isn't required to be made public availability. Or 
perhaps a more configurable bootstrapper where dialogs can be suppressed and 
custom dialogs can be added.



Thanks



Darwin

--

Live Security Virtual Conference

Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

___

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error

2012-07-12 Thread Don Walker

Don Walker wrote
> 
> Here is the situation:
> 
> 1. We allow multiple versions of our product to be installed at the same
> time if they have a different Major.Minor version. I don't believe that
> the MajorUpgrade element supports this option. The UpgradeVersion elements
> shown should provide for this.
> 2. Within the same Major.Minor version the user can upgrade or downgrade
> the product. The AllowDowngrades attribute of the MajorUpgrade element
> does support this.
> 
> I realize that there could be other approaches to implementing this such
> as using a new UpgradeCode for each Major.Minor version. I thought that my
> current approach would be closer to what Windows Installer intended.
> Comments?
> 

This seems to work ok with simple msi files. However, trying to get Burn to
do what I want is a puzzle I need help with:

1. It appears that I will have to use a new UpgradeCode for each Major.Minor
version of a bundle since I don't have the equivalent of UpgradeVersion
elements for bundles. If I do this I would be tempted to do the same with
the msi files that make up the bundle in order to keep things consistent.
2. I can't figure out any way to get a bundle to downgrade a version. It
appears that I'll have to flag the downgrade as an error and require the
user to uninstall the previous bundle. I guess you could argue that the need
to downgrade an install should be rare enough that we don't need to make it
convenient.

let me know if I've missed anything or there are other approaches.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579408.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Install multiple services using single ServiceHost.exe?

2012-07-12 Thread d8xter




Is it possible to use the ServiceInstall element and install multiple Windows 
Services using a single host.exe file? If so, how?
 
 
This works for a single service, but I cannot install the same file to the same 
directory from two different components...ICE30 error.
 

  
  
  

 
 
I have been unable to find another way to specify using the same file for the 
ServiceInstall to use. Do I need to create multiple MSI's, one for each service 
to get around the ICE30 error?
  
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] BalExtension and the Common Public License

2012-07-12 Thread Darwin Baines
I am looking into possibility of creating my own bootstrapper that tweaks the 
standard bootstrapper.

I assume that if I write my bootstrapper from scratch, I shouldn't run into 
complications, but if I start with the standard bootstrapper code and make some 
changes that fits my situation, I've created a derivative work and therefore 
would be required to make the source code publicly available. (At least 
according to Wikipedia)

I imagine there will be people looking to have a place to start with, and the 
standard bootstrapper source code is where they will probably go.

Has this been discussed? Are there any plans to address this? Perhaps a 
bootstrapper template that is released under less restrictive terms where 
derivative source code isn't required to be made public availability. Or 
perhaps a more configurable bootstrapper where dialogs can be suppressed and 
custom dialogs can be added.

Thanks

Darwin
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Component/@Guid error

2012-07-12 Thread bpackard
Rob,

Unless I am mistaken, that criteria: "[no] Property substitutions ..." is
only relevant if I am asking WiX to generate the Guid; which seems to be
indicated in the initial message.

"The Component/@Guid attribute's value '*' is not valid for this
component..."

What has me confused is that the Guid is explicitly specified, and is not
generated. I don't understand why the error is posted. The component was
acceptable within the mergemodule (WiX happily generated the merge module).
But it is choking since I moved it into a lib. 

thanks,
bill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-Guid-error-tp7579390p7579405.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Status of WiX v3.6 Release

2012-07-12 Thread John H Bergman (XPedient)
I find 3.6 very stable.

-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: Thursday, July 12, 2012 11:49 AM
To: General discussion for Windows Installer XML toolset. 
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Status of WiX v3.6 Release

WiX v3.6 RC0 was announced on 4/3/2012 and WiX v3.6 RC was announced on 
5/28/2012.

Does anybody have any guess as to how close we might be to WiX v3.6 RTM?

Hmm... let me ask a different question. We are not using burn yet and I 
understand most of the work right now revolves around burn. Would upgrading now 
to WiX v3.6 (RC or some newer weekly build) be considered stable enough for 
non-burn functionality?

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error

2012-07-12 Thread Don Walker

Rob Mensching-7 wrote
> 
> Or use MajorUpgrade element. 
> 

I don't think that the MajorUpgrade element gives me the flexibility that I
need. My assumptions (and what I believe to be best practice) are:

1. The UpgradeCode is fixed for all versions of the product.
2. The Product Id is set to "*" so a new GUID will be generated for each
build of the installer.

Here is the situation:

1. We allow multiple versions of our product to be installed at the same
time if they have a different Major.Minor version. I don't believe that the
MajorUpgrade element supports this option. The UpgradeVersion elements shown
should provide for this.
2. Within the same Major.Minor version the user can upgrade or downgrade the
product. The AllowDowngrades attribute of the MajorUpgrade element does
support this.

I realize that there could be other approaches to implementing this such as
using a new UpgradeCode for each Major.Minor version. I thought that my
current approach would be closer to what Windows Installer intended.
Comments?

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579403.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Status of WiX v3.6 Release

2012-07-12 Thread Castro, Edwin G. (Hillsboro)
WiX v3.6 RC0 was announced on 4/3/2012 and WiX v3.6 RC was announced on 
5/28/2012.

Does anybody have any guess as to how close we might be to WiX v3.6 RTM?

Hmm... let me ask a different question. We are not using burn yet and I 
understand most of the work right now revolves around burn. Would upgrading now 
to WiX v3.6 (RC or some newer weekly build) be considered stable enough for 
non-burn functionality?

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error

2012-07-12 Thread Rob Mensching
Or use MajorUpgrade element. 

On Wed, Jul 11, 2012 at 12:36 PM, Don Walker wrote:

>
> Chad Petersen wrote
> >
> > I was able to get past this error in your example by adding this inside
> > the Fragment
> >
> > 
> >   
> >  
> >
>
> Scheduling RemoveExistingProducts worked for me too. Ironically, I had just
> finished reading about scheduling it in the Windows Installer help and was
> considering scheduling it after InstallFinalize. I wanted to resolve this
> problem before continuing :-{
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579389.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Component/@Guid error

2012-07-12 Thread Rob Mensching
This part of the error message is pertinent: "[no] Property substitutions
as the key path"

On Wed, Jul 11, 2012 at 12:36 PM, Bill Packard wrote:

> WiX 3.0.5419, VS 2008.
> Attempting to convert merge modules (only used internally) to wixlib.
> Almost there, but have encountered a set of errors that make no sense.
> Example fragment and error are below.
>
>   
> 
>  Guid="DB0A90F0-DCEA-4022-A554-C9A67E561A67">
>Value="1" KeyPath="yes"
>
>  Key="Software\[PROPERTY1]\[PROPERTY2]\Install\Configuration Utility"/>
>Action="removeOnUninstall"
>  Key="Software\[PROPERTY1]\Configuration Utility"/>
> 
> 
>   
>
>
> Source.wxs(61,0): error LGHT0230: The Component/@Guid attribute's value
> '*' is not valid for this component because it does not meet the some of
> the criteria for having an automatically generated guid.  Only components
> with no ODBCDataSource child elements and either exactly one file which is
> the key path or no files and a registry with no Property substitutions as
> the key path may use an automatically generated guid.
>
>
> Several Registry components have this issue, but I am at a loss as to why.
> Both the RegistryValue and the RemoveRegistryKey elements are marked as
> errors; even tho the Guid is not generated.
> If anyone can give me some insight as to why this is happening, and even
> better, what to do about it I would appreciate it.
>
> Thanks,
> bill
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users