I have bought the Expert Business objects and have read up to chapter 13 now. I really love the CSLA.NET framework (I've built some test applications with it). With that said I'm a very conservative programmer, I need others input.
I am building a robust forum, bing, e-commerce store into one and have been trying to learn the CSLA framework as much as possible the last two weeks to make a final decision. There are business rules that require high degree of performance.
I will be using Razor, ASP.NET MVC3, and EF (but all stored procedures).
If I could have anyones opinion on how my adventure will go beforehand using this framework it would be awesome. I understand there are areas I don't have to use CSLA, but with my limited knowledge of the framework I would love to get someone's opinion.
I need it to be highly scalable and unprecedented speed, as my user base is through the roof.
(it's difficult to give an opinion, but even if someone was like Yes, you won't run into any gladiator battles between MVC3 and CSLA would be great!)
Yes, MVC is one of the supported UIs you can use with Csla. One of the goals of the framework is to allow you to build scalable applications, which Csla enables by use of the dataportal. I doubt you'd have any major issues building your business objects against Csla.
Is there a reason you want to use EF if you're going to use stored procedures? Seems to me you're adding another layer you don't need. EF uses ADO.NET behind the scene so why don't you cut out EF and just use ADO.NET. Then you don't have another layer of complexity to deal with. -Paul
I am most familiar with ADO.NET. So I think I may take your suggestion.
Just that when MS goes a certain direction I've usually followed. But I've read more over the last few days and agree. I should use ADO.NET
That's probably a good choice. EF just doesn't work very well with stored procedures. At least not unless you've specifically designed the stored procedures for use with EF. And if you have to go through that work, I'm not sure I see the point...
Copyright (c) Marimer LLC