Original Post
🔒 Locked
Visual Studio Files explained?
Advertisement
Don't know where to look either, but i know some:
.dsp: The project file of VS6, don't delete
.vcproj: The project file of VS2002++, don't delete
.dsw: The workspace file of VS6, can be deleted, but shouldn't
.sln: The workspace file of VS2002++, can be deleted, but shouldn't
.ncp: The browse info is kept there. If Intellisense is acting up, delete it. Also safe to delete
.clw: VS6: The class wizard info. Can be deleted, will be rebuilt on opening the class wizard.
.old, .plg: Safe to delete
There's more, i'm pretty sure...
.dsp: The project file of VS6, don't delete
.vcproj: The project file of VS2002++, don't delete
.dsw: The workspace file of VS6, can be deleted, but shouldn't
.sln: The workspace file of VS2002++, can be deleted, but shouldn't
.ncp: The browse info is kept there. If Intellisense is acting up, delete it. Also safe to delete
.clw: VS6: The class wizard info. Can be deleted, will be rebuilt on opening the class wizard.
.old, .plg: Safe to delete
There's more, i'm pretty sure...
interesting, windows already has the descriptions of the file formats for me.
The following is my list of extentions that are generated from files in your project (so it's safe to delete them - they will just be recreated).
That text can be used as an exclusion list for xcopy, which is the reason I have it.
Quote:
.ilk
.obj
.pdb
.idb
.pch
.res
.resources
.ncb
BuildLog.htm
That text can be used as an exclusion list for xcopy, which is the reason I have it.
Quote:
Original post by Andrew Russell
The following is my list of extentions that are generated from files in your project (so it's safe to delete them - they will just be recreated).Quote:
.ilk
.obj
.pdb
.idb
.pch
.res
.resources
.ncb
BuildLog.htm
That text can be used as an exclusion list for xcopy, which is the reason I have it.
It is not necessarily safe to delete .res/.resx/.resources files if you are using embedded resources or programmatically generated resources in your project. If you are merely generating binary .resources files from .resx files (which is the accepted practice AFAIK), then you can delete the .resources files if you want.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement