11

Fuck nuget, .NET and whole C#, I'm solving problem with dependencies since yesterday.

Comments
  • 5
    What's the problem?

    EDIT: I am a bit triggered.
  • 1
    @hypervtechnics

    After pulling from develop branch all of references went to hell. Clean, rebuild all, reinstalling packages, compiler could not find refs to assemblies, even tho it were clearly there (with valid versions). Missing references for some classes were solved for ex. by opening these "missing" classes with vs.

    After manualy browsing for ref and editing some csprojs, I have managed to finally run application.
  • 4
    partially triggered as well...
  • 4
    @Mercutio217 this sounds like an asp.net project targeting .net 4.0.

    What VS are you running and msbuild version?
  • 1
    @Mercutio217 I think someone did NOT use NuGet instead referenced static dlls. Maybe the paths on your and his/her computer are different.
  • 0
    All is solved. The problem is, one repo is being used for multiple projects, if someone updated one library in one place, it could potentially harm everything. The tool to unify libraries version in all projects is being planned, but we are all swarmed anyway.
Add Comment