When using ORM, should always keep in mind that only one object scope is used. The example came with the package doesn't really explain this well. Should always declare a page_init call which declares the object scope and store it in session and try to keep using it for any business operations:
Telerik's RadUpload control doesn't come with many documentation. The default comes with multiple file slots, with add and delete button but sometimes we might only need just one uploader.
When using ORM, after we have setup the business objects, it's useful if we create some generic methods which can be used in many places.
Sometimes, somehow Telerik controls might suddenly not appear in Visual Studio's toolbox. A quick solution would be mouse hover to toolbox, add a new tab, and then choose items. Then point to the Telerik bin file (Telerik.Web.UI) and that should populate all controls into the toolbox.
Telerik ORM (Open Access Mapping) has been a very useful tool, for mapping database structures into object oriented classes, so called Persistent Classes. This saves a lot of efforts in writing up these classes manually. What's more we could add on to it is to use generic methods on standard adding and deleting transaction.