История изменений

In the .NET build toolkit and command line interface, the C# compiler (csc.exe) itself does not actually require a project file to compile code. However, a project file is required by the higher level dotnet build process. Here are some details:

    The C# compiler csc.exe can compile individual .cs files to .dll or .exe binaries directly through command line parameters without needing a project.
    However, the standard way to build .NET applications is using the dotnet build command.
    dotnet build invokes MSBuild, which relies on the project file (.csproj) to define the build pipeline.
    The project file contains the build configurations, target frameworks, references, source file includes, NuGet dependencies etc.
    MSBuild uses this information during the orchestrated build to compile code, resolve dependencies, package outputs etc.
    So while csc.exe doesn't require a project file directly, dotnet build needs it to define all the components and steps of the build process.
    The project file is XML based and can customize every aspect of the build as needed.

So in summary, the csc.exe C# compiler itself does not strictly need a project file, but the higher level dotnet build pipeline relies on the project file to define the inputs, settings, and orchestration logic needed to fully build a .NET application. The project file is an important part of the managed build process.