<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Tommy Kihlstrøm</title><link href="https://world.optimizely.com/blogs/tommy-kihlstrom/" /><updated>2020-12-09T11:31:17.0000000Z</updated><id>https://world.optimizely.com/blogs/tommy-kihlstrom/</id><generator uri="https://world.optimizely.com/blogs/tommy-kihlstrom/" version="2.0">Optimizely World</generator><entry><title>Caching using decorator pattern in Episerver with StructureMap</title><link href="https://www.epinova.no/folg-med/blogg/2020/caching-using-decorator-pattern-in-episerver-with-structuremap/" /><id>https://www.epinova.no/folg-med/blogg/2020/caching-using-decorator-pattern-in-episerver-with-structuremap/</id><published>2020-12-08T10:27:06.0000000Z</published><updated>2020-12-09T11:31:17.0000000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">I see many developers mix caching into their business logic. They usually start by making their own CachingService. Sounds like you are trying to reinvent the wheel.</summary></entry><entry><title>Using config transforms for IIS Express site on multiple ports</title><link href="https://www.epinova.no/en/blog/using-config-transforms-for-iis-express-site-on-multiple-ports/" /><id>https://www.epinova.no/en/blog/using-config-transforms-for-iis-express-site-on-multiple-ports/</id><published>2019-08-27T10:49:12.0000000Z</published><updated>2019-08-27T11:03:02.0000000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">Manually configuring IIS for multiple hosts is time-consuming work. Here's how to use config transforms to speed up the task.</summary></entry><entry><title>Using config transforms for IIS Express site on multiple ports</title><link href="https://www.epinova.no/en/blog/using-config-transforms-for-iis-express-site-on-multiple-ports/" /><id>https://www.epinova.no/en/blog/using-config-transforms-for-iis-express-site-on-multiple-ports/</id><published>2019-08-27T08:49:12.0000000Z</published><updated>2020-04-03T07:01:30.0000000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">Manually configuring IIS for multiple hosts is time-consuming work. Here's how to use config transforms to speed up the task.</summary></entry><entry><title>Using config transforms for IIS Express site on multiple ports</title><link href="https://www.epinova.no/folg-med/blogg/2019/using-config-transforms-for-iis-express-site-on-multiple-ports/" /><id>https://www.epinova.no/folg-med/blogg/2019/using-config-transforms-for-iis-express-site-on-multiple-ports/</id><published>2019-08-27T08:40:55.0000000Z</published><updated>2020-12-09T11:31:17.0000000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">Manually configuring IIS for multiple hosts is time-consuming work. Here's how to use config transforms to speed up the task.</summary></entry><entry><title>Episerver + Apptus eSales DynamicPages</title><link href="http://streamlined.no/?p=340" /><id>http://streamlined.no/?p=340</id><published>2016-11-16T10:57:06.0000000Z</published><updated>2016-11-17T16:15:46.5300000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">&lt;p&gt;I just wanted to note down what I have done when integration Episerver CMS and Apptus eSales with DynamicPages. ESales relies on building zones with panels to return all data in a single response. As a close implementation Episerver CMS has blocks, blocks can contain custom logic and views depending on the locations the block is shown. &amp;#8230; &lt;a href="https://streamlined.no/2016/11/16/episerver-cms-apptus-esales-dynamicpages/" class="more-link"&gt;Continue reading&lt;span class="screen-reader-text"&gt; "Episerver + Apptus eSales DynamicPages"&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Innlegget &lt;a rel="nofollow" href="https://streamlined.no/2016/11/16/episerver-cms-apptus-esales-dynamicpages/"&gt;Episerver + Apptus eSales DynamicPages&lt;/a&gt; dukket først opp på &lt;a rel="nofollow" href="https://streamlined.no"&gt;Streamlined&lt;/a&gt;.&lt;/p&gt;
</summary></entry><entry><title>EpiServer CMS 9 + AutoMapper</title><link href="http://streamlined.no/?p=333" /><id>http://streamlined.no/?p=333</id><published>2016-11-10T10:54:36.0000000Z</published><updated>2016-11-17T16:15:46.7330000Z</updated><author><name>tommy.kihlstrom@epinova.no</name></author><category term="Blog post" /><summary type="html">&lt;p&gt;Here is a short example of how to properly setup AutoMapper 5.1 in EpiServer CMS 9 with dependency injection. Configuration Start by installing nuget package AutoMapper. Create a class &amp;#8220;AutoMapperConfig&amp;#8221; in the &amp;#8220;Infrastructure&amp;#8221;-folder. (Where Config files are located.) public static class AutoMapperConfig { public static IMapper CreateIMapper() { var mapperConfiguration = new MapperConfiguration(cfg =&amp;#62; cfg.AddProfiles(System.Reflection.Assembly.GetExecutingAssembly())); &amp;#8230; &lt;a href="https://streamlined.no/2016/11/10/episerver-cms-9-automapper/" class="more-link"&gt;Continue reading&lt;span class="screen-reader-text"&gt; "EpiServer CMS 9 + AutoMapper"&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Innlegget &lt;a rel="nofollow" href="https://streamlined.no/2016/11/10/episerver-cms-9-automapper/"&gt;EpiServer CMS 9 + AutoMapper&lt;/a&gt; dukket først opp på &lt;a rel="nofollow" href="https://streamlined.no"&gt;Streamlined&lt;/a&gt;.&lt;/p&gt;
</summary></entry></feed>