In a clean project for which 'emitEntryPoint' is true, if you issue a 'dotnet build' you end up with an executable in the bin dir. If instead you do a 'dotnet compile' in the clean project you only get a dll (and pdb). If you then follow with 'dotnet build' the compile step is omitted (message: 'Project myproj (DNXCore,Version=v5.0) was previously compiled.

1. Difference Between Dll And Exe In Dot Net Banking
2. Difference Between Dll And Exe In Dot Net Login

Skipping compilation.' )output for 'dotnet build':hostpolicy.dllmyproj.depsmyproj.dllmyproj.exemyproj.pdboutput for 'dotnet compile':myproj.dllmyproj.pdb. While testing this out I found out that dotnet compile is no longer available as a command that can be called by the user. So if you update dotnet CLI, compile is no longer callable. Problem solved:)I looked into the incremental issue (why a rebuild is not triggered if the.exe is missing). This happens because, for.net core apps, the exe is not a product of csc, but a product of the Mini Publish that happens after compilation (to make the compilation output executable). So for.net core apps the exe should not be considered for the incrementality of the compile phase.

Difference Between Dll And Exe In Dot Net Banking

Difference Between Dll And Exe In Dot Net Login

Also, ideally, the mini publish should not happen in the Build command but in the Publish command (and then build could call publish to make the app executable). This would keep the 2 commands focused on only one thing.I would put off adding Publish output files to incremental checks for when we're ready to make Publish itself incremental.