C1/Mescius installation folder and Nuget package source

C1/Mescius installation folder and Nuget package source

Posted by: wknauf on 16 January 2024, 2:21 am EST

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 2:21 am EST - Updated 16 January 2024, 2:26 am EST

  Hi C1,

  the latest installer changed the installation folder from “C:\Program Files (x86)\ComponentOne” to “C:\Program Files (x86)\MESCIUS\ComponentOne”.

  But in Visual Studio, I still see a Nuget package pointing to this old directory. Should it point to the new directory and was forgotten by the installer?

  

  744×674 22.8 KB

  Best regards

  Wolfgang

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 3:44 pm EST - Updated 16 January 2024, 3:49 pm EST

  Hello Wolfgang,

  It is quite strange, as at our end the new location of the ComponentOne Local package is updated.
  
  Please see the attached screenshot for reference.

  We request you to please repair the installed version once again with the latest installer and let us know if it gets fixed.
  
  https://developer.mescius.com/componentone/download

  Regards,
  
  Prabhat Sharma.

  

  2695×1174 97.3 KB

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 16 January 2024, 6:15 pm EST - Updated 16 January 2024, 6:20 pm EST

  OK, there seems to be a problem if the user that installs C1 is a admin user, while the developer has a regular user account.
  
  I logged in to my computer with admin user, and here I see a machine wide package source:
  
  

  

  743×434 16.3 KB

  
  
  My own user does not have this, as shown in my initial screenshot.

  Strange that my own user does not have an entry “machine wide package sources”.

  So it is safe to remove the old “ComponentOne” package source?

  I assume the missing Mescius package source is not really a problem - Visual Studio will download the packages from Nuget central, so it would be just s small delay compared to the local package source.

  Best regards

  Wolfgang

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 17 January 2024, 5:41 pm EST

  Hello Wolfgang,

  We have tested with the normal user account at our end and it is showing the correct information as there is in the admin user.

  >>So it is safe to remove the old “ComponentOne” package source?
  
  Yes, you can remove the old “ComponentOne” package source.

  Regards,
  
  Prabhat Sharma.

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 17 January 2024, 9:31 pm EST

  After removing the old package source, Visual Studio displays the machine wide source for me again.

  The reason seems to be that the old user specific package source had the same key “ComponentOne Local” as the machine wide source, so that it overwrote/hid the machine wide source.

  I don’t know who created the user specific package source - maybe some rather old installer, or it was me ;-)…

  So we are done now. Thanks for the support!

  Best regards

  Wolfgang

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 17 January 2024, 9:34 pm EST

  By the way: the installer of 20233 did not clean up the old package source folder in “C:\Program Files (x86)\ComponentOne\Packages”, I see the packages for .611 and .620

• 

  nitin.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 18 January 2024, 11:16 pm EST

  Hi Wolfgang,

  Thanks for the information. The old path isn’t removing while installing from the new installer.
  
  The concerned team will look into this and will fix this issue.

  Regards,
  
  Nitin