I’m sorry, but I couldn’t resist sharing this with you guys (especially if you’re a soccer fan ; ) ). btw, he’s my nephew…and yes, I’m proud :)

In one of the previous posts of the series, we’ve seen how easy it is to build a master-detail scenario with the help of the new DataView control. Today, we’ll keep looking at it and we’ll see how we can build an editable grid. The next two images explain the objective of our post. The first shows the grid in browse mode while the second illustrates what it looks like in edit mode: As you can see, the idea is simple: any row can be in editing or browsing mode (notice that we can only edit one row

One of the cool features MS AJAX preview 6 introduces is better JQuery integration. From now on, MS AJAX components (which have been defined through a script info object registered through a defineScript(s) method call) are exposed as jQuery plugins. This means that you can write something like this: < head runat = "server" > < style type = "text/css" > .sys-template{ display:none; } </ style > < script src = "Scripts/MicrosoftAjax/start.debug.js"

Does it again ! Fantastic come back from the best rally driver of all times…just watch this if you have any doubts…

We can reuse our knowledge of the previous post to create a master-detail scenario. The idea is simple: we configure our master DataView to show all the elements and then we add a second DataView control that will only show the details of the current selected item on the master DataView. I will spare you from long texts and I’ll jump right away into some code (I’m adapting the code from the previous post ): < body xmlns : sys = "BLOCKED SCRIPTSys" xmlns : dv = "BLOCKED SCRIPTSys

As you recall, I’ve started writing about ASP.NET AJAX during preview 5. Meanwhile, preview 6 was out and there were some changes which might break your code. One of the things which changed is the in which way you indicate controls and components declaratively. With preview 5, you’d use only a string which identifies the ID of the control or component. From preview 6 onwards, you’re supposed to use # prefix to indicate an HTML element search by ID and $ prefix to indicate that you’re searching a

In the previous posts , we’ve met commands and saw how to use them from within a DataView control.What I didn’t mention at the time was that the DataView control understand commands named select. In other words, the DataView understands that type of commands and reacts to them by setting the current selected item. Currently, the DataView control exposes several properties related with setting the current selected item: initialSelectedIndex: used for setting the index of the default current selected

This is becoming quite a long series, but what can I do? There’s simply lots of things to talk about in the new MS AJAX preview 6. As you probably recall (if you’ve been following along since I’ve started writing compulsorily about MS AJAX), we started with code written against preview 5 and then moved to preview 6 when it was released. One of the new helpers I’ve been using is the new Sys.create object. This object contains several shortcuts for creating components. For instance, in the previous

Now that you already know what a command is and how to use them in a declarative scenario, it’s time to keep going and see how we can use them from an imperative only approach. You already know how to “define” templates from JavaScript, so I guess we can concentrate on seeing which JavaScript code we need to generate commands. If you’ve used a debugger with the previous sample , then you’ve probably noticed that sys:command attributes (and friends) get transformed into  a Sys.UI.DomElement.setCommand

The DataView control supports the concept of a command. In practice, you can think of a command as a “fancy event” which is generated by MS AJAX controls in response to a DOM click event. Commands have an advantage over traditional DOM event handling: for instance, you can easily pass additional information that will be processed by a command hander. Lets start with a really simple example: < head > < title ></ title > < script type = "text/javascript" src = "Scripts