Being Scott Densmorehttps://blogs.msdn.microsoft.com/scottdensmore
One Angry CoderFri, 01 Aug 2008 16:54:00 +0000en-UShourly1Found my new homehttps://blogs.msdn.microsoft.com/scottdensmore/2008/08/01/found-my-new-home/
https://blogs.msdn.microsoft.com/scottdensmore/2008/08/01/found-my-new-home/#commentsFri, 01 Aug 2008 16:54:00 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/08/01/found-my-new-home/Now that I live in the outside world, I decided I needed a place of my own. You can now find me at http://scottdensmore.typepad.com.

See you there. All 3 of you.

]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/08/01/found-my-new-home/feed/2Unity Lives! Get your copy today.https://blogs.msdn.microsoft.com/scottdensmore/2008/04/04/unity-lives-get-your-copy-today/
https://blogs.msdn.microsoft.com/scottdensmore/2008/04/04/unity-lives-get-your-copy-today/#commentsFri, 04 Apr 2008 19:19:19 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/04/04/unity-lives-get-your-copy-today/
Awesome work by the entire team! You can get it from MSDN here or from CodePlex. Please discuss and provide feedback so we can make this even better. Objects of the code Unite! [I know, corny].

Also: I have built an extension to Unity that i will be blogging about over the weekend. This is an extension to do Interception (ala PIAB) that I ported from the ObjectBuilder work that Brad and I did.

Enjoy!

]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/04/04/unity-lives-get-your-copy-today/feed/2xUnit.net 1.0 RC2 Releasedhttps://blogs.msdn.microsoft.com/scottdensmore/2008/03/16/xunit-net-1-0-rc2-released/
https://blogs.msdn.microsoft.com/scottdensmore/2008/03/16/xunit-net-1-0-rc2-released/#respondSun, 16 Mar 2008 19:27:54 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/03/16/xunit-net-1-0-rc2-released/
I am sure it would have been soon if it wasn't for the late night WoW session (we can blame any bugs on that too). Go read about it from Brad here.
]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/03/16/xunit-net-1-0-rc2-released/feed/0How to get Enterprise Library 3.1 working in VS 2008https://blogs.msdn.microsoft.com/scottdensmore/2008/03/13/how-to-get-enterprise-library-3-1-working-in-vs-2008/
https://blogs.msdn.microsoft.com/scottdensmore/2008/03/13/how-to-get-enterprise-library-3-1-working-in-vs-2008/#commentsThu, 13 Mar 2008 16:08:00 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/03/13/how-to-get-enterprise-library-3-1-working-in-vs-2008/Enterprise Library 3.1 was published for Visual Studio 2005. That is to say: the Guidance Packages and the integrated Configuration Tool were built to work with Visual Studio 2005. The rest of the library works against .NET 2.0 and continues to work with .NET 3.5 apps.

We have done some work to get the integrated tool to work in Visual Studio 2008. If you run the following registry script it will change the keys where VS looks to load the integrated tool package. After you run the script, you will need to run devenv /setup from the Visual Studio 2008 command prompt.

You can download the file from the EntLibContrib project on CodePlex from here.

]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/03/13/how-to-get-enterprise-library-3-1-working-in-vs-2008/feed/18Unity available on CodePlexhttps://blogs.msdn.microsoft.com/scottdensmore/2008/02/12/unity-available-on-codeplex/
https://blogs.msdn.microsoft.com/scottdensmore/2008/02/12/unity-available-on-codeplex/#commentsTue, 12 Feb 2008 19:14:00 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/02/12/unity-available-on-codeplex/The team has done some great work to get this ready. Please provide us feedback and track any issues.

At the p&p Summit in November here in Redmond I gave a talk called "EntLib Refactored". This talk was started by my work done on the EntLib contrib project under the same name. What I wanted to do was make Enterprise Library smaller, simpler and easier to consume. My first attempt was to rewrite the blocks to not depend on Configuration. This was a great first stab, yet I found that what I really wanted was to reduce the size of things (which factoring out config did not do). What I wanted to do was get rid of the factories and use a Dependency Injection Container to wire up the objects. Brad Wilson and myself had been working on Object Builder 2 and Containers on top of them to test it out. What we needed for Enterprise Library was a DI Container.

After working on previous versions of Enterprise Library, we have learned that we needed Dependency Injection (DI) without knowing it and did it at the most basic level. We created factories: which is a form of simple DI. The problem this created is that each individual block was responsible for it's own configuration and configuration was buried at the bottom of the stack. We need to change around the model a bit to make the responsibility of configuration built into the DI Container and remove all that extra code from each block.

Here is a picture of the old way: [BTW Enterprise Library Factory is buried at the bottom in the Core assembly that no one sees.]

Here is the new way:

This looks better. Configuration is about the container. WAHOOOOOO! This means that building a block, using a block adding your extensions and having the configuration all comes through the container. This will make it easier for you to use Enterprise Library with Unity or your current DI container and allow us to deliver more cool things to you, the customer. Look for more on this later.

That all sounds good, yet there is one lagging thing that needed to be addressed: the devil. Backwards compatibility is the work of the devil, and just like the devil, necessary. This is fueled by the fact that Enterprise Library has reached over a million downloads and not having a story would cause a lot of people to swing large baseball bats at us. So the old way will still work working with factories so you can upgrade and migrate slowly.

Unity is a lightweight container built on top of the work of Object Builder 2, with heavy tweeks by Chris Tavaras. You can read more from Grigori and Chris on Unity.

The funny story about Unity is the name. Grigori and I were trying to come up with a name for this DI block and mentioned it to Peter Provost when we settled on Unity (which is better than the Doohicky Application Block that was up on the board). Peter never thought we would get it pass legal... neener neener is what we said when we got it. He said "Enterprise Library 4: Now with more Peace love and Rock n' Roll".

]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/01/31/enterprise-library-4-now-with-more-peace-love-and-rock-n-roll/feed/6Unity and Enterprise Library 4 Teamhttps://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unity-and-enterprise-library-4-team/
https://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unity-and-enterprise-library-4-team/#respondWed, 30 Jan 2008 00:40:00 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unity-and-enterprise-library-4-team/
I am back on the team (and no I am not writing configuration again).

]]>https://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unity-and-enterprise-library-4-team/feed/0Unite with Unityhttps://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unite-with-unity/
https://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unite-with-unity/#respondWed, 30 Jan 2008 00:34:00 +0000https://blogs.msdn.microsoft.com/scottdensmore/2008/01/30/unite-with-unity/
Unity is our new Dependency Injection Container that will soon be available. Read more from Grigori.

For the last nine months I have been working in a group working on a project doing WinFX (.NET 3.0) with CAB. (No, the reports are wrong, I was not living under a rock). I can definitely say that it has been fun working with XAML. Turning a ListBox into a totally new thing with a few lines of code is wicked cool. Now it is time for the next evolution in my career.

To be honest, when I was looking at the next stage of my career 9 months ago, I contacted Jim about the CodePlex project. At that time, he was just getting traction and did not have a spot for me. Little did I know that after I accepted the offer with my current job space would open up. I know what you are thinking because I am thinking the same thing… “Why oh why did I not take the CodePlex pill?”. I saved it for a rainy day. [I live in Seattle.] I start October 24th!.