When I installed Visual Studio, it also placed hundreds of files on my external hard drive. And now the folder structure is full of "junk" that I don't want.
Is it safe to delete these files? Will deleting these files affect my Visual Studio installation (which is on a different disk) at all? Why does VS do this anyway? Why does it place all this crap on a drive I never even gave it permission to put it on in the first place?
You can safely delete any of those files, since, quoting Microsoft KB,
These temporary files are erroneously generated by the installer into the root directory of one of your drives, instead of the temp directory
Those are temporary files indeed and they, still quoting Microsoft,
are generated on the root directory of a drive that has the largest available space in the system
Check Microsoft knowledgebase pages like this for more detail.
What about archiving those files, opening visual studio and check it is still working?
If it doesn't just put the files back where they were...
You should be safe deleting those files. Someone already asked this question. :D
Visual Studio 9.0 Beta Program files in C:\
hope I was helpfull
Jasper.
Cause
These temporary files are erroneously generated by the installer into the root directory of one of your drives, instead of the temp directory.
Resolution
These files are unnecessary and can be safely deleted from the system. The functioning of the runtime library will not be affected by this.
Its a known bug and is fixed in VS2008 SP1.
Ref: https://support.microsoft.com/en-us/kb/950683
Related
I am currently working on a VS Extension that stores solution-specific metadata to a SQLite (.db) file.
Can (and should) I be storing this in the new (as of VS2015) .vs folder that sits alongside the .sln file? Or is this storage location meant for Microsoft'y, internal visual studio'y things only?
Is there a special API or anything that needs to be utilized or can I just dump a load of files and folders in there?
I've searched and not found any real info about extension development and the utilization of that folder.
Thanks!
Should my VS Extension use the “.vs” folder?
Personally, you can use .vs folder but not recommend.
Indeed, there is no specific documentation for the folder .vs. AFAIK, this .vs folder was not invented by the Visual Studio developer team. It is there because someone asked for it. and many other Visual Studio users on the Visual Studio UserVoice page. The IDE team looked at it, thought it through, accepted it and implemented it. This should be the reason why there is no specific documentation for this folder.
Usually, .vs folder is required by Visual Studio to store opened documents, breakpoints, and other information about state of your solution. So, it looks like a normal folder without any other special restrictions, you could use it.
But this .vs will sometimes be deleted and regenerated to solve some issue, and the folder is not intended for source control, source control ignore this .vs folder by default. So, it should not the best solution to use .vs folder.
Is it safe to delete performance session files for Visual Studio 2012?
I did profiling, and removed the session files only from the project but
they were not deleted from the project directory. Now I have huge files, around 8 GB
with extensions .psess, .vsp and .vspx, and I am not sure if it is safe to manually delete
them.
Yes, if you no longer need your performance reports, you can delete them. You can either delete them from the file system directly or, if you prefer using the Performance Explorer in Visual Studio, you can delete your reports from there as well.
If they are removed from the project, and the program still works normally, you should be safe to delete them. If you want to be safe about it, try moving the files to a temporary folder and see if it messes things up without it. If no problems, continue on with the deletion.
I was upgrading from VS 2008 to VS 2010. When I was getting errors in the auto-upgrade saying that files could not be opened, I made (what a I believe to be) a mistake and just went to Explorer and un-checked "read-only" for the containing folders and didn't check the files out. I now want to go through and set those files to "read-only" again, so I don't break stuff. Does anyone know which files are meant to be read-only and which ones, if any, are not?
Files which are not checked out should be read-only. Once a file is checked out, it becomes writable.
the simplest solution is the following:
Mark all files read-write
In Visual Studio Clean the solution to remove all not versioned files
Mark all files read-only
Run "tfpt online" or "tf folderdiff" to find all modified files and check them out
check in files checked out in previous step
run build to make sure everything is fine
Appparantly I'm the only one on the Internet experiencing this problem because I can find ZERO other reports of anyone else encountering it. Unfortunately I've been dealing with it for months and I don't know what else to do.
sometimes when I attempt to delete a folder from visual studio 2010, I get the error
unable to delete folder 'XXXX' this function is not supported on this
system
I can't delete it from the file system either unless I reboot the machine. Apparently there is a lock on it somewhere, but I can't find it. I tried to use Unlocker, but that doesn't work on Windows 7 x64 so I'm stuck.
This happens most often with the App_Theme folder, though it happens with other folders as well.
I would suspect it has something to do with source control (we are using sourcegear fortress), however I've encountered this error at home on my personal projects, and I don't use source control on that...
so does anyone have any ideas? has anyone out there experienced this issue? please help, it's driving me quickly and certainly towards insanity.
same thing to me here, what i am doing to fix that is to delete that file or folder from the file system and after that delete it from visual studio.
This is happened to me because previously I opened file in browser to see what is the content. Probably IIS locked files under this folder so it does not let you delete them.
Do iisreset and try again, it will release lock and you can delete it from visual studio.
You are probably trying to delete a file in a folder for which you don't have permission. Try to move your files to another folder or run Visual Studio as administrator.
This may happen if you do not have folder permissions within windows itself. Give the user folder permissions (full control) for the folder containing the solution and make sure those permissions are inherited by children of the folder. Once that is done (in the case of one of our employees) folders can be deleted from within visual studio.
I have a folder on my hard drive, C:\Program Files\Microsoft SDKs, and I was wondering if it is safe to move it to an external drive. Does Visual Studio or any other tool depend on this particular folder?
There are quite a number of entries in the registry (at least in my registry) that point to that location, so it seems something would work in a less than optimal fashion. At a minimum, it would make the uninstaller a bit confused. It is probably safe to simply rename the directory temporarily and try your builds to see if they still work. Ultimately, though, it seems it would be cleanest to run the installation again to actually remove it and then install to a new location.
Yes. Most Unmanaged code in VSStudio refer to certain include files present in the include folder.
Also some exes in bin folder are also referred to (especially VS2008).
VS2005 refers to an internal Platform SDK location.
VS2008 refers to C:\Program Files\Microsoft SDKs\Windows\v6.0A
However most projects refer to this location via a macro. So if you can find a way to update the macro with the new location, then you should be fine.
Doing this may break some of your applications. If you added a reference to a project by browsing to a DLL installed in this folder, that project will not compile after you move this folder. If you haven't added any references in this manner, you might be OK.