Copying a Visual Studio Setup (MSI) project
In VS2003 setup projects are XML files, so you would think it is a simple matter if you are creating a bunch of related MSIs to copy one as a starting point and edit it. Well it does kind of work the steps are:
Open the .vdproj file and search for
Replace all three GUIDS by generating new ones - uppercase characters only! (select newid() in SQL returns GUIDS in uppercase).
Now when you save and open the copy in VS it works. You might get some strange errors, that will lead you to think this is like a corrupted binary file encoded in XML. Occasionally I have had to throw away a file that renders fine in VS but generates bad MSIs.
I'm still trying to decide if this approach is worth it myself, but it can save a lot of time.
Open the .vdproj file and search for
"ProductCode" = "8:{189150D4-09F3-4998-B4B5-A2372E629E66}"
"PackageCode" = "8:{49B725DB-21AC-4FD1-AB84-95D5D2A9EA16}"
"UpgradeCode" = "8:{6394DA18-20B7-48CB-ACA6-C10B9DFC596B}"
Replace all three GUIDS by generating new ones - uppercase characters only! (select newid() in SQL returns GUIDS in uppercase).
Now when you save and open the copy in VS it works. You might get some strange errors, that will lead you to think this is like a corrupted binary file encoded in XML. Occasionally I have had to throw away a file that renders fine in VS but generates bad MSIs.
I'm still trying to decide if this approach is worth it myself, but it can save a lot of time.
posted by ungeeker at
4:54 am
0 Comments:
Post a Comment
<< Home