Welcome Guest! To enable all features, please Login or Register.



Last Go to last post Unread Go to first unread post
#1 Posted : Friday, April 5, 2013 4:22:51 AM(UTC)

Groups: Registered
Posts: 2

We are using leadtools version 17.5 in the windows application for displaying images.

The windows application is developed in .Net framework 4.0 and âAny CPUâ options is selected while building the application since the application needs to support both 32Bit and 64Bit environments.

We have the lead assemblies in the application folder and it works in single environment, we are manually replacing the 32bit assemblies with the 64bit assemblies to support 64bit environment. We need the application should support both 32Bit and 64Bit environment by maintaining the lead assemblies in different folders say X86 and x64 respectively and this will avoid the manual step for replacing the assemblies.

Can someone let us know the easy and best way in loading the lead assemblies based on the running environment?

Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

#2 Posted : Monday, April 8, 2013 8:52:45 AM(UTC)


Groups: Registered, Tech Support
Posts: 179

You already submitted an email support ticket regarding this issue. We normally do not handle the same request in 2 places, but this time I am going post additional information for the general benefit.

Our .NET assemblies are not built as Any CPU. There are 2 distinct builds, one for 32-bit and the other for 64-bit Windows. This means you have 3 options:
1. You can create a 32-bit only edition of your application. This should work on both Win32 and x64 versions of Windows. With this option, you only deploy our 32-bit DLLs.

2. You can create 2 builds of your application, and do not use the "Any CPU" configuration. This means you will deploy a 32-bit EXE with our 32-bit DLLs, and another 64-bit EXE with our 64-bit DLLs.

3. You can create an EXE built as "Any CPU", but you must only deploy the correct DLLs for the Windows version. This means it is your responsibility to do the following:
a) On 32-bit Windows, copy our 32-bit DLLs in the same folder that contains your exe.
b) On 64-bit Windows, copy our 64-bit DLLs in the same folder that contains the SAME exe.

Mohamed Abedallah
Developer Support Engineer
LEAD Technologies, Inc.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2023, Yet Another Forum.NET
This page was generated in 0.053 seconds.