Wix 3.x - Include .NET 3.5 in WixNetFX extension - Bug 4584

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Wix 3.x - Include .NET 3.5 in WixNetFX extension - Bug 4584

eyoung100
I've been subscribed to this list and the Users list for awhile now.  
I've just never posted to this list until now, so please forgive me if  
this Topic gets a bit Noobish.

I filed <a href="http://wixtoolset.org/issues/4584/">Bug 4584</a>  
about two week ago, and about that time I asked for a Code Biding  
Agreement, etc. I thought Bug 4584 would be easy to update and upload  
after approval, but whoever Worked my bug sent a reply back saying  
that .NET35 behaved differently in Windows 8, and that my supposed  
easy update would be harder than I thought, and then asked me to  
follow up here.

Without going into much detail as I'm still studying code snippets in  
the Branches, would someone please explain how the behavior is  
different?

Carter


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-devs
The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown
Reply | Threaded
Open this post in threaded view
|

Re: Wix 3.x - Include .NET 3.5 in WixNetFX extension - Bug 4584

Rob Mensching-7
IIRC, dism command line options to install the feature differ across Vista, Win7 and Win8. Or something like that. You'll see it when you start investigation how to install NETFX 3.5 on the different operating systems. Microsoft kinda' made a mess of it.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Carter Young [mailto:[hidden email]]
Sent: Tuesday, November 18, 2014 11:10 AM
To: [hidden email]
Subject: [WiX-devs] Wix 3.x - Include .NET 3.5 in WixNetFX extension - Bug 4584

I've been subscribed to this list and the Users list for awhile now.  
I've just never posted to this list until now, so please forgive me if this Topic gets a bit Noobish.

I filed <a href="http://wixtoolset.org/issues/4584/">Bug 4584</a> about two week ago, and about that time I asked for a Code Biding Agreement, etc. I thought Bug 4584 would be easy to update and upload after approval, but whoever Worked my bug sent a reply back saying that .NET35 behaved differently in Windows 8, and that my supposed easy update would be harder than I thought, and then asked me to follow up here.

Without going into much detail as I'm still studying code snippets in the Branches, would someone please explain how the behavior is different?

Carter

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-devs
Reply | Threaded
Open this post in threaded view
|

Re: Wix 3.x - Include .NET 3.5 in WixNetFX extension - Bug 4584

Phill Hogland
True.  My CA uses fondue.exe if possible on Windows 8 and drop back to dism.exe on win 7.  I don't support Vista any more.  On some versions of Win Srv the command is different than on later win srv IIRC.   On Win 8 or later if the netfx3 package is missing from the OS image it must be obtained from the web (or an iso image).  dism fails in this situation whereas if web connection exists fondue.exe downloads the package.  The fondue package name and command line, is different than dism.exe.  True, a mess!

I also tried to use the DISM API as others here suggested when I struggling with this issue.  DISMAPI is a part of Windows 8 or later, but is not redistributable to earlier OS, except each end user could download a larger SDK and get it that why.  An app written to DISMAPI must run against that specific version of the DISMAPI dll.  At least those were the issues a few months back when I was working on this issue.