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 Jul 15, 2023. It is now read-only.
This is a large secondary disk in this computer. I never understood why MSI based installers are so prone to place temporary and permanent files on another drive. There must be a reason for that.
Here's what was written:
I don't understand why the file times are so old. This drive did not exist at that time. The folder is created at a newer date:
So the file dates probably are not the actual create time.
A procmon trace shows the files are unused.
The VS11Root folder also denies my admin account permissions. So there might be a permissions bug. Update: I found that the System process holds handles to that folder. I have no idea why. So this permissions problem is probably an issue with my machine.
The text was updated successfully, but these errors were encountered:
Same problem. I have G:\VS10Root\Common7\IDE\Extensions\Microsoft\CodeContracts\1.9.10714.2 folder while VS2015 is installed on C: drive (default location). Installer is also launched from C:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After installing Code Contracts I find that it placed files at
This appears to be a bug.
This is a large secondary disk in this computer. I never understood why MSI based installers are so prone to place temporary and permanent files on another drive. There must be a reason for that.
Here's what was written:
I don't understand why the file times are so old. This drive did not exist at that time. The folder is created at a newer date:
So the file dates probably are not the actual create time.
A procmon trace shows the files are unused.
The VS11Root folder also denies my admin account permissions. So there might be a permissions bug. Update: I found that the System process holds handles to that folder. I have no idea why. So this permissions problem is probably an issue with my machine.
The text was updated successfully, but these errors were encountered: