ADO.NET Data Services (Astoria) in Visual Studio 2008 SP1
- Posted: Oct 21, 2008 at 1:07 PM
- 53,249 Views
- 3 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
This just seems to me an abstraction layer on top of WCF for people that don't or cannot learn WCF, that want all the "magic" to happen in the designer.
I will have a look again at EF in Visual Studio 10.
2. When you do a Demo like this, it would be great if you cna do a White Board with a small diagram about what you are going to Demo (Bth, this is something your team can suggest to all presenters). Picture speaks 1000 words
3. Saaid Kahn - I personally believe you could have slowed down a little with your Demo Speech, I could barely catch some of the words what you said (sorry, no offense we all are learning
4. My 2 cents - Write down in a small piece of paper (or 3x4 Index cards) in what exactly you are going to Demo & go step-by-step, that will make things easy to understand.
I have just started using this technology mostly because I want to move toward web services. I played with web services in the past trying to serialize data for client side Javascript (JSON), which was difficult at best (it was easier to code it by hand). This seems useful in that you can create a diagram (edmx ADO.NET Entity Data Model) to represent your tables and relations, point this web service to it (svc ADO.NET Data Service), and bingo, instant serialized access to all the data.
Then, you can use Atlas (Microsoft Ajax) to do CRUD (create retrieve update and delete) operations within Javascript at the client browser without knowing a lot of what you are doing. Of course, if you get to this point, you probably know how to do these things anyway. This means you can create a Javascript variable, point it to the database "context" (or in this video, the "service:"), and have array access to records and object access to fields.
It's pretty cool stuff when you don't want all the details of coding, but isn't that the point of abstracting these technologies anyway?
Remove this comment
Remove this thread
close