>Hi Frank,
>
>I've been distributing Telerik WPF controls via regular Setup projects.
>
>Occasionally version conflict may occur. This is when your main project refers a newer Telerik assembly but the setup includes the old one.
>
>Some Telerik assemblies may need to be included in Setup project manually; an example is Telerik Reporting Runtime.
>
>If the main application exits with an error right after the start, it may indicate assembly version conflict or missing assembly. Windows Event Viewer helps in this case.
>
>Telerik library updates should be treated with utmost caution. Never update without sufficient reason, e.g. new important functionality released, essential bugs fixed.
>
>Telerik is known for releasing versions with bugs, though not often. I remember about a year ago a new release came with broken Print function in Reporting assembly. Imagine your customer being unable to send reports to printer. To Telerik's credit they reacted promptly by making an internal build available for downloads.

Thanks Anatoliy,

I didn't even know you could create Setup projects. I've just been manually copying over the necessary files.

I'll be on the lookout for the version conflicts.