“Microsoft .NET applications are built from components. All .NET objects expose important attributes, such as properties, methods, and events. These attributes form the foundation of object-oriented programming. As the architect of Visual Basic .NET objects, you are also responsible for implementing the interface (that is, the properties, methods, and events) necessary for other programmers to use your application’s services. Much of your development time will be spent designing objects and writing the code defining the objects and components exposed and used by your applications.” Read the rest of the article at MSDN.
Creating Components in .NET
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
What’s the deal with generics? Why does MS want it in C#?
Bjarne Stroustrup (designer of C++) recently presented a 1 hour workshop on the multi-paradigm (e.g. object-oriented, generic) features of C++.
Follow the slides whilst listening to the MP3 lecture here:
http://technetcast.ddj.com/tnc_play_stream.html?stream_id=613
He comments that C++ is still the only language that supports all the language features he thinks is important.
… he also does some OS name-dropping in his slides.
Oops. That should have been posted to the C# news item.
At first glance they seem identical. Is .NET COM with sockets?
The hype surrounding .NET makes it sound like it makes innovation obsolete. Who here would rather be a technology consumer rather than producer?
There is no one model that fits everything. Also, humans are not going to go away anytime soon. Why keep chasing the Holy Grail?
Instead of having an API that solves every conceivable problem within any conceivable constraints, why not shoot for a process that doesn’t produce bug-ridden software?
Gotta hand it to Microsoft, getting people to pay you for the opportunity to debug your own software must be pretty sweet.