I am not talking about removing XP support from the installers, but from the WiX tools. While the numbers of end-users still using XP is still high, the number of developers in that group is far smaller. Frankly speaking, developers should be developing on newer platforms and testing on XP. I agree that it would create overhead, but by partitioning the legacy XP code using compiler preprocessor blocks from newer code, the rest of us are freed while also making it easier to purge the XP support when the time comes.
-----Original Message----- From: Rob Mensching Sent: Tuesday, April 30, 2013 11:19 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle creation error using FIPS Creating a separate release would create even more overhead than trying to support it now. It's hard enough to get all of our test cases covered without creating a whole different release for it. <smile/> That said, I generally agree with your statement about Windows XP being on it *support* deathbed. Unfortunately, last numbers I saw showed Windows XP as the second most popular operating system (after Win7) in the world by a large margin. If my numbers are off, please point me at a reputable source with better numbers and we can consider killing Windows XP... I just don't see that happening in the next 5 years (although I'd love to be wrong). On Tue, Apr 30, 2013 at 8:19 AM, David G. van Hoose < david.g.vanho...@gmail.com> wrote: > <soapbox>Windows XP is on its deathbed, and supporting it should not > hinder > mainstream users.</soapbox> > > Why not release an XP build separately from the main build? > > -----Original Message----- > From: Rob Mensching > Sent: Tuesday, April 30, 2013 09:15 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Bundle creation error using FIPS > > Note: IIRC, the huge issue with SHA2 is that Windows XP doesn't have > support for it natively. We'd have a lot of unhappy people if we dumped > Windows XP support so this is going to be harder than it should be. > > > On Tue, Apr 30, 2013 at 6:52 AM, Jonathan Racine < > jonathan.rac...@hybris.com > > wrote: > > > Bug #3287 is now created regarding this issue. > > > > Regards, > > > > Jonathan Racine > > > > -----Original Message----- > > From: Bob Arnson [mailto:b...@joyofsetup.com] > > Sent: April-19-13 8:54 PM > > To: wix-users@lists.sourceforge.net > > Subject: Re: [WiX-users] Bundle creation error using FIPS > > > > n 19-Apr-13 15:13, Jonathan Racine wrote: > > > >From what I can get out of the Domain Policies, only the SHA-2 > > algorithms were enabled. Official reason given is for PCI-Compliance. > > At > > this point would that become a feature request in order to make the brun > > behave correctly using SHA1 or SHA2 ? > > Please file a bug. Likely we'll have to add a feature to allow a > different > > hash algorithm, to be compatible with existing SHA1 hashes. > > > > -- > > sig://boB > > http://joyofsetup.com/ ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
