News for hackers. Stuff that matters.
Re:Open Source .NET three years later by kuschku on Sunday December 24, 2017 @12:37PM (#16000392)
What would the C# tooling workflow then look like? I haven't found anything that's reasonably easy to use with just .NET Core.
Re:Open Source .NET three years later by JamesBarney on Sunday December 24, 2017 @04:17PM (#16001336)
What were you using Gradle to do that you want a c# replacement for?
Re:Open Source .NET three years later by kuschku on Sunday December 24, 2017 @05:38PM (#16001690)
Basically everything. In my web projects, gradle runs css and js minification and compilation, and in game projects, it runs the asset preprocessing.

The build-time code is handled with gradle’s buildSrc folder.

I also obviously use Annotation Preprocessors to pre-generate code for my Java projects, and additional build tools to further minify and optimize the output (e.g., for Android, I also run redex over it).

Basically, gradle for me handles the entire build – fetching dependencies, building native libraries, running code generators, building Java code, binding them together, processing assets, compressing the result, and optimizing it all – and deploying the results.

In nice, and modular steps.