Avoiding OCX Registration

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi,
I have created a C# application that utilises CommandBars and Docking Panes. I am trying to run the application from a network location using the <codebase> feature of the app.config file that allows .NET assemblies to be downloaded to the client. I am also specifying the generated Codejock Interop files (e.g. AxXtremeSuiteControls.dll and XtremeSuiteControls.dll).
This works fine as long as I have the Codejock OCX files registered on the 'target' machine. I am looking for my client to zero footprint for the application.
Does anyone know of anyway to avoid having to have the Codejock OCX files registered on the 'target' machine? (Is this what manifests are for?)

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Daley Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 19 May 2006 Location: United Kingdom Status: Offline Points: 2	Post Options Post Reply Quote Daley Report Post Thanks(0) Quote Reply Topic: Avoiding OCX Registration Posted: 19 May 2006 at 11:21am
	Hi, I have created a C# application that utilises CommandBars and Docking Panes. I am trying to run the application from a network location using the <codebase> feature of the app.config file that allows .NET assemblies to be downloaded to the client. I am also specifying the generated Codejock Interop files (e.g. AxXtremeSuiteControls.dll and XtremeSuiteControls.dll). This works fine as long as I have the Codejock OCX files registered on the 'target' machine. I am looking for my client to zero footprint for the application. Does anyone know of anyway to avoid having to have the Codejock OCX files registered on the 'target' machine? (Is this what manifests are for?)
	Regards, Daley

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 19 May 2006 at 12:18pm
	ocx is ActiveX file that must be registered. You can put ocx file near interop and manually register it in code.... Try to call DllRegisterServer of ocx.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

Zach Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 19 July 2006 Status: Offline Points: 62	Post Options Post Reply Quote Zach Report Post Thanks(0) Quote Reply Posted: 23 July 2006 at 11:40pm
	Actually - http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/rfacomwalk.asp