date:20130423

[WiX-users] Trouble with DotNet

2013-04-23 Thread Nick Miller

Hi All,

I am having a very annoying problem.  I have a managed bootstrapper application 
which requires .Net 4.5.  I have the proper PackageGroupRef in my bundle's 
chain, and it installs .Net 4.5 successfully when there is no .Net installed.  
The problem is that if .Net 4 is already installed I run into one of two 
problems:

If in my BootstrapperCore.config I state:
   
I get the following every time I run the installer no matter what:
   Loading prerequisite bootstrapper application because managed 
host could not be loaded, error: 0x80070490.
   ...
   The prerequisites were already installed. The bootstrapper 
application will not be reloaded to prevent an infinite loop.

If I declare any previous versions for supported framework, the installer 
crashes, and never loads the prereq window.

Any ideas?

Nick
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Entire .NET 4.0 Framework dialog disabled

2013-04-23 Thread Mark Van Dyke

Hello,

I am using Wix 3.8.401.0 and Visual Studio 2010.  I am writing a custom managed 
bootstrapper that bundles my MSI, another 3rd party MSI and it has a .net 4 
prerequisite.  When I use the built-in .NET dialog I have no issues and it 
works great.  However, I am now customizing the UI (basically completely 
changing it).  What happens is that my splash screen comes up, it detects that 
netfx40Redist needs to be installed.  It shows my customized UI beautifully, 
however, every single bit of text and every button is disabled.  The UI is not 
frozen, I can hit the form close button and it prompts me if I want to exit and 
I can exit no problem.  I cannot find anything on the forum or with google 
searches about this specific issue.  Everything similar seems to be related to 
race conditions and the usage of threads which I have resolved a while ago.

Here is my source:

Bundle.wxs

http://schemas.microsoft.com/wix/2006/wi"; 
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
 xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";>
   

  
  
  
  
  
  
  
  











  
  


  
  

  
  



  


  


CostarPReq.thm

http://wixtoolset.org/schemas/thmutil/2010"; 
ImageFile="FormBackground.png">
#(loc.Caption)
Calibri
Calibri
Calibri
Calibri
Calibri

  




#(loc.HelpHeader)
#(loc.HelpText)
#(loc.HelpCloseButton)


#(loc.InstallLicenseTerms)
#(loc.NetInstallAcceptAndInstallButton)
#(loc.NetInstallDeclineButton)
#(loc.TitleWelcome)
#(loc.CostarQualityMessage)
#(loc.TitleMessage)
#(loc.NetProductName)


#(loc.ProgressHeader)
#(loc.ProgressLabel)
[ProgressPackageName]

#(loc.ProgressCancelButton)


#(loc.FailureHeader)
#(loc.FailureLogLinkText)

#(loc.FailureRestartText)
#(loc.FailureRestartButton)
#(loc.FailureCloseButton)




Any help would be appreciated as I cannot find any info on this.

Thank-you very much,
mvd
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Outercurve OSS Conference, May 8-9, Bellevue WA

2013-04-23 Thread Rob Mensching

Greetings all,

It's not often that I start a thread on wix-users but I thought this might
be an event some of you would find interesting.

On May 8th and 9th, the Outercurve Foundation (the keeper's of the WiX
toolset copyright) is holding its first Open Source Conference. They've got
some famous people talking like: Jono Bacon, Scott Guthrie, Donnie
Berkholz, and Ross Gardler.

They even have some less famous people, me, doing hand to
hand combat over software installation and packaging. I'll be going at it
with the project leads for NuGet and CoApp. That should be fun.

