Re: [WiX-users] WixManagedBootstrapperApplicationHost and .NET 2.0

2012-10-16 Thread Igor Brejc
On Mon, Oct 15, 2012 at 7:15 PM, Rob Mensching r...@robmensching.com wrote:

 What does your BootstrapperCore.config file look like? Does it correctly
 indicate the v2 NETFX should be used?
 On Mon, Oct 15, 2012 at 2:18 AM, Igor Brejc igor.br...@gmail.com wrote:


Hi Rob,

I've tried many combinations. Here's a typical one:

configuration
  configSections
sectionGroup name=wix.bootstrapper

type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
BootstrapperCore
  section name=host
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
BootstrapperCore /
/sectionGroup
  /configSections
  startup useLegacyV2RuntimeActivationPolicy=true
supportedRuntime version=v2.0.50727/
supportedRuntime version=v4.0 /
  /startup
  wix.bootstrapper
host assemblyName=MPWI.Agent.BootstrapperCore
  supportedFramework version=v2.0 /
  supportedFramework version=v3.5 /
  supportedFramework version=v4\Full /
  supportedFramework version=v4\Client /
/host
  /wix.bootstrapper
/configuration

Here's the Netfx package fragment from Bundle.wxs:

  Fragment
PropertyRef Id=NETFRAMEWORK20 /

PackageGroup Id=Netfx2Package
  ExePackage Id=Netfx2Exe
  Cache=no
  Compressed=no
  PerMachine=yes
  Permanent=yes
  Vital=no
  SourceFile=C:\Users\brejc\Downloads\NetFx20SP2_x86.exe
  DownloadUrl=
http://download.microsoft.com/download/c/6/e/c6e88215-0178-4c6c-b5f3-158ff77b1f38/NetFx20SP2_x86.exe

  DetectCondition=NETFRAMEWORK20
  InstallCondition=FALSE/
/PackageGroup
  /Fragment

What's really odd is that I've now actually managed to make it work on .NET
2.0-only machine (the .NET missing dialog is no longer shown). But the
problem is that I don't really know what caused it work, and consequently I
cannot know how to deal with this in the future. Now even if I try to force
it back to showing .NET missing dialog, I cannot do it.

One other thing: I'm looking at the burn log from that machine and it
reports NETFRAMEWORK20 condition to be False:

[0DDC:04C8][2012-10-16T09:38:20]: Setting string variable 'Netfx2' to value
'2.2.30729'
[0DDC:04C8][2012-10-16T09:38:20]: Condition 'NETFRAMEWORK20' evaluates to
false.
[0DDC:04C8][2012-10-16T09:38:20]: Detected partially cached package:
mpwi_x86.msi, invalid payload: mpwi_x86.msi, reason: 0x80070570
[0DDC:04C8][2012-10-16T09:38:20]: Detected package: Netfx2Exe, state:
Absent, cached: None

.NET 2.0 is definitively installed on the machine (SP 2).
I'm sure I'm doing something wrong, but I cannot really tell what.

Thanks,
Igor
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WixManagedBootstrapperApplicationHost and .NET 2.0

2012-10-16 Thread Igor Brejc
Ok, I think I'm on to something.
The .NET missing dialog no longer shows I have the following .config
fragment commented out:

host assemblyName=MPWI.Agent.BootstrapperCore
  !--supportedFramework version=v2.0 /
  supportedFramework version=v3.5 /
  supportedFramework version=v4\Full /
  supportedFramework version=v4\Client /--
/host

Once I put the supportedFramework tags back into XML code, the dialog again
starts to show up.
Any explanations?

p.s. one other thing: what is the appropriate supportedFramework for .NET
2.0? v2.0 or just v2?

