<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">akjoshi's Blog</title><subtitle type="html">Born with a black thinking hat</subtitle><id>http://weblogs.asp.net/akjoshi/atom.aspx</id><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/default.aspx" /><link rel="self" type="application/atom+xml" href="http://weblogs.asp.net/akjoshi/atom.aspx" /><generator uri="http://communityserver.org" version="3.0.20510.895">Community Server</generator><updated>2011-11-30T18:31:00Z</updated><entry><title>Agent Smith for Resharper</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2013/04/04/agent-smith-for-resharper.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2013/04/04/agent-smith-for-resharper.aspx</id><published>2013-04-04T04:45:00Z</published><updated>2013-04-04T04:45:00Z</updated><content type="html">Recently I started using a plug-in for&amp;#160; ReSharper: Agent Smith . Although its pretty old tool but somehow there was no solid requirement for using it, so I never tried it. It looks very powerful and useful tool; for the start we are majorly using it’s spell checker feature; one major benefit of using it instead of other spell checkers is that it is compatible with the ReSharper Settings Manager and thus sharing ignored words across team becomes easier. Another benefit is that we can easily control...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2013/04/04/agent-smith-for-resharper.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=10092592" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="Visual Studio" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Visual+Studio/default.aspx" /><category term="General Software Development" scheme="http://weblogs.asp.net/akjoshi/archive/tags/General+Software+Development/default.aspx" /><category term="Resharper" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Resharper/default.aspx" /></entry><entry><title>Focus management Tips &amp; Tricks for nested ListView's part 1</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2013/01/15/focus-management-tips-amp-tricks-for-nested-listviews-part-1.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2013/01/15/focus-management-tips-amp-tricks-for-nested-listviews-part-1.aspx</id><published>2013-01-15T06:28:00Z</published><updated>2013-01-15T06:28:00Z</updated><content type="html">Hi, as every WPF developer would agree with me that handling focus in WPF is a nightmare and every now and then you come across scenarios which makes you pull your hair I recently came across one(more) such scenario and it was a tough task to make focus work properly, I think it will be useful to blog about my experience and solutions I have implemented, so here is the first and easiest part of this series. Scenario : I had a control which consists of nested ListView’s i.e. a parent ListView which...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2013/01/15/focus-management-tips-amp-tricks-for-nested-listviews-part-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=9735070" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Effect of Coffee on our ability to code</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2013/01/15/effect-of-coffee-on-our-ability-to-code.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2013/01/15/effect-of-coffee-on-our-ability-to-code.aspx</id><published>2013-01-15T06:07:00Z</published><updated>2013-01-15T06:07:00Z</updated><content type="html">I hope the effect of coffee is not same on our ability to code In 1995 a group of NASA scientists repeated and refined some earlier tests on the effect that various drugs have on the web building abilities of the common garden spider. They tested the effect of caffeine, benzedrine, marijuana and chloral hydrate and as you can see the results were pretty extreme! Noever, R., J. Cronise, and R. A. Relwani. 1995. Using spider-web patterns to determine toxicity. NASA Tech Briefs 19(4):82. http://en.wikipedia...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2013/01/15/effect-of-coffee-on-our-ability-to-code.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=9753846" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="Off Topic" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Off+Topic/default.aspx" /></entry><entry><title>Finding last visual parent in VisualTree</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2013/01/11/finding-last-visual-parent-in-visualtree.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2013/01/11/finding-last-visual-parent-in-visualtree.aspx</id><published>2013-01-11T06:45:00Z</published><updated>2013-01-11T06:45:00Z</updated><content type="html">Recently I had a requirement where I needed to find the last parent of a particular type in VisualTree. You can easily find an implementation to find the parent but was not able to find one for finding the top most parent of a given type. So I modified the current implementation to get the last parent of a given type in the hierarchy, which was not tough at all. This method is useful when you can have multiple parents of same type in hierarchy and you need to find the top most parent of type T, e...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2013/01/11/finding-last-visual-parent-in-visualtree.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=9734985" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Excel cell behavior for WPF TextBox</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/12/27/Excel-cell-behavior-for-wpf-textbox.aspx" /><link rel="enclosure" type="text/plain" length="6306" href="http://weblogs.asp.net/akjoshi/attachment/9660457.ashx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/12/27/Excel-cell-behavior-for-wpf-textbox.aspx</id><published>2012-12-27T08:16:00Z</published><updated>2012-12-27T08:16:00Z</updated><content type="html">Excel cells have a very special and useful behavior that they become editable as soon as it gets selected but it doesn't changes its visual appearance i.e. caret doesn't becomes visible. User can start typing into it or use Enter or Arrow keys to move around, caret becomes visible as soon as user starts typing into it. Let's implement this behavior for WPF TextBox....(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/12/27/Excel-cell-behavior-for-wpf-textbox.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=9660457" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Resolving harmless binding errors in WPF II : 2 approaches for removing data binding errors due to heterogeneous types in a hierarchical view</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/12/18/resolving-harmless-binding-errors-in-wpf-ii-2-approaches-for-removing-data-binding-errors-due-to-heterogeneous-types-in-a-hierarchical-view.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/12/18/resolving-harmless-binding-errors-in-wpf-ii-2-approaches-for-removing-data-binding-errors-due-to-heterogeneous-types-in-a-hierarchical-view.aspx</id><published>2012-12-18T12:20:00Z</published><updated>2012-12-18T12:20:00Z</updated><content type="html">This is a continuation post to my previous post Resolving harmless binding errors in WPF in which I talked about various ways of&amp;#160; resolving different binding errors etc. I recently came across another situation in which we get these binding errors and how they can be resolved. Problem: If you have a tree with 2 types of items in it and you use different DataTypes for each of them, then you will get binding errors because of missing Properties in either one of the item. In our case we had binding...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/12/18/resolving-harmless-binding-errors-in-wpf-ii-2-approaches-for-removing-data-binding-errors-due-to-heterogeneous-types-in-a-hierarchical-view.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=9607160" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Making animations work for disabled controls</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/06/13/Making-Animations-work-for-disabled-control.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/06/13/Making-Animations-work-for-disabled-control.aspx</id><published>2012-06-13T11:24:00Z</published><updated>2012-06-13T11:24:00Z</updated><content type="html">Some animations don't work if control on which animation is applied is disabled, this post explains a workaround to make animations work on disabled controls. ...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/06/13/Making-Animations-work-for-disabled-control.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8603175" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Outrageous Work Conditions for a Developer analyst</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/06/07/outrageous-work-conditions-for-a-developer-analyst.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/06/07/outrageous-work-conditions-for-a-developer-analyst.aspx</id><published>2012-06-07T11:57:00Z</published><updated>2012-06-07T11:57:00Z</updated><content type="html">Recently came across a job opening sent to me by a HR person on LinkedIn; The service based company is a very big name in IT but the work conditions mentioned in the job description were extremely unusual - I mean who the hell would like to apply for a job where a company wants you to be ready for lifting and transporting of computers, that too on top of extended work hours and weekends. I used to think that JD’s are supposed to encourage candidates to join the company but this one here looks totally...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/06/07/outrageous-work-conditions-for-a-developer-analyst.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8580444" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="General Software Development" scheme="http://weblogs.asp.net/akjoshi/archive/tags/General+Software+Development/default.aspx" /><category term="Personal" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Personal/default.aspx" /></entry><entry><title>Attached Behavior for auto scrolling containers while doing Drag &amp; Drop</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/05/28/Attached-behavior-for-auto-scrolling-containers-while-doing-drag-amp-drop.aspx" /><link rel="enclosure" type="text/plain" length="10351" href="http://weblogs.asp.net/akjoshi/attachment/8543429.ashx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/05/28/Attached-behavior-for-auto-scrolling-containers-while-doing-drag-amp-drop.aspx</id><published>2012-05-28T07:31:00Z</published><updated>2012-05-28T07:31:00Z</updated><content type="html">This is a very common problem in WPF, if you support Drag &amp; Drop within your Items control or across the controls like ListView, TreeView etc. and your List contains hundreds of items then it’s very hard to drag an item at the bottom to the top......(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/05/28/Attached-behavior-for-auto-scrolling-containers-while-doing-drag-amp-drop.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8543429" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Working on WPF application Memory Profiling</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/04/09/working-on-wpf-application-memory-profiling.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/04/09/working-on-wpf-application-memory-profiling.aspx</id><published>2012-04-09T08:51:00Z</published><updated>2012-04-09T08:51:00Z</updated><content type="html">Today, I am going to start with the task of memory profiling the WPF application, on which I am working from past few months. I have successfully done this in past, fixing a lot of memory leaks and improving the performance of WPF applications; As in past, I am hopeful of fixing some very interesting bugs and improve the application performance. I am very excited as current application is very different from the previous WPF applications I had profiled, all the previous application were pure WPF...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/04/09/working-on-wpf-application-memory-profiling.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8381780" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="Profiling" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Profiling/default.aspx" /><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /></entry><entry><title>WPF DataGrid Customization: Resizing Row/Column through DataGridCell gridlines</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/03/28/wpf-datagrid-customization-resizing-row-column-through-datagridcell-gridlines.aspx" /><link rel="enclosure" type="application/x-zip-compressed" length="221130" href="http://weblogs.asp.net/akjoshi/attachment/8367425.ashx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/03/28/wpf-datagrid-customization-resizing-row-column-through-datagridcell-gridlines.aspx</id><published>2012-03-28T08:52:00Z</published><updated>2012-03-28T08:52:00Z</updated><content type="html">In this post I am going to share my experience on how I achieved the functionality to resize DataGrid row/column from any cell in that row (not just the row header). We needed this functionality as our user can hide the DataGrid headers and it is not possible to resize the rows/columns after that....(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/03/28/wpf-datagrid-customization-resizing-row-column-through-datagridcell-gridlines.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8367425" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /><category term="WPFDataGrid" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPFDataGrid/default.aspx" /><category term=".Net" scheme="http://weblogs.asp.net/akjoshi/archive/tags/.Net/default.aspx" /></entry><entry><title>Importance of specifying AncestorType with x:Type in RelativeSourceBinding</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/02/03/importance-of-specifying-ancestortype-with-x-type-in-relativesourcebinding.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/02/03/importance-of-specifying-ancestortype-with-x-type-in-relativesourcebinding.aspx</id><published>2012-02-03T08:26:00Z</published><updated>2012-02-03T08:26:00Z</updated><content type="html">I am really very happy right now, for the past 4 days me and my team were trying to solve a very trivial bug in our application and finally it got resolved by just adding x:Type in our RelativeSource bindings; Can you believe this, a production issue getting resolved just by this simple change, I couldn’t; so I tested this fix at least ten times to believe it Just to give you a background, I am working on developing components for a very large scale financial product having plug-in architecture and...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/02/03/importance-of-specifying-ancestortype-with-x-type-in-relativesourcebinding.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8279109" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /></entry><entry><title>Getting rid of heavy Multivalue Converters : My Encounter with Win Form style WPF apps 2</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/01/15/getting-rid-of-heavy-multivalue-converters-my-encounter-with-win-form-style-wpf-apps-2.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/01/15/getting-rid-of-heavy-multivalue-converters-my-encounter-with-win-form-style-wpf-apps-2.aspx</id><published>2012-01-15T14:46:00Z</published><updated>2012-01-15T14:46:00Z</updated><content type="html">I recently came across the situation where I had to refactor the WPF code written in Win Forms Style ; Code was having a lot of MultiValueConverters used for building the DataContext / ItemSources for Controls/ ListVies/ DataGrids etc. Following is the example of one of the converters I am talking about: &amp;#160; &amp;lt; ListView.ItemsSource &amp;gt; &amp;lt; MultiBinding Converter =&amp;quot;{StaticResource ItemsSourceInsertConverter}&amp;quot; &amp;gt; &amp;lt; Binding ElementName =&amp;quot;EditorControl&amp;quot; Path =&amp;quot;EditorControl...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/01/15/getting-rid-of-heavy-multivalue-converters-my-encounter-with-win-form-style-wpf-apps-2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8258439" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="Converters" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Converters/default.aspx" /><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /></entry><entry><title>Creating custom filters in Resharper To-do Explorer</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2012/01/04/creating-custom-filters-in-resharper-to-do-explorer.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2012/01/04/creating-custom-filters-in-resharper-to-do-explorer.aspx</id><published>2012-01-04T09:06:00Z</published><updated>2012-01-04T09:06:00Z</updated><content type="html">We can create a custom filter in Resharper To-Do explorer to filter out all the to-do items created by a specific person or with a particular string literal. This is very useful in case you are working in a big team and have habit to add To-do comments. Here are the steps to create a new filter with a specific string - Step 1 : Go to Resharper –&amp;gt; Options -&amp;gt; Tools -&amp;gt; To-do Items Step 2 : Create a new Pattern, enter title and the regular expression for strings you want to search – Step 3 ...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2012/01/04/creating-custom-filters-in-resharper-to-do-explorer.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8219334" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="Visual Studio" scheme="http://weblogs.asp.net/akjoshi/archive/tags/Visual+Studio/default.aspx" /><category term="General Software Development" scheme="http://weblogs.asp.net/akjoshi/archive/tags/General+Software+Development/default.aspx" /></entry><entry><title>Resolving harmless binding errors in WPF</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/akjoshi/archive/2011/11/30/resolving-un-harmful-binding-errors-in-wpf.aspx" /><id>http://weblogs.asp.net/akjoshi/archive/2011/11/30/resolving-un-harmful-binding-errors-in-wpf.aspx</id><published>2011-11-30T13:31:00Z</published><updated>2011-11-30T13:31:00Z</updated><content type="html">While developing WPF applications, you will notice a lot of binding errors being displayed in output window. I also faced this problem and tried a lot of things to get to the root cause of the problem. It was very frustrating as AncestorLevel is not used anywhere in code! and I was not able to find the place in code which is responsible for these errors.

Even after searching the various forums and articles there was no solution for this problem; but this was a very common issue and cause of this problem mentioned here, here and here is:
...(&lt;a href="http://weblogs.asp.net/akjoshi/archive/2011/11/30/resolving-un-harmful-binding-errors-in-wpf.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=8082169" width="1" height="1"&gt;</content><author><name>akjoshi</name><uri>http://weblogs.asp.net/members/akjoshi.aspx</uri></author><category term="WPF" scheme="http://weblogs.asp.net/akjoshi/archive/tags/WPF/default.aspx" /></entry></feed>