Anyway, beyond my cage match, I'll also be floating around at the
conference (when I'm not sharpening my sword) so if you're going to be
around let me know.

You can get more details about the conference here:
http://www.regonline.com/builder/site/Default.aspx?EventID=1224520

virtually,

   Rob Mensching
   http://robmensching.com/

I should probably make this a blog post.
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn and chained MSI paths

2013-04-23 Thread Benjamin Leggett

Ok, explicitly specifying that Compression property seems to create a file 
system link to the WiX MSI in the bootstrapper directory when the bootstrapper 
is built, which works for local builds and actual deployment.

Thanks!

-Original Message-
From: Marco Tognacci [mailto:mark...@live.it] 
Sent: Tuesday, April 23, 2013 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn and chained MSI paths

if you set the property Compressed="no" in the MsiPackage it will be not 
embedded into the Burn exe setup.If you want to copy the MsiPackage to a 
different location with a different Directory structure in the bin\Release you 
can set the property Name of the MsiPackage with the output path where to copy 
the MsiPackage after building the exe burn setup.In this case you need to have 
the MsiPackage in a known location at build time as the Burn Bundle as to know 
the package, if you don't have the MsiPackage at build time you can choose to 
Download it when the setup will execute using the DownloadUrl with the path for 
downloading the package (for example from a web location)


> From: blegg...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 23 Apr 2013 20:32:16 +
> Subject: [WiX-users] Burn and chained MSI paths
> 
> Hi all,
> 
> Been playing around with Burn (and searching the archives) and I'm not clear 
> on something.
> 
> I'm using the standard WiX bootstrapper to chain some WiX MSIs that are in 
> the same solution. I don't want to embed the MSIs, need to keep them separate.
> 
> I can of course hardcode the SourceFile path to point to the WiX MSI's output 
> directory. This works fine when I'm building the bootstrapper and all setups 
> manually within Visual Studio.
> 
> The problem is I don't actually want the MSIs deployed in that folder 
> structure for a release (bin\Debug or bin\Release).
> 
> Is there a clean way to handle this? The best I can do right now is adding 
> some post/prebuilds to the bootstrapper project and copying each chained MSI 
> to a specific place on each build and referencing that relative path from the 
> bootstrapper.
> 
> Thanks,
> Ben
> NOTICE: This electronic mail message and any files transmitted with it 
> are intended exclusively for the individual or entity to which it is 
> addressed. The message, together with any attachment, may contain 
> confidential and/or privileged information.
> Any unauthorized review, use, printing, saving, copying, disclosure or 
> distribution is strictly prohibited. If you have received this message 
> in error, please immediately advise the sender by reply email and delete all 
> copies.
> --
>  Try New Relic Now & We'll Send You this Cool Shirt New Relic 
> is the only SaaS-based application performance monitoring service that 
> delivers powerful full stack analytics. Optimize and monitor your 
> browser, app, & servers with just a few lines of code. Try New Relic 
> and get this awesome Nerd Life shirt! 
> http://p.sf.net/sfu/newrelic_d2d_apr
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only 
SaaS-based application performance monitoring service that delivers powerful 
full stack analytics. Optimize and monitor your browser, app, & servers with 
just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! 
http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn and chained MSI paths

2013-04-23 Thread Marco Tognacci

if you set the property Compressed="no" in the MsiPackage it will be not 
embedded into the Burn exe setup.If you want to copy the MsiPackage to a 
different location with a different Directory structure in the bin\Release you 
can set the property Name of the MsiPackage with the output path where to copy 
the MsiPackage after building the exe burn setup.In this case you need to have 
the MsiPackage in a known location at build time as the Burn Bundle as to know 
the package, if you don't have the MsiPackage at build time you can choose to 
Download it when the setup will execute using the DownloadUrl with the path for 
downloading the package (for example from a web location)


> From: blegg...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 23 Apr 2013 20:32:16 +
> Subject: [WiX-users] Burn and chained MSI paths
> 
> Hi all,
> 
> Been playing around with Burn (and searching the archives) and I'm not clear 
> on something.
> 
> I'm using the standard WiX bootstrapper to chain some WiX MSIs that are in 
> the same solution. I don't want to embed the MSIs, need to keep them separate.
> 
> I can of course hardcode the SourceFile path to point to the WiX MSI's output 
> directory. This works fine when I'm building the bootstrapper and all setups 
> manually within Visual Studio.
> 
> The problem is I don't actually want the MSIs deployed in that folder 
> structure for a release (bin\Debug or bin\Release).
> 
> Is there a clean way to handle this? The best I can do right now is adding 
> some post/prebuilds to the bootstrapper project and copying each chained MSI 
> to a specific place on each build and referencing that relative path from the 
> bootstrapper.
> 
> Thanks,
> Ben
> NOTICE: This electronic mail message and any files transmitted with it are 
> intended
> exclusively for the individual or entity to which it is addressed. The 
> message, 
> together with any attachment, may contain confidential and/or privileged 
> information.
> Any unauthorized review, use, printing, saving, copying, disclosure or 
> distribution 
> is strictly prohibited. If you have received this message in error, please 
> immediately advise the sender by reply email and delete all copies.
> --
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service 
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Burn and chained MSI paths

2013-04-23 Thread Benjamin Leggett

Hi all,

Been playing around with Burn (and searching the archives) and I'm not clear on 
something.

I'm using the standard WiX bootstrapper to chain some WiX MSIs that are in the 
same solution. I don't want to embed the MSIs, need to keep them separate.

I can of course hardcode the SourceFile path to point to the WiX MSI's output 
directory. This works fine when I'm building the bootstrapper and all setups 
manually within Visual Studio.

The problem is I don't actually want the MSIs deployed in that folder structure 
for a release (bin\Debug or bin\Release).

Is there a clean way to handle this? The best I can do right now is adding some 
post/prebuilds to the bootstrapper project and copying each chained MSI to a 
specific place on each build and referencing that relative path from the 
bootstrapper.

Thanks,
Ben
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to set a WixVariable using a conditional option?

2013-04-23 Thread Marco Tognacci

I have a Burn setup that need the Net framework 4.5 as prerequisite, but if it 
is installed on a WindowsXP I have to set as prerequisite only the net 
framework 4.0 (as the Net 4.5 can't be installed on Windows XP).My bootstrapper 
(and my application) need only the Net 4.0 but as the net 4.5 has some 
improvement that make my program working better I prefer to install the Net 4.5 
if it is possible.I'd like to install only one of them, in this way I need to 
change the WixVariable that define the Burn prerequisite based on the system 
requirements. As to set the Net 4.5 as prerequisite for the bundle if the 
VersionNT > 6.0

if(VersionNT < 6.0) I have to set only the Net 4.0

I have set the install condition for the two Net Package as only one of them is 
installed as descrbed 
in:http://stackoverflow.com/questions/13314944/how-to-intelligently-install-net-4-x-using-wix-burn
But I can't find a way to set only one of them as prerequisite for Burn 
package.Is there any way to set the WixVariable  "WixMbaPrereqPackageId" with a 
conditional option to be evaluated at runtime?  
  
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix ExePackage can't activate log using Burn

2013-04-23 Thread Marco Tognacci

It work great thanks !

> From: r...@robmensching.com
> Date: Mon, 22 Apr 2013 15:50:56 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Wix ExePackage can't activate log using Burn
> 
> If the "[LogPathVariable]" was passed as an empty string that means the
> variable was interpreted, it just interpreted to empty string. Logging for
> ExePackage's has to be done essentially manual since .exe based installs
> are all very different. However Burn provides a little to help you. The
> following should demonstrate some options:
> 
>  LogPathVariable='ThisExePackageLogPath' />
> 
> Notice how ExePackage/@LogPathVariable defines the name of the variable for
> the log path and how the ExePackage/@InstallCommand uses the result of that
> variable to provide a log file to the ExePackage.  I hope that helps answer
> the question.
> 
> 
> On Mon, Apr 22, 2013 at 10:26 AM, Marco Tognacci  wrote:
> 
> > I have tried with this but the [LogPathVariable] is not valuated and Burn
> > pass an empty string as args, so the exe package report an error, and
> > doesn't install.
> >
> > > From: jacob.hoo...@greenheck.com
> > > To: wix-users@lists.sourceforge.net
> > > Date: Sun, 21 Apr 2013 21:21:42 +
> > > Subject: Re: [WiX-users] Wix ExePackage can't activate log using Burn
> > >
> > > Hmm,
> > >   Just a guess but...
> > >
> > > InstallCommand="/s /v"REBOOT=ReallySupress /qn /l*v
> > [LogPathVariable]""
> > >
> > > And then if it fails, what does the bundle log show when it executes
> > your ExePackage?  What is the error code that is returned? It should log
> > all the options passed to the package so we could track down the issue.
> > >
> > > -Original Message-
> > > From: Marco Tognacci [mailto:mark...@live.it]
> > > Sent: Sunday, April 21, 2013 4:02 PM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] Wix ExePackage can't activate log using Burn
> > >
> > > If I run from cmd the ExePackage in silent mode, and suppress reboot,
> > with this command line parameters it works"/s /v"REBOOT=ReallySupress /qn
> > /l*v %temp%\MyExe.log""
> > > but if I use this InstallCommand in the ExePackage the package return an
> > error and doesn't installInstallCommand="/s /v"REBOOT=ReallySupress
> > /qn""
> > > then I have found the LogPathVariable in the ExePackage, perhaps I must
> > use this to enable logging, or what is this LogPathVariable made for?
> > >
> > > > From: jacob.hoo...@greenheck.com
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Sun, 21 Apr 2013 19:15:46 +
> > > > Subject: Re: [WiX-users] Wix ExePackage can't activate log using Burn
> > > >
> > > > Exe package logging would be dictated by the Exe.  You could try
> > passing /? To the exe to see what parameters it supports. From there, you
> > can customize the parameters the bundle passes to the package to get the
> > desired result.
> > > >
> > > > -Original Message-
> > > > From: Marco Tognacci [mailto:mark...@live.it]
> > > > Sent: Sunday, April 21, 2013 6:59 AM
> > > > To: wix-users@lists.sourceforge.net
> > > > Subject: Re: [WiX-users] Wix ExePackage can't activate log using Burn
> > > >
> > > > Is this a bug in wix, or this is not the right way for enabling log
> > for ExePackage?I have tried to use LogPathVariable="MyExe.log" but the log
> > doesn't work.
> > > >
> > > > > From: mark...@live.it
> > > > > To: wix-users@lists.sourceforge.net
> > > > > Date: Thu, 18 Apr 2013 20:09:29 +0200
> > > > > Subject: Re: [WiX-users] Wix ExePackage can't activate log using
> > > > > Burn
> > > > >
> > > > > Do you have any example about enabling logging of ExePackage in Burn
> > chain?I have tried to use LogPathVariable="MyExe.log" but the log doesn't
> > work.
> > > > >
> > > > >
> > > > > > From: mark...@live.it
> > > > > > To: wix-users@lists.sourceforge.net
> > > > > > Date: Wed, 17 Apr 2013 20:57:07 +0200
> > > > > > Subject: [WiX-users] Wix ExePackage can't activate log using Burn
> > > > > >
> > > > > > I have an exe setup package that I have to install in the chain of
> > Burn, for this I have added an ExePackage.When the Burn setup is running I
> > have the logs for each msi in the format
> > [WidBundleName_Date]_[MSIPackageName].log, but I have no the log for the
> > exe package, if I run the exe with this command line it create the log
> > /l*v %temp%\MyExe.log.If I add this command args to the InstallCommand of
> > the ExePackage it return and error when installing.So I have tried to set
> > LogPathVariable in the ExePackage using the name of the log
> > LogPathVariable="MyExe.log" it doen't create any log file.How can I use
> > this LogPathVariable ? I'd like to have the log on a file with the same
> > naming convention used for the MSI package, how can I do this?
> > > > > > --
> > > > > > --
> > > > > > -- Precog is a next-generation analytics platform capable
> > > > > > of advanced anal

[WiX-users] How do I correctly modify an EventLog?

2013-04-23 Thread David Kauffmann

I would like to create a log file in the Windows EventLog with numerous 
EventLog Sources.
There is this wonderful feature in Wix that lets me do just that: the 
EventSource element in the WixUtilExtension dll.
One thing that is missing from this element is the ability to change the 
default properties of the EventLog which is created with such an element.
I have searched online for this problem and have come along this post on 
stackoverflow post:

http://stackoverflow.com/questions/2372988/how-to-change-event-log-properties-from-wix-script

However, this post does not provide a solution for this problem. In 
conclusion the post states, that a custom action has to be written to 
achieve this task.
I would rather refrain from writing my own custom action, if there is 
another possibility to achieve this. But for now, I would like to ask 
for advice on how to properly write such a custom action.
I have come up with a solution to this problem with the following approach:
- created EventSource elements.
- wrote a custom action that simply sets the eventlog properties.
- added a RegistryKey element.

I will now post the code to each part of the approach and explain why I 
did it that way.
The EventSource elements look like this:


   
   
 
   


   
   
 
   


I want to keep the CustomAction as simple as possible, therefore the 
creation of the EventLog and EventLog Source should be handled by the 
installer. I check for the presence of .Net Framework in order to load 
the correct EventLogMessages dll.

The code of the CustomAction looks like this:

using System;
using Microsoft.Deployment.WindowsInstaller;
using System.Diagnostics;

namespace EvlCA
{
 public class CustomActions
 {
 [CustomAction]
 public static ActionResult UpdateEventLog(Session session)
 {
 EventLog log = new EventLog("MyLog");
 log.MaximumKilobytes = 2048;
log.ModifyOverflowPolicy(OverflowAction.OverwriteAsNeeded, 0);

 return ActionResult.Success;
 }
 }
}
All I'm doing here, as you can see, is to set the properties of the 
EventLog. The funny thing is, that after the log has been installed by 
my installer, the eventvwr.msc snap-in displays the value "1028" for the 
size of the log. I don't understand why that is happening, because the 
ModifyOverflowPolicy method works as expected.
I am very unsure, if using such a simple CustomAction is acceptable.

Do I have to expand it to cover Rollback and Uninstallation?

I have scheduled the CustomAction to run like this:

...
 
 
...

I am unsure about the Execute attribute. When this is set to immediate I 
have to create an InstallExecuteSequence element and schedule it myself. 
I have omitted this element because I assigned the commit value to that 
attribute. Is that correct, or do I have to include an 
InstallExecuteSequnce element anyway?


To compensate for the funny value "1028" I added the following 
RegistryKey element:


   
 
   
   
   
   
 
   


This results in the value I actually desired: 2048. It has to be written 
like that, because according to this post

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/setting-hex-value-for-DWORD-in-registry-td697623.html

the Registry table only stores decimal values. The problem is that 
altering the registry has no effect until the machine is restarted. But 
that is something I can live with, as long as my custom action sets the 
modifyoverflowpolicy correctly.

I would really love to see an extension to the WixUtilExtension library 
which provides an EventLog element with the Attributes 
ModifyOverflowPolicy, MaximumKilobytes, MinimumRetentionDays... 
essentially all the Properties you can set for an EventLog object from 
the System.Diagnostics namespace.

Thanks for your help.

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Install Network Component Type "Service"

2013-04-23 Thread Michael Ogilvie

Hello,

 

I have a NIC GigE filter driver that installs fine but does not add the
service to the NIC's on the computer. How do I install the network
service in wix?

 

 

Thank you,

Michael Ogilvie 

 

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper Upgrade Problem

2013-04-23 Thread Nick Miller

Awesome tip, thanks!



-Original Message-
From: Marco Tognacci [mailto:mark...@live.it] 
Sent: Monday, April 22, 2013 5:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Problem

you have to magae the case when the Command.Display is not Full.you can see the 
InstallationViewModel provided in the Setup of wix, expecially in the functions 
DetectComplete and ApplyComplete

> From: nmil...@livetechnology.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 22 Apr 2013 21:09:19 +
> Subject: [WiX-users] Bootstrapper Upgrade Problem
> 
> Hi All,
> 
> I am trying to upgrade an msi from a custom managed bootstrapper.  For some 
> reason the upgrade fails when trying to remove the cached bootstrapper 
> package.  When the installer tries to run C:\ProgramData\Package 
> Cache\...\MyCustomBa.exe -uninstall -quiet -burn.related.upgrade it just 
> launches the UI for that BA.  Is there something obvious that I could be 
> missing?
> 
> Thanks,
> Nick
> 
> --
>  Precog is a next-generation analytics platform capable of 
> advanced analytics on semi-structured data. The platform includes APIs 
> for building apps and a phenomenal toolset for data science. 
> Developers can use our toolset for easy data analysis & visualization. 
> Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Precog is a next-generation analytics platform capable of advanced analytics on 
semi-structured data. The platform includes APIs for building apps and a 
phenomenal toolset for data science. Developers can use our toolset for easy 
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MSI Package not installing after upgrade even though InstallCondition set to "1"

2013-04-23 Thread Rob Mensching

The log file shows that Burn believes the package is already installed
therefore no operations are necessary. Not clear to me what the issue is
(however, setting your InstallCondition to "1" is very strange thing to do
and could have interesting side effects in the future).


On Tue, Apr 23, 2013 at 3:48 AM, andy smith  wrote:

> I have a burn 3.6 installation with a number of packages in the chain. One
> of the MSIPackages  I want installed no matter what other msi packages are
> each time, and therefore have forced the InstallCondition to "1"
>
>Id="msi_SharedComponents"
> SourceFile="..\..\External
> References\MSI\6.0\6.0.164.0\SetupSharedComponents.msi"
> InstallCondition="1"DownloadUrl="http://oururl.
> ../setupsharedcomponents.msi"
> DisplayName="Shared Components"
> Compressed="no"
> Vital="yes" />
>
> As you may have guessed by the post title, during an upgrade the package is
> uninstalled but not reinstalled during a quiet / passive upgrade.
>
> I've obviously made a wrong assumption somewhere about forcing the
> InstallCondition. Any help would be appreciated.
>
> What follows is just to state what's happening in the logs if it helps...
>
> In the install log, after "Apply begin" this package isn't listed as a
> verified acquired payload like the other packages, such as...
>
> [0A24:0DBC][2013-04-23T11:04:51]: Verified acquired payload: msi_Sales at
> path: C:\Documents and Settings\All Users\Application Data\Package
> Cache\.unverified\msi_Sales, moving to: C:\Documents and Settings\All
> Users\Application Data\Package
> Cache\{42B9B03B-15C3-48D0-B605-F574B1374160}v6.0.166.0\SetupSales.msi.
> ... and then afterwards there is no "Applying execute package"... so it's
> not that it tried to re-install the package and failed - it doesn't want to
> know about the package
>
> >From the planning stage..
>
> Planned package: msi_SharedComponents, state: Present, default requested:
> Present, ba requested: Present, execute: None, rollback: None, cache: No,
> uncache: No, dependency: Register
> Planned package: msi_Reports, state: Absent, default requested: Present, ba
> requested: Present, execute: Install, rollback: Uninstall, cache: Yes,
> uncache: No, dependency: Register
> Planned package: msi_Sales, state: Absent, default requested: Present, ba
> requested: Present, execute: Install, rollback: Uninstall, cache: Yes,
> uncache: No, dependency: Register
>
> reports and sales re-install fine. SharedComponents doesn't. I assume that
> "execute: None" vs. "execute: Install" in the other packages is key...
>
> --
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] REMOVE ME PLEASE

