how to use design pattern in vb 2005

Search: Go

Home

About

User Group Events

Other Events

News

Downloads

Discussions

General Discussions

Event Discussions

Job Board

ASP.NET

VB.NET

CSharp

Study Group

Do you want to sponsor an Event?
Contact the .NET User Group at sponsors@torontoug.net

Online:

There are currently:
80 Guests.

0 of 6,455 Members.

Hosting
provided by

Home > Discussions > VB.NET

Notify me of new comments

Author

Thread: how to use design pattern in vb 2005

vijay1

how to use design pattern in vb 2005
Posted: Sunday, July 16, 2006 7:30 PM (EST)

I have over 3 years exp with vb6. Mostly i have developed fat client. Also I have worked as c# developer for few months. I understand oop concepts and have experience in developing classes. However I have not designed 3 tier applications only by myself. Now i am working on a project in which I have to convert vba access application (300 forms) to vb.net windows application. I am in the process of analyzing existing application in order to get some info (business rules.............). I decided to develop a three tier application. The backend is sql server 2000 .I need advice>>

1)How to decide which pattern to use for which layer?(factory,mvc)>>

2)should i use use case?>>

3)how to break the business into objects/classes?>>

4)is it a must i use use interface or abstract class?>>

5) I am looking for a book/s which explains how to develop a object oriented application using design pattern/use case.....?(looking for a simple book)I have read one/two books on design pattern. They are confusing me.>>

Thanks in advance>>

Comments:

Author Thread:

indigofire

how to use design pattern in vb 2005
Posted: Wednesday, March 05, 2008 1:07 PM (EST)

The reply is a little late, but I have a good book on <a href="http://www.apress.com/book/view/9781590592748">patterns in VB.NET from APress</a>. It's for the framework 1.0 (the original VB.NET), and there are a couple of smaller mistakes, but overall it gives a good picture of how to apply patterns. The most important aspect to remember is to analyze your business needs first and then apply the pattern that fits. Which one to use can't be predetermined, although some come up more often than others. To answer your questions: 1) This is the core of the design process. You must analyze what you're trying to do, and then decide which patterns fit and which don't - and sometimes none of them will! Sometimes it's more than one, and you have to make a design decision as to which one works "best". 2) Absolutely. Use cases are the start and end to any design (IMHO). They might be trivially simple, and might not even need a diagram, but at least have it written down somewhere. 3) That is precisely the job of a good OO designer, and really the difference between a programmer and an architect. 4) Depends on the pattern, but if the pattern specifies that something be abstract, then it must be in order for the pattern to work properly. Usually this is for a reason. 5) The Apress book is good at giving examples. One thing I must stress: VB6 is not object oriented. Sure it could deal with some objects, and had data structures, but it's not an object-oriented language, and you cannot implement patterns or really any reasonably good design in it. VB.NET, C#, and any other OO language is a world apart, and there is much learning to do in order to use it properly - and not just in syntax. You must change the way you think. Good luck! -kms