Comments on: Extension Methods & Single Responsibility Principle http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools. Mon, 26 Jul 2010 02:01:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Luciano Evaristo Guerche (Gorše) http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1346 Luciano Evaristo Guerche (Gorše) Wed, 11 Feb 2009 13:26:34 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1346 Jason, I believe extension methods must be used with very high caution in that they don't belong to the class or interface they act in, so when extending the class or implementing the interface, extension methods code are not inherited. Talking about interfaces, as extension methods are not part of the interface's contract, their existence and signatures aren't even checked on implemented classes. Jason,

I believe extension methods must be used with very high caution in that they don’t belong to the class or interface they act in, so when extending the class or implementing the interface, extension methods code are not inherited. Talking about interfaces, as extension methods are not part of the interface’s contract, their existence and signatures aren’t even checked on implemented classes.

]]> By: Weekly Link Post 79 « Rhonda Tipton’s WebLog http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1320 Weekly Link Post 79 « Rhonda Tipton’s WebLog Mon, 02 Feb 2009 03:20:24 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1320 [...] Jason Young does a great job explaining Extension Methods & Single Responsibility Principle. [...] [...] Jason Young does a great job explaining Extension Methods & Single Responsibility Principle. [...]

]]> By: Jay http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1316 Jay Wed, 28 Jan 2009 06:37:18 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1316 Hi Does subversion VM has LDAP authentication ? Hi
Does subversion VM has LDAP authentication ?

]]> By: Chris Marisic http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1312 Chris Marisic Tue, 27 Jan 2009 07:45:36 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1312 I just hate static helper classes, they are so .NET 2.0. I feel any method that can be put into a static helper class should be an extension method in .NET 3.5. If there's ever a point where the implementation might need to change based on the object implementation or what class implements the interface that it should be moved internally to the class as a regular method. I just hate static helper classes, they are so .NET 2.0. I feel any method that can be put into a static helper class should be an extension method in .NET 3.5. If there’s ever a point where the implementation might need to change based on the object implementation or what class implements the interface that it should be moved internally to the class as a regular method.

]]> By: admin http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1311 admin Mon, 26 Jan 2009 22:56:45 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1311 Tuna, your approach would work fine. Maybe my example wasn't the best since reporting is probably an involved operation. Most of the time, I do it as you described. I just thought this was a fairly elegant solution for certain cases where the overhead of your approach might be a bit too much. The point was that there are other ways of separating your code while still operating a certain interface. People may already be doing this, and the other point I was trying to make was that extension methods give us a little more elegant way of "attaching" this functionality. Tuna, your approach would work fine. Maybe my example wasn’t the best since reporting is probably an involved operation. Most of the time, I do it as you described. I just thought this was a fairly elegant solution for certain cases where the overhead of your approach might be a bit too much.

The point was that there are other ways of separating your code while still operating a certain interface.

People may already be doing this, and the other point I was trying to make was that extension methods give us a little more elegant way of “attaching” this functionality.

]]> By: Tuna Toksoz http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1310 Tuna Toksoz Mon, 26 Jan 2009 21:51:38 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1310 Hi Chris, The thing is that Extension methods should be used when you can't modify the code. I also believe that, if you want to provide an SRP with a lot flexibility, you can have IReportGenerator { IReport GenerateReport(ReportData); } I _believe_ you shouldn't use Extension Methods jst for the sake of SRP. Anyway this issue sounds more of a personal taste, doesn't it? Hi Chris,
The thing is that Extension methods should be used when you can’t modify the code. I also believe that, if you want to provide an SRP with a lot flexibility, you can have
IReportGenerator
{
IReport GenerateReport(ReportData);
}

I _believe_ you shouldn’t use Extension Methods jst for the sake of SRP.

Anyway this issue sounds more of a personal taste, doesn’t it?

]]> By: Chris Marisic http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1309 Chris Marisic Mon, 26 Jan 2009 21:20:44 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1309 Tuna, why would you feel that way? I think this is the absolute intention of extension methods. I agree with you poster that this is a much preferred solution than having helper classes every where. Tuna, why would you feel that way?

I think this is the absolute intention of extension methods.

I agree with you poster that this is a much preferred solution than having helper classes every where.

]]> By: Tuna Toksoz http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html/comment-page-1#comment-1302 Tuna Toksoz Mon, 26 Jan 2009 18:19:56 +0000 http://www.ytechie.com/2009/01/extension-methods-single-responsibility-principle.html#comment-1302 I believe this is an abuse of Extension methods. I believe this is an abuse of Extension methods.

]]>