Zip Component, Email Component, Encryption Component ActiveX Control for Zip Compression .NET Components for ASP.NET
ActiveX and .NET Components for Zip Compression, Encryption, Email, XML, S/MIME, HTML Email, Character Encoding, Digital Certificates, FTP, and more ASP Email ActiveX Component

  

  

  

  

  

 

ActiveX DLLs - 32-bit or 64-bit, which do I need?

  • If using Visual Basic 6.0, you'll always use the 32-bit DLLs, even on 64-bit Windows computers. The VB6 IDE is a 32-bit app and therefore at design-time it should reference 32-bit DLL's (even if running VB6 on a 64-bit computer). VB6 produces 32-bit apps, and therefore at application runtime 32-bit DLL's are required (even if on an x64 computer).
  • The simple rule is that the DLL (32-bit or 64-bit) must match the application (32-bit or 64-bit) that loads it. This applies to whatever may be loading the DLL -- whether it's IIS, a Windows Service, your application, or an Integrated Development Environment (such as Delphi, VB6, Visual Studio, etc.)
  • If your IDE is a 32-bit application, then you generally should "add", "import", or "reference" the 32-bit ActiveX DLL's at design time. If you then deploy to a 64-bit environment, such as w/ IIS running in 64-bit mode, then instead deploy the 64-bit build of the ActiveX DLL instead of the 32-bit build.
  • In most cases, your IDE will be 32-bit and it will produce 32-bit applications, and therefore you will always use the 32-bit ActiveX DLL's on both 32-bit and 64-bit computers.


Privacy Statement. Copyright 2000-2012 Chilkat Software, Inc. All rights reserved.

(Regarding the usage of the Android logo) Portions of this page are reproduced from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.

Send feedback to support@chilkatsoft.com

Software components and libraries for Linux, MAC OS X, IOS (IPhone), Android™, QNX, Solaris, HP-UX, RHEL/CentOS
Microsoft Windows 7, Vista, XP, 2000, 2003 Server, 2008 Server, and Windows 95/98/NT4.