The AdoNetDataContext object: what about saving?

Comments

# william apken said on Monday, November 09, 2009 5:52 PM

Great job. Sorry to see it end.

# william apken said on Monday, November 09, 2009 5:59 PM

I would like to see authentication services provided by MS Ajax.  How they work with the AdoNet Data Service and  RESTful services.

If I understand it correctly, you can set permissions when you create the AdoNet Data Service.

Then base upon permissions granted, AdoNetDataServices will only return the items that this user has permission to view.

I have not tried this yet. I'm not sure, but I think I saw this in a video by Pablo Castro. (this may not be his name, but I think it is close).

Just an idea.

# Scott Wade said on Monday, November 09, 2009 6:44 PM

And idea for a topic...is something I'm not finding very much information on yet:  How to correctly incorporate custom scripts for use with the new Script Loader in the Microsoft Ajax Library Preview 6, and related, how to both load and use the Ajax Control Toolkit scripts-only through the Script Loader and the exact syntax needed when using Sys.require() for each of the controls, with examples being used with Preview 6 using imperative syntax instead of any declarative syntax.  

# luisabreu said on Tuesday, November 10, 2009 6:53 AM

William, i think that should "just work". doesn't it?

Scott, I think that you should wait a little more because I expect that the ACT will be added in the near future. In other words, I expect that when MS AJAX is released, we'll have the client files for ACT updated so that they can be used with the script loader. If you can't wait, then I think I've written a post that shows what you need to do do adapt your script files so that they can be used by the script loader. You'll have a little bit of work though because you'll have to get the ACT client files dependencies right...

# william apken said on Tuesday, November 10, 2009 9:34 AM

Access to all ACT would be cool for sure.

I have not tried to use the MS Ajax ApplicationServices yet. So I don't know.

Still putting the final touches  on my dataView implemented as a component.

My next step will be trying to implement a formComponent and the first case I want to test is a login form that require no postbacks.

Then on to my question about integration of authentication and AdoNetDataContext.

Do you think we will see a preview 7 or will we finally get a beta?

# Andy said on Tuesday, November 10, 2009 12:02 PM

Great series. Have followed your hints to use the new DataView.

I'm having problems using the JavaScriptSerializer with data from DataView.get_data() with nested DataViews, as proxy properties on the model data such as __msajaxbindings and __msajaxdispose cause circular references.

Have you come across this? What's the best way to get the JSON raw output from nested DataViews? As I'm using jQuery.ajax requests, not the DataContext/Proxy.

# luisabreu said on Tuesday, November 10, 2009 3:00 PM

William,  I'm almost positive that you can simply apply asp.net security to your services and everything should just work out.

Andy, can you be more specific? The properties you mention end up being added to the HTML elements, not to the data...Can you build a small demo and put it here? or send it to me by mail and I'll try to take alook...

# Andy said on Tuesday, November 10, 2009 4:34 PM

Hope the below formats OK! Thanks for any help.

Nested templates:

<div id="edit" class="sys-template">

<form onsubmit="return false;">

<label>Title</label>

<input sys:value="{binding title}"/>

<div sys:attach="dataview"

dataview:data="{{ $dataItem.content.sections }}"

class="sys-template">

<label>Body</label>

<textarea>{binding body}</textarea>

</div>

<button onclick="onSave()">Save</button>

</form>

</div>

<div id="maincontent"></div>

JSON:

var instance = { title: 'New document', content: { sections: [ { body: 'Enter text here' } ]};

Init:

var view = Sys.create.dataView("#maincontent" , { itemTemplate: '#edit', data: instance});

The problem:

When view.get_data() is called, each of objects in the "sections" array have __msajaxbinding and __msajaxdispose properties. This means that Sys.Serialization.JavaScriptSerializer.serialize(view.get_data()) fails, complaining of circular references.

Am I binding the "sections" incorrectly?

# luisabreu said on Wednesday, November 11, 2009 3:57 AM

Oh, the bindings...right :)

You're absolutely right here. The only thing I can think of is cloning the objects without using the __ms props...I'm saying this because it looks like the client serializer will always serialize everything by default and it seems like there's no way to pass a list of non-serializable props...

# luisabreu said on Wednesday, November 11, 2009 4:00 AM

btw, one more observation: why are you putting a form inside the template?

# Andy said on Wednesday, November 11, 2009 7:40 AM

Yes, the form element isn't needed. It's as I was testing out JSON and traditional HTTP Post payloads. There are multiple edit templates on the page.

It's still tricky trying to clone the data object, or at least in a generic way for any entity type, as the quick way to clone the data object I tried via jQuery.extend(true, {}, view.get_data()) similarly errors due to the circular references from the __msajaxbindings.

Yes, it certainly would be good in the Microsoft Ajax Library to have either JavaScriptSerializer or a (deep) clone method that take a list of properties to ignore.

# luisabreu said on Wednesday, November 11, 2009 8:33 AM

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...

Leave a Comment

Title (required) 

Name: (required) 

Website: (optional)

Comments (required) 

Remember Me?