Ironing code, geek t-shirts and even presentations!


A New Blog!


This blog has been serving me for a long time. Very grateful for it and for the amazing readers I've got. 

But it's time to move on!
So.... I'm happy to announce -
This is my new blog and all posts will be written there from now on.


My Chrome Developer Tools Interview at .NET Rocks! is Available


During NDC London I did an Interview with Carl Franklin and Richard Campbell from .NET Rocks! regarding Chrome Developer Tools. It was a fun experience for me and hopefully an enriching one for the audience!

And go download OzCode!

All the best,

ngValue - CodeValue's first AngularJS Conference!

Hi all!

I am delighted to announce CodeValue's first AngularJS conference - ngValue.

This conference has been in our minds for a while now and finally we got the time to make it happen. It will take place on the 26th of November at Cinema City, Herzeliyya, Israel. 

In the last 3 years my division at CodeValue, the Web divison,  has been involved in various angular-based projects. We have learned a lot from these projects and come to conclusions which we carry to our next projects - where we make use of our vast experience and of course, learn even more.
ngValue is intended to fullfil our desire to share our experience. It is targeted towards devs, leaders and decision makers who are thinking about getting into AngularJS or had some experience with it already and would like to get some insights from our experience.

The conference is gonna be half a day and will be all around AngularJs  - from the basics, through best practices and case studies, to our expert panel where you can ask us any question you like.

It's gonna be super awesome, so beware!  :)

For registration and more details, visit the conference website:

Feel free to contact me if you have any questions.
All the best,

Code Snippet: Find an Element in Page By its Angular Scope ID

Recently I was working on one of my projects and ran into a very illusive scope - I needed to know to which element it belonged but just couldn't find it on through the Elements Panel. So I wrote a small code snippet that you can paste to the console, or put somewhere in your code - it searches the DOM stating from a root element that it's given and looks for an element that has an angular scope with a specific ID attached to it.

