GdPicture Imaging

[arimetsap]

Hi,

The GdViewer4 reference states that "You must copy the msvbvm60.dll and the gdviewerpro4.ocx into c:\%Windows%\System32\". However I'm afraid we cannot install anything to system folders, is there any alternatives for doing that?

- What are the downsides it I register the ActiveX component to other folder than System32?

- Why and when the "msvbvm60.dll" needs do be distributed with GdViewer? Is GdViewer compatible with other versions of msvbvm60.dll, or do we need to use that particular version that comes with GdViewer? If I don't distribute msvbvm60.dll but use the version that comes with operating system, what is the oldest compatible version (or operating system)?

Thanks in advance,
- Ari

[Loïc]

HI,

Code: Select all

The GdViewer4 reference states that "You must copy the msvbvm60.dll and the gdviewerpro4.ocx into c:\%Windows%\System32\". However I'm afraid we cannot install anything to system folders, is there any alternatives for doing that?

Yes you can. In fact you can copy gdviewerpro4.ocx anywhere. You just need to register it using the regsvr32 command or through your deployment tool.

Code: Select all

- Why and when the "msvbvm60.dll" needs do be distributed with GdViewer?

The GdViewer uses some functions of this dll. You can copy this file in a folder defined into the path of your system or into your application folder.

Is GdViewer compatible with other versions of msvbvm60.dll

Maybe. However it don't recommend you to deploy your application with an older version of this dll. GdViewer has been built using the last one...

Best regards,

Loïc

[arimetsap]

Cool, thanks.

About msvbvm60.dll: if the GdViewer explicitly loads this library, it would be great if there were a method to define an explicit folder from where the msvbvm60.dll is searched. However I understand that this may be difficult if you don't control the dll loading, but another sub-library loads the .dll ..

Br,
- Ari