• Application Isolation
  • Your COM components are defined within the scope of your application.
  • Other versions for these same components will not interfere with your application.
  • Allows COM version control that is independent of other installed applications

• Component Protection
  • Future installations can’t overwrite your components creating a version mismatch (DLL hell)
  • Future unistallations will not remove a component that is required by your application.

• Streamlined Installations/Uninstallations
  • All of your applications requirements reside underneath its application folder. Upgrade by replacing the contents of the folder, uninstall by removing the folder.
  • Your application can run from inside a zipped folder on a thumb drive.

• Freedom
  • Removes the dependency of a centralized registry
  • Leave No Trace… You never “touch” a user’s Registry

RegFree loading of COM/OCX components requires no special code in your application. All that’s required is a matching set of manifest files, one application manifest and for each COM component used in your Clarion application; a dependentAssembly manifest.

DependentAssembly manifests are simple XML structures, they are easy to create but it is the values that are hard to come by. One could go digging around inside the registry looking for those values hoping that the value used is the correct one for a given COM component. One mishap and the component will not load. This make them very delicate in the fact that the values must be “correct” for RegFree to work.

This is where the RegFree COM Manifest Generator really shines, you are a few mouse clicks away from a valid dependentAssembly being created for a given OCX being used with your Clarion application.

Screen Shots

Splash Screen

Registered COM/OCX Servers and Controls

Dual manifest editors

Settings and Options

Windows SxS Event viewer