3 ms·
A while ago I wrote a batch script that assembled a project with csc instead of using Visual Studio. This was so easy and refreshing to work with. Source contro
by maxxxxx 10y ago
A while ago I wrote a batch script that assembled a project with csc instead of using Visual Studio. This was so easy and refreshing to work with. Source control worked, build times were incredibly fast and the result was independent of Visual Studio settings.
I really want my good old makefiles back for C#. For build management Visual Studio adds a lot of complexity and weird behaviors.
- flukus 10y agoI wrote a couple of months ago about using make with .net (the focus is on make): http://flukus.github.io/2016/11/30/2016_11_30_Rediscovering-Make/ http://flukus.github.io/2016/11/30/2016_11_30_Rediscovering-... The problem is that I still need VS for debugging, which means build via msbuild. I've heard .net comes with a cmd line debugger (that's compatible with gdb even), though I've never used it.
- digitalpacman 10y agoThose are msbuild settings, not visual studio settings.
- maxxxxx 10y agoMy point was that, in a team, the output of the build depends on Visual Studio settings of each developer.
- digitalpacman 10y agoThose are msbuild settings, not visual studio settings.
- groovy2shoes 10y agoDoes Visual Studio not come with nmake anymore? While I prefer BSD make, nmake wasn't half bad. Had all the essentials and then some.