LA.NET [EN] - All Comments

How to build types that can be consumed from XAML

ASPInsiders — Thu, 19 Nov 2009 11:13:04 GMT

Now that you know how to use custom types in XAML, you might be wondering if there are any thing you

How to build types that can be consumed from XAML

LA.NET [EN] — Thu, 19 Nov 2009 10:32:44 GMT

Now that you know how to use custom types in XAML, you might be wondering if there are any thing you

Associating XAML namespaces to CLR namespaces

LA.NET [EN] — Thu, 19 Nov 2009 10:10:53 GMT

Take a look at the following (simple) XAML: < UserControl x : Class = "SilverlightApplication1

XAML languages features

ASPInsiders — Wed, 18 Nov 2009 15:46:01 GMT

As I’ve said before, Silverlight supports only a subset of the existing XAML keywords you can use in

XAML languages features

LA.NET [EN] — Wed, 18 Nov 2009 15:15:17 GMT

As I’ve said before, Silverlight supports only a subset of the existing XAML keywords you can use in

XAML: using content properties

ASPInsiders — Tue, 17 Nov 2009 12:40:34 GMT

In the previous post , we’ve seen that we can use one of two approaches for setting the value of a property:

XAML: using content properties

LA.NET [EN] — Tue, 17 Nov 2009 12:06:56 GMT

In the previous post , we’ve seen that we can use one of two approaches for setting the value of a property

XAML and property elements

ASPInsiders — Tue, 17 Nov 2009 10:31:03 GMT

In the previous post , we’ve started looking at same basic XAML. At the time, we’ve defined a simple

XAML and property elements

LA.NET [EN] — Tue, 17 Nov 2009 10:20:14 GMT

In the previous post , we’ve started looking at same basic XAML. At the time, we’ve defined a simple

re: Introducing XAML

Mark Perry — Tue, 17 Nov 2009 09:36:26 GMT

I am really looking forward to this series having just recently started learning Silverlight myself.

Keep up the good work.

re: The global:: qualifier in C#

samantha ramos — Mon, 16 Nov 2009 10:29:59 GMT

what is a qualifiers use in a sentence?

pleas help me i really need it

re: No more hacks for the MS AJAX’s binding problem

luisabreu — Sat, 14 Nov 2009 11:34:49 GMT

Thank Dave...he's the one that spotted the problem :)

re: No more hacks for the MS AJAX’s binding problem

Andy — Sat, 14 Nov 2009 09:35:33 GMT

Brill. Thank you. All my "body" properties will from now on be renamed "bodyText"!

No more hacks for the MS AJAX’s binding problem

ASPInsiders — Fri, 13 Nov 2009 10:28:36 GMT

At least, when the RTM version is released! Ok, I guess you need some context: in the previous post ,

No more hacks for the MS AJAX’s binding problem

LA.NET [PT] — Fri, 13 Nov 2009 09:46:36 GMT

At least, when the RTM version is released! Ok, I guess you need some context: in the previous post

No more hacks for the MS AJAX’s binding problem

LA.NET [EN] — Fri, 13 Nov 2009 09:26:37 GMT

At least, when the RTM version is released! Ok, I guess you need some context: in the previous post

re: MS AJAX: bindings and serialization

Andy — Thu, 12 Nov 2009 11:07:09 GMT

Yes, I assumed __msajaxdispose and __msajaxbindings would be only added to dom elements. But I think it's a quirk of nested DataViews these get added to the actual data object. Or certainly with the bindings as in this test case, with the Beta/0910 library version.

re: MS AJAX: bindings and serialization

luisabreu — Thu, 12 Nov 2009 09:25:14 GMT

hum...Andy, I'm not sure if I follow...I mean, I was under the impression that __msajaxdispose is added to UI elements (ie, HTML elements)...am i wrong?

re: MS AJAX: bindings and serialization

Andy — Wed, 11 Nov 2009 21:40:09 GMT

Cheers for the Cleanup/Restore thoughts. Will give it a go.

My current prototypes remove the bindings and dispose properties, then re-add a dispose array. It's a fix of sorts for the current Library Preview! Seems like aspects of the binding and component model could cause trip-ups when used with other frameworks.

var data = view.get_data();

Array.forEach(data.content.sections, function(e) {

delete e.__msajaxbindings;

delete e.__msajaxdispose;

});

$.ajax({

type: "POST",

contentType: "application/json",

url: "/document/put",

data: Sys.Serialization.JavaScriptSerializer.serialize(data),

success: onSuccess,

error: onError

});

// if refresh call needed in app __msajaxdispose must be an array

// MicrosoftAjaxComponentModel.debug.js line 1173

Array.forEach(data.content.sections, function(e) {

e.__msajaxdispose = [];

});

view.refresh();

re: The AdoNetDataContext object: what about saving?

luisabreu — Wed, 11 Nov 2009 14:33:49 GMT

Yes, writing it in a reusable manner is not that easy...I guess you could always reproduce the serialization code used by the serializer and adapt it so that it doesn't copy the properties...