May 30 2009

Telerik Sales Dashboard Demo for Silverlight and WPF

Telerik just release the Telerik Sales Dashboard Demo for both Silverlight and WPF.

Check this blog post for more info on the Dashboard: Telerik Dashboard for Silverlight and WPF


Hope you enjoy it!

Tags: , ,

May 29 2009

Telerik WebUI Test Studio

I want to invite you to check the article titled "Telerik WebUI Test Studio" on the magazine that is authored by my colleague Rawane Madi.

The article can be reached at: Telerik WebUI Test Studio


Good work Rawane! Keep it up.


Tags: ,

May 26 2009

Model-View-ViewModel in Silverlight

A very nice article to share that shows how to develop an MVVM Application in Silverlight 2.0.

Check the article here: Model View ViewModel in Silverlight 2.0


Hope you enjoy it,


May 18 2009

XAML Power Toys for WPF and Silverlight 2.0 - V4.0

A very nice Visual Studio 2008 SP1 Add-in that you can find handy when developing with Silverlight 2.0 is the XAML Power Toys for WPF and Silverlight.

You can create a XAML business form by using a simple form that drives you step by step in selecting in creating your rows and columns.

You can also create a XAML business form based on a domain object in your project, and much more features.


If you are developing in Silverlight 2.0, it is a must to check this Add-in. XAML Power Toys for WPF and Silverlight 2.0 V 4.0

Hope this helps,

Tags: ,

May 2 2009

Internal Access Modifier on C# Namespaces

Category: C# | silverlight 2.0[email protected] @ 00:08

As part of a Silverlight applicatin I am currently developing, I have a small API that ships with the application that allows extending it with more features. I had few "Default" implementations inside the API and hence I placed them within a Namespace where all classes are marked as Internal.

Now, when I started working on the app, I created a Visual Studio Blank Solution. So the Silverlight application and the API are in the same blank empty solution inside VS 2008. When I access the main Namespace of the API, I always get to see the name of the default implementations, however as empty since all classes inside it are internal. 

So how can I hide the Namespace that contains all those implementations? I read this blog here "" which helped me do what I want, but I thought of illustrating a bit more here in this post to clarify the idea more.

Rule 1: Make sure all the classes inside the Namespace you want to hide are marked as Internal.

Rule 2: If you add a reference to a project whose source code is in the same solution, you will always see the Namespace name however empty with no classes.

Rule 3: If you add a reference to a project whose source code is not present in the current application, the Namespace name that contains all internal classes will be hidden.


I tried it out and seems to work very nice.

Hope this helps,

Tags: ,