assembly version mismatch

[Rodion]

Hi,

1. I installed a demo version from a website just to see what controls there are that I can use and it installs a clickonce app with version 2013.2.805.40
2. I install an actual msi from file server which has a separate set of dlls with different version 2013.2.0724.45 (which is supposed to be used for development, not demo)
3. Aparently there isn’t a proper 805 version of msi downloadable from the website
4. When I try to compile my project that uses MSI version I constantly get this
   1. "Could not load file or assembly. Telerik.Windows.Controls, Versrion=2013.2.805.40, Culture=...."
   2. Which is saying that dll I have referenced needs version 805 instead of the one I have 724 even though I never installed 805 other than demo app
   3. There are no references to 805 anywhere in my project, why it wants to link to those dlls is beyond me...
5. When I try to remove demo app (which is supposed to remove any trace of that 805 version), I get the same error
6. When I try a different version msi installed after I blew 805 version (I think I tried 905) I get the same error. One would think that getting a fresh set of dlls without any remnants to 805 left in the system would fix, but no….

Your help is very much appreciated... I'm at a halt stop where I can't use any Telerik controls, and I don't know how to clean it up...

[Rodion]

Could I please get some attention from Telerik staff on this?

Thank you!

[Petya]

Hello,

Thank you for contacting us!

2013.2.805.40 is an internal build version of RadControls for WPF. Latest internal builds are built automatically from our development environment and are shipped only as assemblies, i. e. no .msi files or click-once demos were shipped with that version. Further, there is no internal build with version number 905. That said, I am not sure what exactly you've downloaded or whether you downloaded it from Telerik's website and am having a hard time understanding the fifth point you made - When I try to remove demo app (which is supposed to remove any trace of that 805 version), I get the same error.

Generally, the exception you are facing suggests that conflicting versions of the assemblies are referenced in your project. I suggest you try cleaning and rebuilding your solution. If this does not help, please try removing all RadControls for WPF references from your project, deleting manually the bin and obj folders, adding the needed references again and rebuilding. Note that if your solution contains more than one project referencing Telerik assemblies, you should start rebuilding the projects from the one that does not have any dependencies on the others.

I hope this helps! Let us know how it goes.

Regards,
Petya
Telerik

[Rodion]

Thank you for your reply.

Please see attached screenshot of an error. version 805 is/was out there, I could not have downloaded this elsewhere other than telerik website.

To clarify my "When I try to remove demo app (which is supposed to remove any trace of that 805 version), I get the same error." - basically I'm saying that after uninstalling ClickOnce demo application (version 805) I am still getting that same error.

As for cleaning/removing/recreating references, I have tried that a number of times, I have even gone as far as creating a blank project with only one WPF telerik control on it to ensure isolated environment and was still getting that error.

Also, aside from reference mismatch, that error could also mean that assemblies that I am linking were compiled referencing other strong typed assemblies and version numbers got fused into manifest. Or there are some fancy Emit compilation going on at runtime (which I tend to lean towards) because such behavior is very strange.

Thank you!

[Petya]

Hi,

I am still not sure I understand you correctly. As I said, LIBs are uploaded weekly and you can verify that in your profile. However, our ClickOnce examples are updated only with official releases and there is no 805 version of them.

Overall, our assemblies are indeed strong typed and in a project you should make sure to reference only .dlls from the same version. However, no Emit compilation is executed.

We would highly appreciate if you can open a support ticket and send us the sample project you isolated, i.e. the one containing a single control from the suite but still causing the issue. Thank you in advance!

We're looking forward to hearing from you.

Regards,
Petya
Telerik