66020 members! Sign up to stay informed.

Sponsored Links


Resources

.NET Research Library
Get .NET related white papers, case studies and webcasts

.NET architecture .NET architecture .NET architecture Messages: 5 Messages: 5 Messages: 5 Printer friendly Printer friendly Printer friendly Post reply Post reply Post reply XML XML XML

VB.NET barely OO

Posted by: Doug Adams on March 07, 2005 DIGG
I know that .NET is OO, but you are hard pushed to find VB.NET apps that are really OO. I think the reason for this is twofold.

Firstly, most VB.NET developers are coming from VB. Most java/c++ developers are writing in c# on .NET. The second reason is that .NET, especially in windows programming, seems still, to be obsessed with the database. You have all these controls that bind to a datasource, directly from the UI. What happened to objects??

Threaded replies

·  VB.NET barely OO by Doug Adams on Mon Mar 07 08:17:18 EST 2005
  ·  VB.NET barely OO - yea right by John Saunders on Mon Mar 07 11:01:38 EST 2005
    ·  I Agree... by John Saunders (W, III) on Mon Mar 07 11:34:41 EST 2005
    ·  On the evidence by Doug Adams on Mon Mar 07 12:03:20 EST 2005
      ·  On the evidence by Rockford Lhotka on Mon Mar 07 16:39:39 EST 2005
        ·  Depressing? Yeah by Doug Adams on Tue Mar 08 04:21:27 EST 2005
  Message #160118 Post reply Post reply Post reply Go to top Go to top Go to top

VB.NET barely OO - yea right

Posted by: John Saunders on March 07, 2005 in response to Message #160092
Any .Net developer that is not programming to an object oriented model, hasn't had sufficient training, and/or experience. Bindingg UI controls directly to the datasource is nice, if all your worried about is a deadline, and the RAD model is accepted, but good .Net developers all have the ability to create scalable N-Tier applications and do.

Don't blame VB.Net, blame the developer using VB.Net.

  Message #160124 Post reply Post reply Post reply Go to top Go to top Go to top

I Agree...

Posted by: John Saunders (W, III) on March 07, 2005 in response to Message #160118
I agree with the other John Saunders :-)

I'll add that many people who wonder "where's the OO in VB.NET" have recently read a book or article on VB.NET which did not emphasize OO. From this, they conclude that VB.NET does not support OO since, if it did, that would have been in the book. This is a false assumtpion.

John W. Saunders, III

  Message #160130 Post reply Post reply Post reply Go to top Go to top Go to top

On the evidence

Posted by: Doug Adams on March 07, 2005 in response to Message #160118
Maybe I could have titled my post better. I feel that people are bringing a lot of baggage to VB.NET from VB. I have worked on three previously written VB.NET projects and struggled to find a real class. Programmers where just writing the old style of code and wrapping it in Public Class /End Class clause.

  Message #160175 Post reply Post reply Post reply Go to top Go to top Go to top

On the evidence

Posted by: Rockford Lhotka on March 07, 2005 in response to Message #160130
If we are honest with ourselves we'll realize that precious little Java or C# (or even C++) code is actually object-oriented either.

Windows Forms and Web Forms are event-driven procedural models. Sure we _use_ objects, but we don't usually apply OO design to the UI.

Data access code is typically linear. Again, we _use_ objects from ADO.NET, but our actual data access code is most commonly linear, not even procedural.

Most applications have their business logic in or near the UI. At best this logic is typically in some sort of function library. In a class of course, but not designed with OOD...

The fact is that the _vast_ majority of software created in ANY language today is data-centric, event driven and mostly procedural. It is very rare to find an application where the UI, business logic and data access are built following real OO design...

Depressing? Yes. But this is reality...

Rocky

  Message #160243 Post reply Post reply Post reply Go to top Go to top Go to top

Depressing? Yeah

Posted by: Doug Adams on March 08, 2005 in response to Message #160175
I have to agree with Rocky. I keep find duplicated logic because people are not creating objects to model the objects in their system. If different parts of the system are going directly to the same table for different reasons, then we have probably got duplicated code and logic. This can be the source of bugs as the application ages.

Also, it seems that .NET applications is tightly coupled with database stored procedures. I think this is good, as long as the procedures ARE KEPT SIMPLE. I have come across quite a few apps where most of the logic is in the proc. Thats fine, but you can really inherit or share this kind of logic.

I would like to see an emergence of a proper class models. Lets take the business logic back from the UI and the database!

Recent active threads Recent active threads Recent active threads More More More
PPT to SWF (Flash) and PDF to SWF Conversion in .NET Application
Integrating 3rd Party Single Sign On into SharePoint Portal 2003
[ANN] Agile Cambridge 2010 - October 14-15
Solutions for open source data quality
Talend Appoints Vice President of Corporate Development
We had a fire at work today
How to add barcoding support to ASP.NET Mobile websites (VB.NET
More active threads »
Top posters of the weekTop posters of the weekTop posters of the week
This list contains the members who have made the most posts in all forums over the last 7 days:
  1. aspose seo
  2. Guru Talend
  3. Mark Dalgarno
  4. Jim Thorstad
  5. Sophie Everett
Hot threads Hot threads Hot threads More hot threads More hot threads More hot threads

Eclipse vs. Visual Studio at EclipseCon 2006

Speaking at EclipseCon 2006, Java developer and independent consultant Madhu Siddalingaiah compared Microsoft's Visual Studio IDE to the open source development environment of Eclipse.
(32 comments, last posted December 29, 2007)

Tech Talk: Peter Provost on CAB and Agile development

In this tech talk, Microsoft's Peter Provost talks about the design of the Composite UI Application Block and how the p&p team has led Microsoft in the adoption of Agile methodologies.
(0 comments, last posted April 17, 2006)

Book excerpt: Framework Design Guidelines

Chapter 4 of Framework Design Guidelines, titled "Type Design Guidelines," presents patterns that describe when and how to design classes, constructs and interfaces. In this chapter, Abrams and Cwalina divide types into four groups and discuss the do's and don'ts of type design.
(2 comments, last posted July 07, 2006)

Q&A: Miguel "Mono Man" De Icaza

Paul Ferrill caught up with prime open-source .NET applications driver Miguel De Icaza at Novell's BrainShare conference last week. They discussed the status of Windows Forms for Mono (it's coming along) and VB.NET for Mono (it looks like it's out).
(5 comments, last posted March 30, 2006)

Tech Talk: Jack Greenfield on software factories and DSLs

In this tech talk, Microsoft Visual Studio architect Jack Greenfield discusses the company's approach to Domain-Specific Languages, or DSLs, and the part they play in software factories.
(0 comments, last posted March 15, 2006)
More hot threads »

News | Blogs | Discussions | Tech talks | Patterns | Reviews | White Papers | Downloads | Articles | Media kit | About
All Content Copyright ©2007 TheServerSide Privacy Policy      Powered by JIVE
Site Map