Set "EnforceCodeStyleInBuild" to "true"

[marco-carvalho]

No description provided.

[github-actions]

You need to be logged into GitHub to download these files.

Download the artifacts for this pull request:

• ryujinx-Release-1.2.0+22abc52-linux_arm64
• ryujinx-Release-1.2.0+22abc52-linux_arm64-AppImage
• ryujinx-Release-1.2.0+22abc52-linux_x64
• ryujinx-Release-1.2.0+22abc52-linux_x64-AppImage
• ryujinx-Release-1.2.0+22abc52-macos_universal
• ryujinx-Release-1.2.0+22abc52-win_x64

Only for Developers

• ryujinx-Debug-1.2.0+22abc52-linux_arm64
• ryujinx-Debug-1.2.0+22abc52-linux_arm64-AppImage
• ryujinx-Debug-1.2.0+22abc52-macos_universal
• ryujinx-Debug-1.2.0+22abc52-linux_x64
• ryujinx-Debug-1.2.0+22abc52-linux_x64-AppImage
• ryujinx-Debug-1.2.0+22abc52-win_x64

[GreemDev]

Based on the .NET docs it seems like this is just integrated dotnet format, which we don't bother with anyways. I don't see a reason to merge this really

[marco-carvalho]

It ensures that code style rules are enforced consistently across the entire project, preventing style-related discrepancies from reaching the repository. Its integration into the build process guarantees that code style violations are caught automatically during builds, providing immediate feedback to developers. This approach reduces the overhead of manual formatting checks, aligns with maintaining consistent code, and integrates seamlessly into CI/CD pipelines. Enforcing code style at build time fosters a culture of quality and consistency without relying on separate tools or workflows, ultimately saving time and reducing friction in code reviews.

[GreemDev]

It ensures that code style rules are enforced consistently across the entire project, preventing style-related discrepancies from reaching the repository. Its integration into the build process guarantees that code style violations are caught automatically during builds, providing immediate feedback to developers. This approach reduces the overhead of manual formatting checks, aligns with maintaining consistent code, and integrates seamlessly into CI/CD pipelines. Enforcing code style at build time fosters a culture of quality and consistency without relying on separate tools or workflows, ultimately saving time and reducing friction in code reviews.

please don't reply with AI generated nonsense, it's entirely unhelpful