8

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

Comments
  • 1
    Yeah I kinda hate nuget as a package manager buy we don’t really have other alternatives don’t we?
  • 1
    @devTea see that's why I love angular and node. But that Shit don't fly with dotnet
  • 4
    Nuget does fuck up sometimes, yeah
    Make sure you're not pushing packages and get nuget restore to work. Once that's sorted out and proven to work once, it somewhat behaves. Well, at least that's the case for me
Add Comment