This is bad news. I should be able to reference say icon 167 from Shell32.dll without having to include the dll itself(for sure illegal) or extracted icon files (maybe illegal) in the installation package. If you copy-paste the .lnk files to another machine, they automatically find the referenced icons form shell32.dll, so why not support this when creating shortcuts with MSI?
Possible legal issues could be avoided by creating the lnk file beforehand, and including it as a normal file in the installation. This of course defeats the whole purpose of MSI powered shortcuts and the whole dynamic generation of them is also gone down the drain ... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-a-shortcut-using-shell32-common-icons-tp5002673p7432661.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
