-----Original Message-----
> > I think leaving the blocks behind is not a smart idea. In my opinion you > > should use the blocks as your first choice (because there are a lot of code > > that you don't have to do yourself) in that way you will finish earlier and > > with code that has been tested by professionals. > First of all, I am a professional. So are you. I'm sure the quality > of the framework is high (admittedly, I have not played with it much), > but the fact that it is developed and tested by supposedly superior > developers is not a reason I would choose to use it. Now, in the case > of the EntLib, I know some of the guys who are working on that stuff, > and they *are* superior to me :), but that's beside the point. My > statements are general in nature. When you take a complex and > feature-rich framework and insert it into your application, you get > all the baggage that may go along with it. If you have studied the > particular app block and believe you can save yourself significant > effort by using it, go for it. However, many developers seemingly try > to make use of every app block they can, even to solve a very simple > problem that they could handle themselves. I think this is poor > practice. I'm not saying that this is the case for the OP. Again, > this is generally speaking. Jajaja don't take it that way. I was saying professional tester's, not professional developer. I never doubted I was talking with a professional. What I mean is that they have a professional team that tests and revises every single line of code. > > Then test your application in an environment similar to the one it is going > > to be deployed, only then (and I stress only then) if the is a strong issue > > with performance go down to the code and fix the problem by removing the > > block only in that part of the app (and I stress only in that part) > Yes, of course. Premature optimization is a huge time waster. My > problem with some of the app blocks is not that they don't perform > well, but that they can introduce more complexity than they remove, in > many cases. I think they are like design patterns, they might be more complex, but it will be easier for me to understand your app (in the case I will have to maintain it), because we are all going to speak the same language. I know how dataaccess is like EntLib became the universal language!!! We have seen be huge improvements in the Latin American community with the use of similar frameworks. You have projects over here that state that you have to use the framework. In that way, they are sure that all the partners involved in the project can be replaced and the new one will rapidly catch on. This is subject called by some architectural governance A l e j a n d r o G. J a c k | P r i n c i p a l C o n s u l t a n t | <mailto:[EMAIL PROTECTED]> 15-5755-9122 =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
