Re: Delphi Product Manager questioned
- From: Barry Kelly <barry.j.kelly@xxxxxxxxx>
- Date: Sat, 17 Jun 2006 15:06:38 +0100
"I.P. Nichols" <nospam@xxxxxxxxxx> wrote:
"Barry Kelly" wrote:
The current VS05 Orcas extensions (I'm thinking of the integrated
designer thing) are currently quite unstable. Also, WinFX (aka .NET 3)
doesn't change the CLR, so a version of Delphi that supports .NET 2 will
support .NET 3 at the language and debugging etc. level.
That's patently not correct, the currently available Orcas Extensions are
quite stable and as for the integrated WPF designer (aka Cider) it isn't
unstable but rather just not yet feature complete, however that doesn't
really figure into the equation since almost all the WinFX developers are
using the much more capable Expression Interactive Designer (aka Sparkle),
which integrates with Visual Studio, as their designer and that will
continue to be the case even after Orcas is released.
OK. I'll take you word for it; perhaps they've been updated since I last
looked. The last time I installed the WinFX IDE extensions it broke my
VS installation. It was a very negative experience.
As for your second claim that Highlander will support .NET 3.0, I'll remain
dubious until people start using Highlander to develop .NET 3.0 projects.
My point is that .NET 3.0 doesn't change the .NET 2.0 runtime, so
compiler and debugger support etc. for 2.0 should all work.
Another interesting thing about this: you'd still be able to use the
LINQ (& XLINQ & DLINQ) libraries in a Delphi that supports .NET 2. It
would be more verbose due to the requirement to explicitly refer to the
correct extension methods, but it would work.
Isn't this similar to saying that one can use Delphi 2006 to develop .NET CF
apps which certainly didn't impede the defections to Visual Studio
It isn't the same at all: the compact framework is a different
framework, with a different mscorlib etc. .NET 3.0 isn't changing the
underlying engine, so any support for the C# 2.0 compiler and the .NET
2.0 runtime will still be able to call the C# 3.0 (i.e. LINQ etc.)
runtime libraries.
I know it's not ideal, but it's significantly better than missing CF
support: completion and debugging etc. should work. When you look at
what LINQ is actually doing, it's fairly easy to do the C# 3.0 compiler
syntax rewriting yourself.
Speaking of interesting approaches to using LINQ, check out Microsoft's
"Blinq" which is the prototype of a tool for generating ASP.NET websites for
displaying, creating, and manipulating data based on database schema. You
can read about it's capabilities and download a preview from here:
http://www.asp.net/sandbox/app_blinq.aspx?tabid=62
Interesting. From the abstract, it almost sounds like a code-generator
based RoR for .NET.
-- Barry
--
http://barrkel.blogspot.com/
.
- References:
- Re: Delphi Product Manager questioned
- From: Bryce K. Nielsen
- Re: Delphi Product Manager questioned
- From: Nick Hodges (Borland/DevCo)
- Re: Delphi Product Manager questioned
- From: Bryce K. Nielsen
- Re: Delphi Product Manager questioned
- From: Nick Hodges (Borland/DevCo)
- Re: Delphi Product Manager questioned
- From: Bryce K. Nielsen
- Re: Delphi Product Manager questioned
- From: Nick Hodges (Borland/DevCo)
- Re: Delphi Product Manager questioned
- From: Bryce K. Nielsen
- Re: Delphi Product Manager questioned
- From: Nick Hodges (Borland/DevCo)
- Re: Delphi Product Manager questioned
- From: Jan Derk
- Re: Delphi Product Manager questioned
- From: Brian Moelk
- Re: Delphi Product Manager questioned
- From: I.P. Nichols
- Re: Delphi Product Manager questioned
- From: Barry Kelly
- Re: Delphi Product Manager questioned
- From: I.P. Nichols
- Re: Delphi Product Manager questioned
- Prev by Date: Re: Delphi Product Manager questioned
- Next by Date: Re: Conference This Year
- Previous by thread: Re: Delphi Product Manager questioned
- Next by thread: Re: Delphi Product Manager questioned
- Index(es):
Relevant Pages
|