Zuker On Foundations

The MetadataExchangeClient has resolved more than MaximumResolvedReferences

This error was resulted in a specific scenario where I tried to pull a service metadata using .NET MetadataExchangeClient.

The reason was that the metadata consisted with more metadata references than the limit defined on my MEXClient instance. (The default is 10)

Solution - Increase the limit.

MetadataExchangeClient mexClient = new MetadataExchangeClient();
mexClient.MaximumResolvedReferences = MaximumResolvedReferences; //some constant

PyBinding MarkupExtension: use Python statements for Data Binding

A very nice extension built for WPF, Read the full details Here.

E.g. -

<Polyline Points="{ln:PyBinding PointCollection([Point(p.Time,
               p.Value * $(Container.ActualHeight))
               for p in $(.MarketData.DataPoints)])}"

               Stroke="IndianRed" StrokeThickness="1" />

Very cool!

NDepend

I finally had the chance to look into the NDepend tool.

In short:

"NDepend is a tool that simplifies managing a complex .NET code base. Architects and developers can analyze code structure, specify design rules, plan massive refactoring, do effective code reviews and master evolution by comparing different versions of the code."

I decided to NDepend a component assembly written in our project - the output was very cool.
I was able to see the analyzing reports. There's a lot of information exposed there.

You can use that tool to extract practical development practices and potential improvements that should be made.
Moreover, you can use CQL (Code Query Language) to execute queries against the actual code and examine whatever you wish, sweet!

To sum things up, my experience with the tool had been very positive and I do see potential usage in utilizing development practices with this tool.

Very cool

Making Ajax calls to server using PageMethods and Session_End

We were working on a project where there was used the ajax pattern of PageMethods in order to call to the server.

We experienced a weird behavior where calling the operation marked as WebMethod (required to be called as part of the PageMethods) caused weird occurrences in the Session_End global event handler.

After dwelling into it, we found that the issue was solved once we enabled the session state in the WebMethod attribute.

I thought it might be worth sharing.

Enabling cross-domain calls for Silverlight on self-hosted WCF services

Read the full details Here.

Carlos came up with an elegant way to enable cross domain calls from silverlight to self hosted WCF service.

Such calls requires the server to allow cross site scripting which is done by placing a settings XML file in the web site root.
But what about the cases where you self host a service in a process and you're not in the context of a web site root?

Well, that's what the post is about.