Are some enterprise library application blocks obsolete?

Question

With the introduction of newer paradigms in ASP.Net, are some of the application blocks in the Corporate Library becoming obsolete? For example, see the following:

• Membership in ASP.Net, role and profile as opposed to a block of security applications.
• LINQ to SQL and Entity Framework as opposed to data access application block

Are the above application blocks relevant? Can someone illustrate when and why to use one over the other?

Answer 1

As a manufacturer of the Microsoft Enterprise Library, I felt it was important to explain the concept of "carefully managed obsolescence." So, I posted an extended answer on my blog.