Rockford LhotkaBeantown.NET INETA User Group is hosting Rocky Lhotka, Principal Technology Evangelist for Magenic as well as Microsoft Regional Director, MVP, and renowned technologist.

Rocky is the author of CSLA .NET, which is a framework for managing and implementing business logic whether it be in a single-tier or a distributed multi-tier system.  His topic on Wednesday is CSLA.NET as the ‘M’ in MVC/MVP/MVVM (abstract below).  The session will be held at the New England Research and Development Center in Cambridge, from 6 –8 p.m.  And if the title doesn’t have enough acronyms, here’s another… be sure to RSVP via e-mail by 3 p.m. on Wednesday to facilitate the sign-in process at the security desk, and more importantly, ensure there’s enough pizza on hand!

 

CSLA .NET as the 'M' in MVC/MVP/MVVM

Building a UI today can feel like wading into alphabet soup with MVC, MVP, MVVM and numerous other consonant-heavy acronyms. Nearly all of these patterns have one thing in common: the letter ‘M’, which stands for “Model”. The Model is the part of the application responsible for things like business and data processing, and is arguably the core of the application.


CSLA .NET is one of the most widely used development frameworks on the .NET and Silverlight platforms. The primary focus of CSLA .NET is to help in the creation of a rich object-oriented business layer that expresses the needs of the business domain model. In other words, CSLA .NET is all about helping create a powerful object model for an application. It should come as no surprise then, that CSLA .NET can fit naturally into many of the UI patterns.


At the same time, many of the UI patterns were devised on non-.NET platforms where powerful RAD concepts like data binding and UI designers don’t exist. Due to this, many of the “traditional” uses of these patterns prevent the use of productive RAD concepts and tooling, and that is an unforgivable loss. In this talk, Rocky will discuss how CSLA .NET helps implement powerful models, and how the most common UI patterns can be used to reap their benefit, without giving up the power of .NET itself.