You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 19, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 19, 2019. It is now read-only.
[Documentation] Document decision for Shims versus other technologies #633
I am wondering why you aren't simply using shortcuts, soft or hard links instead of the generation of shim executables. This seems to be a much simpler way with less complications.
Apologies if I don't give you a direct answer but after answering the question several times already (all are searchable and readily readable) - I think we just need to document it on the wiki.
changed the title [-]Question about shims: Why not just a shortcut or hard link?[/-][+][Documentation] Document decision for Shims versus other technologies[/+]on Dec 3, 2014
Activity
ferventcoder commentedon Dec 3, 2014
Apologies if I don't give you a direct answer but after answering the question several times already (all are searchable and readily readable) - I think we just need to document it on the wiki.
[-]Question about shims: Why not just a shortcut or hard link?[/-][+][Documentation] Document decision for Shims versus other technologies[/+]ferventcoder commentedon Dec 3, 2014
Also, questions work out much better on the mailing list - chocolatey at googlegroups dot com.