Re: About speed

"Dave Nottage [TeamB]" <rot13.qnivqa@xxxxxxxxxxxxxx> a écrit dans le message
de news: 44a0ecd3$1@xxxxxxxxxxxxxxxxxxxxxxxxx

| I'm interested to know which feature most would consider to be
| significant, next to generics.

Generics has to be the most significant feature which has radically changed
my code, allowing me to scrap a great deal of "typesafe" code that was mere
repetition with the type changed.

Apart from that :

Interfaces that no longer follow the COM model. This makes it impossible to
keep Win32 code that *had* to use QueryInterface, _AddRef and _Release in
order to keep track of what interfaces were supported, etc. I also found
that, in Win32, I had to create a great many more interfaces, just to avoid
mixing object and interface references. .NET 2.0 interfaces are much simpler
to manage and now I have a lot less interfaces, much to Jim Cooper's relief
:-)

Multicast Delegates. These allow me to scrap having to implement the
Observer pattern as a separate concern in every class, every time I wanted
multicast notification.

Reflection as opposed to the limited RTTI allows me to examine properties
without having to declare them as published; now I can have "RTTI" even on
private fields, methods, events, etc. The caveat is that you don't overuse
reflection as there is a speed penalty involved.

Attributes are a great way of extending the metadata available, once again,
as long as you don't overuse them.

The whole .NET framework just has so many useful classes, interfaces and
delegates that have caused me to scrap so many little utility class that I
had to write in Win32. e.g. most of my MVP framework has bitten the dust due
to the Binding class provided by the framework. If I were to continue using
my MVP as it wass, I would have been fighting how the "data-aware" framework
wanted to work.

There's more but, for me, these features alone were enough to persuade, not
only me but, my client who wanted to rewrite his large application in a much
more modular fashion and could have chosen Win32, but needed to think about
future OSs like Vista.

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer


.

Relevant Pages

  • Re: a pre-beginners question: what is the pros and cons of .net, compared to ++
    ... since it is compiled to the machine level by the framework. ... interfaces still should be written in C++. ... IBM wanted the new OS to have all the newest technology and a better ... Microsoft produced two lines of Operating systems that allowed ...
    (microsoft.public.dotnet.general)
  • Re: starting with 2.7
    ... >> interfaces are probably ready to go regardless. ... > because you don't see any use to that particular feature that you can ... tightly coupled to the kernel, and those during ... > some commercial apps rely on modules (firewalls, virtual machines, ...
    (Linux-Kernel)
  • Re: a pre-beginners question: what is the pros and cons of .net, compared to ++
    ... Framework is filling in a very large number of the useful calls that were ... Web controls will run on newer ... XML and various CGI/ISAPI interfaces. ... > certainly don't need .NET to run web services. ...
    (microsoft.public.dotnet.general)
  • Re: starting with 2.7
    ... > interfaces are probably ready to go regardless. ... because you don't see any use to that particular feature that you can guarantee ... >> justify it anymore. ... It's possible that 2.6 has fewer of those known bugs, ...
    (Linux-Kernel)
  • Re: starting with 2.7
    ... >> interfaces are probably ready to go regardless. ... > not because you don't see any use to that particular feature that you ... > userspace anymore, but also involves modules interfaces sometimes because ... > current patches to new releases with very few efforts. ...
    (Linux-Kernel)