Comments on: The Great EPiServer Informed Response http://www.markeverard.com/blog/2010/04/20/the-great-episerver-informed-response/ The only consistency is change itself Tue, 07 Feb 2012 22:30:52 +0000 hourly 1 By: uberVU - social comments http://www.markeverard.com/blog/2010/04/20/the-great-episerver-informed-response/comment-page-1/#comment-4 uberVU - social comments Wed, 21 Apr 2010 12:58:41 +0000 http://www.markeverard.com:/blog/?p=5#comment-4 <strong>Social comments and analytics for this post...</strong> This post was mentioned on Twitter by joelabrahamsson: RT @ev2000: My response http://bit.ly/9eBXGZ (to http://bit.ly/cYut0A), some available solutions to the apparent 'problems' with #EPiServer... Social comments and analytics for this post…

This post was mentioned on Twitter by joelabrahamsson: RT @ev2000: My response http://bit.ly/9eBXGZ (to http://bit.ly/cYut0A), some available solutions to the apparent ‘problems’ with #EPiServer…

]]> By: Stefan Forsberg http://www.markeverard.com/blog/2010/04/20/the-great-episerver-informed-response/comment-page-1/#comment-3 Stefan Forsberg Tue, 20 Apr 2010 17:40:11 +0000 http://www.markeverard.com:/blog/?p=5#comment-3 I have a feeling that EPiServer, like many other companies that are closely tied to Microsoft, have followed the "Microsoft way" of developing. And since MS themself, at least not publically, haven't pushed for instance TDD, Unit testing, IoC or any of those other acronyms coming from the Alt.Net world neither have EpiServer. And since many of the companies that uses EpiServer has a similar relation to MS and EpiServer it really hasn't been that "important" to us either. What has happened with MS (and the whole chain down from there) is that since the introduction of asp.net MVC (or around that time) this is something that MS talks about too. And not in terms of being a fun/cool alternative but rather something that makes it easier to deliver business value. So if you look at what has happened in the last year or two the development process has changed a lot for the better. My hope is that the more people, both in the .Net world in general and in the EpiServer world, starts to talk about these topics the more open source projects like the ones you mention above gets developed and when EpiServer sees where the wind is blowing I have no doubt that they will follow. I have a feeling that EPiServer, like many other companies that are closely tied to Microsoft, have followed the “Microsoft way” of developing. And since MS themself, at least not publically, haven’t pushed for instance TDD, Unit testing, IoC or any of those other acronyms coming from the Alt.Net world neither have EpiServer. And since many of the companies that uses EpiServer has a similar relation to MS and EpiServer it really hasn’t been that “important” to us either.

What has happened with MS (and the whole chain down from there) is that since the introduction of asp.net MVC (or around that time) this is something that MS talks about too. And not in terms of being a fun/cool alternative but rather something that makes it easier to deliver business value. So if you look at what has happened in the last year or two the development process has changed a lot for the better. My hope is that the more people, both in the .Net world in general and in the EpiServer world, starts to talk about these topics the more open source projects like the ones you mention above gets developed and when EpiServer sees where the wind is blowing I have no doubt that they will follow.

]]> By: Joel Abrahamsson http://www.markeverard.com/blog/2010/04/20/the-great-episerver-informed-response/comment-page-1/#comment-2 Joel Abrahamsson Tue, 20 Apr 2010 13:49:01 +0000 http://www.markeverard.com:/blog/?p=5#comment-2 Excellent post Mark! I think you summed up many of the available solutions that are available already. It should also be added that the EPiServer dev team are aware of many of the problems and I know there are plans to fix them in future versions. While it's easy to complain about problems and bad/old architecture in frameworks I think it's important that we take a pragmatic approach and point them out to the developers in a constructive manner and/or try to provide ways of fixing them ourselves. Given that we use EPiServer, as with any system, we need to constantly give EPiServer's developers feedback based on our experiences. The EPiServer user groups in Stockholm and Oslo is one such forum and we need to find others as well. Excellent post Mark!

I think you summed up many of the available solutions that are available already.

It should also be added that the EPiServer dev team are aware of many of the problems and I know there are plans to fix them in future versions.

While it’s easy to complain about problems and bad/old architecture in frameworks I think it’s important that we take a pragmatic approach and point them out to the developers in a constructive manner and/or try to provide ways of fixing them ourselves.

Given that we use EPiServer, as with any system, we need to constantly give EPiServer’s developers feedback based on our experiences. The EPiServer user groups in Stockholm and Oslo is one such forum and we need to find others as well.

]]>