Browse Prior Art Database

Registering com dll’s with “com extract at build”, without adding content to the COM tables in a minor upgrade

IP.com Disclosure Number: IPCOM000240729D
Publication Date: 2015-Feb-23
Document File: 2 page(s) / 239K

Publishing Venue

The IP.com Prior Art Database

Related People

Kajal Kumar Biswas: AUTHOR

Related Documents

158639: IP.COM

Abstract

This invention talks about doing COM registration of COM files in a different way in a minor upgrade, which were getting registered via the COM installer tables in the msi package. The dependency on the installer tables are cut off by this invention thus allowing the patch to be a un-installable patch.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 57% of the total text.

Page 01 of 2

Registering com dll's with "com extract at build", without adding content to the COM tables in a minor upgrade

Abstract -

This invention talks about doing COM registration of COM files in a different way in a minor upgrade, which were getting registered via the COM installer tables in the msi package. The dependency on the installer tables are cut off by this invention thus allowing the patch to be a un- installable patch.

Detailed description of the invention (discussing the problem and the solution) -

In order to make the patch un-installable there are certain rules to be followed. Without following these basic principles we cannot uninstall a minor upgrade patch.

    The rules which stopped us from making a patch un-installable was the COM entries getting populated in the COM tables during minor upgrades. Minor upgrade patch rules clearly says that no rows should get added to the com tables i.e. we cannot have clsids/progids added to com files which have the "com extract at build" set to 'Yes'.

This means we cannot un-install a patch if we do com development for this kind of components marked with this property.

As a result to solve this issue, I came with a solution which I'll describe now.

There are group of components in the installer for which we do dynamic extraction of COM data and place it in the class, progid, mime, extension etc, tables known as the com tables in a windows installer package. In the full release we do not have a problem. But when we move...