Topic Path: Migrating to Indy.Sockets Version 10 > Packages Changes
Packages Changes

One significant change in Indy 10 is the reorganization of the library into four separate packages. 

  • IndySystem
  • IndyCore
  • IndyProtocols
  • IndySuperCore

Each package, except IndySystem, consists of both a runtime and designtime .DPK file for Delphi compiler versions 4, 5, 6, 7, 8, Delphi 2005, Delphi 2006, and Kylix 3. (IndySystem has only a runtime .DPK file - the designtime .DPK is not required.) 

.DPK files for the packages include the package name and the compiler version as part of the package file name. For instance, the IndySystem package file for Delphi 7 is represented by the following: 




For platforms that offer support for .Net, the package file naming convention is similar but includes a suffix that indicates support for the .Net platform. For example: 




For packages that include designtime components, an additional package file is available. For instance, the designtime IndyCore package file for Delphi 7 is represented by the following: 




.DPK files are located in the same directory as the source code for the package. The following is a list of the package file names and directory names relative to the Indy installation directory: 


Indy Packages for Delphi 4 Pro and Enterprise




Indy Packages for Delphi 5




Indy Packages for Delphi 6




Indy Packages for Delphi 7




Indy Packages for Delphi 8



Indy Packages for Delphi 2005 (Win32 support)




Indy Packages for Delphi 2005 (.Net support)




Indy Packages for Delphi 2006 (Win32 support)




Indy Packages for Delphi 2006 (.Net support)




Installing Indy Using Package Files


Installation of the Indy library using the package files is a very simple process. Package files need to be built in the following order: 

  • IndySystem
  • IndyCore
  • IndyProtocols
  • (optional) IndySuperCore (for Delphi 7 only)

If a package has both runtime and designtime .DPK files, the runtime .DPK must be compiled. The designtime .DPK file must be compiled and installed in the IDE. Since source code resides in separate directories for each package, the directory name for any dependent package must be added to the library search path using the IDE options. For example, the following steps are required to install Indy 10 for Delphi 7 including the optional IndySuperCore package: 


Package file name 


Changes to the Uses Clause


As a result of package and unit changes, the Uses clause in programs may need to be edited to reflect that the proper file name is in use. This could be a result of different search or library paths in the IDE, but most often it is because something moved from one unit to another unit and can no longer be resolved at compile time. 

When attempting to open a project created with a prior version of Indy, you may receive warnings about missing properties when loading DFM files. This is caused by Forms or Frames that contain visual Indy components with properties that have been removed or renamed in Indy

  1. In most cases, you can Ignore the error message, recompile, and
save to the form to eliminate the warning. In the worst case, you may be required to removed the troublesome component and re-add the component in the IDE. 

For more information about .Net-specific code and issues, please refer to the Delphi documentation in the "Porting Applications to VCL for .Net" section. 


Copyright 1993-2006, Chad Z. Hower (aka Kudzu) and the Indy Pit Crew. All rights reserved.
Post feedback to the Indy Docs Newsgroup.