Vanishing combobox

4 posts, 0 answers
  1. Nathan
    Nathan  avatar
    2 posts
    Member since:
    Jan 2015

    Posted 16 Dec 2015 Link to this post

    Upon merging latest code from our main development branch I realized that every edit-enabled RadComboBox on our application had vanished.  We use the Windows 7 theme via implicit styles with UI for WPF 2015.3.1104.45.  VS 2015's Live Visual Tree showed the controls and all simple combo boxes (no editing) worked as normal.   I went back in time until I found the changeset that broke the code and found that the references had indeed changed but not in any way that seems like it should break anything.  I compared loaded modules for the working code and the broken code and the exact same Telerik assembly dll's are loaded from the exact same location.  As best I can tell ONLY combo boxes are not drawing. I keep thinking I am missing something really obvious here.  Any ideas?

     

    Thanks,
    Nathan

  2. Nasko
    Admin
    Nasko avatar
    587 posts

    Posted 17 Dec 2015 Link to this post

    Hi Nathan,

    We tried to reproduce the observed by you issue on our side, however we were not able to due to the specificity of the scenario. From the provided description it seems the editable RadComboBoxes does not apply their Template and because of that they are not visualized. As this is specific to your scenario we could only guess what is causing it - it could probably be caused by some wrong referencing of the binaries. Also, if you have modified the default template of the editable RadComboBox, please check if some change in it might prevent it from applying to the control.

    What you could try to do is to delete bin and obj folders in Windows Explorer and clean and rebuild the solution. Next you need to check if all assemblies are the same version and you are referencing the right one (if they are Xaml or NoXaml binaries). 

    If that does not help we will need a sample project that reproduces the issue or some detailed information how to reproduce it on our side in order to continue our investigation.

    Hope this helps.

    Regards,
    Nasko
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for WPF is Visual Studio 2017 Ready
  4. Nathan
    Nathan  avatar
    2 posts
    Member since:
    Jan 2015

    Posted 17 Dec 2015 in reply to Nasko Link to this post

    Nasko,

    Thanks for the quick response.  This is a perplexing problem but I have learned a little bit more.  It turns out that if my project references look like this the combo box appears:

     

    <Reference Include="Telerik.Windows.Controls">
      <SpecificVersion>False</SpecificVersion>
      <HintPath>..\..\..\Program Files (x86)\Telerik\UI for WPF Q3 2015\Binaries.NoXaml\WPF45\Telerik.Windows.Controls.dll</HintPath>
    </Reference>

    But if I use absolute paths or reference the assemblies in my build folders the combo box vanishes:

    <Reference Include="Telerik.Windows.Controls">
      <SpecificVersion>False</SpecificVersion>
      <HintPath>\Program Files (x86)\Telerik\UI for WPF Q3 2015\Binaries.NoXaml\WPF45\Telerik.Windows.Controls.dll</HintPath>
    </Reference>

    This is very odd.  Both paths are valid and at runtime the exact same assembly dlls are being loaded.  I put the relative paths back in and the problem has gone away but now the developer's working directories must all be basically the same to build the app.

    Regards,

    Nathan

     

  5. Nasko
    Admin
    Nasko avatar
    587 posts

    Posted 20 Dec 2015 Link to this post

    Hi Nathan,

    We are not sure what might be causing this issue. It seems that your solution is trying to load the Telerik assemblies from different locations -  the dll's in your project were referenced from the local installation folder of the UI for WPF suite. This is why I wanted to ask you if you can remove all Telerik assemblies from your solution and add them again from the location where you've extracted them.

    Next unload your project and examine its definition. Specifically, I'd suggest looking at the Reference definitions and if the HintPath is the same for all assemblies. Finally, you can remove this hint path to make sure that all assemblies will be taken from the default Telerik installation on your machine again.

    Hope this will help you.

    Regards,
    Nasko
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top