Outside of a niche space, I really don't think Core will catch on. And people
who install Core quickly understand what that means and I don't think they are
going to be terribly surprised if an installer tells them .NET is required.
Heck there is a "admin console" for core out there written in PowerShell and
WinForms. :-)
I've seen chatter lately that AMD and Intel driver packages require the .NET
framework. Probably not a concern for a VM but still.
My question would be "why" you were asked to confirm your software would work
on core. Was it just a "what if" check or do you actually have a customer user
story? My installs will take a dependency on something but they will also
properly gate check that the dependency exists.
Re: PE. It's funny you say that. Every once in awhile my boss will ask me for
something that seems impossible to me. And yet he expects me to figure it out
since I'm his architect. He wants to be able to reflect the contents of an
MSI and "install it" either from a Win PE environment or while servicing an
offline image. I can't even imagine how that would be possible and yet he
will claim it is. What do you mean by get your software installed under Win
PE. Do you just slipstream it into the WIM?
----------------------------------------
From: "Bruce Cran" <br...@cran.org.uk>
Sent: Saturday, November 09, 2013 4:58 PM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown
twice (on Windows XP) if bootstrapper contains driver-installation
On 11/9/2013 10:28 PM, Christopher Painter wrote:
>
> And the default contains PowerShell and .NET. It seems like you are
> playing both sides.... trying to make the defaults seem more important
> then they are while at the same time talking about how someone could
> remove PowerShell which is not a default.
>
> In 2013, I feel very comfortable in making .NET my partner in the
> general case. I answer questions on StackOverflow every day and the
> vast majority of developers are still writing horrible InstallScript,
> VBScript, JScript, InstallUtil, EXE, .BAT custom actions. It's hard
> enough to get through to them with C#... C++ is a lost cause.
>
Good point. I was attempting to counter your "I would question why
software is even being installed on a machine like that." - i.e. Windows
Core installations are going to be increasingly common. I guess it
depends what sort of software you're writing, whether you can assume
.NET is going to be present, and whether it's likely to be installed on
servers. In the last few weeks I've had to ensure not only that
installations on Core worked, but that we could also get our software
installed under WIndows PE, which doesn't have Windows Installer!
--
Bruce Cran
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
