Ayende @ Rahien

Francois Tanguay commented on Ayende's Design Guidelines: Rule #1

Tue, 26 Feb 2008 17:51:12 GMT

That's why I wished there was a way to promote a type object into a generic scope: foreach(Type type in GetComponentTypes()) { // New using scope keyword! using() { myContainer.RegisterComponent(); } }

Andrey Shchekin commented on Ayende's Design Guidelines: Rule #1

Sat, 23 Feb 2008 23:43:43 GMT

Exactly. http://api.castleproject.org/html/M_Castle_MicroKernel_DefaultKernel_ResolveServices__1.htm immediatelly comes to mind.

Andrey Shchekin commented on Ayende's Design Guidelines: Rule #1

Sat, 23 Feb 2008 23:43:43 GMT

Exactly. http://api.castleproject.org/html/M_Castle_MicroKernel_DefaultKernel_ResolveServices__1.htm immediatelly comes to mind.

Ayende Rahien commented on Ayende's Design Guidelines: Rule #1

Sat, 23 Feb 2008 15:02:48 GMT

Yes, this is for published API. If you control the code, it doesn't really matter, since you can always change that. Nevertheless, you need to carefully consider what you believe a published API is

Christopher Bennage commented on Ayende's Design Guidelines: Rule #1

Sat, 23 Feb 2008 14:25:51 GMT

I guess the context here is when you are publishing an API? In a project where I control and consume the code base, it's YAGNI.

Symon Rottem commented on Ayende's Design Guidelines: Rule #1

Sat, 23 Feb 2008 10:15:14 GMT

I completely agree - this is something I've run into a few times and providing an API without non-generic alternatives just generates friction for the consumer.