Develop registration-free .NET application with DicomObjects.ocx
When you are going to use DicomObjects.ocx, normally you will have to register it, either manually via Regsvr32.exe or some sort of installer program which does it automatically for you. This is all fine when you have the permission (as a developer, you are almost guaranteed to be the system admin), but exception will be thrown when you are restricted user (i.e. people using the pc on your client site).
People can solve this problem by logging in as system admin to run the regsvr32.exe or the installer program, but this will always require a system admin user name and password which normal users probably don't have.
That's why we have this page here, to show you how to make a simple change in your project to make it registration-free. As shown in the following picture:
Select DicomObjects from the "References" list, then change the "Isolated" from False to True. Rebuild your project and that's it!
The change we made here is making the application registration free. So if you deploy it onto a test machine which doesn't have DicomObjects.ocx registered, the application will run as if DicomObjects.ocx is registered. What happens is when you set the "Isolated" property of DicomObjects to true, Visual Studio creates an XML manifest file named YourAppName.exe.Manifest that contains the ClassID and type library information for the DicomObjects.ocx — the same information that was previously stored in the registry.
The above approach is known as the "Reg-Free COM" supported in the operating systems such as XP(Service Pack 2), Windows Server 2003 and Windows Vista. The downside of this approach is that the same DicomObjects.ocx is isolated and won't be accessible to other programs.