<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Writing ... or Just Practicing? : Enterprise Library</title><link>http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/</link><description>Tags: Enterprise Library</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Try, Try, and Try Again</title><link>http://blogs.msdn.com/b/alexhomer/archive/2012/02/12/try-try-and-try-again.aspx</link><pubDate>Sun, 12 Feb 2012 07:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10264354</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=10264354</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2012/02/12/try-try-and-try-again.aspx#comments</comments><description>&lt;p&gt;There are some seemingly simple phrases that trip so easily off the tongue, but end up leaving you tongue-tied. Or, if not physically entangled, then tied in knots both architecturally and programmatically. Our intrepid little band of developers and writers just encountered an interesting example of one of these disarticulating phrases: namely "reliable messaging".&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2012/02/12/try-try-and-try-again.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10264354" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Software/">Software</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Network/">Network</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Architecture/">Architecture</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Cloud/">Cloud</category></item><item><title>Additional Integrational Hybridization</title><link>http://blogs.msdn.com/b/alexhomer/archive/2011/10/09/additional-integrational-hybridization.aspx</link><pubDate>Sun, 09 Oct 2011 05:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10216058</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=10216058</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2011/10/09/additional-integrational-hybridization.aspx#comments</comments><description>&lt;p&gt;For some unaccountable reason, my semi-coherent bluster a couple of weeks ago wandered across the topic of integration when discussing Windows Azure hybrid applications. Since then, I've been delving deeper into the whole area of hybrid application challenges as we fine-tune our thoughts on the third of our series of guides about designing and developing applications for Windows Azure. And it seems that we in the IT developer community are dragging our heels when it comes to inventing exciting new words.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2011/10/09/additional-integrational-hybridization.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10216058" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Architecture/">Architecture</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Cloud/">Cloud</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Weird/">Weird</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Words/">Words</category></item><item><title>Hybrid Triangulation (with Cat Food and Bananas)</title><link>http://blogs.msdn.com/b/alexhomer/archive/2011/09/26/hybrid-triangulation-_2800_with-cat-food-and-bananas_2900_.aspx</link><pubDate>Mon, 26 Sep 2011 05:23:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10207797</guid><dc:creator>Alex Homer</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=10207797</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2011/09/26/hybrid-triangulation-_2800_with-cat-food-and-bananas_2900_.aspx#comments</comments><description>&lt;p&gt;Once again I'm at one of those gloriously satisfying stages in my p&amp;amp;p working life when I'm trying to define the structure for a new guide. We know what technologies we want to cover, how we will present the guidance, and the kind of sample that we'll provide to demonstrate the all-encompassing wonderfulness of the technologies on offer. But after two weeks of watching videos, perusing technical documents, consulting experts, and RSI from repeated spells of vicious Visioing, I'm still floundering in a cloud of Azure confusion.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2011/09/26/hybrid-triangulation-_2800_with-cat-food-and-bananas_2900_.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10207797" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Design+Patterns/">Design Patterns</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Guidance/">Guidance</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/S_2B00_S/">S+S</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Architecture/">Architecture</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Cloud/">Cloud</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Azure/">Azure</category></item><item><title>Time to Stop Typing and Start Thinking</title><link>http://blogs.msdn.com/b/alexhomer/archive/2011/09/12/time-to-stop-typing-and-start-thinking.aspx</link><pubDate>Mon, 12 Sep 2011 03:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10198569</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=10198569</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2011/09/12/time-to-stop-typing-and-start-thinking.aspx#comments</comments><description>&lt;p&gt;It's amazing how, sometimes, things get simpler the more you fiddle with them. Or, to be more precise, something that seems to be evolving into an increasingly complicated problem turns out to be easy to resolve when you step back and look at it from another direction. I guess it's what they call "lateral thinking"; the archetypal example being letting air out of the tyres of a truck that's just a bit too tall to pass under a low bridge.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2011/09/12/time-to-stop-typing-and-start-thinking.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10198569" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Software/">Software</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Management/">Management</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Network/">Network</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Guidance/">Guidance</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Server+2008/">Server 2008</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category></item><item><title>It Configures</title><link>http://blogs.msdn.com/b/alexhomer/archive/2010/05/09/it-configures.aspx</link><pubDate>Sun, 09 May 2010 05:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10008718</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=10008718</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2010/05/09/it-configures.aspx#comments</comments><description>&lt;p&gt;Some weeks ago, I rambled on for a while about making a use case for scenarios. It came about through an experience working on a project where a specific set of features of the software were so complex and unintuitive when you randomly played with them that it seemed almost impossible to provide potential users with any useful guidance on what they were actually there for. I can now reveal that the software in question was the new configuration tool for version 5.0 of Enterprise Library.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2010/05/09/it-configures.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10008718" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Software/">Software</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Agile/">Agile</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Guidance/">Guidance</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category></item><item><title>Some Consolation...</title><link>http://blogs.msdn.com/b/alexhomer/archive/2009/10/11/some-consolation_2E00__2E00__2E00_.aspx</link><pubDate>Sun, 11 Oct 2009 05:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9891759</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=9891759</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2009/10/11/some-consolation_2E00__2E00__2E00_.aspx#comments</comments><description>&lt;p&gt;I remember when I first started writing books about "Active Server Pages" how we had no end of problems creating sample code that users could easily install and run. There was no SQL Server Express with its auto-attach databases mechanism, no built-in Web Server in Visual InterDev (this was the days before Visual Studio as we know it now), and you couldn't even assume that users had a permanent Internet connection (the vast majority were on a dial-up connection). So you had to create complicate set of scripts and a setup routine, even for ASP samples, that registered the components you needed and populated the database, as well as providing a long list of prerequisites.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2009/10/11/some-consolation_2E00__2E00__2E00_.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9891759" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Languages/">Languages</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Guidance/">Guidance</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category></item><item><title>Five Go To The Library</title><link>http://blogs.msdn.com/b/alexhomer/archive/2009/05/10/five-go-to-the-library.aspx</link><pubDate>Sun, 10 May 2009 08:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9597137</guid><dc:creator>Alex Homer</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.msdn.com/b/alexhomer/rsscomments.aspx?WeblogPostID=9597137</wfw:commentRss><comments>http://blogs.msdn.com/b/alexhomer/archive/2009/05/10/five-go-to-the-library.aspx#comments</comments><description>&lt;p&gt;Our little documentation department here at p&amp;amp;p occasionally gets some odd requests. I've done the "write some fictitious stories about corporations that don't exist" bit in the past (as content for a sample application, in case you were wondering), and the "write a technical article about cloud computing but don't mention any products or technologies" thing (it was a very short article). Combine this with an emerging policy of rewriting everything four times when people keep changing their minds about what they want, and you can see why I'm usually quite busy.&lt;/p&gt;...(&lt;a href="http://blogs.msdn.com/b/alexhomer/archive/2009/05/10/five-go-to-the-library.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9597137" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Documentation/">Documentation</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Guidance/">Guidance</category><category domain="http://blogs.msdn.com/b/alexhomer/archive/tags/Enterprise+Library/">Enterprise Library</category></item></channel></rss>