2013-04-23 Thread S.Mizukoshi


-- 
日本エンジニアリング（株）
  技術統括部　ソフトウェア部　ソフトウェア1課
水越　智史
〒214-0038 川崎市多摩区生田2-9-2
TEL  :(044)931-1316
FAX  :(044)931-1321
Email:satoshi.mizuko...@jp.advantest.com

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] MSI Package not installing after upgrade even though InstallCondition set to "1"

2013-04-23 Thread andy smith

I have a burn 3.6 installation with a number of packages in the chain. One
of the MSIPackages  I want installed no matter what other msi packages are
each time, and therefore have forced the InstallCondition to "1"

  http://oururl.
../setupsharedcomponents.msi"
DisplayName="Shared Components"
Compressed="no"
Vital="yes" />

As you may have guessed by the post title, during an upgrade the package is
uninstalled but not reinstalled during a quiet / passive upgrade.

I've obviously made a wrong assumption somewhere about forcing the
InstallCondition. Any help would be appreciated.

What follows is just to state what's happening in the logs if it helps...

In the install log, after "Apply begin" this package isn't listed as a
verified acquired payload like the other packages, such as...

[0A24:0DBC][2013-04-23T11:04:51]: Verified acquired payload: msi_Sales at
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\.unverified\msi_Sales, moving to: C:\Documents and Settings\All
Users\Application Data\Package
Cache\{42B9B03B-15C3-48D0-B605-F574B1374160}v6.0.166.0\SetupSales.msi.
... and then afterwards there is no "Applying execute package"... so it's
not that it tried to re-install the package and failed - it doesn't want to
know about the package

