Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

InprocServer32 Registry Entries


5 replies to this topic

moverton

moverton
  • Members
  • 22 posts

Posted 31 October 2001 - 16:55

I have an installation created in Developer 7 (MSI).  I am using extract at build for my components, and when they get registered on the target machine, an InprocServer32 entry is created with a hex value,  example:

[HKEY_CLASSES_ROOT\CLSID\{FDCB2348-6A5D-44B5-9115-4845F9F3F92A}\InprocServer32]
@="C:\\Program Files\\Common Files\\Adaytum\\Contributor25\\MTS\\DataProcessing25.dll"
"ThreadingModel"="Apartment"
"InprocServer32"=hex(7):4e,00,5e,00,58,00,62,00,35,00,52,00,71,00,7e,00,74,00,\
 40,00,26,00,6f,00,54,00,54,00,59,00,76,00,62,00,6e,00,75,00,21,00,4d,00,54,\
 00,53,00,43,00,6f,00,6d,00,70,00,6f,00,6e,00,65,00,6e,00,74,00,73,00,3e,00,\
 69,00,2c,00,65,00,54,00,7a,00,24,00,59,00,70,00,57,00,3f,00,48,00,7d,00,6f,\
 00,32,00,47,00,65,00,31,00,57,00,5e,00,74,00,00,00,00,00


Does anyone understand what this is for.  Part of it appears to be the name of the feature with which the component was installed.  They also appear for system files which were installed as part of merge modules.

If the same component is registered manually this key is not present, and it appears to be causing developers problems when they compile newer version of the components on their machines (it is still trying to use the old ones).

Thanks,
Martin


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 07 November 2001 - 17:17

I think this entry is used by Windows Installer for resiliency.

moverton

moverton
  • Members
  • 22 posts

Posted 08 November 2001 - 12:27

But it is just too good for a development environment.  Is it possible to switch off this resialancy?

Thanks,
Martin


mikech

mikech
  • Members
  • 1 posts

Posted 30 January 2002 - 00:07

I'm running into the same thing with ISWI 2.03.  I would love to find a way to turn it off.  If anybody knows how to disable this or even any additional information about it, please reply.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 31 January 2002 - 14:34

This entry is required for autorepair
Autorepair is a feature of Windows Installer (the operating system component from Microsoft, not the development tool from InstallShield).
One way to avoid it would be not to use MSI technology.

Dave I

Dave I
  • Members
  • 195 posts

Posted 05 February 2002 - 12:14

One, cheeky way to get around the repair is:

Run Regedit export the following key: HKEY_CLASSES_ROOT\Installer\Features\{Your Product GUID}

Now keep this safe as you will need it later.

Delete this key, Yes delete it.  You can now hack away all day long, without the repair kicking in.

Remember though, to import the key back into the registry prior to uninstalling, otherwise windows installer wont know what to remove, will it?  


Hope this helps,
Dave

I accept no responsibility for PC's destroyed, days lost or lives taken.