Question: Is there a way to bind a Silverlight control to an object (or database table's row) which contains the values of several control's properties, doing so without by define the binding for each property?

For instance:
Let's say I have the class (or entity based on database table's row) with the following values:

```
class TextBlockValues
{
    public string Text{get; set;}
    public string HorizontalAlignment{get; set;}
    public string VerticalAlignment{get; set;}
}

```

I want to bind it to a TextBlock in my silverlight application (again without explicit specify the binding for each property).

Thank you for your time.

Answer: 
I have the same issue with relative URLs in a rendered control in the same fashion I think that you are experiencing. 

My problem is that I noticed the request.path is relative to the service call, apparently AJAX or IIS creates a subdirectory under your current page and that's why ResolveClientUrl or "tilde" resolves to an extra parent directory ...

So in your case my guess is that your control is actually created in 

<http://Test.aspx/TestMethod> (the name of the WebMethod)

This is actually what is happening to me, all my Urls have an extra ..\ prepended.
Marty
Everything that Marty described is correct, and I'm not sure how to fix this issue either, but here's a workaround that I use, which detects when the extra "../" is prepended and corrects the situation by readding the subdirectory into the URL:

```
        // this is the link that will be appended to the fullpath+subdirectory of the app
        var resolvedLinkInBrowser = this.ResolveClientUrl(builtUrl);

        if (resolvedLinkInBrowser.Contains("../"))
        {
            // when an ajax call is made, it is made using a service call. This service call for some
            // reason does not think that it should serve links relative to the subdirectory, but thinks
            // that it should serve links relative to the root of the domain. That is why when the link is resolved,
            // WebForms adds a '../' to the link, to get it back to the root domain. Since we've detected this case,
            // we can insert the subdirectory in to our not-yet-resolved url, to force the resulting url to be correct.
            // this is a workaround. If this issue can be fixed any other way, please do that.
            builtUrl = builtUrl.Replace("~/", "~" + HttpRuntime.AppDomainAppVirtualPath + "/");
        }

```