Combined 32-bit and 64-bit development

[TheLeePiper]

We are updating our 32-bit code set for compilation in 64-bit. One of the development realities is that there will be some period of 32-bit and 64-bit development overlap as we get everything worked out. My first question is if this documentation page is still relevant: https://dynoinsight.com/Help/V6_0/Compo ... d/x64.aspx?

Then, do you have any other particular suggestions about how to best manage the DLL usage? I am assuming that the project needs to point to the proper bitness of KerCADe.DLL, but are there other "best practices" you can suggest? Thanks!

[Nick]

Hello

The topic you mention is related to the old KC interface. With the new _DG interface, introduced in v6.0 you do not need to add anything in the code. It should compile OK for both bitnesses.

Starting with v7.0 in .NET applications you can use AnyCPU configuration and do not think about bitness at all. DGK installs both bitnesses and selection of the assembly to load is done at runtime depending on the bitness the application runs.

It is automatic for native applications as well: Selection of bitness in the case is done at compile time. At runtime the ActiveX control will load the correct assembly because it is linked to it.

So, if you use versions 7.0 to 7.3 you should be OK for both bitnesses support without any effort.

Just to remind for other readers: Starting from v7.4 DGK will not have anything related to 32 bit. This is the state of the industry.

Regards

[TheLeePiper]

I am also concerned about installation and registration of both 32-bit and 64-bit DLLs. I haven't tried to do so, but can you register both bit versions?

[Nick]

Certainly. If is what the downloadable DGK installers do automatically. Full DGK installer, redistributable exe and the merge module all include binaries for both bitnesses and register them when installed.

[TheLeePiper]

Got it. Thanks!