>From the planning stage..

Planned package: msi_SharedComponents, state: Present, default requested:
Present, ba requested: Present, execute: None, rollback: None, cache: No,
uncache: No, dependency: Register
Planned package: msi_Reports, state: Absent, default requested: Present, ba
requested: Present, execute: Install, rollback: Uninstall, cache: Yes,
uncache: No, dependency: Register
Planned package: msi_Sales, state: Absent, default requested: Present, ba
requested: Present, execute: Install, rollback: Uninstall, cache: Yes,
uncache: No, dependency: Register

reports and sales re-install fine. SharedComponents doesn't. I assume that
"execute: None" vs. "execute: Install" in the other packages is key...
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Set Directory @ Runtime

2013-04-23 Thread John Ludlow

You probably have the action sequenced incorrectly. Make sure it comes
after CostFinalize, because it's only at this point that the install
understands the parent-child relationship between the directories.

Also, read this to see whether the issues described apply to you:
http://blogs.msdn.com/b/heaths/archive/2006/06/14/be-careful-or-even-avoid-using-type-35-custom-actions.aspx


On 23 April 2013 06:00, yogesh bandiwadekar
wrote:

> Hi All
> Below shown is my directory structre.
>
> 
>
> 
> 
> 
> 
>   
> 
>   
>   
> 
>   
> 
>   
>  
>
> I am changing DIRVMSOS Dynamically with type 35 custom action.
> This custom action only changes DIRVMSOS value not the child directory
> value.
>
> for example
>
> I set DIRVMSOS =d:\temp
> it get set to d:\temp but child directory points to defalut location that
> is c:\VMSOS\Config, c:\VMSOS\Config2, c:\VMSOS\License
>
> Can anybody tell me what is wrong  in it?
> What do i need to do for this?
>
> Thanks
> Yogesh
>
> --
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] REMOVE ME PLEASE

