Can anyone confirm my understanding of Delphi package libraries. Dclusr50.dpk - Component library - Contains header information for units(.pas), compiled units (.dcu), package libraries (.bpl), and compiled packages (.dcp). Can be changed by using Components/Install Components from the IDE. Vcldb50.bpl - Package library - Collection of components - simular to windows DLL libraries. Different between Delphi 3 and Delphi 5 libraries.
Can be changed by selecting Components/ Install Packages fromIDE. Vcldb50.dcp - Compiled Package (Package header). Collection of.bpl libraries. Added by selecting Add Runtime Package from Project options.
This is the extent of my knowledge. Now the reason for this overview is to find out how to simply install a new unit (.pas or.dcu) to the Component library. Thanks in advace for any enlightment. Let's try to fix this: DPK files are the source code files for packages. Like DPR is your project's source code. You could say it stands for Delphi PacKage, like DPR for Delphi PRoject.
Delphi Runtime Error 217
BPL is a compiled package. This is a special DLL that Delphi builds from a DPK. It's just like a DLL with some additional code for Delphi. A BPL is a DLL, but a DLL is not necessarily a BPL. A BPL contains the compiled code of components so that they can be used by your program. You don't have to worry about accessing the library - putting the component on a form does that. There is a difference between runtime and designtime BPLs.
Runtime BPLs can not include any code that provides special features for your component in the Delphi IDE (at least not in D5, this has been discussed here a lot). That means, you can not place code for property editors, context menu extensions (when right clicking a component) etc. In a runtime BPL. Runtime BPLs can not be installed in the IDE.
Designtime BPLs however, can contain both the component's code and IDE extension code. Designtime BPLs are the ones you install to add the component icons to the palette. Example: you have a button component. For the caption property, you've written a nice editor that the IDE displays when you click the ellipsis-button in the Object Inspector. You can't put the component source code and the editor source code together in one unit and install it into a runtime BPL. You must split the code.
The component code (WITHOUT the Register procedure) goes into one unit, and the Register procedure and the property editor code go into a different unit (of course it 'uses' the other unit with the component's source code). You now add the component unit to a runtime package and the register unit into a designtime package and you're fine. Otherwise you get errors. However, when putting the component and property editor code into one unit, you can still add this unit to a designtime only package. That's fine as well. DCP files are a concatenation of the component units.
I THINK (and that's my personal opinion) that DCP files are needed for design time packages only. When not using runtime packages, the code is copied from the DCP into your compiled EXE so you can use it independently. When using a runtime package, other code used that REFERS to the runtime package's code. DCP files are created when compiling a package. Packages were introduced to decrease the size of applications. Instead of linking the code of all components into your EXE-file, you can ship it as a separate file (the BPL file).
Your EXE-file uses the BPL file like a DLL, getting the component code from there. For example: you have a large project with several executable files. There is a subset of components all those applications use. Instead of linking those components into every single EXE-file (increasing its size), use a runtime package. All the EXE-files use the same runtime package - the size in total is smaller.
The package functions like a runtime library. Also, you can use packages to distribute your components in binary form (not shipping the source code). Then you must ship the BPL and the DCP file. About installing units: You only need to install a unit if it containts a component which you intend to use at design time. You can add normal units to a package (I think) but that wouldn't make much sense, as you can't use a normal unit like a component anyway.
The exception is: the unit is needed by a component. Then it will be implicitly added to the package if you don't add it manually. If you just want to USE a unit, put it into your project folder. If you need it in more than one projects, add it to a folder that is in the library path (e.g. Delphi5 lib).
To install a component, just use the 'Component/Install Component' menu item. This brings up a dialog where you can select the package you want to add the component to. Adding to Delphi's standard packages is not recommended (also, not allowed, I think). It's best to use the DCLUSR50.DPK package or a new package you create for your own components. Try to group them, e.g. Make a DCLFREEWARE.DPK and DCLSHAREWARE.DPK or anything you want as a categorization. Hire car drivers sydney jobs. To distinguish designtime from runtime packages, I recommend putting 'dcl' before the package name, e.g.
DclFreeware50.dpk for designtime package and freeware50.dpk for runtime package. Did that help you? I hope I got everything right here. If I wrote bullshit, please update me on that topic as well;-) Regards Thorsten. Quote This is the extent of my knowledge. Now the reason for this overview is to find out how to simply install a new unit (.pas or.dcu) to the Component library. Component Install and browse to the pas file you want to install.
OK it and choose a package to install it into. Alternatively, create a whole new package with File New Package and proceed as stated. Madness takes its toll.
Please have exact change ready. 'That's Bill for ya, always sharpening his sleeping skills.'
ICQ: 91418899 http://members.nbci.com/edduffe. I'm trying to install Delphi 3 database components into my Delphi 5 environment. Why Borland does not distribute database components with D5 standard, I have no idea. Every other major framework (ie Visual Basic, powerbuilder, etc does). Borland used to favor the individual develper, why abondon us now?
My Delphi 3 environment is composed of the following: 1. DCLUSR30.DPK - Source library. VCLDB30.DPL - Design time library (BPL in Delphi 5).
VCLDB30.DCP - Runtime package library (DCP in Delphi 5). The DBCTRLS.PAS/DCU units. Let me know if this can even be attempted. Thanks in advance. Quote My Delphi 3 environment is composed of the following: 1. DCLUSR30.DPK - Source library. VCLDB30.DPL - Design time library (BPL in Delphi 5).
VCLDB30.DCP - Runtime package library (DCP in Delphi 5). The DBCTRLS.PAS/DCU units. Let me know if this can even be attempted. DCLUSR30 (as the name suggests) is meant for your own private components.
This won't contain anything if you haven't installed anything! VCLDB30.X are the compiled DB packages for Delphi 3.
I don't think you'll even be able to install them in the IDE. You can try, but I don't think that goes well with the license agreement. Regards Thorsten. Quote wrote: I'm trying to install Delphi 3 database components into my Delphi 5 environment. Why Borland does not distribute database components with D5 standard, I have no idea.
WIthout source, you can't. The internal structure of a package is version dependent. So you can only use packages compiled with the same version of Delphi. The hierarchy tree of the VCL changes from version to version, so you need a lot of source changes until you can use low level D3 source in Delphi 5.
Regards from Germany Franz-Leo. Quote snowskier wrote: I'm trying to install Delphi 3 database components into my Delphi 5 environment. Why Borland does not distribute database components with D5 standard, I have no idea. Every other major framework (ie Visual Basic, powerbuilder, etc does). Borland used to favor the individual develper, why abondon us now?
My Delphi 3 environment is composed of the following: 1. DCLUSR30.DPK - Source library. VCLDB30.DPL - Design time library (BPL in Delphi 5). VCLDB30.DCP - Runtime package library (DCP in Delphi 5). The DBCTRLS.PAS/DCU units.
Let me know if this can even be attempted. Thanks in advance. TK - Jeff Overcash (TeamB) Talk about failure (Please do not email To fall is not to fail me directly unless Failure isn't about falling down asked. Thank You) Failure is staying down (Marillion). One more newbie question regarding components DPKs. The DPK file contains a requires and contains clause. The package I'm trying to install requires VCL50 (I assume this points to a DCP library), and a contains clause which points to a.PAS unit - this is strait forward.
And so is using the IDE to install another unit in a existing package. What I don't understand is how to include the package in your project. Is it used in your source to locate other source modules?
The aforementioned sample has a.PAS and a.DCR file included. The.DCR file is another animal I haven't used directly. I have read Borlands online documentation and cannot get a clear view of the DPK/DCR concept. Thanks in advance for your enlightenment. Quote The aforementioned sample has a.PAS and a.DCR file included.
The.DCR file is another animal I haven't used directly. I have read Borlands online documentation and cannot get a clear view of the DPK/DCR concept. OK, I'll try and explain.
Delphi programming is based on the component concept. A component is an object (the Object Oriented way, meaning: it is a class) which you can place on your forms at design time. Components can either be visual (acting like a control in your window) or non-visual (you only see it at design time). Example: TTimer is non-visual, TEdit is visual.
Visual components are used to actually design the user interface. Non-Visual components can assist other components or create links between components, but they can not be seen at runtime. TAction is a good example. It is non-visual, but at runtime, it determines the captions and states of TMenuItem or TButton controls (as an example). The advantage is that components are highly reusable and redistributable. Just drop them on the form and there you are - you can set properties, react to events and whatever. The difference between a normal class and a component would be that a component provides some kind of visual feedback, even if it is only at design time (for non-visuals).
You can set properties and events in the Object Inspector. Normal classes (e.g. Mp4 downloader pro registration key. TStream or TRegistryIniFile) can not act like a component.
You can't see or use them at design time (unless you write a component that encapsulates the functionality, meaning, it internally uses TRegistryIniFile but allows you to specify the registry key at design time). Now, Delphi allows you to install new components in addition to the ones that it provides itself. Components that Delphi 'knows' are shown in the component palette. You can get MILLIONS of components on the internet or you can write them yourself (should I discuss this here as well??;-))). Now it gets a little more complicated: Mostly, an installable component consists of at least two files: the unit with the source code of the class, and an additional resource file, which just contains one image (24x24 bitmap). The unit file and the resource file have the same name. Example: smiley.pas and smiley.dcr ('Delphi Component Resource').
The bitmap icon is used by Delphi and put into the component palette. That's the only purpose of the DCR file - to give you a visual representation of the component on the palette. The icon is also used to draw non-visual components on your form at design time. E.g., if you drop a TTimer onto your form, you see a button-like thing with the timer symbol on it. That's the design-time representation of the Timer-component.
If you DON'T provide a DCR file, you get a standard icon for the component. That may either be the icon that belongs to the component you derived the new component from, or (if there is no such 'base-component') a standard icon. E.g., if you create a new toolbar-component deriving from TToolbar without creating a DCR file, your new toolbar will have the same icon as TToolbar on the palette. So far so good, now: Delphi lets you organize your components in packages. A package is like a bundle of components that may (but don't need to) serve the same purpose or have something in common. It's basically your decision how to group them. Maybe split it up into freeware/shareware or visual/non-visual - whatever.
You can add as many packages as you like. For example, if you've downloaded an internet component suite from the internet, most probably a package source file was included as well which you can directly open and install. All the internet components are bundled into one package. Again: The component is the smallest part of the entire thing. It's just a class which you can use at designtime on your form. A package is a bundle of such components (or maybe even just one) which can be registered with Delphi. ONLY if it is registered with Delphi, the components are visible on the palette.
A package can 'require' one or more other packages. That means, the other packages contain code that is needed by one of the components in the first package = the first package needs to 'use' the other packages. The other packages need to have been compiled before. All installed packages are listed when you click on 'Component/Install packages'. Each entry in the list of design packages stands for an installed package. The mark in front of the item says, whether the package is available at design time. You can 'show' or 'hide' entire packages here without deinstalling them.
For example, your current project doesn't need the internet component suite you've just installed. So why have the components on the palette?
Remove the mark in front of the name of that package and the components are hidden from the palette. Later, if you need them, just come back and set the mark - there they are again.
Now it gets even more complicated: you can create design time and runtime packages. A runtime package acts like a DLL for your program (and the IDE as well). It contains the component code your program relies on, but that component code is not statically linked into your program. Your program just contains references to the runtime package = the exe-size is smaller, but you need to ship one or more additional package library files, like you'd need to ship other DLL you use. The difference between a runtime and a design time package is that components from a design time package are statically linked into your project = your exe grows, but on the other hand you don't need to distribute other package files. You can't install runtime packages in Delphi. To use components from a runtime package, you need a design time package that requires the runtime package (read on, please.).
You declare your package to be runtime or design time (or both) in the projects options of the package. Normally, you create design time packages. You don't have to do anything to 'use' a design time package. You just drop a component on the form and the code is taken from the package and linked into your project. Again: you then don't have to ship the package file with your project. Things are a little different with runtime packages. DEEP BREATH.
When you create a component, you need to write a procedure named 'Register'. This procedure is called when the package is installed with Delphi. It tells Delphi the class name of the component(s) to install and the name of the page on the palette where the component should appear. If the author of the component wrote some nice property editors for his component, they are registered here as well. A runtime package MAY NOT contain such design time code (because the design time stuff relies on code that is not available for runtime packages). If it does, you most probably won't be able to compile the runtime package. You need to split the code into two units.
The author of the component will most probably have done that. If it's your own work, you need to do that. The first unit contains the component's source code only (without the register procedure). You can add this unit to a runtime package and compile this package. Now you need to install the component in Delphi to be able to use it. You do so by adding the other unit (the one that contains the property editors and the Register procedure) to a design time package, which you later install. You may have to 'tell' the package manually that it requires the runtime package.
Now you can work with your component like you normally would. If you build your project without runtime packages (see project options), the code is again taken from the package and statically linked. You don't have to redistribute the runtime package file. HOWEVER, if you tell the compiler to use runtime packages, you'll need to redistribute the runtime package you created above! Please note that this is a 'one way problem'. You can add units that contain property editors, component source code and the register procedure to a design time package.
You can also add components that are split up like described above to a design time package (you just need to add both units to it). But you can't add a unit that contains the design time code to a runtime unit. I'll try to make pictures (use COURIER font to view).
First of all, how are the packages used by the Delphi IDE? +-+ +-+ Delphi IDE - dynamically uses - Design Time Package +-+ +-+ +. Thanks for your perseverance and excellent input. And since you're still responding I will ask one more message on this thread.
I understand design time and runtime packages and how to use them - thank god. And my understanding of the DPK is he keeps info on source units so they can be compiled into a project. What I still unclear is how to use the DPK library within the IDE. I've seen package clauses in source units, but there must be additional magic which takes place besides simply specifying the DPK in source. Thanks for the useful advice. Quote And my understanding of the DPK is he keeps info on source units so they can be compiled into a project.
Well, nearly, but not quite. Before I continue I have to correct what I said before: it seems like you can add any kind of unit to a package. I'll explain this later.
First of all, you can use units that are not part of a package. That is true for both 'normal' units and component units. You can even use components that are not part of a package, but then you MUST create them manually at runtime and can not use the Object Inspector at design time. To do THAT, the component unit must be installed into a package, which is then installed in Delphi (that's what I explained last time).
Units you use without adding them to a package must of course reside somewhere in the library path. You need design time packages to make COMPONENTS available at design time. That means, the Delphi IDE does not 'know' about components unless they are included in an installed design time package.
For Delphi, a design time package is like a plugin from which it takes information about the components it displays on the palette and where the corresponding compiled units can be found for static linking. This doesn't seem to have any effect on the unit files, meaning: you still need the unit files for all the components and units included in the package, as Delphi needs to statically link them into your project. Runtime packages contain compiled unit source code that is available at runtime. Like a DLL exports a set of functions and procedures. You can not install runtime packages in the IDE, but you can create a design time package that contains the code to register components with the IDE that are part of the runtime package. So the runtime library acts like a DLL for the design time library (the RT package contains the code, the DT package contains information for Delphi on how to use that code).
The design time package REQUIRES the runtime package. Now there are two cases: 1) You are building your project WITHOUT runtime libraries Delphi takes all the code and compiles it into your exe file. That is: code from standalone units, code from units in design time packages AND code from runtime packages. The latter is taken from the runtime packages DCP file. You get a single exe file that does not require any additional runtime packages. 2) You are building your project WITH runtime libraries Delphi first of all looks up the runtime libraries it should use from your project options. You can edit this list.
For example, you can instruct Delphi to use no runtime libraries but the one that contains your own components. Delphi then takes code from standalone units, units that are part of design time packages and units that are NOT part of the runtime libraries you have selected and statically links it to your exe. Then it creates references to any code that is contained in the runtime libraries you've selected and links them into your project. Now you get an exe file that is smaller but requires one or more additional runtime libraries.
Example 1: you are NOT using any third party components, but only components that were installed during the Delphi installation. You tell Delphi in the project options to use ALL standard runtime packages for compilation, then your exe would be very small, but depending on the components you use you'd have to distribute one or more runtime packages. Example 2: you are creating a console application that ONLY uses the unit Windows. You're building with runtime packages. Presumably, your exe size wouldn't change much, but you'd have to redistribute VCL50.BPL along with your application, as the unit Windows is part of the VCL50.BPL package and your application contains references to that package as you use the unit Windows.
Quote What I still unclear is how to use the DPK library within the IDE. That depends: 1) Design time packages Open the DPK file, press the 'Install' button in the little designer window and if there were no errors, Delphi registers the BPL file with the IDE and from now on uses it automatically (it displays the components used).
The DPK file is only important because it is the source code of the compiled file. Just like a DPR file is (part of) the source code of a DLL or EXE.
2) Runtime packages You don't explicitly use the runtime package at designtime. You use it implicitly by installing a design time package that requires it.
You only use it at runtime (if you're compiling with runtime packages) by using code from it. That is: by using a component that is installed into the runtime package, or by using a unit that is included in that runtime package. Quote I've seen package clauses in source units, but there must be additional magic which takes place besides simply specifying the DPK in source. Could you give me a code sample for that? I've NEVER EVER seen a unit that contained a package clause. Are you sure that you're not talking about Java here? There's just a WEAKPACKAGEUNIT compiler directive, but you can read about that in the help.
I may be wrong, but I'll say it like that anyway: there is NO way of a unit specifying to which package it 'wants to belong'. Also there's no way of USING a package by specifying something like a 'use package X' clause. I repeat: you use a package by using code that is compiled into the package, either by using a component at design time (which first uses the design time package, and maybe after that a runtime package), or by using a unit that is part of a runtime package.
Regards Thorsten.
In fact, an strange problem in happening. When installing, I put the serial key, and the next screen comes with no text.
This screen should display the Licence Agreement. So, the next screen have the title “Information” also cames with no text in the box. After choose a typical install mode, another screen with Remote Dataset Licence Agreement comes without text, and after the last screen with the button “next”, an error occurs: “Error copying file: unknown error code: -1 Source file:.cnf Destination file: “. On the next screen, when files should start to be copied, another error message comes: “Setup has detected a -113 error while attempting to copy files.
This indicates that setup could not find a file in the runimage directory. If you have copied the install directory to new location you will also need to copy the runimage. This error may also occur if you are installing from a network and you do not have the CD root mapped to a drive letter.
Component: program files main program files. File: runimage delphi50 bin orbpas50.dll Error: -113. Thanks in advance for some tips, Hylson.
Library Notes The libraries can be stored in the Windows system folder, or with the programs, although the single-file install will place the libraries in the Windows system folder. I assume you will have downloaded all the libraries, but in these instructions I'll write as if you haven't. I expect you understand all the Zip stuff as well, but I'll write as if you are a complete beginner. No offence intended, simply that I can then re-use the notes! All libraries can be found on the page. Most libraries are contained in a single installable.EXE files, the olthers are Zip files.
You will need a tool like WinZip to extract the files from the Zip archive. When referring to the folder 'Windows system', I mean the one where KRLN386.exe lives - this is a system file. Do not put the libraries in folders off the Windows system folder as the libraries will not they be found. Windows XP notes Windows XP may require that you load the libraries directly into the folders of the programs you wish to run.
Although a slight nuisance, this should protect you from DLL updates for one program which break other programs. Please bear this in mind when installing the libraries. If you have 'Hide protected operating system files' checked in Windows XP, you may not see the.DLL files in the Zip file Windows XP/2000/NT note Windows XP, 2000 and NT normally use the Windows System32 or WinNT System32 folder rather than Windows System. Please bear this in mind when installing the libraries. The single-file install will do this for you automatically. Explorer View - Options menu Be warned that as supplied, Windows Explorer hides file types including DLLs from you. Uncheck the View - Options - 'Hide files of these types:' if you want to see the DLLs once they have been extracted from the Zip archive.
I mention this as at least one person complained that the Zip archive was incomplete. You can reset the 'Hide.' Option later if you want. I am currently making most applications built with Delphi 5, so you are unlikely to need the Delphi 4 library.
Delphi 5 runtime - VCL50.BPL. Download the runtime. Extract and run the included.exe file Delphi 4 runtime - VCL40.BPL.
Download the. Extract the file VCL40.BPL. Copy the file VCL40.BPL to your Windows System folder At this point, the programs should start, but could complain of other DLLs being missing. The name of the DLL is the clue to what to download next. Pentium PNG library - lpng-px.dll.
If lpng-px.dll is missing. Download the (new version).
Microsoft Runtime Download
Extract the file lpng-px.dll. Copy the file lpng-px.dll to your Windows System folder. As this is a new version, you cannot use it in place of the old version, so do not try and rename it to LPng.dll! PNG library - LPng.dll. If LPng.dll is missing. Download the (old version). Extract the file LPng.dll.
Copy the file LPng.dll to your Windows System folder Intel JPEG library - IJL15.dll. If IJL15.dll is missing. Download the runtime. Extract and run the included.exe file. Intel JPEG private library - IJL15PVT.dll Due to an incompatibility discovered only after an update to the Intel JPEG library was released, TVwriter needs its own private version of this library.
The correct file is included with the TVwriter Zip archive. Because the file is a local patch rather than a version for all software to use, it has a different name and should be copied to the TVwriter.exe folder rather than the Windows system folder.
If IJL15PVT.dll is missing. Download the. Extract the file IJL15PVT.dll. Copy the file IJL15PVT.dll to the same folder as TVwriter.exe Intel Image processing libraries - IPL.dll, IPLxx.dll. Download the runtime. Extract and run the included.exe file Intel Signal processing libraries - NSP.dll, NSPxx.dll.
![]() ![]()
Download the runtime. Extract and run the included.exe file. OpenGL library The OpenGL Library which is required for WXtrackGL is included in all recent versions of Windows, however the original Windows 95 requires a 483KB update from Microsoft site named. Other errors and external exception C000001D AMD 350 and later with Windows 95 If using an AMD 350 device or later with Windows 95, please ensure you have the. Older Cyrix Processors You may find that very early Cyrix processors e.g. P150+ do not return the CPU ID that is required by the Intel libraries to determine which processor is in use.
In this case, you may need the CPUIDEN program from. Due to a conflict between the Pentium III processor and older versions of the operating system, in particular Windows NT and possibly Windows 95, you may get an error 'External Exception C000001D'. This may be resolved by upgrading to Windows 98, or applying the latest Windows NT Service Pack (SP5 or SP6). I had the problem when I upgraded from a Pentium II to a Pentium III, and found that reapplying the NT Service pack cured the problem.
If this does not resolve the problem for you, please go to your Windows system folder, rename the file nspA6.dll to nspA6-old.dll (the exact name is unimportant), and rename the Pentium II library nspM6.dll to nspA6.dll. Similarly, rename the file iplA6.dll to iplA6-old.dll, and rename the Pentium II library iplM6.dll to iplA6.dll.
This fix makes Pentium III processors use the older the Pentium II library which do not use the new streaming SIMD instructions. If you do not have this problem, there is no need to rename any files. Copyright ©, Edinburgh Last modified: 2015 Jan 18 at 09:32.
From The.Net Runtime Library for Delphi is designed to provide a way to interact with applications written in anyone of the.Net languages: C#, Visual Basic.Net, Delphi.Net, JScript.Net and others. Programmers can produce software by combining pascal source codes with.Net Framework and other.Net libraries. The.Net Runtime Library for Delphi can be used to: Hosts the.Net Common Language Runtime (CLR) in Delphi.
Loads assemblies from.Net dll or executable file without registering the Library as COM in Delphi. Loads.Net assemblies from Global Assembly Cache (GAC) without prior registration of the assembly types as COM.
Accesses.Net assembly types and members of the types which includes fields, properties, methods events etc. Creates an instance of a.Net object from the types of the loaded assemblies. Calls static and non-static members of the.Net types from the loaded assemblies. The members include fields, properties, methods and events. Handles and raises.Net exceptions and also get information about the type of the exception.
Accesses, handles and invokes.net events and delegates from Delphi. Contains all the assemblies and types in the.Net Framework Class Libraries. Hosts.Net controls in Delphi Forms. Contains a utility which imports.net dll, executable or Web Service Definition Language (WSDL) and generates Delphi classes from the loaded assemblies. There are 2 main libraries that constitutes the.Net Runtime Library for Delphi, these are: 1. Host Class Library: This is also called Delphi Host Class Library or DHCL. This Library contains Delphi classes and interfaces for starting and hosting the Common Language Runtime which manages memory, thread execution, code execution, code safety verification, compilation, and other system services.
Framework Class Library: The Delphi Framework Class Library (DFCL) is a Delphi interface representation of the.NET Framework class library which is a collection of reusable types that tightly integrate with the Delphi Host Class Library.Net Assembly/WSDL Importer: A tool which is part of the.Net Runtime Library for Delphi is used to import.net assemblies, WSDL or Web Service XML schema and generates Delphi classes from the types of the imported assemblies. Full Specifications What's new in version 6.0.0.1 Stability and performance improvements. General Publisher Publisher web site Release Date August 14, 2017 Date Added September 13, 2017 Version 6.0.0.1 Category Category Subcategory Operating Systems Operating Systems Windows XP/Vista/7/8/10 Additional Requirements None Download Information File Size 51.18MB File Name DotNetRuntimeLibrary4DelphiTrial.exe Popularity Total Downloads 13 Downloads Last Week 1 Pricing License Model Free to try Limitations 30-day trial Price $179.99.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |