delphi-2009

Does that mean that I can't share a Form between delphi 2007 and 2009? Yes. It is not possible unless you remove the properties that are not published in Delphi 2007 from the DFM. Ondrej Kelle DoubleBuffered has been in TWinControl for some time now. The difference in Delphi 2009 is that it's published now. If you can live with only ignoring the errors (and not making the properties work instead), here is a possible solution: unit Delphi2009Form; interface uses Windows, Classes, SysUtils, Controls, Forms; type {$IFDEF VER200} TDelphi2009Form = class(TForm); {$ELSE} TDelphi2009Form = class

Does Delphi support internationalization in any way? I've seen that I can add different languages for a project, but that seems to create multiple instances of the dfm files. Am I right that the language therefore cannot be changed at runtime? How do you handle internationalization (if you do)? Are there any best-practices? I have once experimented with runtime change of languages. It worked great, but I needed to write lots of code myself (and circumvent the dfm files). The problem is, it is a lot of hassle and you almost never need this. The better option (in my opinion) is to create a base

I'm producing builds using MSBuild, and build configurations set up in the dproj on the command line. It's slightly disconcerting that the size of the executables thus produced are different (not by much, but still!) to what an IDE build produces. Any ideas why? I would have thought the same compiler is used? To see what IDE is doind, check Tools | Options | Environment Options | Compiling and Running | Show Command Line And you can check the compiler messages. The main power of building from the Delphi command-line compiler is standardization - you explicitly identify the options (on the