The System.Web.Abstractions

re: The System.Web.Abstractions

Chuck Durfee — Wed, 11 Mar 2009 18:15:17 GMT

Cache can be instantiated and used in non-Web applications through HttpRuntime.Cache, as discussed by many include Scott Hanselman (www.hanselman.com/.../UsingTheASPNETCacheOutsideOfASPNET.aspx). Hence, no need to wrap it.

re: The System.Web.Abstractions

Josh — Wed, 04 Jun 2008 01:10:22 GMT

Another reason for abstract class. Is an interface requires you to override all methods while an abstract class you can choose to just override what you want to mock for unit testing.

undev.spaces.live.com/.../cns!6526A337A687E45D!214.entry

re: The System.Web.Abstractions

luisabreu — Tue, 03 Jun 2008 22:52:03 GMT

Yes and no.

I'm not sure that this model is good. I would prefer interfaces with new functionality being added to a new derived interface.

Even though versioning might have been the main idea behind this approach, I still think that the biggest advantage is in testing...

abraços!

re: The System.Web.Abstractions

Giovanni Bassi — Tue, 03 Jun 2008 22:34:51 GMT

Hello Luis,

They used Abstract Classes for a purpose: to do not create versioning problems on future releases.

Take a look at Phil Haack's posts:

haacked.com/.../versioning-issues-with-abstract-base-classes-and-interfaces.aspx

haacked.com/.../abstract-base-classes-have-versioning-problems-too.aspx

It makes sense, right?

Um abraço,

Giovanni Bassi