Hi David,
Thank you for the additional information.
The only scenario that is known to us to cause this behavior of the designer is when NoXaml dlls are used and the xaml files are not merged. Having in mind the information about the binaries you are using, I would kindly ask you to check again all of the binaries. Let me explain why I ask this of you: when a Telerik project is created - Telerik.Windows.Controls and Telerik.Windows.Themes.Office2013 dlls are automatically referenced, and Telerik.Windows.Controls is NoXAML.If you add other assemblies, the designer would stay empty, because the theme's xaml files are not yet merged for all assemblies. So, if in your scenario you're creating a Telerik project, this may be the explanation for the blank designer - please confirm whether this is the case.
If you are using XAML files and the designer is still blank, maybe there is something left cached by Visual Studio. To ensure everything with the references is ok, you can try the following:
http://www.telerik.com/blogs/xaml-theming-implicit-styles-versus-stylemanager
Hope this helps.
Regards,
Geri
Telerik by Progress
Thank you for the additional information.
The only scenario that is known to us to cause this behavior of the designer is when NoXaml dlls are used and the xaml files are not merged. Having in mind the information about the binaries you are using, I would kindly ask you to check again all of the binaries. Let me explain why I ask this of you: when a Telerik project is created - Telerik.Windows.Controls and Telerik.Windows.Themes.Office2013 dlls are automatically referenced, and Telerik.Windows.Controls is NoXAML.If you add other assemblies, the designer would stay empty, because the theme's xaml files are not yet merged for all assemblies. So, if in your scenario you're creating a Telerik project, this may be the explanation for the blank designer - please confirm whether this is the case.
If you are using XAML files and the designer is still blank, maybe there is something left cached by Visual Studio. To ensure everything with the references is ok, you can try the following:
- Check references paths: all assemblies should be of the of the same type and version and should be referenced from the same location - the Telerik installation folder is best, i.e. \Binaries.NoXaml\WPF45 for example. This guarantees there would be no mismatch in dlls.
- After you are sure everything is ok with the paths, you can unload the project and delete bin and obj folders in the project's folder. Then you can reload the project, clean and rebuild it. This guarantees no cached dlls are left.
- The designer cache can sometimes cause trouble too. You can clear designer cache by deleting all subfolders in C:\Users\[user]\AppData\Microsoft\VisualStudio\14.0\Designer\ShadowCache
Please try the suggested and let us know the outcome.
If the described behavior persists, we would greatly appreciate a video displaying the creation of the project, adding references and code, just to be sure we're on the same page and are not missing something.
As for your question regarding the use of NoXAML assemblies - we have quite a detailed blog post on the topic, it should answer your questions. You can check it here:If the described behavior persists, we would greatly appreciate a video displaying the creation of the project, adding references and code, just to be sure we're on the same page and are not missing something.
http://www.telerik.com/blogs/xaml-theming-implicit-styles-versus-stylemanager
Hope this helps.
Regards,
Geri
Telerik by Progress
Do you need help with upgrading your AJAX, WPF or WinForms project? Check the Telerik API Analyzer and share your thoughts.