Yup, I'm pretty sure that was one of the articles I found. (At the very
least, I found several saying the same thing)

The point was that I was (sort of) expecting the burn engine to have a code
path which didn't try to call this function if the OS happens to be Windows
XP/Server 2003 RTM.

If that's not possible because it's statically linked or something, or it's
deemed not worth fixing then that's OK because we don't actually support XP
ourselves, we just would have preferred a better error



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dec-tp7599178p7599181.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to