<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for 42</title>
	<atom:link href="http://buksbaum.us/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://buksbaum.us</link>
	<description>Random thoughts filtered through a babelfish.</description>
	<lastBuildDate>Fri, 11 May 2012 15:39:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on How To Do Logging with Caliburn.Micro by Apurva</title>
		<link>http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/comment-page-1/#comment-2366</link>
		<dc:creator>Apurva</dc:creator>
		<pubDate>Fri, 11 May 2012 15:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/#comment-2366</guid>
		<description>I am trying to log unhandled exceptions in my bootstrapper...and I use this code to get Logger...

ILog _log=LogManager.GetLog(typeof(StructureMapBootStrapper));

But I always get nulllogger back and so I cant log any unhandled exceptions. Any help is highly appreciated!!!
Thanks</description>
		<content:encoded><![CDATA[<p>I am trying to log unhandled exceptions in my bootstrapper&#8230;and I use this code to get Logger&#8230;</p>
<p>ILog _log=LogManager.GetLog(typeof(StructureMapBootStrapper));</p>
<p>But I always get nulllogger back and so I cant log any unhandled exceptions. Any help is highly appreciated!!!<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Logging.log4net by Apurva</title>
		<link>http://buksbaum.us/2011/07/06/introducing-caliburn-micro-logging-log4net/comment-page-1/#comment-2364</link>
		<dc:creator>Apurva</dc:creator>
		<pubDate>Thu, 10 May 2012 16:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/07/06/introducing-caliburn-micro-logging-log4net/#comment-2364</guid>
		<description>Hello,

I am using your package to integrate log4net with Caliburn Micro in my WPF Application. I do have a few questions on using this package-

1) So I assume that with this new package, I dont need to create Log4netLogger class as shown in your sample? Please correct me if I am wrong.

2) How do I use this logger in my bootstrapper? I am trying to write unhandled exceptions to log in my bootstrapper.

3) I noticed that this logging seems to work fine only on my machine. But when I deploy this application, I dont see any logs getting created. Is there any configuration step I should be taking care of?

Appreciate your help!
Apurva</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I am using your package to integrate log4net with Caliburn Micro in my WPF Application. I do have a few questions on using this package-</p>
<p>1) So I assume that with this new package, I dont need to create Log4netLogger class as shown in your sample? Please correct me if I am wrong.</p>
<p>2) How do I use this logger in my bootstrapper? I am trying to write unhandled exceptions to log in my bootstrapper.</p>
<p>3) I noticed that this logging seems to work fine only on my machine. But when I deploy this application, I dont see any logs getting created. Is there any configuration step I should be taking care of?</p>
<p>Appreciate your help!<br />
Apurva</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Logging by Jaans</title>
		<link>http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/comment-page-1/#comment-2281</link>
		<dc:creator>Jaans</dc:creator>
		<pubDate>Fri, 09 Mar 2012 04:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/#comment-2281</guid>
		<description>Thanks for the efforts and the logger.

Can you please update it for SL5 and create an updated logger NuGet package for it?

