mattc58 wrote:
So what are most folks using these days? It's been a few months since I last used the product, and at that time I used the self-servicing template to great effect.
The system I'm building is a standard ASP.NET web system with a SQL Server 2000 database. This project will be larger than the last system I built, and will eventually incorporate some e-commerce type functionality. I'm thinking maybe 20-30 tables.
We're also doing some more SOA type work on this project, though I'm not sure how much of an impact that will have on this conversation.
If you're comfortable with selfservicing, use that for the projects you do, unless you need remoting, which is supported in selfservicing, but clashes a bit with the selfservicing code, as .Save() on teh client isn't saving at all, adapter is more suitable with a distributed application.
Both philosophies (paradigms if you will) are equal to us and I try to implement functionality I add for both, however if functionality can't be implemented (due to hte global nature of selfservicing for example) I of course skip it, but no paradigm is left behind or considered less useful, they serve different points of view on how persistence should be realized and also the setup of the application.
The next generation of the runtime libraries + templates, for .NET 2.0, will also sport both, but will be developed differently. Now, selfservicing was developed earlier and adapter later, but functionally, selfservicing is just a wrapper around a global adapter, so that will be an internal change, but from the outside, it will be the same (with some api changes of course, but that's unavoidable).
