Design Decision Advice 1

[eb24]

I developing an app in C# 2005 and would like some advice on how I should go with my next step:

I have a Solution with a couple of projects in it from different developers (.dll) and some are mine. I need to implement some common functionality that will be used by other developers for some of these Windows Forms. Such functionality are buttons that pop-up othe dialogs/windows and perform their duties. These components are items like Notes, References, etc. Basically, when Users click on these buttons of the main form(s), they will be able to Add (notes for example to that record set).

What do you all suggest? Base classes, stand-alone forms, Interfaces, or what do you recoomend?

Any and all advice will be greatly appreciated.

 

[jmeckley]

how do the assemblies interact? are they different layers dal, bll, gui, or is each assembly a seperate project (all gui, logic and data access in 1 dll) that needs to be compiled into a larger project.

i think we need more info on how your project is assembled before we could give any sound advice on what you options are.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[eb24]

Let me start off by saying that I come from an ASP.NET background and have started working on Windows Forms. For the sake of output, my ASP.NET work was quick and dirty and I had poor practices in place. It's been over 5 years since I"ve really implemented some good OOP and Design Patterns into my work (worked on Windows apps), but am looking forward to the challenge. I have taken out my GoF book and will need to refresh on my OOP concepts.

Anyways, my current Solution has a Class Library that has code that was generated by CodeSmith which is following the Model-View-Controller Design Pattern (MVC), so thus the DAL and BLL is all located there. I have the start-up project as a stand-alone Windows Form. I also have another Class Library where I have some UserControls. In many files, I am referencing other assemblies that have been built by other developers.

Does this help? Let me know if more clarification is needed. Any and all assistance will be greatly apprreciated.

 

[jmeckley]

what exactly do you want the Notes, References, etc. to be?
are they gui controls, services for business logic or data acces logic, or all 3?

how will the objects be used within the application?

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[eb24]

I want these 'shared' components to be implemented as buttoons on forms. Upon clicking on these buttons, a form is displayed allowing the user to enter its pertinent data related to the main form.

For example, if the User is working on the main form, there will be some buttons displayed, e.g. Notes. The user can then enter Notes related to that record.

Does this help?

 

[jmeckley]

that seems straight forward.
1. I would create a form with the proper controls related to notes along with a save and cancel button.
2. when user clicks save, pass the data to the Notes Service and save the data.
3. when the user clicks cancel, undo changes and close the form.

this assumes your always preforming the same action with the data. if however you want to preform different actions on the data I would recommend creating an event delegate for the save and cancel actions.
here is more info on events/delgates [

http://www.akadia.com/services/dotnet_delegates_and_events.html

]

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[eb24]

Thanks for the advice! I'll reply back soon to post what direction I take.