Thanks</description>
		<content:encoded><![CDATA[<p>Thanks for the efforts and the logger.</p>
<p>Can you please update it for SL5 and create an updated logger NuGet package for it?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gentle Introduction to MEF&#8211;Part Three by Sambhaji</title>
		<link>http://buksbaum.us/2011/11/21/gentle-introduction-to-mefpart-three/comment-page-1/#comment-2279</link>
		<dc:creator>Sambhaji</dc:creator>
		<pubDate>Sat, 03 Mar 2012 14:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/11/21/gentle-introduction-to-mefpart-three/#comment-2279</guid>
		<description>I am facing one issue. Why RealMEF Project (which contains UI) does not build without following line..

using System.ComponentModel.Composition;

It gives error following error if we do not use above namespace.

Argument 1: cannot convert from &#039;TranformationEngine&#039; to &#039;System.ComponentModel.Composition.Primitives.ComposablePart&#039;

But same code works if we use this namespace. I dont know the reason. Maybe I am missing something here..</description>
		<content:encoded><![CDATA[<p>I am facing one issue. Why RealMEF Project (which contains UI) does not build without following line..</p>
<p>using System.ComponentModel.Composition;</p>
<p>It gives error following error if we do not use above namespace.</p>
<p>Argument 1: cannot convert from &#8216;TranformationEngine&#8217; to &#8216;System.ComponentModel.Composition.Primitives.ComposablePart&#8217;</p>
<p>But same code works if we use this namespace. I dont know the reason. Maybe I am missing something here..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gentle Introduction to MEF&#8211;Part One by Gentle Introduction to MEF&#8211;Part Three &#124; 42</title>
		<link>http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/comment-page-1/#comment-1942</link>
		<dc:creator>Gentle Introduction to MEF&#8211;Part Three &#124; 42</dc:creator>
		<pubDate>Mon, 21 Nov 2011 23:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/#comment-1942</guid>
		<description>[...] project modified over three steps. This is Part Three, where I complete the application created in Part One and modified to use MEF in Part Two. This part will show MEF composing the application from [...]</description>
		<content:encoded><![CDATA[<p>[...] project modified over three steps. This is Part Three, where I complete the application created in Part One and modified to use MEF in Part Two. This part will show MEF composing the application from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To Do Logging with Caliburn.Micro by Caliburn Micro with NLog &#8211; how to use logger and log to XML file</title>
		<link>http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/comment-page-1/#comment-1824</link>
		<dc:creator>Caliburn Micro with NLog &#8211; how to use logger and log to XML file</dc:creator>
		<pubDate>Sun, 23 Oct 2011 08:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/#comment-1824</guid>
		<description>[...] Hi i try use Nlog in with caliburn micro, I have use this tutorial http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/. [...]</description>
		<content:encoded><![CDATA[<p>[...] Hi i try use Nlog in with caliburn micro, I have use this tutorial <a href="http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/" rel="nofollow">http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Shirl</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1769</link>
		<dc:creator>Shirl</dc:creator>
		<pubDate>Tue, 27 Sep 2011 05:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1769</guid>
		<description>In the complicated world we live in, it&#039;s good to find simple soluiotns.</description>
		<content:encoded><![CDATA[<p>In the complicated world we live in, it&#8217;s good to find simple soluiotns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1752</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1752</guid>
		<description>Raised as Issue # 2 (https://github.com/dbuksbaum/unity.extensions/issues/2)</description>
		<content:encoded><![CDATA[<p>Raised as Issue # 2 (<a href="https://github.com/dbuksbaum/unity.extensions/issues/2" rel="nofollow">https://github.com/dbuksbaum/unity.extensions/issues/2</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1751</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1751</guid>
		<description>Raised as Issue # 1 (https://github.com/dbuksbaum/unity.extensions/issues/1)</description>
		<content:encoded><![CDATA[<p>Raised as Issue # 1 (<a href="https://github.com/dbuksbaum/unity.extensions/issues/1" rel="nofollow">https://github.com/dbuksbaum/unity.extensions/issues/1</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1750</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1750</guid>
		<description>Looks like some errors in the formatting of the documentation. Thanks for the catch, I will try and reproduce.</description>
		<content:encoded><![CDATA[<p>Looks like some errors in the formatting of the documentation. Thanks for the catch, I will try and reproduce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1749</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1749</guid>
		<description>Thanks Allen. I will see if I can create a test case to reproduce.</description>
		<content:encoded><![CDATA[<p>Thanks Allen. I will see if I can create a test case to reproduce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1748</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Fri, 23 Sep 2011 15:50:25 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1748</guid>
		<description>On another note, is there some way to get rid of these compiler warnings?  

BTW: For my own reasons, I have put your extensions into my Helpers namespace but otherwise this is the same UnityExtensions.cs and TypeTrackingExtensions.cs.  If you are not comfortable with that I will go change the namespace references throughout.

Helpers\TypeTrackingExtension.cs(52,66): warning CS1570: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension&#039; has badly formed XML -- &#039;A name contained an invalid character.&#039;
Helpers\TypeTrackingExtension.cs(65,33): warning CS1591: Missing XML comment for publicly visible type or member &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.Initialize()&#039;
Helpers\TypeTrackingExtension.cs(71,30): warning CS1591: Missing XML comment for publicly visible type or member &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.Remove()&#039;
Helpers\TypeTrackingExtension.cs(103,30): warning CS0168: The variable &#039;ex&#039; is declared but never used
Helpers\TypeTrackingExtension.cs(131,30): warning CS0168: The variable &#039;ex&#039; is declared but never used
Helpers\TypeTrackingExtension.cs(208,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve()&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(219,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(230,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(T)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(230,89): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(T)&#039; has cref attribute &#039;defaultValue&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(244,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string, T)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(244,89): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string, T)&#039; has cref attribute &#039;defaultValue&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(260,35): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.ResolveAll()&#039; has cref attribute &#039;IEnumerable&#039; that could not be resolved
Helpers\TypeTrackingExtension.cs(273,35): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.ResolveAll(bool)&#039; has cref attribute &#039;IEnumerable&#039; that could not be resolved
Helpers\UnityExtensions.cs(102,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\UnityExtensions.cs(114,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\UnityExtensions.cs(126,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, T)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\UnityExtensions.cs(126,89): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, T)&#039; has cref attribute &#039;defaultValue&#039; that could not be resolved
Helpers\UnityExtensions.cs(139,53): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string, T)&#039; has cref attribute &#039;T&#039; that could not be resolved
Helpers\UnityExtensions.cs(139,89): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string, T)&#039; has cref attribute &#039;defaultValue&#039; that could not be resolved
Helpers\UnityExtensions.cs(154,35): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.ResolveAllToEnumerable(Microsoft.Practices.Unity.IUnityContainer)&#039; has cref attribute &#039;IEnumerable&#039; that could not be resolved
Helpers\UnityExtensions.cs(168,35): warning CS1574: XML comment on &#039;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.ResolveAllToEnumerable(Microsoft.Practices.Unity.IUnityContainer, bool)&#039; has cref attribute &#039;IEnumerable&#039; that could not be resolved</description>
		<content:encoded><![CDATA[<p>On another note, is there some way to get rid of these compiler warnings?  </p>
<p>BTW: For my own reasons, I have put your extensions into my Helpers namespace but otherwise this is the same UnityExtensions.cs and TypeTrackingExtensions.cs.  If you are not comfortable with that I will go change the namespace references throughout.</p>
<p>Helpers\TypeTrackingExtension.cs(52,66): warning CS1570: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension&#8217; has badly formed XML &#8212; &#8216;A name contained an invalid character.&#8217;<br />
Helpers\TypeTrackingExtension.cs(65,33): warning CS1591: Missing XML comment for publicly visible type or member &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.Initialize()&#8217;<br />
Helpers\TypeTrackingExtension.cs(71,30): warning CS1591: Missing XML comment for publicly visible type or member &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.Remove()&#8217;<br />
Helpers\TypeTrackingExtension.cs(103,30): warning CS0168: The variable &#8216;ex&#8217; is declared but never used<br />
Helpers\TypeTrackingExtension.cs(131,30): warning CS0168: The variable &#8216;ex&#8217; is declared but never used<br />
Helpers\TypeTrackingExtension.cs(208,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve()&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(219,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(230,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(T)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(230,89): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(T)&#8217; has cref attribute &#8216;defaultValue&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(244,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string, T)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(244,89): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.TryResolve(string, T)&#8217; has cref attribute &#8216;defaultValue&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(260,35): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.ResolveAll()&#8217; has cref attribute &#8216;IEnumerable&#8217; that could not be resolved<br />
Helpers\TypeTrackingExtension.cs(273,35): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.TypeTrackingExtension.ResolveAll(bool)&#8217; has cref attribute &#8216;IEnumerable&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(102,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(114,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(126,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, T)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(126,89): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, T)&#8217; has cref attribute &#8216;defaultValue&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(139,53): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string, T)&#8217; has cref attribute &#8216;T&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(139,89): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.TryResolve(Microsoft.Practices.Unity.IUnityContainer, string, T)&#8217; has cref attribute &#8216;defaultValue&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(154,35): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.ResolveAllToEnumerable(Microsoft.Practices.Unity.IUnityContainer)&#8217; has cref attribute &#8216;IEnumerable&#8217; that could not be resolved<br />
Helpers\UnityExtensions.cs(168,35): warning CS1574: XML comment on &#8216;AASHTO.ElementMigration.VisualElementMigrator.Helpers.UnityExtensions.ResolveAllToEnumerable(Microsoft.Practices.Unity.IUnityContainer, bool)&#8217; has cref attribute &#8216;IEnumerable&#8217; that could not be resolved</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1747</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Fri, 23 Sep 2011 15:24:38 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1747</guid>
		<description>Once again I have failed to get the arguments to show up.  

RegisterType( &lt;T&gt;,&lt;T&gt; )</description>
		<content:encoded><![CDATA[<p>Once again I have failed to get the arguments to show up.  </p>
<p>RegisterType( &lt;T&gt;,&lt;T&gt; )</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1746</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Fri, 23 Sep 2011 15:21:37 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1746</guid>
		<description>So I see that I failed to send you an example to test with.  My bad.  Somewhere in my calling code I was passing a null for the type to the RegisterType() of Unity, which will raise an ArgumentNullException.  So I am trapping it in this extension handler in order to not blow up with no message. Since all my code is now much more mature it is difficult to determine where I made this mistake anymore, but if you create a test passing null to one of the Unity RegisterType calls it will raise the ArgumentNullException here and then all is not well....


&lt;code&gt;
 private void OnNewType(object sender, RegisterEventArgs e)
    {
      HashSet names;
      string name = string.IsNullOrEmpty(e.Name) ? string.Empty : e.Name;
      if (e.TypeFrom == null)
          throw new ArgumentNullException(&quot;The TypeFrom argument cannot be null – use .RegisterType(,); instead of …RegisterType(); to avoid this error&quot;);
     
      if (!_registeredTypes.TryGetValue(e.TypeFrom, out names))
      { //  not found, so add it
        _registeredTypes.Add(e.TypeFrom, new HashSet(new string[] { name }));
      }
      else
      { //  already added type, so add name
        names.Add(name);
      }
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>So I see that I failed to send you an example to test with.  My bad.  Somewhere in my calling code I was passing a null for the type to the RegisterType() of Unity, which will raise an ArgumentNullException.  So I am trapping it in this extension handler in order to not blow up with no message. Since all my code is now much more mature it is difficult to determine where I made this mistake anymore, but if you create a test passing null to one of the Unity RegisterType calls it will raise the ArgumentNullException here and then all is not well&#8230;.</p>
<p><code><br />
 private void OnNewType(object sender, RegisterEventArgs e)<br />
    {<br />
      HashSet names;<br />
      string name = string.IsNullOrEmpty(e.Name) ? string.Empty : e.Name;<br />
      if (e.TypeFrom == null)<br />
          throw new ArgumentNullException("The TypeFrom argument cannot be null – use .RegisterType(,); instead of …RegisterType(); to avoid this error");</p>
<p>      if (!_registeredTypes.TryGetValue(e.TypeFrom, out names))<br />
      { //  not found, so add it<br />
        _registeredTypes.Add(e.TypeFrom, new HashSet(new string[] { name }));<br />
      }<br />
      else<br />
      { //  already added type, so add name<br />
        names.Add(name);<br />
      }<br />
</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gentle Introduction to MEF&#8211;Part One by Tampa# Sixth Meeting &#8211; Async &#38; MEF &#124; Tampa#</title>
		<link>http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/comment-page-1/#comment-1700</link>
		<dc:creator>Tampa# Sixth Meeting &#8211; Async &#38; MEF &#124; Tampa#</dc:creator>
		<pubDate>Fri, 26 Aug 2011 18:37:09 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/#comment-1700</guid>
		<description>[...] http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/" rel="nofollow">http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Autofac by tracstarr</title>
		<link>http://buksbaum.us/2011/06/12/introducing-caliburn-micro-autofac/comment-page-1/#comment-1698</link>
		<dc:creator>tracstarr</dc:creator>
		<pubDate>Fri, 26 Aug 2011 00:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=367#comment-1698</guid>
		<description>I&#039;ve been using your implementation of the bootstrapper for a while now. However, I&#039;ve just found an issue when trying to use Bind.Model in xaml. The Caliburn.Micro.Bind.ModelChanged function will call IoC.GetInstance(null, key), which is not handled in the bootstrapper getinstance method. I&#039;m not yet sure how to fix this myself, i&#039;ve just discovered it.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using your implementation of the bootstrapper for a while now. However, I&#8217;ve just found an issue when trying to use Bind.Model in xaml. The Caliburn.Micro.Bind.ModelChanged function will call IoC.GetInstance(null, key), which is not handled in the bootstrapper getinstance method. I&#8217;m not yet sure how to fix this myself, i&#8217;ve just discovered it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by david</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1697</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 25 Aug 2011 12:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1697</guid>
		<description>Ok. I dislike exposing externals, so I will try and come up with another way to do deal with this. I have created an issue to track this at https://github.com/dbuksbaum/Caliburn.Micro.Autofac/issues/1</description>
		<content:encoded><![CDATA[<p>Ok. I dislike exposing externals, so I will try and come up with another way to do deal with this. I have created an issue to track this at <a href="https://github.com/dbuksbaum/Caliburn.Micro.Autofac/issues/1" rel="nofollow">https://github.com/dbuksbaum/Caliburn.Micro.Autofac/issues/1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by tracstarr</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1696</link>
		<dc:creator>tracstarr</dc:creator>
		<pubDate>Thu, 25 Aug 2011 11:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1696</guid>
		<description>Well, in my case it&#039;s for accessing my data layer services. I use the lifetimescope in this way to make sure I don&#039;t have a constant open connection and instances of service classes open.

What I&#039;ve done since this post was to expose the container property as public, and then in the GetInstance i added:

if (serviceType == this.GetType()) return this

That allows me to use IoC.Get().Container.BeginLifetimeScope

It&#039;s the only thing i&#039;ve come up with so far.</description>
		<content:encoded><![CDATA[<p>Well, in my case it&#8217;s for accessing my data layer services. I use the lifetimescope in this way to make sure I don&#8217;t have a constant open connection and instances of service classes open.</p>
<p>What I&#8217;ve done since this post was to expose the container property as public, and then in the GetInstance i added:</p>
<p>if (serviceType == this.GetType()) return this</p>
<p>That allows me to use IoC.Get().Container.BeginLifetimeScope</p>
<p>It&#8217;s the only thing i&#8217;ve come up with so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by david</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1695</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 25 Aug 2011 02:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1695</guid>
		<description>Good question. I don&#039;t have an answer yet, but I will give it some thought. Can you provide a use case for this?</description>
		<content:encoded><![CDATA[<p>Good question. I don&#8217;t have an answer yet, but I will give it some thought. Can you provide a use case for this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by tracstarr</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1694</link>
		<dc:creator>tracstarr</dc:creator>
		<pubDate>Thu, 25 Aug 2011 01:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1694</guid>
		<description>What about when I need to use specific lifetimescope within a using from a viewmodel? How can I do this without exposing the container? Or will I just have to?

using (var scope = Container.BeginLifetimeScope(&quot;Commit&quot;))
{
   ....
}</description>
		<content:encoded><![CDATA[<p>What about when I need to use specific lifetimescope within a using from a viewmodel? How can I do this without exposing the container? Or will I just have to?</p>
<p>using (var scope = Container.BeginLifetimeScope(&#8220;Commit&#8221;))<br />
{<br />
   &#8230;.<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gentle Introduction to MEF&#8211;Part One by Gentle Introduction to MEF&#8211;Part Two &#124; 42</title>
		<link>http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/comment-page-1/#comment-1691</link>
		<dc:creator>Gentle Introduction to MEF&#8211;Part Two &#124; 42</dc:creator>
		<pubDate>Mon, 22 Aug 2011 16:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/08/20/gentle-introduction-to-mefpart-one/#comment-1691</guid>
		<description>[...] same project modified over three steps. This is Part Two, where I show the application created in Part One using [...]</description>
		<content:encoded><![CDATA[<p>[...] same project modified over three steps. This is Part Two, where I show the application created in Part One using [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Code Contracts for Safer Code by -= Perlis Languages =-</title>
		<link>http://buksbaum.us/2011/04/20/using-code-contracts-for-safer-code/comment-page-1/#comment-1672</link>
		<dc:creator>-= Perlis Languages =-</dc:creator>
		<pubDate>Sun, 14 Aug 2011 15:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=239#comment-1672</guid>
		<description>[...] Using code contracts for safer code [...]</description>
		<content:encoded><![CDATA[<p>[...] Using code contracts for safer code [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Logging by Caliburn.Micro.Logging for NLog and log4net Updated &#124; 42</title>
		<link>http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/comment-page-1/#comment-1669</link>
		<dc:creator>Caliburn.Micro.Logging for NLog and log4net Updated &#124; 42</dc:creator>
		<pubDate>Fri, 12 Aug 2011 19:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/#comment-1669</guid>
		<description>[...] Introducing Caliburn.Micro.Logging [...]</description>
		<content:encoded><![CDATA[<p>[...] Introducing Caliburn.Micro.Logging [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Autofac by Caliburn.Micro.Autofac 1.2.1 Released &#124; 42</title>
		<link>http://buksbaum.us/2011/06/12/introducing-caliburn-micro-autofac/comment-page-1/#comment-1668</link>
		<dc:creator>Caliburn.Micro.Autofac 1.2.1 Released &#124; 42</dc:creator>
		<pubDate>Fri, 12 Aug 2011 01:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=367#comment-1668</guid>
		<description>[...] see Introducing Caliburn.Micro.Autofac for [...]</description>
		<content:encoded><![CDATA[<p>[...] see Introducing Caliburn.Micro.Autofac for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Autofac by Caliburn.Micro.Autofac 1.2 Released &#124; 42</title>
		<link>http://buksbaum.us/2011/06/12/introducing-caliburn-micro-autofac/comment-page-1/#comment-1666</link>
		<dc:creator>Caliburn.Micro.Autofac 1.2 Released &#124; 42</dc:creator>
		<pubDate>Thu, 11 Aug 2011 04:13:45 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=367#comment-1666</guid>
		<description>[...] just released Caliburn.Micro.Autofac 1.2 to NuGet. Please see Introducing Caliburn.Micro.Autofac for [...]</description>
		<content:encoded><![CDATA[<p>[...] just released Caliburn.Micro.Autofac 1.2 to NuGet. Please see Introducing Caliburn.Micro.Autofac for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1601</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 25 Jul 2011 12:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1601</guid>
		<description>Thanks</description>
		<content:encoded><![CDATA[<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1600</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Mon, 25 Jul 2011 10:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1600</guid>
		<description>Sorry for the lack of clarity here.  Let me see if I can put in the right example.</description>
		<content:encoded><![CDATA[<p>Sorry for the lack of clarity here.  Let me see if I can put in the right example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Autofac by Caliburn.Micro.Autofac 1.1 Released &#124; 42</title>
		<link>http://buksbaum.us/2011/06/12/introducing-caliburn-micro-autofac/comment-page-1/#comment-1560</link>
		<dc:creator>Caliburn.Micro.Autofac 1.1 Released &#124; 42</dc:creator>
		<pubDate>Tue, 12 Jul 2011 02:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=367#comment-1560</guid>
		<description>[...] just released Caliburn.Micro.Autofac 1.1 to NuGet. Please see Introducing Caliburn.Micro.Autofac for [...]</description>
		<content:encoded><![CDATA[<p>[...] just released Caliburn.Micro.Autofac 1.1 to NuGet. Please see Introducing Caliburn.Micro.Autofac for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Logging by Introducing Caliburn.Micro.Logging.NLog &#124; 42</title>
		<link>http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/comment-page-1/#comment-1554</link>
		<dc:creator>Introducing Caliburn.Micro.Logging.NLog &#124; 42</dc:creator>
		<pubDate>Thu, 07 Jul 2011 03:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/#comment-1554</guid>
		<description>[...] my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.NLog which integrates NLog into Caliburn.Micro. [...]</description>
		<content:encoded><![CDATA[<p>[...] my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.NLog which integrates NLog into Caliburn.Micro. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro.Logging by Introducing Caliburn.Micro.Logging.log4net &#124; 42</title>
		<link>http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/comment-page-1/#comment-1553</link>
		<dc:creator>Introducing Caliburn.Micro.Logging.log4net &#124; 42</dc:creator>
		<pubDate>Thu, 07 Jul 2011 03:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/07/04/introducing-caliburn-micro-logging/#comment-1553</guid>
		<description>[...] my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.log4net which integrates log4net into [...]</description>
		<content:encoded><![CDATA[<p>[...] my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.log4net which integrates log4net into [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To Do Logging with Caliburn.Micro by Introducing Caliburn.Micro.Logging &#124; 42</title>
		<link>http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/comment-page-1/#comment-1547</link>
		<dc:creator>Introducing Caliburn.Micro.Logging &#124; 42</dc:creator>
		<pubDate>Tue, 05 Jul 2011 03:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/#comment-1547</guid>
		<description>[...] did not want to include it twice. This led me to do a quick refactoring of the logging code from How to do Logging with Caliburn.Micro to create a new assembly Caliburn.Micro.Logging which would include the common code between the [...]</description>
		<content:encoded><![CDATA[<p>[...] did not want to include it twice. This led me to do a quick refactoring of the logging code from How to do Logging with Caliburn.Micro to create a new assembly Caliburn.Micro.Logging which would include the common code between the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Type Tracking Extension for Unity by Introducing Hazware.Unity.TypeTracking &#124; 42</title>
		<link>http://buksbaum.us/2009/02/08/type-tracking-extension-for-unity/comment-page-1/#comment-1523</link>
		<dc:creator>Introducing Hazware.Unity.TypeTracking &#124; 42</dc:creator>
		<pubDate>Fri, 17 Jun 2011 03:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=75#comment-1523</guid>
		<description>[...] few years ago I wrote Type Tracking Extension for Unity and Extending and Demonstrating the Type Tracking Extension for Unity, and while I have been using [...]</description>
		<content:encoded><![CDATA[<p>[...] few years ago I wrote Type Tracking Extension for Unity and Extending and Demonstrating the Type Tracking Extension for Unity, and while I have been using [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by david</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1522</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 17 Jun 2011 02:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1522</guid>
		<description>Can you provide a test case that causes this problem? I would like to add it to the unit tests and then I can verify the solution you provided and add it in.</description>
		<content:encoded><![CDATA[<p>Can you provide a test case that causes this problem? I would like to add it to the unit tests and then I can verify the solution you provided and add it in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by Introducing Caliburn.Micro.Autofac &#124; 42</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1520</link>
		<dc:creator>Introducing Caliburn.Micro.Autofac &#124; 42</dc:creator>
		<pubDate>Mon, 13 Jun 2011 03:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1520</guid>
		<description>[...] year I wrote Bootstrapping Caliburn.Micro with Autofac and it has since become one of my most popular posts. While the code presented in the post worked [...]</description>
		<content:encoded><![CDATA[<p>[...] year I wrote Bootstrapping Caliburn.Micro with Autofac and it has since become one of my most popular posts. While the code presented in the post worked [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1512</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Wed, 08 Jun 2011 17:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1512</guid>
		<description>Dang!  Anyway, pass from and to types to register type!!!</description>
		<content:encoded><![CDATA[<p>Dang!  Anyway, pass from and to types to register type!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1511</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Wed, 08 Jun 2011 17:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1511</guid>
		<description>RegisterType(&amp;lt T,T &amp;gt) is what was supposed to show up.  !!!</description>
		<content:encoded><![CDATA[<p>RegisterType(&amp;lt T,T &amp;gt) is what was supposed to show up.  !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending and Demonstrating the Type Tracking Extension for Unity by Allen</title>
		<link>http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/comment-page-1/#comment-1510</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Wed, 08 Jun 2011 17:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2009/08/20/extending-and-demonstrating-the-type-tracking-extension-for-unity/#comment-1510</guid>
		<description>Appears that if the RegisterEventArgs to event OnNewType do not have  a value for e.TypeFrom, bad things happen.  I solved this in my own way by simply changing all the RegisterType statements to look like:
 ...RegisterType();
instead of
 ...RegisterType();

 to avoid this error.

viz

 private void OnNewType(object sender, RegisterEventArgs e)
    {
      HashSet names;
      string name = string.IsNullOrEmpty(e.Name) ? string.Empty : e.Name;
      if (e.TypeFrom == null)
          throw new ArgumentNullException(&quot;The TypeFrom argument cannot be null - use .RegisterType(); instead of
 ...RegisterType(); to avoid this error&quot;);
      if (!_registeredTypes.TryGetValue(e.TypeFrom, out names))
      { //  not found, so add it
        _registeredTypes.Add(e.TypeFrom, new HashSet(new string[] { name }));
      }
      else
      { //  already added type, so add name
        names.Add(name);
      }
    }</description>
		<content:encoded><![CDATA[<p>Appears that if the RegisterEventArgs to event OnNewType do not have  a value for e.TypeFrom, bad things happen.  I solved this in my own way by simply changing all the RegisterType statements to look like:<br />
 &#8230;RegisterType();<br />
instead of<br />
 &#8230;RegisterType();</p>
<p> to avoid this error.</p>
<p>viz</p>
<p> private void OnNewType(object sender, RegisterEventArgs e)<br />
    {<br />
      HashSet names;<br />
      string name = string.IsNullOrEmpty(e.Name) ? string.Empty : e.Name;<br />
      if (e.TypeFrom == null)<br />
          throw new ArgumentNullException(&#8220;The TypeFrom argument cannot be null &#8211; use .RegisterType(); instead of<br />
 &#8230;RegisterType(); to avoid this error&#8221;);<br />
      if (!_registeredTypes.TryGetValue(e.TypeFrom, out names))<br />
      { //  not found, so add it<br />
        _registeredTypes.Add(e.TypeFrom, new HashSet(new string[] { name }));<br />
      }<br />
      else<br />
      { //  already added type, so add name<br />
        names.Add(name);<br />
      }<br />
    }</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Patterns 101 &#8211; Factory Pattern by Delegates &#38; Lambda Expressions Review &#124; Tampa#</title>
		<link>http://buksbaum.us/2011/05/11/patterns-101factory-pattern/comment-page-1/#comment-1431</link>
		<dc:creator>Delegates &#38; Lambda Expressions Review &#124; Tampa#</dc:creator>
		<pubDate>Sat, 14 May 2011 16:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2011/05/11/patterns-101factory-pattern/#comment-1431</guid>
		<description>[...] David gave a short presentation on the Factory Pattern as part of the “Patterns 101” segment. You can find the full post here. [...]</description>
		<content:encoded><![CDATA[<p>[...] David gave a short presentation on the Factory Pattern as part of the “Patterns 101” segment. You can find the full post here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Caliburn.Micro &#8211; Hello World by Ravi Tamada</title>
		<link>http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/comment-page-1/#comment-1412</link>
		<dc:creator>Ravi Tamada</dc:creator>
		<pubDate>Mon, 02 May 2011 13:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/#comment-1412</guid>
		<description>Very good tutorial. The best i had found with MVVM pattern.

Thank You</description>
		<content:encoded><![CDATA[<p>Very good tutorial. The best i had found with MVVM pattern.</p>
<p>Thank You</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Caliburn.Micro &#8211; Hello World by Jason</title>
		<link>http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/comment-page-1/#comment-1411</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Mon, 02 May 2011 08:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/#comment-1411</guid>
		<description>Great quickstart tutorial! Thank you</description>
		<content:encoded><![CDATA[<p>Great quickstart tutorial! Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Caliburn.Micro &#8211; Hello World by Nitro</title>
		<link>http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/comment-page-1/#comment-1409</link>
		<dc:creator>Nitro</dc:creator>
		<pubDate>Sun, 24 Apr 2011 17:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/01/caliburn-micro-hello-world/#comment-1409</guid>
		<description>Great tutorial. caliburn micro really needs some walk though tutorials like this.</description>
		<content:encoded><![CDATA[<p>Great tutorial. caliburn micro really needs some walk though tutorials like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Patterns 101 &#8211; Observer Pattern by Visual Studio &#38; Defensive Programming Resources &#124; Tampa#</title>
		<link>http://buksbaum.us/2011/04/20/patterns-101observer-pattern/comment-page-1/#comment-1406</link>
		<dc:creator>Visual Studio &#38; Defensive Programming Resources &#124; Tampa#</dc:creator>
		<pubDate>Fri, 22 Apr 2011 00:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=244#comment-1406</guid>
		<description>[...] Patterns 101 &#8211; Observer Pattern [...]</description>
		<content:encoded><![CDATA[<p>[...] Patterns 101 &#8211; Observer Pattern [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Code Contracts for Safer Code by Visual Studio &#38; Defensive Programming Resources &#124; Tampa#</title>
		<link>http://buksbaum.us/2011/04/20/using-code-contracts-for-safer-code/comment-page-1/#comment-1405</link>
		<dc:creator>Visual Studio &#38; Defensive Programming Resources &#124; Tampa#</dc:creator>
		<pubDate>Fri, 22 Apr 2011 00:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=239#comment-1405</guid>
		<description>[...] Using Code Contracts for Safer Code [...]</description>
		<content:encoded><![CDATA[<p>[...] Using Code Contracts for Safer Code [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a Virtual Assistant to Offload Noise by Hiring A Virtual Assistant &#8211; Status Update &#124; 42</title>
		<link>http://buksbaum.us/2009/04/04/using-a-virtual-assistant-to-offload-noise/comment-page-1/#comment-1381</link>
		<dc:creator>Hiring A Virtual Assistant &#8211; Status Update &#124; 42</dc:creator>
		<pubDate>Tue, 05 Apr 2011 20:06:49 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/?p=96#comment-1381</guid>
		<description>[...] my previous post Using a Virtual Assistant to Offload Noise, I defined the 6 steps I planned to follow. The six steps [...]</description>
		<content:encoded><![CDATA[<p>[...] my previous post Using a Virtual Assistant to Offload Noise, I defined the 6 steps I planned to follow. The six steps [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Caliburn.Micro ViewModel File Template for ReSharper by Berryl</title>
		<link>http://buksbaum.us/2010/08/27/caliburn-micro-viewmodel-file-template-for-resharper/comment-page-1/#comment-1306</link>
		<dc:creator>Berryl</dc:creator>
		<pubDate>Wed, 16 Feb 2011 01:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/27/caliburn-micro-viewmodel-file-template-for-resharper/#comment-1306</guid>
		<description>Other topics I would love to see with Caliburn have to do with extending PropertyChangedBase or Screen for things like:
1) forwarding basic object overrides to the Model (primarily Equality &amp; GetHashCode, assuming you have some domain superclass / entity)
2) IsDirty tracking, perhaps implementing System.ComponentModel.IEditableObject
3) validation, making use of some sort of model validator (I like NHibernateValidator) 

Cheers!</description>
		<content:encoded><![CDATA[<p>Other topics I would love to see with Caliburn have to do with extending PropertyChangedBase or Screen for things like:<br />
1) forwarding basic object overrides to the Model (primarily Equality &amp; GetHashCode, assuming you have some domain superclass / entity)<br />
2) IsDirty tracking, perhaps implementing System.ComponentModel.IEditableObject<br />
3) validation, making use of some sort of model validator (I like NHibernateValidator) </p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Caliburn.Micro ViewModel File Template for ReSharper by Berryl</title>
		<link>http://buksbaum.us/2010/08/27/caliburn-micro-viewmodel-file-template-for-resharper/comment-page-1/#comment-1305</link>
		<dc:creator>Berryl</dc:creator>
		<pubDate>Tue, 15 Feb 2011 19:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/27/caliburn-micro-viewmodel-file-template-for-resharper/#comment-1305</guid>
		<description>Nice job making exposing these pieces of functionality and making them accessible and usable in their own right (when I first saw Caliburn it just looked so...different!).

Looking forward to seeing one on the Conductor pattern, in particular. 

Not to mention some of the other mysteries that do ultimately turn out to be 42 :--)</description>
		<content:encoded><![CDATA[<p>Nice job making exposing these pieces of functionality and making them accessible and usable in their own right (when I first saw Caliburn it just looked so&#8230;different!).</p>
<p>Looking forward to seeing one on the Conductor pattern, in particular. </p>
<p>Not to mention some of the other mysteries that do ultimately turn out to be 42 :&#8211;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Caliburn.Micro – Lightweight MVVM &amp; WPF by Bob Baker</title>
		<link>http://buksbaum.us/2010/07/31/introducing-caliburn-micro-lightweight-mvvm-wpf/comment-page-1/#comment-1304</link>
		<dc:creator>Bob Baker</dc:creator>
		<pubDate>Mon, 07 Feb 2011 23:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/07/31/introducing-caliburn-micro-lightweight-mvvm-wpf/#comment-1304</guid>
		<description>I&#039;m new with Caliburn.Micro. Are you aware of any good examples of instantiating a ChildWindow to edit a single instance of a collection from a viewmodel using CM conventions (Window.Show, and IResult come to mind) -- you know, the typical list view and then edit action to edit or add a new item. I find a lot of general discussion about it, but no concrete examples, which is how I learn best. Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;m new with Caliburn.Micro. Are you aware of any good examples of instantiating a ChildWindow to edit a single instance of a collection from a viewmodel using CM conventions (Window.Show, and IResult come to mind) &#8212; you know, the typical list view and then edit action to edit or add a new item. I find a lot of general discussion about it, but no concrete examples, which is how I learn best. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by Craigology</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1301</link>
		<dc:creator>Craigology</dc:creator>
		<pubDate>Tue, 14 Dec 2010 02:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1301</guid>
		<description>Nice post. Had same issue as @wizbit. This works, using TryResolve, possibly more efficient too.

protected override object GetInstance(Type serviceType, string key)
{
    object instance;
    if (string.IsNullOrWhiteSpace(key))
    {
        if (Container.TryResolve(serviceType, out instance))
        {
            return instance;
        }
    }
    else
    {                
        if (Container.TryResolveNamed(key, serviceType, out instance))
        {
            return instance;
        }
    }

    throw new Exception(string.Format(&quot;Could not locate any instances of contract {0}.&quot;, key ?? serviceType.Name));
}</description>
		<content:encoded><![CDATA[<p>Nice post. Had same issue as @wizbit. This works, using TryResolve, possibly more efficient too.</p>
<p>protected override object GetInstance(Type serviceType, string key)<br />
{<br />
    object instance;<br />
    if (string.IsNullOrWhiteSpace(key))<br />
    {<br />
        if (Container.TryResolve(serviceType, out instance))<br />
        {<br />
            return instance;<br />
        }<br />
    }<br />
    else<br />
    {<br />
        if (Container.TryResolveNamed(key, serviceType, out instance))<br />
        {<br />
            return instance;<br />
        }<br />
    }</p>
<p>    throw new Exception(string.Format(&#8220;Could not locate any instances of contract {0}.&#8221;, key ?? serviceType.Name));<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bootstrapping Caliburn.Micro with Autofac by wizbit</title>
		<link>http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/comment-page-1/#comment-1300</link>
		<dc:creator>wizbit</dc:creator>
		<pubDate>Sat, 04 Dec 2010 14:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/20/bootstrapping-caliburn-micro-with-autofac/#comment-1300</guid>
		<description>Could be the version of AutoFac(Autofac-2.3.2.632-NET40) I am using, but your GetInstance() implementation doesn&#039;t compile... correction for this version of AutoFac is:

        protected override object GetInstance(Type service, string key)
        {
            if (string.IsNullOrWhiteSpace(key))
                if (container.IsRegistered(service))
                    return container.Resolve(service);
            else
                if (container.IsRegisteredWithName(key, service))
                    container.ResolveNamed(key, service);

            throw new Exception(string.Format(&quot;Could not locate any instances of contract {0}.&quot;, key ?? service.Name));
        }

Changes are just the IsRegisteredWithName() and ResolveNamed() calls.

Thanks for the posts... helping lots

Wiz</description>
		<content:encoded><![CDATA[<p>Could be the version of AutoFac(Autofac-2.3.2.632-NET40) I am using, but your GetInstance() implementation doesn&#8217;t compile&#8230; correction for this version of AutoFac is:</p>
<p>        protected override object GetInstance(Type service, string key)<br />
        {<br />
            if (string.IsNullOrWhiteSpace(key))<br />
                if (container.IsRegistered(service))<br />
                    return container.Resolve(service);<br />
            else<br />
                if (container.IsRegisteredWithName(key, service))<br />
                    container.ResolveNamed(key, service);</p>
<p>            throw new Exception(string.Format(&#8220;Could not locate any instances of contract {0}.&#8221;, key ?? service.Name));<br />
        }</p>
<p>Changes are just the IsRegisteredWithName() and ResolveNamed() calls.</p>
<p>Thanks for the posts&#8230; helping lots</p>
<p>Wiz</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To Do Logging with Caliburn.Micro by Marcel Lamothe</title>
		<link>http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/comment-page-1/#comment-1297</link>
		<dc:creator>Marcel Lamothe</dc:creator>
		<pubDate>Fri, 08 Oct 2010 19:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://buksbaum.us/2010/08/08/how-to-do-logging-with-caliburn-micro/#comment-1297</guid>
		<description>I also wanted to say thanks - you&#039;ve done a great job explaining Caliburn step by step. I&#039;m looking forward to the rest of the series!</description>
		<content:encoded><![CDATA[<p>I also wanted to say thanks &#8211; you&#8217;ve done a great job explaining Caliburn step by step. I&#8217;m looking forward to the rest of the series!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