function findScope(id, el) {
  if (angular.element(el).scope().$id == id) { return el; }
  for (var i = 0; i < el.childNodes.length; i++) {
    var result = findScope(id, el.childNodes[i]);
    if (result) { return result; }

// Example usage:
findScope('05W', document.body);

The "Man in the Middle" Debugging Technique

When debugging web applications, every once in a while you find yourself wondering why an input field value is not what it's supposed to be. And the bigger the application, the harder to find the problematic piece of code responsible... Do not despair! in the web, like in the web, there's always a workaround... I call this debugging technique - the Man in the Middle technique.

So what's the problem, anyway?

Here's a sample code that reproduces the problem. You can also find it on jsfiddle:

The Solution

To find out who's moved your cheese, or changed your value for that matter, we're gonna take advantage of JavaScript's free spirit - the spirit that allows us to do whatever we want - delete defined objects, redefine them, and generally enjoy some dangerous fun when we want it.
For what we need we're going to redefine the input field's value property so we can set a breakpoint or write to console every time the value is changing. This is the entire trick... 
The main piece of code that enables our solution is this:
Object.defineProperty($("#foo").get(0),"value", { 
  set: function(val) { debugger; }

And this is the complete solution on jsfiddle:

And this is, dear readers, the Man in the Middle debugging technique.

All the best,

Using Inline Templates for Directives

When writing angular directives you usually use two kinds of templates - a string that goes into the template property, or a path to a file containing the template which goes into the templateUrl property. The less known brother of these is the inline template option, which is what this blog post is about.

What are Inline Templates?

Inline templates are templates that you define inside your HTML pages within <script> tags. This is an "in-between" approach between the string template and the file template - on the one hand, you don't have to define the template as a string (who loves doing that?? it's such a horrible experience) and on the other hand, angular doesn't need to request the template from the server because it already loads with the page.

What Is It Good For?

A lot!
Well, a few use cases that this approach will make sense for:
  • Instead of using the template property which forces you to write the template as a string.
    If you're a fan of concatenating strings, then this might not appeal to you. But if you are, hmmm, well, you probably have other problems :)
  • When you create a DSL for your application which involves a bunch of directives which will, for sure, be loaded - put all the templates on the main page. This will eliminate the calls to the server for fetching the templates.
  • The last bullet works for every directive that will certainly be loaded at some point.
In my applications I usually create a single partial page which gets loaded with the master layout page and put there all the directive templates I need.

How do You Define Inline Templates?

It's very simple!
To define the template, just add a <script> tag with type="text/ng-template" and a unique id, for example, id="/templates/my-head.html":

On the directive side, use the templateUrl property and set its value to the script tag id. In our case, that would be "/templates/my-head.html":
m.directive("myHead", function() {
  return {
    templateUrl: "/templates/my-head.html"

Why Not, Then?

There a few disadvantages for using inline templates that you should be aware of:
  • Some IDEs will not provide autocompletion inside <script> tags. 
  • People usually prefer to have the template file on its own because it's easier to find on the file tree.
    This is pretty true. However, you can continue working with separate file and then write a simple build script that will take all the template files and bundle them into a single file before going to production.


Inline directive templates is a super simple and powerful solution that makes a lot of sense for various use cases. For some reason the documentation on this feature is pretty much not existing so I hope now it will get the acknowledgment it deserves :)

Write Angular and prosper!

Code Samples from IDNDUG – August 2013

Last night I took the stage at the Israeli .NET User Group and introduced how web development is done today in a session named “How The Cool Kids Create Chats Today?”. Images (courtesy of Dror Helper and Ariel Ben Horesh):

Israeli .NET User Group AUG 2013 - How The Cool Kids Create Chats Today - Shay FriedmanIsraeli .NET User Group AUG 2013 - How The Cool Kids Create Chats Today - Shay Friedman

I had a blast. Thanks to all the attendees who came and listened!

I promised to upload the code from the presentation and I’m a man of my word so…
the solution can be downloaded from: 
The code here has a bit more features than what I showed yesterday and includes custom styles with LESS (look for less files in the Content/less folder) and the general UI design is done via Twitter Bootstrap.

Last but not least – a hidden Easter egg - open the chat in two browsers and make sure one of them is Chrome. Sign in to the chat from both browsers and send a message from the other browser that says *trees* (including the asterisks). Enjoy! Smile

If you have questions or anything else, let me know.
All the best,

Local IIS Not Working and the horrifying “The Server Committed a Protocol Violation” Error

The Problem

I was working on a web site on my local computer. When I wanted to run the web site on my local IIS, I suddenly received a 404 Not Found error for everything hosted on my local IIS.
I tried to run iisreset (even twice, of course!) and it didn’t help. I then tried to start debugging from within Visual Studio, just to see what happens – then I received the OMFG error: “The Server Committed a Protocol Violation. Section=ResponseStatusLine”.


I turned to my old friend, Google. He (or she?) helped me find Martin Kulov’s post -, which suggested that some application had already been using port 80 (the one IIS is using). This results in IIS not being able to load and eventually throwing all of these doomsday errors.

The Solution

I downloaded TCPView to figure out which application is responsible for all the mess. I was surprised (or not) to find out which application it was:

Local IIS Not Working and the horrifying “The Server Committed a Protocol Violation” Error

It was SKYPE!!!! WTF???

Killing Skype and restarting IIS solved the problem and I was able to go back to work.

Note: I’m using Skype

All the best,

My Interview on Herding Code is Published!

At this year’s NDC I had the honor to chat with Jon Galloway and Scott Allen, who are half of the Herding Code crew. We chatted about subjects related to my NDC talks – Roslyn, C#’s dynamic capabilities, and the DLR. 

Last week our chat was published as an Herding Code episode, and it is available to hear and download at

Enjoy the episode and thanks Herding Code for having me!

All the best,

Video, Slides and Code from my Session at aspConf 2012 – ASP.NET MVC Tips, Tricks and Hidden Gems

Last week I had the honor of taking part in the community-driven, ASP.NET-related, virtual event – aspConf 2012. My session was named ASP.NET MVC Tips, Tricks and Hidden Gems and it was generally about things I found to be important from my ASP.NET MVC experience – some were more basic and some were more hidden, too hidden some would say :)

I had lots of fun doing the session, and hopefully the attendees has fun too :)

A big big thanks to the aspConf crew – Javier Lozano, Jon Galloway, Eric Hexter, and friends – you guys did an AMAZING job! thanks!

Anyway, everything from my session is now on the interwebs – video, slides and code samples:


Can be watched and downloaded on channel9:


The slides are available on SlideShare:


Code Samples

All code samples from the session are available on my github page:

That’s it. If you have any questions, let me know!
All the best,