Upgrade Wizard Creates lib Directory

4 posts, 0 answers
  1. Joel Palmer
    Joel Palmer avatar
    175 posts
    Member since:
    May 2009

    Posted 29 Oct 2013 Link to this post

    Can you explain to me the purpose of creating the lib directory during an upgrade?  This seems to be a new way of operating and it creates havoc with the projects that are shared between multiple solutions.  If I upgrade solution 1 it creates all the reference files then updates the references for project 1 pointing to that directory.  If I upgrade solution it creates another set of the same files but now project 1 points to the new directory.  Shouldn't it just point to the GAC reference?

    Also, this means that every solution ends up adding the same files to Source control because "everything in this directory" belongs in there.
  2. Yana
    Yana avatar
    4973 posts

    Posted 31 Oct 2013 Link to this post

    Hi Joel,

    Thank you for contacting us and sorry for the caused inconvenience.

    You can prevent copying the assemblies in a local lib folder by unchecking the "Add referenced assemblies to solution" option in the Upgrade Wizard (check the attached screenshot). Note that this setting is preserved and it will not be needed to un-check it for each project.

    I hope this helps.

    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. Geovani
    Geovani avatar
    5 posts
    Member since:
    Feb 2014

    Posted 30 Aug 2018 in reply to Yana Link to this post

    Is it possible to configure the upgrade wizard to use an existing directory other then "lib" for example we keep all our 3rd party dependencies in the Library folder (structure below)

    Project Root  - Library - RCWF - 2018.2.621

                          - Component - Component Files

    When ever we upgrade; the wizard creates a lib folder at root instead of finding the old files inside Library - RCFW - XXXX.X.XXX and upgrading the files in that directory; see screenshots 


  4. Nikola
    Nikola avatar
    49 posts

    Posted 31 Aug 2018 Link to this post

    Hello Geovani,

    The Visual Studio extensions depend on the file structure you have described in order to manage the product versions installed. For the time being, we do not plan to allow for customization of the lib folder. As things are you can either use the structure that the extension creates and then place the other 3rd party assemblies in the lib folder or manually substitute the assemblies in the RCWF folder.

    In case you have any other questions we remain at your disposal.

    Progress Telerik
    Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Back to Top