Component GUID contains a specific id, what rules do we follow when a new GUID get generated?
Updated: 31 Aug 2010 | 1 comment
Component GUID contains a specific id, what rules do we follow when a new GUID get generated?
Is there a guideline or a specific rules to follow by?
For example, if a DLL interface has changed or updated, do we regenerate the GUID?
Or, if a DLL has been added a new exported function, do we regenerate the GUID?
TIA
Discussion Filed Under:
Comments
MSI.CHM
The windows installer SDK help file MSI.CHM has all the rules you need.
The concept behind the component GUID is that no two components should have the same GUID unless they are IDENTICAL in every respect.
Therefore, even a single byte change in a DLL makes the DLL different to any version that went before, and a new component containing this DLL will require a new GUID.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.