Once installed, packages are listed in the Registry under HKEY_CURRENT_USER\Software\Borland\Delphi\ Components meant to be used in the IDE can only be installed as a package, ie.
a DPK master file along with one or more PAS files to be compiled into DCUs and aggregated in a single BPL file that will be registered into the IDE.
You wonder whether you have in fact been having those dreams all your life, and somehow managed to forget about them until now.
Some nights you awaken suddenly and cry out, terrified at the vivid recollection of the strange and powerful creatures that seem to be lurking behind every corner of the dungeon in your dream. As each night passes, you feel the desire to enter the mysterious caverns near the ruins grow stronger.
Eventually you can resist the yearning to seek out the fantastic place in your dreams no longer.
-Following conditions are now support on Types, Methods, Fields: Could Be Internal, Could Be Internal Protected, Could Be Protected, Could Be Private, Should Be Public -Could Be Internal is also supported on Namespaces.
- The assemblies compiled with 'Any CPU' were tag as 'x86' in the Project Properties assembly Window.
Components can be distributed either as Typically, commercial components are provided as binary files, but some can also be bought with source files. PAS or DCU files) can be added to an existing package, or to a brand new package through either File Install Component (when adding to an existing package, the default file is DCLUSR. A package file has the extension BPL, and is just a Borland-specific version of a DLL with added functions like Get Package Info Table(), ie.
routines that live in a file separate from the caller EXE, and that can be loaded dynamically when needed. EXE command-line Borland utility to display information containted in a BPL file.