有哪些好的资源可以帮助 VB6 开发人员团队了解面向对象范例？
该团队熟悉 ASP.NET，并且已经在 VB.NET 工作了几年，但他们只是没有在对象方面的思维上进行转变。事实上，他们对 C++ 和非托管环境的短暂了解可能会对 OOP 感到有点害怕。工作让他们太忙了，以至于没有时间充分吸收 .NET 和 OOP 提供的好处。
我正在寻找一些轻量级资源（即：博客文章、文章），我可以与开发人员和/或经理共享这些资源，这将有助于以精美呈现的方式引入面向对象范例。该语言可以是 C# 或 VB.NET，但首选 VB.NET。
谢谢！
The team is familiar with ASP.NET and has been working in VB.NET for several years, but they just haven't made the transition in thinking in terms of objects. In fact, they may be a little intimidated by OOP from brief glimpses they've seen of C++ and unmanaged environments. Work has kept them busy enough that they haven't had time to properly absorb the benefits that .NET and OOP provides.
I'm looking for some lightweight resources (i.e.: blog posts, articles) that I can share with both developers and/or managers which would help to introduce the object oriented paradigm in a nicely presented fashon. The language could be in either C# or VB.NET, though VB.NET would be preferred.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
另一种对我来说非常有效的方法是举办一系列不限成员名额的棕色袋午餐。这是当你邀请你的同事（不是要求）到会议室讨论面向对象的某些方面时。
每个人都自带午餐。你可以时不时地买个披萨来激励他们来，但你不会每周都这样做。
每周始终在同一地点和同一时间进行。您的发言总是简短，不超过 30 分钟，留出充足的时间来提问和讨论我们如何在公司中使用它。按时开始并按时虔诚地完成。
发布时间表，强调如果他们参加所有会议，他们就能从中获得最大收益，但如果他们错过了一场会议，他们仍然可以赶上。
以下是一些示例主题：
到那里。
这里
遗产。
你会在现实生活中使用的。
我告诉你，如果你让这些事情变得有趣，你会惊讶地发现你的员工能如此迅速地跟上进度。
然后，世界上最好的后续措施是实施 结对编程 和 友好的代码演练。如果你不做其中一项或两项，这些教训可能就不会被记住。
Another approach that has worked spectacularly for me is to host an open-ended series of brown bag lunches. This is when you invite your coworkers (not demand) to a conference room where you discuss some aspect of OO.
Everyone brings their own lunch. And you can buy a pizza now and then to incent them to come, but you wouldn't do this every week.
Always have it the same place and the same time every week. You'll always talk briefly, no more than 30 minutes, leaving plenty of time for questions and discussion on how we use this in our company. Start on time and finish religiously on time.
Publish the schedule, emphasizing that they'll get the most out of it if they attend all sessions, but if they miss one, they can still catch on.
Here are some example topics:
get there.
inheritance for here
inheritance.
that you'd use in real life.
I'm telling you, if you make these things interesting, you'll be amazed at how quickly your people will come up to speed.
Then, the best followup in the world is to implement Pair Programming and Friendly Code Walkthroughs. If you don't do one or both of these, the lessons will likely not stick.
O'Reilly 的《Head First 面向对象编程》麦克劳林等人的同事。
以下是更多内容的链接：Head First OOAD
很棒的书。很棒的系列。易于阅读并易于掌握 OO 的概念，这正是您和您的团队所追求的。
（来源：coverbrowser.com）
Head First Object-Oriented Programming from O'Reilly & Associates by McLaughlin, et al.
Here's a link for more: Head First OOAD
Great book. Great series. Easy to read and easy to grasp the concepts of OO, which is what you're after with your team.
(source: coverbrowser.com)
对于使用 VB 进行 OOP...
开始使用 VB.Net 进行面向对象编程
使用 Visual Basic .Net 进行面向对象编程
取决于您可能需要的经验程度还可以阅读有关面向对象的分析和设计的内容。这些将帮助您了解如何做到这一点。
首先进行面向对象的分析和设计
使用应用程序进行面向对象的分析和设计
MS 关于 VB.Net 中的 OO 的文章：
http://msdn.microsoft.com/en-us/library/aa289512(VS. 71).aspx
有点旧，但提供了基础知识...
根据我的经验，团队对事件驱动模型的根深蒂固程度将极大地影响团队移动/拥抱 OO 的效率。这比我愿意承认的在 .Net 中使用对象而不真正理解 OO 更容易。从 VB6 开始，继续以经典方式进行卡车运输太容易了。 OOA 和如果您的团队似乎只是 .Net 中对象的“用户”而不是在自己的代码中实际创建类，那么 OOD 书籍可能是一个很好的起点。
For OOP with VB...
Beginning Object-Oriented Programming with VB.Net
Object-Oriented Programming with Visual Basic .Net
Depending on how experienced one is you may want to also read about Object-Oriented Analysis and Design. These will help you to wrap your head around how to do it.
Head First Object-Oriented Analysis and Design
Object-Oriented Analysis and Design with Applications
MS article on OO in VB.Net:
http://msdn.microsoft.com/en-us/library/aa289512(VS.71).aspx
A little old but gives the basics....
It has been my experience that depending on how entrenched the team is on the event driven model will greatly influence how effective the team moves/embraces OO. It's easier than I would like to admit to just use objects in .Net and not really understand OO. Coming from VB6 it was too easy to keep on trucking the classic way. The OOA & OOD books may be a great starting point if your team seems to be just "users" of the objects in .Net versus actually creating classes in their own code.
我以前曾与具有不同技能的 VB 开发人员一起工作过（大多数具有 VB6 背景）。设计模式可能已经需要太多的抽象思维。
如果他们非常了解业务需求，我可以建议“裸对象”类型的方法吗？这种方法让每个人都可以可视化对象、封装、继承、关系和组合，并且可以减轻 OOAD 最初的痛苦。您可以使用您企业中的具体示例，而不是书中的人为示例。
这是一条漫长的路——祝你好运！
PS如果您有兴趣，我提供了一个支持裸对象模式的工具。
I've worked with VB developers of varying skills before (mostly from a VB6 background). Design Patterns might already require too much abstract thinking on their part.
If they're pretty savvy with business requirements, can I suggest a 'Naked Objects' type approach? This approach let's everyone visualise objects, encapsulation, inheritance, relationships and composition, and can ease the initial pain of OOAD. And you can use concrete examples from your business, instead of contrived examples from a book.
It's a long road - best of luck!
P.S. If you're interested, I provide a tool that supports the Naked Object pattern.
设计模式
从单个角度来看，这本书实际上相当“轻量级”图案。
Design Pattens
The book is actually pretty "lightweight" from the perspective of a single pattern.