Are the DLLs Installed to GAC?

12 posts, 0 answers
  1. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 28 Nov Link to this post

    Hi,

    I am setting up a new development machine--brand new install of Windows and Visual Studio. When I install the UI for WPF package, it does not install the assemblies into GAC. They don't show up in the reference manager. However, the Reporting tools for WPF show up fine. Other existing environments that we have on other machines have them installed in GAC and they automatically show up in the references list. Am I missing something?

    I am using VS 2017 v15.4.5

  2. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 28 Nov in reply to Ben Link to this post

    Literally immediately after I posted this, I removed a Telerik reference that wasn't found and VS 2017 flickered and refreshed the references. They are all showing up now. Seems it was just a VS 2017 issue.
  3. Nikola
    Admin
    Nikola avatar
    19 posts

    Posted 29 Nov Link to this post

    Hi Ben,

    First of all I am glad you were able to resolve the issue.

    For the Telerik UI for WPF product we do not add any assemblies in the GAC. We register the folders containing the assemblies under the following registry keys based on the .NET Framework version:

     - HKCU\Software\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx
     - HKCU\Software\Microsoft\.NETFramework\v4.5.50709\AssemblyFoldersEx

    Perhaps there was a problem loading the assemblies from the registry into the Reference Manager. If the problem occurs again or you have any other questions we remain at your disposal.

    I am looking forward to your reply.

    Regards,
    Nikola
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
  4. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 29 Nov in reply to Nikola Link to this post

    That makes more sense. Thanks for the clarification.
  5. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 29 Nov Link to this post

    Actually, I still seem to be having issues with this. The references are somehow recognized now (I can build my project) but Visual Studio designer is showing errors. I went to re-add all Telerik references and they are not showing in the Reference Manager. I just went to the location you mentioned above and it is empty. I do not have any subkey called .NETFramework under HKCU\Software\Microsoft.

    Perhaps the installer does not create this .NETFramework key if it is missing? The ReportViewer assemblies are still showing fine. Are they registered with Visual Studio differently?

  6. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 29 Nov in reply to Ben Link to this post

    I found the location of the Reporting assemblies atComputer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\Reporting R3 2017 SP1

    however there is no similar subkey entry for the Telerik UI for WPF assemblies in any of the .NET Framework version keys.

    I checked the locations you mentioned above for 64-bit keys as well and found nothing.

     

  7. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 30 Nov Link to this post

    Hi there,

    I inspected the installer and it appears the registry keys are only installed for VS 2015 and lower. My development environment only has VS 2017 Community. There is no entry in the FeatureComponents table of the UI for WPF installer that would install these registry keys.

    More details for your developers:

    From what I can gather from the MSI, the registry keys are added by the components DotNetFrmAssemblyFolders40 and DotNetFrmAssemblyFolders45. These are included with each Visual Studio Extension Feature offered by the installer except the Visual Studio 2017 extension feature(s). The name of the feature in my case is TelerikVSExtensionsVS2017Community but there are also features defined for the Professional and Enterprise versions of VS 2017. Therefore, my machine that only has VS 2017 doesn't get these keys and the references are not shown in the Reference Manager.

     

     

  8. Nikola
    Admin
    Nikola avatar
    19 posts

    Posted 30 Nov Link to this post

    Hello Ben,

    Thank you for taking the time to look into the problem and provide more details. 

    I can confirm that the observed behavior is a bug on our side. I have already logged an item in our backlog and we will provide a fix with one of the upcoming releases. I have added 2000 points to Your Account for the effort you put into investigating the possible cause for the issue.

    On a different account you can find the assemblies we add under the AssemblyFoldersEx registry key in the {InstallLocation}\Telerik UI for WPF R3 2017\Binaries (Binaries.NoXaml) folder. You can Browse to them and add them to the Reference Manager this way. 

    Also I would like to ask you for more details regarding the Designer errors you mention in one of your previous posts. The errors might be due to the Xaml assemblies being used in the project as they do not get full design-time support as the NoXaml assemblies as outlined in this documentation article. Yet without more details I would not elaborate further.

    I am looking forward to your reply.

    Regards,
    Nikola
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
  9. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 30 Nov in reply to Nikola Link to this post

    I'm not sure why, but when I first set everything up, Visual Studio seemed confused about the references. It gave me errors that went something like "RadButton could not be set to type object of type RadButton" and it was not rendering any Telerik UI controls.

    I do not believe it was a Telerik issue, I think it was a VS 2017 issue. It is not clear if it was an issue with the Telerik references not appearing in the Reference  Manager or not, but it should have been working regardless. Once I got the references showing up properly (I manually added the registry keys), I then deleted any cached Visual Studio data for my project (the .vs folder and any bin and obj folders) and rebuilt everything. Now it works fine.

     

    A side note: I'm finding that Visual Studio 2017 aggressively caches data about projects (they are trying to make it run faster), but they have a number of bugs to work out. When new classes are pulled from git or any odd issue occurs with references, VS2017 will often not refresh the cached data for intellisense properly and display all sorts of odd errors that are not actually errors. Issues like this are among the top voted issues in their user feedback. For example: https://developercommunity.visualstudio.com/content/problem/141635/switching-branches-in-git-breaks-intellisense.html

  10. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 30 Nov Link to this post

    Oh and thanks for the follow-up and points!
  11. Ben
    Ben avatar
    11 posts
    Member since:
    Mar 2017

    Posted 30 Nov Link to this post

    Oh and thanks for the follow-up and points!
  12. Nikola
    Admin
    Nikola avatar
    19 posts

    Posted 04 Dec Link to this post

    Hi Ben,

    I am glad you were able to resolve the problem at your end.

    The issue might not be caused by our controls directly yet it might have not occurred at all if the registry entries were added. This is an oversight at our side as the behavior is inconsistent with previous Visual Studio versions. 

    Also I would like to thank you once again for the continuous effort you put into looking up details about the possible cause of the problem. Your suggestions are much appreciated and we will take them into consideration while developing the fix.

    In case you have any further question do not hesitate to get back to us.

    Regards,
    Nikola
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
Back to Top