Ln -s /Volumes/ "New Volume"/ "New Folder" ~/Library/"Application Support"/OldFolderį) Open Application when New Volume is mounted on Mac (appears in Finder) Note: if NewFolder or NewVolume has a space in the name, then quotes are needed for link (ln) command: Note: NewFolder was copy destination on NewVolume in step C) while OldFolder was the folder that was copied: Logos4, Verbum, or Noet ln -s /Volumes/ NewVolume/ NewFolder ~/Library/"Application Support"/OldFolder.Open Terminal (inside Utility folder in Applications).Noet uses ~/Library/"Application Support"/Noetĭ) Rename old Logos4, Verbum, or Noet folder in ~/Library/"Application Support"Į) Create a Symbolic link from the new folder on New Volume to ~/Library/"Application Support"
Verbum uses ~/Library/"Application Support"/Verbum Logos uses ~/Library/"Application Support"/Logos4 MacOS & OS X default is your ~/Library folder being hidden, with many ways to see contents => ī) Make sure Application and its Indexer are NOT runningĬ) Copy your Application Support folder with Resources, Indexes.Not supported (System Requirements) and not recommended due to stability & performance issues by Faithlife.
Use this method to relocate your personal Application Support folder to an external drive. Relocate your folder with Resources, Indexes. ++ refer to Quick Installation onto multiple computers for the default location of Logos/Verbum folders. Execute rd "%localappdata%\Logos" in a Command Prompt.
Start > Run > cmd.exe, or type cmd in the Windows Search box. If it was copied, you must delete the original folder.
It would sure be nice sense VS now has a self healing mode if we could move VS and log in and not get the error message of, your license has expired, when it clearly has not. The system settings set to future and not compatibility.
Its brutal having to re-download every time the system crashes, I have had to reinstall every 2 months, I don't know whats happening in development with windows but do to the constant changes it seems that a lot of dll's are no longer compatible with having
I tried the installing to another drive and yes the install eventually failed, I have tried other directories and they eventually failed as well. I agree Bob there should be a way to move any Visual Studio, I am sure it would save Microsoft bandwidth as well as us, it's a huge file and when you've been doing some work it gets bigger fast.