On Tue, Oct 16, 2012 at 10:14 AM, Igor Brejc igor.br...@gmail.com wrote:

 On Mon, Oct 15, 2012 at 7:15 PM, Rob Mensching r...@robmensching.comwrote:

 What does your BootstrapperCore.config file look like? Does it correctly
 indicate the v2 NETFX should be used?
 On Mon, Oct 15, 2012 at 2:18 AM, Igor Brejc igor.br...@gmail.com wrote:


 Hi Rob,

 I've tried many combinations. Here's a typical one:

 configuration
   configSections
 sectionGroup name=wix.bootstrapper

 type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
 BootstrapperCore
   section name=host

 type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
 BootstrapperCore /
 /sectionGroup
   /configSections
   startup useLegacyV2RuntimeActivationPolicy=true
 supportedRuntime version=v2.0.50727/
 supportedRuntime version=v4.0 /
   /startup
   wix.bootstrapper
 host assemblyName=MPWI.Agent.BootstrapperCore
   supportedFramework version=v2.0 /
   supportedFramework version=v3.5 /
   supportedFramework version=v4\Full /
   supportedFramework version=v4\Client /
 /host
   /wix.bootstrapper
 /configuration

 Here's the Netfx package fragment from Bundle.wxs:

   Fragment
 PropertyRef Id=NETFRAMEWORK20 /

 PackageGroup Id=Netfx2Package
   ExePackage Id=Netfx2Exe
   Cache=no
   Compressed=no
   PerMachine=yes
   Permanent=yes
   Vital=no
   SourceFile=C:\Users\brejc\Downloads\NetFx20SP2_x86.exe
   DownloadUrl=
 http://download.microsoft.com/download/c/6/e/c6e88215-0178-4c6c-b5f3-158ff77b1f38/NetFx20SP2_x86.exe
 
   DetectCondition=NETFRAMEWORK20
   InstallCondition=FALSE/
 /PackageGroup
   /Fragment

  What's really odd is that I've now actually managed to make it work on
 .NET 2.0-only machine (the .NET missing dialog is no longer shown). But
 the problem is that I don't really know what caused it work, and
 consequently I cannot know how to deal with this in the future. Now even if
 I try to force it back to showing .NET missing dialog, I cannot do it.

 One other thing: I'm looking at the burn log from that machine and it
 reports NETFRAMEWORK20 condition to be False:

 [0DDC:04C8][2012-10-16T09:38:20]: Setting string variable 'Netfx2' to
 value '2.2.30729'
 [0DDC:04C8][2012-10-16T09:38:20]: Condition 'NETFRAMEWORK20' evaluates to
 false.
 [0DDC:04C8][2012-10-16T09:38:20]: Detected partially cached package:
 mpwi_x86.msi, invalid payload: mpwi_x86.msi, reason: 0x80070570
 [0DDC:04C8][2012-10-16T09:38:20]: Detected package: Netfx2Exe, state:
 Absent, cached: None

 .NET 2.0 is definitively installed on the machine (SP 2).
 I'm sure I'm doing something wrong, but I cannot really tell what.

 Thanks,
 Igor

--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WixManagedBootstrapperApplicationHost and .NET 2.0

2012-10-15 Thread Rob Mensching
What does your BootstrapperCore.config file look like? Does it correctly
indicate the v2 NETFX should be used?
On Mon, Oct 15, 2012 at 2:18 AM, Igor Brejc igor.br...@gmail.com wrote:

 Hi,

 I have a simple problem: I've written a managed bootstrapper (WiX v3.6)
 written in .NET 2.0. On my developer machine (I have .NET 2.0 up to 4.0
 installed), everything works fine - my bootstrapper runs and installs.
 Now I'm testing in on an Win XP (with only .NET 2.0 installed), I always
 get the Microsoft .NET Framework Required... screen. I've tried different
 things, like:

- Using RegistrySearch to find the .NET 2.0 key and then using this as a
condition in ExePackage. The key is there in the registry.
- Using standard properties like NETFRAMEWORK20 as conditions.
- Playing with .exe.config file, setting thinks
like supportedRuntime, supportedFramework, runtimeVersion etc.

 I've been really struggling with this, read through all of the docs,
 googled for it, tried a million things, and none of them seem to work -
 .NET 2.0 doesn't seem to get detected. All the samples I found on the web
 use .NET 3.5 or 4.0 as an example and I cannot get it work with 2.0.

 So my questions are:

1. What is the right procedure for setting .NET 2.0 as a minimum
requirement? The minimum bare essentials in the .WXS, .config etc?
2. Alternatively: is there a way to turn off the whole .NET detection
thing in the bootstrapper?

 Any help would be _greatly_ appreciated!
 Thanks,
 Igor Brejc

 --
 Don't let slow site performance ruin your business. Deploy New Relic APM
 Deploy New Relic app performance management and know exactly
 what is happening inside your Ruby, Python, PHP, Java, and .NET app
 Try New Relic at no cost today and get our sweet Data Nerd shirt too!
 http://p.sf.net/sfu/newrelic-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually,

   Rob Mensching
   http://RobMensching.com LLC
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users