4 ms·
My biggest hold-out for using C# at a medium-sized company would still be how awful Projects and Solutions are, when working with a big team. I'd have to devel
by VikingCoder 5y ago
My biggest hold-out for using C# at a medium-sized company would still be how awful Projects and Solutions are, when working with a big team.
I'd have to develop my own tooling, first.
- DaiPlusPlus 5y agoI don't see how that could possibly be a problem. Yes, the old (pre-.NET Core), .csproj files were a mess, but the post-2017 .csproj/.props/.targets files are a pleasure to work with.
- VikingCoder 5y agoWell, that's good to hear. We had problems where you would add some dependencies, and I would add the same dependencies, but the GUIDs would be different, and then everything was impossible to merge. You're saying that's gotten better?
- hnrodey 5y agoSounds like you were doing something wrong to manage your solution files.
- hackerfromthefu 5y agoTo be fair every now and then the project files would get messed up by the tooling, and happened more often with nuget. It's still rare though and can be fixed by digging in to what's going on, or just recreating the projects and readding the source files.
- hnrodey 5y agoOur repo has nearly 15k .cs files across 700 .csproj files. If we can do this successfully, I think anyone can.
- codenesium 5y agoWith .net core references are much cleaner. There isn't a reference to every file it's handled automatically. The whole csproj hell you're talking about is gone now.