I have been doing some research on Component-based Scalable Logical Architecture. I wanted to find out if this is something alot of .Net developers are familiar with and if there are companies that use this.
Printable View
I have been doing some research on Component-based Scalable Logical Architecture. I wanted to find out if this is something alot of .Net developers are familiar with and if there are companies that use this.
Hi,
I never used their framework per say, but after reading wikipedia's explanation of CSLA, I noticed that I design Business Objects in a similar way as the provided example.
I prefer to build everything from scratch, so there's no room for 'guessing' what is doing in any given situation.
HoraShadow
we use it as a base for our architecture. It has some features in it that we didn't need, and was missing a few other things we needed, so our System Architect broke it down, stripped out stuff we didn't need, added the things we did need, and put it back together. That now forms the basis from which all of out business objects and lists are born.
-tg
I appreciate the input.
I will be using this for the job I just got yesterday and wanted to find out what it was.
At first I was scared it was some proprietary form of .Net programming and I was not interested in that.
Nope... it's a business framework put together by Rocky Lhotka... the idea being that it provides some base core functionality that you can then expand on to make the development of business objects easier. It takes a lot of effort to set up, but once it's in place, it's quite easy to use.
-tg
It's an implementation of Rocky's vision of business objects.
I looked at it a few years ago at a different company, and it had good stuff in it, but overall, perhaps far too much stuff for most applications. His books are at the very least a good read and exercise.
Yeah, the company I just started with uses it. The learning curve is quite high and I have been worried that CSLA is not something I can take with me to another job.