<div>
you probably could do it by defining an appropriate postbuild event step.<br />
<br />
but why would you do that? deleting the obj modules would make the executable out-of-date cause the input files for the build were no more available. so every time later you have to make a full build and when you start the program from visual studio you always was asked whether to make a new build. <br />
<br />
Sara
</div>


<div>
I thought the obj files are intermediate files the get used during the build, and the final build files are created in bin?
</div>


<div>
yes. you are right. you don't need the obj files for execution. <br />
<br />
but the build process would make an incremental build (beside you make a rebuild or clean before build). and when invoking from visual studio the obj files were checked whether they have a timestamp older than the executable. if you delete all those files you would get a warning that your program is not up-to-date because of this.<br />
<br />
why do you want to delete the files? <br />
<br />
Sara
</div>


<div>
I would not do it.<br />
<br />
The obj folder is used internally by Visual Studio during the build process. If you delete it, you will eventually end up with slower builds because some of the files in there are being reused build after build. If you delete them, the compile will need to recreate them or copy them again each time you compile.<br />
<br />
For intance, if you use a COM dll in your application, the interop dll needed for a VB.NET application in order to connect to COM will have to be recreated everytime, and this be time consuming if the COM dll is a big one.<br />
<br />
The only thing you can gain from that is to save some space on the hard disk.
</div>


<div>
Maybe I did not ask the question correctly. &nbsp;I do not want to delete the folder. &nbsp;I do not want to delete any &nbsp;intermediate file. &nbsp; I have a couple DLL project. &nbsp; After building, I always end up with 2 identical copies of the DLL - one in bin and one in obj. &nbsp; &nbsp;Then we back up our source code project, we are backing up the obj folder because it's a subfolder. &nbsp;I just did not want to backup the DLL in the obj folder. &nbsp;We end up with copies
</div>


<div>
<div class="content wysiwyg-content">
Is there a way to tell Visual Studio to delete the intermediate obj files after a successful build?
</div>
</div>


Is there a way to tell Visual Studio to delete the intermediate obj files after a successful build?

Visual Studio - obj folder file

Visual Basic .NET (VB.NET) is an object-oriented programming language implemented on the .NET framework, but also supported on other platforms such as Mono and Silverlight. Microsoft launched VB.NET as the successor to the Visual Basic language. Though it is similar in syntax to  Visual Basic pre-2002, it is not the same technology,

Visual Basic.NET

Development in most programming languages is frequently done with an editor or integrated development environment (IDE). An IDE is a software application that provide comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger. XCode, Visual Studio, Adobe Dreamweaver and Eclipse are some of the more popular development tools, but an editor or IDE can be anything from simple text editors to sophisticated programs. Related topics: All programming and development language, database and web based content management systems topics

Editors IDEs

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.