Have the following questions
(1) the installation program, the DLL and OCX files should be installed under the SYSTEM32, or can be installed to program your own installation directory
(2) the DLL and OCX what circumstance can need not registered, what circumstance must be registered, the registration files in the program after unloading is retained, or a piece of and procedures for unloading (delete)?
(3) a 32-bit system DLLS and OCX files in the installation, if you need to install to the system directory, that in a 64 - bit operating system, which should be installed to the system directory,

Thank you all!

CodePudding user response:

1, see need, anywhere;
2, under normal circumstances the basic need to register; Can complete registration in the main program startup, logout when unloading, of course, also can do that;
3, according to a warrior (zhao4zhong1? Say syswow64 directory

CodePudding user response:

reference 1st floor Topc008 response:

1, see need, anywhere;
2, under normal circumstances the basic need to register; Can complete registration in the main program startup, logout when unloading, of course, also can do that;
3, according to a warrior (zhao4zhong1? Say syswow64 directory

Thank you very much,

CodePudding user response:

General development themselves program use alone can be considered in the application directory, other third parties, sharing can be put to the system directory, or a third party components have a specified directory do,
2, 3 two parts is the job of the installation program will automatically processing,

To do our own file copy, you won't be registered, log off, delete the work?
The problem is too much to consider,

CodePudding user response:

In a 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL

CodePudding user response:

reference 4 floor zhao4zhong1 response:

under the 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL

SETUPFACTORY9.1 I was used to automatically register these files, if under a 64 - bit system, it can automatically handle is placed in the 64 exe and DLL in the directory c: \ Windows \ sys tem32 directory or in a 32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory

CodePudding user response:

reference 5 floor feerserr reply:

Quote: refer to 4th floor zhao4zhong1 response:

In a 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL

SETUPFACTORY9.1 I was used to automatically register these files, if under a 64 - bit system, it can automatically handle is placed in the 64 exe and DLL in the directory c: \ Windows \ sys tem32 directory or in a 32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory

Try not to know.

CodePudding user response:

You see what installation tools do you use, I use the installshield

1, make your own DLL, ocx and own exe used to own targetdir, inside your own DLL, ocx but and other exe utility (such as your company's other software collocation use) in the system,

2. Possible version conflict DLL, ocx in own targetdir inside

3. com DLL, ocx need to register, such as using vb6 you make; .net to make to see when do you have to set some don't, either in

4. You should automatically difference packaging tools, if you want to in 64 under the special requirement on the 32 bit, so we need indicated, otherwise your tool should be able to automatically identify

5. Third party controls generally throw into the gac, or look at your request