Plácido, this thread is full of sarcasm. Here is an analogy: You do to a Car Dealer (doesn't matter which one) and say "I need to get from here to there. Should I buy one of you cars?"
1. Of course the dealer wants you to buy his car, he will not likely send you across the street to his competitor. in other words: yes, most users here will say NH is the right/good choice for your ERP 2. As a buyer of a car you haven't told the dealer what you are using the car for: how many miles will you drive. will be be on country roads, city, highway, off-roading? How many people need to travel in the car? Do you need storage room? Do you prefer manual or automatic transmission? etc. etc. In other words, other than building an ERP, what problems is the ERP system solving? How does data access fit into the ERP system? Does your team have any experience with NH? How much time can to dedicate to learning NH? What restrictions/regulations are in place that would/ could limit the use of any ORM? On Jun 15, 11:23 am, Wayne Douglas <[email protected]> wrote: > lolz - oh me oh my > > On Mon, Jun 15, 2009 at 4:20 PM, Plácido Bisneto > <[email protected]>wrote: > > > > > Should I ask you why we shouldn't use NH to build an ERP, Fábio?? > > > Plácido Bisneto > > > 2009/6/15 Fabio Maulo <[email protected]> > > > When a customer ask me "Should i User Nhibernate for MY ERP ?" my answer is > >> "NO". > >> Btw after they investigate others solution, in general, they end using NH > >> ignoring my advise. > >> -- > >> Fabio Maulo > > -- > Cheers, > > w:// --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
