Caching and Security blocks

Topics: Caching Application Block , Security Application Block
May 12, 2008 at 6:51 PM
As a newcomer to both ASP.NET and Enterprise Library, I have a question.
What has the Caching and Security app blocks have to offer MORE than the
default stuff that exists in the .NET framework? Why should someone use them
if he/she is covered by the default ASP.NET behavior?

TIA
Iordanis
May 12, 2008 at 9:46 PM

I do not know the gritty details of the differences but a key advantage is that by using the application blocks you are not bound to ASP.NET.  You could implement a caching layer on top of your database and make use of that from any application (WinForms, ASP.NET, CAB, Web Services...).  This applies to most of the blocks.

Also, I would advise against using ASP.NET Cache since it forces you to cache from presentation layer (ASP.NET pages) which is bad.

May 13, 2008 at 11:58 AM
When it comes to Security, there are really no overlapping features between ASP.NET's and EntLib's offerings. EntLib's Security block provides authorization and caching of credentials, but you're expected to rely on ASP.NET for Membership, Role and Profile management services.

You can take a look at EntLib's Security QuickStart for a sample on how these security features can be integrated.

Hope this helps,
Fernando


iordanis wrote:
As a newcomer to both ASP.NET and Enterprise Library, I have a question.
What has the Caching and Security app blocks have to offer MORE than the
default stuff that exists in the .NET framework? Why should someone use them
if he/she is covered by the default ASP.NET behavior?

TIA
Iordanis