During rebuild after a computer crash, I re-installed Delphi 7, then Delphi 2007. We skipped installation of Delphi 2006. However, now I would like to install Delphi 2006 before Embarcadero discontinues allowing for download of the latest version of D2006.
Is it possible to install Delphi 2006 on this computer without having an adverse impact on the other two installations?
My only concern is the potential problem of mixup in the SYSTEM PATH variable, where each version of Delphi uses the system PATH value to remember the location of the BPL files. Then the system PATH statement holds multiple BPL path locations created by each Delphi installation. However, each version Delphi only finds and uses the FIRST BPL path found in the list of paths - which always happens to be the most recent install. (Delphi installs insert - rather than append - the BPL path references at the beginning of the current system PATH value.) If this happens, then it is possible, for example, for Delphi 7 to reference the BPL files of Delphi 2007. Of course, that's not good at all. This is something that I know how to work around - if it is the only issue.
I'm hoping that the answer is not "uninstall Delphi 2007 first." That is painful for me as it takes significant time to re-install all the add-on components.
I have installed Delphi 5, Delphi 2006, Delphi 2007 and Delphi 2009 in various orders on several computers (laptop, work machine, home desktop, etc.) and have been fine.
I believe since 2007 is based on the 2006 version, that installing 2006 after 2007 is installed will most likely cause some problems. If you absolutely have to have a copy of 2006 for testing purposes, I strongly recommend setting up a virtual machine using VMWare or Virtual PC. This will allow you to test against 2006 directly...if you have 2006 and 2007 installed on the same machine, then your not testing 2006... your testing 2006 with 2007 installed.
Related
Anybody know if delphi xe7 compatible with windows 10?
Embarcadero says that XE8 is compatible. But tells nothing about XE7.
Yes, you can install XE7 on Windows 10, and the executables that it produces are compatible with Windows 10.
Embarcadero have been producing a lot of marketing recently that implies that you need XE8 to do Windows 10 development. Truth be told, you can use any version of Delphi beyond Delphi 1. Of course the newer versions make life easier, and clearly you need XE2 or later to target 64 bit executables.
So far as I can see, the only Windows 10 specific feature that is offered with XE8 is a Windows 10 style. That was what I took from a conversation with Marco Cantú on the subject. I guess that would be useful for FMX targets. If you are targeting classic VCL apps, and use the standard system theme, then this is of no interest. There's no point at all in faking the system style when you can let the system give you the true style. My old Delphi 6 applications, built with Mike Lischke's theme manager code, look and feel on Windows 10 identical to an application built with XE8.
Although Embarcadero says that XE8 is compatible with Windows 10, I'm unable to install or load our existing bpl projects using XE8 with Windows 10.
I moved to XE8 because our projects wouldn't build with Windows 10 using XE4.
You can install and run Delphi XE7 on a Windows 10 machine. And of course you can compile your projects on Windows 10.
But there were no enhancements made in the VCL or FireMonkey towards the new operating system. There is no official support for Windows 10. Your applications may not look and feel 100% like other applications do on Windows 10. But they can still be run as long as long as they don't use any old API that is no longer supported on Windows 10.
You can install and run Delphi XE7 on a Windows 10 machine.
My Win7 now installed RAD Studio 2010 with Delphi 2010, can I install Delphi XE3 separately? So both Delphi 2010 and XE3 work on the same Windows?
Thanks!
Yes you can. You can install all versions of Delphi side by side on a single machine. I'm currently sitting at a machine with D6, 2010, XE, XE2 and XE3.
Different people have different ways to organise side by side installations. I personally remove all references to Delphi from my system PATH variable. Then if I need to do anything at the command line I make sure I execute the rsvars.bat for the target version. That sets all the environment variables needed for that Delphi version. At that point executing dcc32.exe results in the target version of the command line compiler being invoked.
They should work. However some certain components might be buggy like different versions of BDE or maybe different versions of remote debugger core. But in general if you install lesser version with updates and then install more newer one - it should work. Unless some bugs happen.
But when you'd compile your projects or libraries, if you want to use both IDEs you should be very accurate about DCU and DCP paths, BPL names and such, so they would not be mixed in same place. DCU and DCP should be written into and searched in different folders. BPL names should have version-denoting suffix to them. and such.
I am trying to automatically figure out which Delphi version (of Delphi 5 to XE2 installed on my computer) to use to open a given project without upgrading that project by mistake.
Up to Delphi 7 there is a .dof file in .ini format for each project.
Delphi 5 does not have any entry which might help, but starting from Delphi 6 there is a [FileVersion] section which contains the following values:
Delphi 5: N/A
Delphi 6: 6.0
Delphi 7: 7.0
So I guess that settles that, since older Delphi versions do not concern me.
For Delphi 2005 and 2006 there is a .bdsproj file in XML format containing a version entry:
\BorlandProject\PersonalityInfo\Option\Option
In Delphi 2005 it looks like this:
<Option Name="Version" Type="String">1.0</Option>
In Delphi 2006 like this:
<Option Name="Version">1.0</Option>
So I could look whether the attribute "Type" exists and depending on that decide on Delphi 2005 or 2006.
Could somebody please have a look at his Delphi 2005 and 2006 projects and verify this difference? (Or do you maybe have got a better idea?)
edit: I just tried to verify this and found, that Delphi 2005 does not always add the Type-Attribute. So now I am stuck.
edit: Maybe the GUID stored there is unique to the Delphi version?
Delphi 2005: {87D03616-A4C7-4B5A-AF0F-0164EA60BC59}
Delphi 2006: {CFE1BEE6-6FDE-4241-8CA5-D38D14EAA768}
Somehow I doubt it, I am afraid that the GUID may represent different SKUs (Professional / Architect etc.). But maybe you could verify this?
Starting with Delphi 2007 there is a .dproj file in a different XML format. The Delphi 2007 format does not contain any version entry I could find, but from Delphi 2009 on there seems to be the following entry:
\project\PropertyGroup\ProjectVersion
These are the values I found in my .dproj files:
Delphi 2007: N/A
Delphi 2009: 12.0
Delphi 2010: 12.0
Delphi XE: 12.3
Delphi XE2: 13.4
If these are correct, I could reliably determine Delphi 2007, XE and XE2. But how do I distinguish between Delphi 2009 and 2010?
Also, these numbers look odd to me. Does anybody know whether there are any differences between the various updates of Delphi, e.g. did the original Delphi XE2 release maybe start with 13.0 and with each update increment the number after the dot? But if that's the case, how did Delphi XE get 12.3?
(There is a similar question How can I tell what version of Delphi was used to create a project but the single answer there is quite limited.)
Just in case anybody else needs this: I have just added a page to the Delphi Wiki which summarizes all answers and adds information for newer Delphi versions (currently up to Delphi 10.4.1).
I have now compared the .bdsproj files of Delphi 2005 and 2006 and there is no difference. Also, there is no difference between the .dproj files created by Delphi 2009 and 2010.
So the answer is:
if a .dproj file exists -> read \project\PropertyGroup\ProjectVersion
empty -> Delphi 2007
12.0 -> Delphi 2009 or 2010
12.2 or 12.3 -> Delphi XE1 (according to Uwe Schuster)
13.4 -> Delphi XE2
if a .bdsproj file exists -> Delphi 2005 or 2006
if a .dof file exists -> read [FileVersion]\version
empty -> Delphi 5 (or possibly older)
6.0 -> Delphi 6
7.0 -> Delphi 7
Unfortunately this does not allow me to write a program that automatically starts the correct Delphi version for a given project.
Maybe I will let the program ask the user if there are two possibilities and store his answer in a .ini file so the next time the program knows which Delphi version to start.
btw: The reason I was looking into this is that I have several times accidentally opened Delphi 2007 projects with a later Delphi version which upgraded it and I had to reverse these changes by hand. This has become so annoying that I wanted to prevent it by registering my own program as handler for .dpr files.
The version numbers in the *PROJ files are not bound to releases or updates and not all versions hit the streets.
Delphi XE RTM used version 12.2
Delphi XE Update #1 uses version 12.3
Delphi XE2 (RTM till Update #4) uses 13.4
Just installed XE3 (RTM).
14.3 XE3 (C++ & Delphi)
Today I find this topic googlin about Delphi edition (Standard, Professional, Enterprise).
Anyway I checked some .dof files spread in mine machine and there is facts related to ancient delphi versions:
if a .dof file exists -> read [Directories]/Packages
Delphi 3
[Directories]
OutputDir=
UnitOutputDir=
SearchPath=
Packages=VCLX30;VCL30;INETDB30;INET30;
Delphi 5
[Directories]
OutputDir=.
UnitOutputDir=.
PackageDLLOutputDir=.
PackageDCPOutputDir=.
SearchPath=
Packages=Vcl50;Inet50;Inetdb50;Vclx50;Indy50;
Additional info can be finded near end of dof file:
D3:
[Excluded Packages]
C:\Program Files\Borland\Delphi 3\Bin\DCLDSS30.dpl=Delphi Decision Cube Components
C:\PROGRAM FILES\BORLAND\DELPHI 3\BIN\DCLTEE30.DPL=Delphi TeeChart Components
D5:
[Excluded Packages]
$(DELPHI)\Bin\CorIde50.bpl=Borland Core IDE Package
$(DELPHI)\Bin\direct50.bpl=Borland Direct IDE Package
I need to migrate to RAD Studio and have this installed on a new workstation. At the moment I still need to develop with Delphi 6 until we get all the necessary control updates and sort out the version control.
So my question is can I just install Delphi 6 on the same machine with no adverse impact for either product?
Thanks in advance.
There are no problem to install D6 and RAD 2009 at the same machine.
I think that it's better install first the previos version (first D6 and after D2009), but it's not absolutly necesary.
Regards and excuse for my bad english.
Installing them on the same system is no problem at all.
For migration, our clients have good experience with migrating to Delphi 2007 first, then do the Unicode migration to Delphi 2009 or Delphi 2010 second.
Doing both migration at the same time can work, but usually result in a migration that is too complex to do in one step.
--jeroen
I have delphi 3 to 2009 installed in my machine and I dont have any problem with any of the the Delphi IDEs. Only the BDS 2006's C++ IDE does not work anymore. There is a problem when C++ builder 2006 and 2007 installed in the same machine.
Is there any conflict?
All new versions of Delphi can always be installed safely /next/ to older version.
Each new version should be installed in its own directory.
If you are going to install multiple versions, always install the oldest version first, and then work your way to the newest.
We work very hard to make sure that all versions of Delphi coexist together. But again, never install one version directly on top of another.
I am running 2007 and 2009 on the same machine (this machine) just fine. The only problem you might have is if you are compiling components to the same directory - you will just need to rebuild all your DCU's and packages each time, or make version specific packages and directories.
Install them in their own directories, and make sure you keep package binaries separate, you should be fine. I've got 2009, 2007, 2006, 7 and 5 all on this machine with no issues.
I have at least 4 Delphi versions on one machine. They do not bite each other.
I always install older versions first because i had once problems if i did this the other way round.
Yes - as Rob said (Robsoft) I have both working here. Delphi has always been very good at co-existing with other versions.
Obviously you can only have one version as the default for opening Delphi files.
Should not conflict.
I did D2007 on the same machine as D2006 with absolutely no problems (I was shocked, actually).
I haven't tried D2009 yet, but it should be ok.
This guy had problems though. Hopefully his issues were due to the custom setup he describes in that article.
A colleague of mine (think he has an account on here as dcraggs now) has got them both running on the same machine just fine, I believe.
Certainly would be a huge own-goal from Embarcadero if installing D2009 broke an already-installed D2007, given the way that the components and DCUs are not compatible - I suspect a fair number of people will need to have both around for a while (some of us still need D5 and D7 too!)
CodeGear stated (don't have a link handy, sorry) that there should be no conflict. I haven't yet installed D2009 on my workhorse PC so I don't know if that is correct.
The settings in registry have different path and packages have different names so there really should be no problems.
I have Delphi 2007 and I have installed 2009 yesterday with no visible problems so far. Both seem to work fine.
Appears to be no problem. Installed D2009 with TurboDelphi and 2007 and 2, 5 and 7 all on the same Vista machine
Both 2007 and 2009 have Jedi JVC and JVCL installed on them. All appear to work fine. Hope that helps.
.. and if you compile existing packages make sure you give them a new name (e.g. suffix with D12) as each version's BPL directories are in the path.
Installed D2009 Enterprise on VMWare instance running Vista Business with an existing D2007 Enterprise installation. Perhaps I did something incorrectly, but I began to experience errors in the D2007 IDE, as well as a very strange error, unknown fieldtype, in exe files compiled with D2007. I uninstalled D2009, and the errors have gone away.
You should always install the older version first. I tried to install 2009 first and then 2007 but the setup of 2007 failed.
Uninstalling 2009, and starting with 2007 first fixed the install problems.
In theory, it's possible, but if you use many third-party (or your own) libraries, it can get hairy pretty fast. I tend toward developing on Virtual machines, for this and other reasons. But, YMMV.
Should be fine. I have Delphi 7, 2006, 2007, 2009 with 3rd party libs Dev Express and Rem Objects for all (except Dev Express for 2009 - is it out yet?) and all work flawlessly. As others pointed out the versions were installed oldest to newest.
The installations won't interfere with each other, although the Delphi 2009 and Delphi 2007 projects are not compatible, and can't be shared.
Moving along with the order of release is a must. Install older first. Uninstalling may get tricky though.
How to fix Delphi 2009 data explorer?