Same thing for these two, except we don't even have an existing source of truth for them because components and upgrade codes are MSI-specific concepts. SkinCrafter Installer v.1.0 SkinCrafter Installer is a freeware. Using msiexec you can pass command line parameters to the wrapped setup. This tool can convert your setup executable to an MSI package. > Where are the existing sources of truth for the UpgradeCode and the MSI Wrapper v.2.0.7.0 EXE to MSI converter tool. So because of that, I generated a new GUID to fill in there, and I think it's better to keep that one in place. So in our usage this GUID is meaningless and only there because the schema requires one.įor that reason I'd kind of prefer to specifically avoid using any identifier that actually refers to something already, so that we can reserve it for if we ever end up building a "real" MSI installer that's not just a wrapper. ![]() In a normal MSI, the product ID would be used to determine whether the product is already installed or not, but this MSI won't actually install anything (as far as the Windows Installer framework is concerned). Well, since we're using MSI in kind of a strange and confusing way here, none of these GUID's are used for anything meaningful. > wix file will be updated to reflect this? > Also, I assume the source of truth for the guid will continue to be I guess /browser/installer/windows/msi/ (which does not currently exist) seems like the obvious spot for it. > mhowell: where do you plan to store the wix file in tree? (In reply to Kim Moir ET from comment #7)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |