First preview of new Telerik RadWizard for Winforms

As you may know the Telerik Roadmap for Q1 2011 for WinForms includes a long awaited RadWizard control that allows you to break down your complex processes into simple steps, much like installation wizards.

The Telerik Blogs have just released the first visual preview and information about the new RadWizard which can be found in this blog post by the WinForms team.

Resolve Cannot find resource XXX.rlinq embedded in assembly - Telerik Open Access

Just recently, I've been playing with Telerik's Open Access ORM. Now that I have it all set up and working correctly, I find it a joy to use. Unlike the ORMs of old, there is no complex XML configuration. Like an old DBA friend of mine used to say, it's no longer like kicking a whale up a beach.

When I started with it, I went through the on-line tutorial, and follwed everything it said to get my first test solution up and running. but I received an error.

Cannot find resource XXX.rlinq embedded in assembly XXX.

I also noticed that the rlinq diagram had not mapped the types correctly.

After a few attempts, I went to the Telerik Forums, and eventually got my answer. This is an issue that will soon be fixed in the next release, but the workaround is so simple.

In Visual Studio 2010, when you start a new project it adds the project to a temp location until you decide to save the solution in it's 'real' project location (E.g. in your Projects directory).

Simply ensure that you have built and saved your solution before adding your rlinq diagram and it will all work like a dream,

If you experience the error in the screenshot above where the types have not been created correctly, then closing and re-opening the rlinq diagram solves this.

This is due to be resolved in the next release, but until then, I hope someone finds this of use.

Better debugging with RadControlSpy

Telerik controls are simple wrappers and do not implement detailed functionality. Rather, each control has as a direct descendant an instance of the RootRadElement class. This RootRadElement wraps the actual functionality of the control and acts to transfer events to and from the RadControl class.

In turn, the RootRadElement has a descendant tree of RadElement classes that implement the actual logic required by the control. Because of this, when you want to change a property of a RadControl or add a new element to extend it, you will find the RadControlSpyForm really useful.

The RadControlSpyForm is a tool to let you examine the detailed internal structure of any RadControl. It is not a stand-alone tool. Rather, the Control Spy is supplied as part of a library that you compile into your application. After adding this library, you can start the Control Spy and use it to examine and alter properties of any RadControl which is currently running.

So, let's start with a simple scenario. You have a RadListControl on your form, and you change the back color property.

Me.RadListControl1.BackColor = Color.Red

but when you run your application, you see that the back color has not changed.

So, we need RadControlSpy.

• Add a reference to the RadControlSpy assembly. By default, you can find a copy in C:\Program Files\Telerik\Telerik RadControls for WinForms<current version>\Examples\bin
• In your form load event, add the following (VB example)

        Dim form As New RadControlSpy.RadControlSpyForm()

        form.Show()

So, we were able to find the correct area to set the back color for the list control. RadControlSpy is really powerful and is useful for finding out all sorts of information about your RadControls.

Get FREE licenses for the next release of Just Code

Just Code (Telerik's add-in for Visual Studio 2005, 2008 and 2010 that peforms navigation, refactoring and code analysis for C# and VB.Net) is soon to get decompile features that will allow decompilation of both members and types.

Telerik are also giving away free licenses of the next release of Just Code to the first 500 people that send Telerik an e-mail to decompile@telerik.com. No need for any special format - your name and (optional) some ideas on what decompilation features you would like to see most would be welcome.

For more information, see the Telerik Blogs