OpenAccess 101 Webinar Follow-Up

Tuesday, April 21, 2009 by OpenAccess ORM Team | Comments 1

Okay, so I am really late in posting this follow-up, but I wanted to make sure those of you who haven’t already noticed know that my last webinar, OpenAccess ORM 101, is up on Telerik TV. If you missed the webinar, or if you just want to see it again, head on over and check it out. Also, for those of you who had questions during the session or who are interested in the demos I showed during the webinar, you can find answers and source code below.

Click here to watch “OpenAccess ORM 101” on Telerik TV

Enjoy!

[Source Code]

[Q&A]

1 Comments

  • Garry Clark 21 Apr 2009

    Kevin,
    I really enjoyed your first webinar and have registered for the upcoming one. However now that I have had tiem to play with OpenAccess a bit more I do have soem questiosn and was wondering if these will be covered in the upcoming Webinar.

    In the last webinar you showed a very quick and simple, yet powerful, example of dropping a Radgrid on to a Webform and having the ORM manage all the updates, deletes, etc... My question though is if I use custom edit forms or I am not using a grid to display my data then how do I go about doing these same types of DB transactions. I can not figure out how to bind my controls to the datasource in other words.

    My next topic I would like covered if possible is the WCF functionality of OpenAccess, which I know in your 101 Webinar you said  that WCF was not nativetly supported by OpenAccess, which is fine I can add the attributes to my classes, but again how do I go abotu getting the data bound to controls and updated again. I read all of the disconnected API stuff about the ObjectContainer, but have been unsuccessful in my attempt to implement this. Also as far as best practices should the DAL be located in my WCF Service or should this be split out?

    Hopefully these questions make sense and again thank you for your wonderful webinars. I find them very helpful!

Add comment

  1. Formatting options
       
     
     
     
     
       
  2. (optional, emails won't be shown on public pages)
  3. (optional)