2013-04-23 Thread Ian Pender



Ian Pender | Desktop Developer
Huddle - Collaborate intelligently

ian.pen...@huddle.com | +44 (0)203 598 1564 | 
www.huddle.com | @huddle

London | New York | San Francisco

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] PayloadGroupRef as child of Bundle (WiX 3.6)

2013-04-23 Thread Tobias S

Regarding layout-only payloads: For us we use much additional payload e.g.
documentation, videos, CD Browser content and so on for CD image layout ...
mostly handled now by msbuild copy as here e.g. things like recursive
copying of **\*.pdf possible.


2013/4/22 Rob Mensching 

> Seems reasonable probably not implemented originally because we didn't
> expect many layout-only Payloads. They are usually very rare (like maybe an
> autorun.inf or readme.txt).
>
>
> On Thu, Apr 18, 2013 at 10:56 AM, tom  wrote:
>
> >
> >
> > add
> >
> > PackageGroupRef inside the chain
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PayloadGroupRef-as-child-of-Bundle-WiX-3-6-tp7585152p7585281.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> >
> --
> > Precog is a next-generation analytics platform capable of advanced
> > analytics on semi-structured data. The platform includes APIs for
> building
> > apps and a phenomenal toolset for data science. Developers can use
> > our toolset for easy data analysis & visualization. Get a free account!
> > http://www2.precog.com/precogplatform/slashdotnewsletter
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
>
> --
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix ExePackage can't activate log using Burn

