Linked by Thom Holwerda on Fri 24th Feb 2012 17:53 UTC
General Development "In this blog post (and the one that will follow) we'd like to introduce a few of the broad reaching experience improvements that we've delivered in Visual Studio 11. We've worked hard on them over the last two years and believe that they will significantly improve the experience that you will have with Visual Studio."
Thread beginning with comment 508415
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Look what we've done
by snorkel1 on Sat 25th Feb 2012 03:19 UTC in reply to "RE: Look what we've done"
snorkel1
Member since:
2012-02-25

You simply have to recompile and they work fine and dandy
even in XE2 assuming you have the source, and most 3rd party components include the source, and if you doing run time you just have to recompile the package.

Delphi XE2 is really nice and I would take it and the native single exe applications it creates any day over Visual Studio .not.

Most developers simply do not use BPL for run time packages since you can compile everything right into the exe.

Reply Parent Score: 1

RE[3]: Look what we've done
by Hiev on Sat 25th Feb 2012 16:30 in reply to "RE[2]: Look what we've done"
Hiev Member since:
2005-09-27

Even if you don't use the runtime packages the bpls are necessary for compilation, and in some cases, even with the source the migration may not be an easy task, first, with the migration to UTF-8 strings (and if you are using a component that is making calls to an external .dll made in c then good luck with that)
then with the migration to 64 bits integers.

I wish they would be better in this area, just allowing some degree of compatibility between releases.

Edited 2012-02-25 16:33 UTC

Reply Parent Score: 2

RE[4]: Look what we've done
by henderson101 on Tue 28th Feb 2012 21:34 in reply to "RE[3]: Look what we've done"
henderson101 Member since:
2006-05-30

Even if you don't use the runtime packages the bpls are necessary for compilation, and in some cases, even with the source the migration may not be an easy task


I remember migrating Delphi 1 code (16-bit) to Delphi 2 (32-bit). So many hidden issues. Then some code went to Delphi 3 via Delphi 2 or from Delphi 1 (depending on how far te port was in progress.) that was even harder in some cases, as the Delphi 2 release sort of "hacked" around the conversion to 32-bit in some areas. And then there was the custome collection classes that had been ported to Delphi 1 from Borland Pascal 8 (the Delphi 1 beta, before is got renamed and dropped support for DOS.) mostly coded in inline Assembler. NOW THAT WAS A PORT!

Bottom line - it's total BS to claim Delphi is backwards compatible with little cost. It is not. Every port forward requires a complete recursive test and full regression testing. It literally costs 6 months+ on any sizeable product and is not feasible in many cases.

Our .Net 2 code still compiles in VS 2010 and runs fine. And our 1.1 assemblies still link and work as described. Try doing tat with a BPL from any prior version of Delphi... Or DCU. Yeah we still have to regression test, but as te code is compiling against the same target, it's pretty simple to do.

Reply Parent Score: 2

RE[3]: Look what we've done
by henderson101 on Tue 28th Feb 2012 21:04 in reply to "RE[2]: Look what we've done"
henderson101 Member since:
2006-05-30

You simply have to recompile and they work fine and dandy
even in XE2 assuming you have the source, and most 3rd party components include the source, and if you doing run time you just have to recompile the package.


This is a nice claim, but my experience was that Delphi shops tend to stick on a known good version for years (I was still using Delphi 5 in 2006.) It was never fun getting Delphi 6+ code to compile, but gosh darn it, we did.

Delphi XE2 is really nice and I would take it and the native single exe applications it creates any day over Visual Studio .not.


Delphi was nice, but it doesn't have half the polish that .Net does. Linq and Reflection alone crap all over Delphi as I last used it. The VCL is crumbly and old. It has some serious design flaws, some stuff (BPL) were crap and unreliable.

Most developers simply do not use BPL for run time packages since you can compile everything right into the exe.


You can do this with .net. You can pre Jit it, combine all of the assemblies in to one and even AOT compile it.

Reply Parent Score: 2