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

Reply via email to