TFS 2010 without EXE files copied after successful build

Question

I have a TFS 2010 installation along with Visual Studio 2010 (also installed on the server), I created an assembly definition for a C # project. The build ends successfully, but I do not have .exe files in my folder folder, but I can find the DLL, however

Has anyone experienced the same problem before?

Answer 1

Thank you for your answers, this was exactly the problem, one of the three projects was set to "x86" instead of "AnyCPU", I noticed that after organizing the folders of the binary files (since by default TFS puts everything in the same folder, this can be hard to see) using the message: http://lajak.wordpress.com/2011/05/07/customize-binaries-folder-in-tfs-team-build/.

Now the problem is resolved. Thank you for your help and have a nice day.

Answer 2

This may be a problem with your build configurations.

In the solution editor, right-click on the solution and select "Configuration Manager". This will result in a list of all projects in the solution. The project that creates the "EXE" is probably set to "x86", and the project (s) that create the "DLL (s)" is probably set to AnyCPU.

You must have a “Platform” for each of them, plus a “Platform” for “Mixed Platforms,” which will build all the projects.

Now check your build definition. Browse the Process tab and see the Items to Build setting, make sure you create Release | Mixed Platforms. If you get only DLLs in your build release, I suspect your build is set to "Release | AnyCPU"

Answer 3

The entire TFS-Build stream can be observed if you queue a new assembly and set Verbosity = diagnostic
After the assembly is complete, open it and select View Log.

A BinariesDirectory gets its value within the Initialize Binaries Directory .
Another variable called OutputDirectory gets the value inside Initialize OutputDirectory , based on what is based on BinariesDirectory .
MSBuild returns the result in this OutputDirectory .
Finally, inside Copy Files to Drop Location everything under BinariesDirectory will be copied to the drop folder.

The activity that Microsoft.TeamFoundation.Build.Workflow.Activities.CopyDirectory does, which does not focus on any extension, simply copies the entire directory.

To find out what you are reporting, you can use a non-standard XAML process template, or your MSBuild arguments are somehow changed or * exe-csproj have a hard output path.
In any case, if you follow the build log as described above, you can find the culprit.
Good luck