<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Nimesh Manmohanlal</title><link href="http://world.optimizely.com" /><updated>2014-10-12T19:56:53.0000000Z</updated><id>https://world.optimizely.com/blogs/Nimesh-Manmohanlal/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Cross cutting concerns in EPiServer using Dynamic Proxies</title><link href="https://www.nimeshjm.com/?p=171" /><id>&lt;p&gt;Cross cutting concerns should be handled in an unobtrusive way, i.e. implemented in a way they don&amp;#8217;t require any modifications to your original features. One way to achieve this is by using Aspect Oriented Programming, more specifically using Castle Dynamic Proxies to intercept method calls at runtime with StructureMap. The code examples below were implemented [&amp;#8230;]&lt;/p&gt;
&lt;p&gt;The post &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com/cross-cutting-concerns-episerver-using-dynamic-proxies/&quot;&gt;Cross cutting concerns in EPiServer using Dynamic Proxies&lt;/a&gt; appeared first on &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com&quot;&gt;Random musings on technology&lt;/a&gt;.&lt;/p&gt;
</id><updated>2014-10-12T19:56:53.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Debug EPiServer Search (lucene)</title><link href="https://www.nimeshjm.com/?p=167" /><id>&lt;p&gt;A quick note to self: To debug the EPiServer Search indexing, the below should be added to EPiServerlog.config: [crayon-543ac7547844a039566255/] &amp;#160;&lt;/p&gt;
&lt;p&gt;The post &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com/debug-episerver-search-lucene/&quot;&gt;Debug EPiServer Search (lucene)&lt;/a&gt; appeared first on &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com&quot;&gt;Random musings on technology&lt;/a&gt;.&lt;/p&gt;
</id><updated>2014-09-03T19:50:04.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer workflows – emails not being sent</title><link href="https://www.nimeshjm.com/?p=159" /><id>&lt;p&gt;The most commonly used workflow in EPiServer is the Sequential approval workflow. It is primarily used to assign tasks and send notifications through the various stages of page publication. Troubleshooting workflows is no easy task. You typically have to enable Windows Workflow Foundation diagnostics and examine the logs. You can achieve this by adding the [&amp;#8230;]&lt;/p&gt;
&lt;p&gt;The post &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com/episerver-workflows-emails-not-being-sent/&quot;&gt;EPiServer workflows &amp;#8211; emails not being sent&lt;/a&gt; appeared first on &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com&quot;&gt;Random musings on technology&lt;/a&gt;.&lt;/p&gt;
</id><updated>2014-08-28T19:39:05.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer remote events troubleshooting</title><link href="http://www.nimeshjm.com/?p=36" /><id>&lt;p&gt;EPiserver uses WCF to send and receive events between servers configured in a multi-server setup (load-balanced or enterprise). A site in a server will send events (publisher) to one or many sites in other servers (subscriber). This is an example of an enterprise setup, with one publishing server and two public facing web servers. To [&amp;#8230;]&lt;/p&gt;
&lt;p&gt;The post &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com/episerver-remote-events-troubleshooting/&quot;&gt;EPiServer remote events troubleshooting&lt;/a&gt; appeared first on &lt;a rel=&quot;nofollow&quot; href=&quot;https://www.nimeshjm.com&quot;&gt;Random musings on technology&lt;/a&gt;.&lt;/p&gt;
</id><updated>2013-02-01T19:37:53.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>