When preparing an installation file for deployment of a standalone application, which items need to be registered by the installation process?

I see several references here to registering some .ocx's, but no specific information on what or how. I also suspect this has changed with 7.0 since OIPI has been assimilated.

I tried installing a partially completed application on a client's Win 2000 computer WITHOUT registering anything, and everything seems to work normally except for printing and print previews. I assume there are still a few OIPI components that need special attention.

I realize I could just run the 7.0 update against the installed application and everything would be registered, but I want to learn how to do this right from within the install script. It would help at least knowing what needs to be registered during the installation.

Do we need to have an updated client install?

Thanks!

Jim,

If you are only using the OIPI for printing, then you would only need to register the two primary OCX controls to get a 7.0 application to work on a fresh machine. From a command line here is how you would do that:

REGSVR32 path\VSPRINT7.OCX

REGSVR32 path\VSPDF.OCX

If you are using an installation program then that should handle the registration for you as long as you flag those files appropriately within the install project.

If your application uses the Revelation Reporter, then you might have to run the same client install as before in order for that tool to work.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

This is what I was doing in Installshield:

LaunchApp(svTarget ^ "vbrun60sp5.exe /Q","");

LaunchApp(svTarget ^ "RegSVR32.exe /s vsprint7.ocx","");

LaunchApp(svTarget ^ "RegSVR32.exe /s vspdf.ocx","");

Is the first line no longer required?

Jim,

From everything I've read about vbrun60sp5.exe it is only used to get the OIPI to run. I assume that was essential because originally it was a VB application. Now that that the core components of the OIPI, i.e. the VideoSoft OCX controls, are directly on an OI window rather than a VB form it would seem to me that this is no longer necessary.

Another very cool thing about OI supporting OLE!

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Jim-

First line no longer needed. It installes the VB runtime components required for OIPI32.EXE; since we don't use that anymore, we don't need line one.

Mike

I appreciate the help.

I made my own client install with a script to install and register the two OIPI .ocx's, and create application icons on the workstation. Problem solved. It's easy once you know what needs done!

(It also helps if you make sure you are logged into the workstation with administrator priveledges first!)

I assume from this discussion the file vbrun60sp5.exe can be deleted.

Perhaps a couple of sentences on this subject could find their way into the online documentation or knowledgebase? I think new users would appreciate that.

Thanks,

Jim

Thanks Mike, I'll change my installshield script.

View this thread on the Works forum...