<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Joni Hietala</title><link href="http://world.optimizely.com" /><updated>2018-05-27T09:12:20.0000000Z</updated><id>https://world.optimizely.com/blogs/joni-hietala/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Figuring out missing references (dlls)</title><link href="http://jonihietala.com/?p=292" /><id>We had a nasty little bug in one of our development stage Episerver projects. Everything ran and worked smoothly, but one day Episerver’s error logs started to report an exception regarding the Episerver.Find.Commerce module. However, the site seemed to work properly so the bug hunt could be scheduled to another day. Things escalated when Episerver &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2018/05/27/figuring-out-missing-references-dlls/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Figuring out missing references&amp;#160;(dlls)&lt;/span&gt;&lt;/a&gt;</id><updated>2018-05-27T09:12:20.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Figuring out missing references (dlls)</title><link href="http://jonihietala.com/?p=292" /><id>We had a nasty little bug in one of our development stage Episerver projects. Everything ran and worked smoothly, but one day Episerver’s error logs started to report an exception regarding the Episerver.Find.Commerce module. However, the site seemed to work properly so the bug hunt could be scheduled to another day. Things escalated when Episerver &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2018/05/27/figuring-out-missing-references-dlls/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Figuring out missing references&amp;#160;(dlls)&lt;/span&gt;&lt;/a&gt;</id><updated>2018-05-27T07:12:20.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Using Interfaces to get more compatible content elements in Episerver</title><link href="http://jonihietala.com/?p=231" /><id>Interfaces are more or less basic stuff in programming and in Episerver development. You probably have seen these guys (IThisAndThat, IEtc..) all over the reference solutions (AlloyDemoKit, Quicksilver, &amp;#8230;). In this blogpost, I’ll be taking a concrete approach how to make one of the AlloyDemoKit’s content blocks more compatible with other content elements using an &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2017/10/23/using-interfaces-to-get-more-compatible-content-elements-in-episerver/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Using Interfaces to get more compatible content elements in&amp;#160;Episerver&lt;/span&gt;&lt;/a&gt;&lt;img alt=&quot;&quot; border=&quot;0&quot; src=&quot;https://pixel.wp.com/b.gif?host=jonihietala.com&amp;#038;blog=135512771&amp;#038;post=231&amp;#038;subd=jonihietala&amp;#038;ref=&amp;#038;feed=1&quot; width=&quot;1&quot; height=&quot;1&quot; /&gt;</id><updated>2017-10-23T07:00:49.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Reviewing Episerver trainings: CMS Fundamentals and Commerce Online Bootcamp</title><link href="http://jonihietala.com/?p=156" /><id>I have had the privilege to participate in couple of Episerver’s trainings. Both for the CMS and for the Commerce. CMS training was a 3-day CMS fundamentals course and the Commerce was a 5-day online boot camp session. For those who are thinking about participating, and wondering will these trainings give you any useful insights, &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2017/10/16/reviewing-episerver-trainings-cms-fundamentals-and-commerce-online-bootcamp/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Reviewing Episerver trainings: CMS Fundamentals and Commerce Online&amp;#160;Bootcamp&lt;/span&gt;&lt;/a&gt;&lt;img alt=&quot;&quot; border=&quot;0&quot; src=&quot;https://pixel.wp.com/b.gif?host=jonihietala.com&amp;#038;blog=135512771&amp;#038;post=156&amp;#038;subd=jonihietala&amp;#038;ref=&amp;#038;feed=1&quot; width=&quot;1&quot; height=&quot;1&quot; /&gt;</id><updated>2017-10-16T07:00:46.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Testing your Episerver site performance with Netling</title><link href="http://jonihietala.com/?p=135" /><id>In the previous post, I wrote about profiling your Episerver site and how important it is to spot bugs and performance issues early on. Now it&amp;#8217;s time to create some traffic in your development environment and analyse how well your site performs under load. We will be using a free open source tool called Netling &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2017/10/09/testing-your-episerver-sites-performance-with-netling/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Testing your Episerver site performance with&amp;#160;Netling&lt;/span&gt;&lt;/a&gt;&lt;img alt=&quot;&quot; border=&quot;0&quot; src=&quot;https://pixel.wp.com/b.gif?host=jonihietala.com&amp;#038;blog=135512771&amp;#038;post=135&amp;#038;subd=jonihietala&amp;#038;ref=&amp;#038;feed=1&quot; width=&quot;1&quot; height=&quot;1&quot; /&gt;</id><updated>2017-10-09T07:00:54.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Smashing bugs from your Episerver site with Stackify Prefix profiler</title><link href="http://jonihietala.com/?p=108" /><id>We all know that bug happens. They are inevitable during development, and basically in every step-in software lifecycle. The thing that makes a difference, is to catch them as early as you can. You do not want to be in a situation where production site is suffering huge performance issues with only handful of requests. &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2017/10/02/smashing-bugs-from-your-episerver-site-with-stackify-prefix-profiler/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Smashing bugs from your Episerver site with Stackify Prefix&amp;#160;profiler&lt;/span&gt;&lt;/a&gt;&lt;img alt=&quot;&quot; border=&quot;0&quot; src=&quot;https://pixel.wp.com/b.gif?host=jonihietala.com&amp;#038;blog=135512771&amp;#038;post=108&amp;#038;subd=jonihietala&amp;#038;ref=&amp;#038;feed=1&quot; width=&quot;1&quot; height=&quot;1&quot; /&gt;</id><updated>2017-10-02T07:00:04.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Adding a “View on Website” -button to context menu in navigation tree</title><link href="http://jonihietala.com/?p=74" /><id>Ever had a problem where you would like to open or get the full public address of a page from the editor view in Episerver? Or is it a problem at all? So, we have a few ways to get the full public url: Navigating the site, if you have a navigation for those pages. &amp;#8230; &lt;a href=&quot;https://jonihietala.com/2017/09/25/adding-a-view-on-website-button-to-context-menu-in-navigation-tree/&quot; class=&quot;more-link&quot;&gt;Continue reading &lt;span class=&quot;screen-reader-text&quot;&gt;Adding a &amp;#8220;View on Website&amp;#8221; -button to context menu in navigation&amp;#160;tree&lt;/span&gt;&lt;/a&gt;&lt;img alt=&quot;&quot; border=&quot;0&quot; src=&quot;https://pixel.wp.com/b.gif?host=jonihietala.com&amp;#038;blog=135512771&amp;#038;post=74&amp;#038;subd=jonihietala&amp;#038;ref=&amp;#038;feed=1&quot; width=&quot;1&quot; height=&quot;1&quot; /&gt;</id><updated>2017-09-25T18:42:17.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>