Obtain 29458_firedac_xe4_update_2_for_rad_studio_delphi_c_ent_ult_arch.zip from a registered Delphi XE4 or higher license: http://cc.embarcadero.com/item/29458:
(When not running as Administrator: elevate to Administrator)
Welcome screen: press next
License screen: accept, then press next
Destination selection screen: keep C:\Program Files (x86)\Embarcadero\FireDAC, then press next
Select components screen: keep the selection (Full installation), then press next
Select IDEs screen: choose Delphi 2007 (but not Delphi 2006), then press next
Select Demo Databases screen: keep the settings (do not choose Interbase / Firebird server as then you have to provide the credentials for the server), then press next
Start menu screen: keep Embarcadero FireDAC, then press next
Ready to install screen: press install
After installation: press finish, then read the readme
or later browse to <file:///C:/Program%20Files%20(x86)/Embarcadero/FireDAC/Readme.html>
That’s what actually tells you:
The installer automatically installs FireDAC in the Delphi XE4 and C++ Builder XE4 IDEs. For older versions of the IDEs, you can run the installer with the /SHOWIDE command line parameter.
The actual BPL sometimes is in C:\Users\<username>\AppData\Local\Documents\RAD Studio\5.0\Bpl\AnyDAC_Dcl_D11.bpl
The cause is that the BPL gets loaded from %BDSCOMMONDIR% which on some systems points to
%PUBLIC%\Documents\RAD Studio\5.0
and on others points to
%LOCALAPPDATA%\Documents\RAD Studio\5.0
This seems to be the case on machines where more different Windows users are using Delphi.
The installer does not fully recognize this distinction, so copies the BPL to %LOCALAPPDATA%\Documents\RAD Studio\5.0\Bpl and registers it as being in %PUBLIC%\Documents\RAD Studio\5.0\Bpl.
On these machines there is a difference between the definition of BDSCOMMONDIR in these registry keys:
Had to investigate some Assembly Loading issues, so I wrote two batch files to enable and disable the .NET Fusion Log:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Besides commit statements from hg or git like this:
hg commit -m “fixes #6, resolve ticket #5 and see ticket #9 and ticket #5 in the tracker”
The best is to start with the command, then finish the comment (commands in the middle of a comment are far less reliable).
There is a whole bunch of commands for which BitBucket tries to understand conjugations of verbs:
Command
“Verb”
Conjugation(s)
resolve
close
close
closes
closed
closing
resolve
fix
fix
fixed
fixes
fixing
resolve
resolve
resolve
resolves
resolved
resolving
reopen
reopen
reopen
reopens
reopening
hold
hold
hold
holds
holding
wontfix
wontfix
wontfix
invalid
invaldate
invalidate
invalidates
invalidated
invalidating
You can also use the word “issue” in the middle to just link to an issue like this syntax:
links to issue #1
Finally, you can refer from issues to change sets using a cset syntax: <<cset 2f2f8d4cae7da0e37a5ffbc81c527cb67cc56015>> where the hex number is from a URL in your commit list (for instance in https://bitbucket.org/jeroenp/fastmm/commits)
You can just hg update to the closed branch then do another hg commit and it will automatically reopen.The closed flag is just used to filter out closed branches from hg branches and hg heads unless you use the --closed option – it doesn’t prevent you from using the branches.
For a long time, I’ve persuading people to install English versions of their operating systems (especially on server side) at least for some parts of their environment.
The main reason is that searching for English error messages gives you a much bigger chance of finding the cause than non-English ones.
I’m still standing by that recommendation, but life has become a bit easier because of these two sites that offer quite good translations of Windows Error messages in many languages to English: