Comments on: I do not like the trend for EPiServer web.config! http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/ Chatter about EPiServer, ASP.NET, CSS and Web Development. Thu, 29 Jul 2010 09:07:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Mikael Söderström http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/comment-page-1/#comment-3345 Mikael Söderström Fri, 30 Oct 2009 12:46:11 +0000 http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/#comment-3345 Why not use the same method as in .NET 4.0? Since there is a new version of the CLR (the first new since .NET 2.0) they had the ability to move all settings to machine.config. Wouldn´t it be possible to do the same in EPiServer? Why not just move some of the configuration settings to machine.config? There is a lot of shared properties between all the sites on a single server. Why not use the same method as in .NET 4.0? Since there is a new version of the CLR (the first new since .NET 2.0) they had the ability to move all settings to machine.config.

Wouldn´t it be possible to do the same in EPiServer? Why not just move some of the configuration settings to machine.config? There is a lot of shared properties between all the sites on a single server.

]]> By: Magnus Stråle http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/comment-page-1/#comment-3341 Magnus Stråle Thu, 22 Oct 2009 06:10:18 +0000 http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/#comment-3341 You can take a look at our new configuration guideline over at http://world.episerver.com/Blogs/Magnus-Strale/Dates/2009/10/What-do-we-do-about-config-file-bloat/ You can take a look at our new configuration guideline over at http://world.episerver.com/Blogs/Magnus-Strale/Dates/2009/10/What-do-we-do-about-config-file-bloat/

]]> By: Henrik Nystrom http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/comment-page-1/#comment-3340 Henrik Nystrom Wed, 21 Oct 2009 23:11:38 +0000 http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/#comment-3340 I couldn't agree with you more, Fredrik. Removing all the default values and examples from the production install and ship the public templates with a full web.config with all default values, examples and comments. Then developers can use that to discover and learn about configuration settings as Ted mentions. I'm also worried about references to page IDs, page type IDs and other things that is getting added lately. These values changes between environments and deployments and being in an environment where we pass on deployment scripts to a hosting engineer this is a nightmare. Always good to read your posts! Cheers Henrik I couldn’t agree with you more, Fredrik.

Removing all the default values and examples from the production install and ship the public templates with a full web.config with all default values, examples and comments. Then developers can use that to discover and learn about configuration settings as Ted mentions.

I’m also worried about references to page IDs, page type IDs and other things that is getting added lately. These values changes between environments and deployments and being in an environment where we pass on deployment scripts to a hosting engineer this is a nightmare.

Always good to read your posts!

Cheers
Henrik

]]> By: Ted Nyberg http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/comment-page-1/#comment-3338 Ted Nyberg Wed, 21 Oct 2009 16:44:59 +0000 http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/#comment-3338 I agree in general, and I loved the chart! :) I think it's great to separate the configuration into different .config files (not just connection strings) - it definitely makes versioning and deployment easier! Just 2 cents on default values - I don't think they should be removed for EPiServer-specific configuration elements. They may well be left out for standard ASP.NET elements, but EPiServer-specific elements' default values should be kept so that developers know what the default values are (and also which settings you can change). I agree in general, and I loved the chart! :)

I think it’s great to separate the configuration into different .config files (not just connection strings) – it definitely makes versioning and deployment easier!

Just 2 cents on default values – I don’t think they should be removed for EPiServer-specific configuration elements.

They may well be left out for standard ASP.NET elements, but EPiServer-specific elements’ default values should be kept so that developers know what the default values are (and also which settings you can change).

]]> By: Martin S. http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/comment-page-1/#comment-3336 Martin S. Wed, 21 Oct 2009 16:03:47 +0000 http://blog.fredrikhaglund.se/blog/2009/10/21/i-do-not-like-the-trend-for-episerver-webconfig/#comment-3336 Spot on, great post and tips to EPiServer. This Web.Config maintenance hell will also be a bit easier with .NET 4 :) Spot on, great post and tips to EPiServer. This Web.Config maintenance hell will also be a bit easier with .NET 4 :)

]]>