Technology

CodePlexContainer Gets Virtual Method Interception aka OB4Life Taking It Back

Scott Densmore — Thu, 28 Jun 2007 21:30:00 GMT

We (Brad and I) were at it again. After finishing up some other CodePlex tasks for the last few weeks, we are finally finished with the last big task for CodePlex Container: Virtual Method Interception.

You can read about it here.

Now that the container is finally done, I will be able to get back to finishing the EntLibRefactored project. This will involve me making some major changes to how EntLib works. During this time, maybe we can get xml configuration of the container so that the configuration of EntLib is at the container level. Right now it will be slow going (not my full time day job :)), yet I think this will be a much better design and use.

Please send us feedback through the project site.

Taking it back....OB4LIFE!

Technorati Tags: CodePlex, ObjectBuilder

Event Broker in CodePlex Container

Scott Densmore — Mon, 11 Jun 2007 16:56:00 GMT

Looks like Brad and I are on a roll. We did Event Broker on Friday. You can read about it here. Hopefully we can get virtual interception done next week.

Technorati Tags: ObjectBuilder

CodePlex Container gets Interception

Scott Densmore — Thu, 07 Jun 2007 23:16:00 GMT

Todays check in marks a new day for the Codeplex Container. We now have method interception via remoting. I have been talking about this for a while and finally we have our first fully functional check in. Check it out here.

The interception (method interception) is loosely based upon the PIAB work from Enterprise Library 3.0. Our goal was to have a code only version and then add the syntax candy via attributes after. All this work is done in the context of ObjectBuilder and our container. So you can get the same functionality of configuration and rules doing the work with different strategies. I am going to try and spend some time on this in the EntLibRefactored project soon.

Technorati Tags: CodePlex Client, ObjectBuilder

CodePlex Client June 2007

Scott Densmore — Mon, 04 Jun 2007 21:21:00 GMT

We just released the latest CodePlex Client with patch support. Read the pretty words here.

On a personal note, this has been a blast to work on with Brad. We have introduced some great customer value and a new version of ObjectBuilder fell out of us building a real application (I am sure someone will say they could have done it in 20 minutes with one hand tied behind their back :)).

Technorati Tags: CodePlex, CodePlex Client, CPC, ObjectBuilder

Enterprise Library without Configuration

Scott Densmore — Wed, 23 May 2007 17:38:00 GMT

At the end of Enterprise LIbrary v1, we knew .NET 2 was coming and that there would need to be changes to configuration. The biggest thing I heard (from Brad, Peter, Jim, Brian etc) was that the blocks should be completely independent from configuration. At the same time we were really talking about Dependency Injection and how we could accomplish removing configuration with this mechanism (at the same time figuring out .NET 2.0 config and the changes we wanted for EntLib V2).

While we were working on EntLib V2, we were working in the same room as the Composite Application Block team where Brad, Peter and Ed come up with ObjectBuilder. We decided we would use ObjectBuilder as the DI framework and and build our own container (EnterpriseLibraryFactory). By doing this we could inject config into the blocks given an IConfigurationSource. Given all the learnings, changes, etc, I don't feel we made it to the finish line when breaking out configuration. I think to really get to the solution we needed to remove the dependency of the Common library from all the other code. Enter EntLib V3.

Enterprise Library version 3 is another great release, yet I am sad that the configuration did not get much attention (of course that is probably because I had written it 12 times before). Now that we have the EntLibContrib project on CodePlex I thought I would start putting up the code that I have migrated to not use config. You can find it there in the EntLibRefactored folder of the project. I have my own solution so I can refactor more as I go along. All the original EntLib assemblies are in the 3rd party directories so you don't have to install it. Eventually, they will not be necessary. Wouldn't this be a cool way to run EntLib 4?

Why am I doing this?

Good question. Developing a product and using it are two different things. We use ObjectBuilder and EntLib V2 for the CodePlex site. What we wanted was the new PIAB (Process Invocation Application Block) for the interception mechanism. Looking at the block, I discovered that to use it we needed to drag along the Common and ObjectBuilder library. I didn't mine ObjectBuilder but taking Common was out of the question... we were still using EntLib V2. If I didn't have a dependency on the Common library, I could use ObjectBuilder and PIAB since they were the same.

This is the major reason that I decided that it was time to start this process of removing the dependency of configuration from the blocks. My first stab was to rewrite PIAB using the EntLib V3 binaries... and I have to say it was pretty easy. You could take the same approach (and I will eventually) with the rest of the library.

What is next?

I have a few more things I want to do while removing the configuration. If you think about removing the configuration from PIAB, you could move it further down the stack. You could then build a container that did both DI and AOP. This is what we are doing for CodePlex. Watch here for updates. Brad and I should have some new code for you that includes just this!

Technorati Tags: Enterprise Library, ObjectBuilder

Subversion Support on CodePlex

Scott Densmore — Tue, 22 May 2007 17:54:00 GMT

Man, we are adding Subversion support.... I had no idea.

Technorati Tags: CodePlex

CodePlex Client is Released

Scott Densmore — Fri, 11 May 2007 17:40:00 GMT

After a couple of months of testing and using it internally, CodePlex Client source is on CodePlex. Read the full announcement from Brad, and get the code here.

Technorati Tags: CodePlex, CodePlex Client, CPC

Unit Testing Goes Pro!

Scott Densmore — Fri, 30 Mar 2007 16:45:00 GMT

I guess all the rants finally paid off. Unit Testing is going to be available in Visual Studio Pro. I think this is great, yet I agree with Brad that Unit Testing is so fundamental that it should be part of the SDK just like MSBuild. Time to start another petition.

Swimming to Dublin

Scott Densmore — Thu, 29 Mar 2007 20:27:00 GMT

I miss Casper. One of our friends, Sarah, sent me directions to go see him from New York. I think that swim at step 23 is going to kill me.

CodePlex Source Control Client Shipped

Scott Densmore — Tue, 27 Mar 2007 16:17:00 GMT

When I joined the team in October, Brad was working on a little tool that would enable an "edit-merge-commit" style for CodePlex. This allows the ability to work offline with the TFS infrastructure. Over the past couple of months I have had the pleasure (Brad may not agree) of working on CodePlex Source Control Client (cpc). You can read all about it here.

Please give your feedback!