When creating internet download bootstrappers that reference Microsoft
packages, what are the best practices?
For example InstallShield has a Setup Prerequisite that can download
vstor40_x86.exe from Microsoft.com through go.microsoft.com/fwlink link ID that
resolves to the download url for that EXE. InstallShield didn't create a PRQ
for vstor40_x64.exe and I need to make one. I've found the Microsoft page that
has the download links for x86/x64.exe but I can't find an fwlink ID that
resolves to the x64.
What is Microsoft's position on this? Do they document the fwlink ID's
anywhere
and do they want us linking to Microsoft so that they can control the
availability or is this a bad practice which is just leaching off of Microsoft?
Chris
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
