As we are constantly trying to make the Telerik OpenAccess ORM learning resources and documentation better and easier to use, we have made some changes that you might find very useful. Getting Started Videos Recently we released two sets of entry level videos on working with Telerik OpenAccess ORM. You can choose your scenario between Database First or Model First approach the short series of 2-3 videos will guide you from creating your model to updating your changes to/from the database. Check them out and don't forget to LIKE them. Feel free to post some feedback about your learning experience either here or in YouTube! Online...

One of the lesser talked about and yet really useful features of the Beta 2 release is the introduction of Kendo UI models and the concept of “syncing” with the Kendo UI DataSource.  It was mentioned briefly in the Beta 2 release announcement last week. One of...

In the past, most developers’ approach to code is that you should write it once and hopefully never have to debug or revisit it again. This stems from the traditional waterfall approach of software development where we were trying to completely describe the entire system up front perfectly. Change was bad and bugs were not accounted for and left for the end. The Agile movement ushered in the first change to this mentality. Agile introduced the concept of refactoring, or writing your software once and then revisiting it (often if needed) and restructuring its internals for improvement (without changing its external outputs). Refactoring is a core tenant of test driven...

I’ve just posted up a new video on Telerik TV to help folks working in Silverlight understand how to automate tests around popup child windows: Automating Silverlight Popup Child Windows with Test Studio Make sure to view the video in HD for best clarity! About the author Jim Holmes Jim Holmes has around 25 years IT experience. He is co-author of "Windows Developer Power Tools" and Chief Cat Herder of the CodeMash Conference. He's a blogger and evangelist for Telerik’s Test Studio, an awesome set of tools to help teams deliver better software. Find him as @aJimHolmes on Twitter.

Raise your hand if something similar to this has ever happened to you: You write a functional test that uses your system’s UI to create a user. You automate navigating to the proper screen, you get all the right values filled in, the Submit button gets clicked, and you do a check for the “User created!” message. You run the test a couple times to make sure everything’s working smoothly. Things look good, so you check it in to source control, where it gets wrapped in to your regular automation runs. Shortly after a new bug gets filed stating newly ...