2013-04-23 Thread Tobias S

The
"/s /v"REBOOT=ReallySupress /qn /l*v %temp%\MyExe.log""
seems a command for an InstallShield exe which wraps an MSI. Is it possible
to use the MSI directly ?
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Trouble with DotNet

[WiX-users] Entire .NET 4.0 Framework dialog disabled

[WiX-users] Outercurve OSS Conference, May 8-9, Bellevue WA

Re: [WiX-users] Burn and chained MSI paths

Re: [WiX-users] Burn and chained MSI paths

[WiX-users] Burn and chained MSI paths

[WiX-users] How to set a WixVariable using a conditional option?

Re: [WiX-users] Wix ExePackage can't activate log using Burn

[WiX-users] How do I correctly modify an EventLog?

[WiX-users] Install Network Component Type "Service"

Re: [WiX-users] Bootstrapper Upgrade Problem

Re: [WiX-users] MSI Package not installing after upgrade even though InstallCondition set to "1"

[WiX-users] REMOVE ME PLEASE

[WiX-users] MSI Package not installing after upgrade even though InstallCondition set to "1"

Re: [WiX-users] Set Directory @ Runtime

[WiX-users] REMOVE ME PLEASE

Re: [WiX-users] PayloadGroupRef as child of Bundle (WiX 3.6)

Re: [WiX-users] Wix ExePackage can't activate log using Burn

18 matches

Site Navigation

Mail list logo

Footer information