.NET drinking game:
* Drink every time IntelliSense refuses to tell you what the actual error is because it's too busy choking on lambda syntax from a decade ago
* Take a shot every time you discover a closed, unresolved Github issue discussing your current showstopping build/CI problem
* Finish your drink every time the solution to your problem involves either manual edits to your CSPROJ (or whatever) file, or creating a new project altogether and copying all your fucking files over

Fucking hate working with dotnet. Just spent half an hour fixing the most fucked up bug.

So I installed a nuget package on my computer, tested everything, it worked, and pushed. My classmates then pulled it to their pc, and holy hell broke loose.

Everything was red, it couldn't even import System! By a turn of luck, I looked in the .csproj file, and saw that it had made an absolute path to the nuget package on my computer. Well no fucking wonder it only worked on mine then!

And here's the weird thing: it only did it now, it hasn't done it with the other packages we've imported

Does anyone feel like Microsoft went back to .csproj from project.json because they want users to sway towards using Visual Studio?

You can make WSL and VSCode fight over how a csproj should be written. VS2017 doesn't care and runs no matter who was previous.

It's 2018, but the question about how to rename `.csproj` visual studio project is actual.

I pass the day writing a script to encapsulate the migration of the old csproj to the new format. But, when the open source app returns an error of migrating the script continue. I check the return code and when it's an error, it's return 0.

After many tries, I return to my house and start looking at the open source code for understand what's happening and try to correct it.

OMFG, I cannot change the code to return an `int` instead of void. The method is in the public area of the code.

I very happy that this app, it's open source, so I can do my own version for my need.

When the missing reference error goes away when you delete the Target block lines in .csproj

Hogwarts stuff right here

When you add a new file to a project, Visual Studio shows only the types that it thinks are relevant.
It's based on a guid in the .csproj file. Yes, a guid.
A magic number, only longer.
Changed to another one that allows me to add the files, added the files, restored previous number. Project unloadable, restored with git, lost several hours of work. If only I committed before trying this. Lesson learned. Trust git. Never trust Visual Studio.