This one is very dear to me, I’ve been carrying it in my head for about a year now. Lately I’ve been very focused on my family and work and that left very little time for writing. Recently I had the chance to finally sit down and put it on paper.
This poem, written first in Hebrew is called “You’re Home” and in Hebrew: “את לי בית” is dedicated to my wife, Shani.
The English translation is below. Read more…
This one is the latest of my poems, written recently for my daughter’s first birthday in the beginning of the year.
No translation yet to English so only the Hebrew version for now. The English name for this poem would be “Your Journey”. I’ll try to publish the translation soon.
Without further ado:
Back in July of 2011 (has it been that long ago?) I published what was my latest poem in Hebrew Eich Nifradim (How to Part).
I revisited that poem recently and decided to take a crack at translating it to English and I think it actually turned out quite nicely.
This poem holds a dear place in my heart as i read it in my grandfather’s funeral in the summer of that year…
So here it is:
The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.
Here’s an excerpt:
4,329 films were submitted to the 2012 Cannes Film Festival. This blog had 21,000 views in 2012. If each view were a film, this blog would power 5 Film Festivals
In the first part of this article I showed how I’ve been testing code using MEF and a generic base class that is in charge of wiring up the dependencies.
In this part I will focus on how I got WCF to wire up my web service using MEF in what I think is quite an elegant way.
My first requirement was to be able to write a web service that will use dependencies (imports) but that wouldn’t require me to write the composition code in the service class itself. Most of the examples I saw online didn’t provide me with a good way to do that unfortunately.
Until I came across this excellent post by Tim Roberts which shows how to tap into the WCF pipe-line and have your services composed automatically instead of having to do it per service or including wire-up code in your classes.
While the code Tim provided was a great start I thought it wasn’t just right for me. Specifically it was the fact that it required custom code in the Global.asax file which for me was not as elegant as it should be.
So I’ve done a bit more digging into the WCF pipe-line and discovered that I could achieve an elegant, completely configuration-based solution by implementing my own endpoint behavior.
In the end I needed to only create 3 classes to achieve this: EndpointComposedElement, ComposedEndpointBehavior and ComposedInstanceProvider.
This article will focus on how I’ve adopted unit testing in .NET using MEF and how to also apply this to WCF web services.
I haven’t been dedicated to unit testing for a long time but once I started I couldn’t stop. There are many great benefits to doing unit tests, I wont list them here but a good article to read is at: Agitar.com
What made me build something on my own? I wanted something light that I could also integrate into existing code without making too many changes. So I focused on a couple of things: Testing and Dependency Injection. I wanted an elegant solution that didn’t rely on external libraries or that will require a steep learning-curve.
In this article I will focus on these topics and how I solved it for myself. I’m not going to dive into other topics such as The SOLID principals, TDD, Dependency Injection, Mocking, etc. If these terms are not familiar to you, I suggest you read up on them first.
I’m actually going to divide this article into two parts, to keep them shorter and to the point:
- This first part will discuss how to do testing with MEF.
- The second will discuss how to use MEF and test for a WCF service.