When and why does Visual Studio create a subfolder of "x86" inside "bin" after assembly?

I have a solution with many projects containing 3 executable projects. All my projects are configured on the target platform "x86", in the solution configuration manager I even deleted others, such as "Mixed" and "Any processor" (this is because I use some third-party libraries that restrict me to stick to x86). All three executable projects are simple WinForms applications created using C # for the full .NET 4 profile.

Now, when I create one of my executable projects, its output is embedded in the bin / x86 / Release directory. When I create another executable project, its output is built into bin / Release without the x86 subfolder.

Why is this - at first glance - inconsistency?

UPDATE

I need to fix this because I would like to run some scripts after successful builds, and they expect the result to be in a consistent folder structure.

+3
c # visual-studio msbuild
source share
1 answer

If you go to Project> Properties> Build in Visual Studio, you will see the target platform (among other settings).

This folder is created if the build target is 32-bit (X86) or "Any processor"

Finally, check the Exit folder: Projects> Properties> Exit Path

+5
source share

All Articles