[Mono-list] critical problem !!!!!!!

Adrien Dessemond adrien.dessemond at softhome.net
Sat Jun 9 14:22:49 EDT 2007

At 11:49 2007-06-09, you wrote:

[Could you, please, translate your code in english when you ask 
questions here ? More people will be glad to think about your 
troubles and this will make your chances of having mutiple advices higher :-) ]

>         [assembly: AssemblyVersion("")]
>         public class AnnuaireDAL
>         {
>                 public AnnuaireDAL() {  }
>                 public CarteDeVisite ExtraireCarte (string nomSearch
>) {
>                         return null ;
>                 }
>                 public void AjouterCarte (CarteDeVisite carte) {

Personal feedback experience : I would try to manage my "visit cards" 
as a collection of VisitCards (say VisitCardsCollection) objects, as 
it better integrates in the .Net framework philosophy and help both 
in keeping a robust and flexible object design. Next I would consider 
my Directory class ("AnnaireDAL") as something that manages 
CardsCollection objets (directory update/query/....). You have really 
nice language features like properties indexers and generics, 
consider them at your advantage. May the classes/interfaces in 
System.Collections.Generic could help you a lot too (Dictionary ? 
List ?). It is just another OO approach, it does not pretend to be a 
"better" one.

Kind regards,


More information about the Mono-list mailing list