Re: Thinking Clearly

David Clegg wrote:
OK, perhaps that was a bad choice of words. But I consider it more .NET
2.1 than .NET 3.0, as it seems to be a set of extra sub-frameworks and
classes to compliment the existing .NET 2.0 ones, rather than a full
replacement of the classes, SDK and compilers.

That's right, essentially .NET 3.0 is: .NET 2.0 + WCF + WPF + WF + WCS.

WCF = "Indigo" Windows Communication Framework
WPF = "Avalon" Windows Presentation Framework
WF = Windows Workflow Framework
WCS = Windows Cards Space

I think this is a good link describing what .NET 3.0 is:
http://www.idesign.net/idesign/DesktopDefault.aspx?tabindex=0&tabid=13
http://tinyurl.com/nrork

I must admit I'm no expert on exactly what .NET 3.0 will entail, but my
understanding (which I'll gladly have corrected, BTW) is that it is a
framework, and not a development tool, upgrade. So I'd be interested in
hearing what you refer to here.

I'm no expert either, but FMPOV, there will be a *ton* of work required
on the IDE end of things to support these things. WPF requires new
designers. WCF and WF will require some IDE integration to help create
these solutions visually. WCS might need a wizard or some kind of GUI
manager; I'm not sure.

Not trying to be argumentative, BTW;
I,m genuinely curious, and a brief Google is being frustratingly
ambiguous. For example :-

"The Windows Communication Foundation (previously codenamed "Indigo")
is Microsoft's unified framework for building secure, reliable,
transacted, and interoperable distributed applications."

This doesn't really tell me whether this is a framework that is going
to require some special design-time support to consume.

From that link above:

"3. Developers can continue developing using Visual Studio 2005, and
even install special extensions to Visual Studio 2005 that support .NET
3.0. That said, Visual Studio 2007 will include dedicated high-end
design tools for .NET 3.0, so it is likely once those are available that
developers will adopt the new tools. "

And considering that the compiler version isn't going to change with
the 3.0 release, there doesn't appear to be any new compiler support
required.

This is why ISTM on the surface that Highlander users should be able to
consume .NET 3.0 without an IDE upgrade. After all, it seems the VS
developers are going to be in the same boat.

I believe that supporting .NET 3.0 "properly" will require much more
intensive IDE work than .NET 2.0 did.

Sure, Microsoft may well impose restrictions on the installation of
things such as the Sparkle designer, meaning it won't install unless VS
is, but that remains to be seen, and they didn't take that approach
with the current .NET SDKs.

Cider is the piece that will require IDE work.

Yeah, but for some developers this adoption may also have a positive
flow on effect for their customers, as they would have a more
productive development environment and framework. Delphi developers
don't get the same level of improvement here, as a lot of the
productivity gains that other developers received with migration to
..NET (and the accompanying IDE) we've had for quite a few years.

Which is another good point IMO why Delphi for .NET and VCL.NET have had
problems getting traction: it has to compete with Delphi Win32 and VCL.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • I want support both version 1.0 and 1.1??
    ... I install a older .Net Framework version. ... the IDE will add this information for you ... Please help me to support both version. ...
    (microsoft.public.dotnet.framework)
  • ANN: kbmMW v. 2.01 released
    ... The latest edition of kbmMW adds to the existing WIB by now allowing for hub/spoke topology in addition to the normal ... the developers API is the same as if traditional request/response communication setups are used. ... - multi database transactional support. ...
    (borland.public.delphi.thirdpartytools.general)
  • RE: Quality of FreeBSD
    ... FreeBSD development model typically addresses change at the tree HEAD, ... Probably it is no longer important to support chip ... > project schedule means, with long, long list of new features. ... I think you'll find many FreeBSD developers enjoy working on FreeBSD best ...
    (freebsd-stable)
  • My changing warrant wont revise before I reach it.
    ... fine developers. ... Hey, I'll support the mine. ... employees to the physical damp memory, ... When Haji's marginal composition pulls, ...
    (sci.crypt)
  • Re: Borland interview on ALM - why am I not surprised?
    ... > ALM vision - contrary to the ... "For a long time we were an IDE company, and I think our focus on the ... What we've grown up into is a view that developers are ... compiler technology or any kind of unique technology produced by Borland to ...
    (borland.public.delphi.non-technical)
Loading