0
Previously, I kept authored code in a folder inside Program Files.
By "code" I mean any kind of code you, as a programmer, would write.
However, with the new permission model in Windows 8.1, storing files there requires elevated sessions for PowerShell (for example) when running commands that change folder contents (file removal, edits, creation).
As such, where would a good place to store code be?
The Unix model would suggest to store it under your user documents, ~/user/username/documents/.
Any suggestions for Windows systems?
EDIT: Hopefully, made the question clearer.
Francisc
Posted 2015-09-01T12:49:37.067
Reputation: 967
2What do you mean by "code"? I'm a software developer and to me, "code" means "uncompiled source code". I'd never store that in Program Files, nor would I store it in ~/user/username/documents, so perhaps I'm confused. – ChrisInEdmonton – 2015-09-01T12:51:59.753
i see nothing wrong with
C:\Users\You\. This is the place where you have access rights by design. If you are using system that you share with others, keep your stuff under mentioned path. If you are and admin and the computer is private, use any path you want outside of the system restricted directories. – mnmnc – 2015-09-01T13:00:20.190Codemeans anything you author, uncompiled if it's a language that requires compilation for example. – Francisc – 2015-09-01T13:01:24.8971What bothers me about
C:\Users\Youis that's where crap like Microsoft pictures, and Games are automatically created. It's sort of like a place where there's junk created by the OS and other apps, to me anyway. – Francisc – 2015-09-01T13:02:21.697It seems that your "code" is referring to powershell, bash or cmd scripts. You can put them where you like. How about
%USERPROFILE%\documents\scripts? – DavidPostill – 2015-09-01T13:03:52.870That's not true, PowerShell and bash are mentioned as things that perform actions on folders. – Francisc – 2015-09-01T13:04:53.637
1I tend to use c:\source so that in the rare cases where a fully qualified path is required it evaluates the same on each team members box, and is easy to access. We do occasionally have trouble when a teammate puts their code within their profile, and isn't careful about how they handle pathing when submitting the code to source control for other developers to access. Additionally only certian user accounts may be used to merge to specific branches (like release) and in that case the developer must access their code under a differant user account, so user isolated storage is an impediment. – Frank Thomas – 2015-09-01T13:39:43.517
To be fair, you have had to elevate permissions when running something out of Program Files, since Windows Vista not just Windows 8.1. – Ramhound – 2015-09-01T14:04:15.677
Yeah, but using the RunAs dialog would start any program with Admin privileges. – Francisc – 2015-09-01T14:37:19.210