This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 34%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER7%3C/text%3E%3C/svg%3E)
Every time I make a debug or release run of the applications I am working on, Visual Studio generates five files that do not get cleaned up. Assume my application (which uses the x64 platform) is named ABC, these files are located in:
ABC\obj\x64\Debug\net8.0-windows
ABC\obj\x64\Debug\net8.0-windows10.0.26100.0
and
ABC\obj\x64\Release\net8.0-windows
ABC\obj\x64\Release\net8.0-windows10.0.26100.0
Again with my application named ABC and with String8 being an (apparently) random string of eight characters, the files are named:
ABC_String8_wpftmp.AssemblyInfo.vb
ABC_String8_wpftmp.AssemblyInfoInputs.cache
ABC_String8_wpftmp.assets.cache
ABC_String8_wpftmp.GeneratedMSBuildEditorConfig.editorconfig
ABC_String8_wpftmp.vbproj.BuildWithSkipAnalyzers
I just recently discovered this so hundreds and hundreds of these files had accumulated in those directories. Is this normal behavior? Is there a Visual Studio setting that would tell it to delete these files?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
yes. These files are the output of the source compile. they are only recreated by the build, if the source files are newer. there is a folder for debug vs release, and subfolder for each architecture.
note: if you delete them, the next build will recreate them, though the build may be slow.
Thanks for the info, Bruce, but my question is why not use the same file names for each build rather than creating new file names for each build? I assume there is no information of value in all the old build files.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more