I'm in Nuget Helll
-
It's just a giant clusterf*ck... :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013IMHO, the benefits outweigh the cons for me, regarding Nuget or Nougat. However, it can be painful, especially when configuring everything for the first time. You could hop in the ole' hot rod and tear up the town, to blow off some steam. Just a thought... :)
-
I dunno - I used to quite like it.[^]
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
:thumbsup:
-
To avoid problems we remove the Nuget config file from the VS solution and add the dll's manually. This way there will be no "surprises" when Nuget tries to update automically to a new version.
You mean delete packages.config (and the packages folder)? I tried that, but that was even worse. I don't know what's up with that... We have a local repository because we can't connect to net with our dev boxes. VS2015 (we''re using update 3, with Nuget 3.4.4) appears to have stopped updating packages from the local store. This is depressing. :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
You mean delete packages.config (and the packages folder)? I tried that, but that was even worse. I don't know what's up with that... We have a local repository because we can't connect to net with our dev boxes. VS2015 (we''re using update 3, with Nuget 3.4.4) appears to have stopped updating packages from the local store. This is depressing. :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013#realJSOP wrote:
You mean delete packages.config
Uh oh!
#realJSOP wrote:
and JUST the packages folder)
Just the packages folder should be deleted. Deleting the packages.config will hurt very badly. Also, the problem is probably related to the packages cache -- (IT's TERRIBLE!!! when it happens). But you can clear it. Tools...Options... NuGet Package Manager (see image : https://i.stack.imgur.com/uVdMY.png[^] ) When NuGet works, it works. When it doesn't....agh!!!!
-
You mean delete packages.config (and the packages folder)? I tried that, but that was even worse. I don't know what's up with that... We have a local repository because we can't connect to net with our dev boxes. VS2015 (we''re using update 3, with Nuget 3.4.4) appears to have stopped updating packages from the local store. This is depressing. :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Now I think I know what your problem is, Nuget changed the location of it's cache in newer versions.
Quote:
NuGet 3.5 and earlier uses packages-cache instead of the http-cache, which is located in %localappdata%\NuGet\Cache
See: How to manage the global packages, cache, temp folders in NuGet | Microsoft Docs[^]
-
It's just a giant clusterf*ck... :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Meh. Never used it and I don't plan to. It seems like one of those things the script kiddies use to avoid doing their jobs/homework. Real developers don't use it.
-
Meh. Never used it and I don't plan to. It seems like one of those things the script kiddies use to avoid doing their jobs/homework. Real developers don't use it.
PIEBALDconsult wrote:
Real developers don't use it.
troll bait. :suss:
-
It's just a giant clusterf*ck... :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I started the project from scratch five times in VS2015. Each time, Nuget refused to update all of the packages (it had issues with the Owin stuff). So then, I created the project in VS2017, and updated all of the packages successfully. And the app even ran (albeit in a completely virginal state). Finally, I opened that project in VS2015, and it compiled/ran there as well. I guess VS2015/Nuget is an unstable combination.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
It's just a giant clusterf*ck... :|
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Been there, bro. It shouldn’t be that hard should it.
cheers Chris Maunder
-
Been there, bro. It shouldn’t be that hard should it.
cheers Chris Maunder
Indeed...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I started the project from scratch five times in VS2015. Each time, Nuget refused to update all of the packages (it had issues with the Owin stuff). So then, I created the project in VS2017, and updated all of the packages successfully. And the app even ran (albeit in a completely virginal state). Finally, I opened that project in VS2015, and it compiled/ran there as well. I guess VS2015/Nuget is an unstable combination.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Meh. Never used it and I don't plan to. It seems like one of those things the script kiddies use to avoid doing their jobs/homework. Real developers don't use it.
PIEBALDconsult wrote:
Real developers don't use it.
Bullshit.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
-
It probably is cache related, when you clear the Nuget cache(s) that should help (see my previous reply for a link)
It was a virgin install of VS2015.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Been there, bro. It shouldn’t be that hard should it.
cheers Chris Maunder
The fun starts when my colleagues decide to use different versions of e.g. NewtonSoft JSON and everything must be bundled together in one installation directory. When they also decide to mix .NET and .NET Core in one solution things get even more fun :-D
-
#realJSOP wrote:
You mean delete packages.config
Uh oh!
#realJSOP wrote:
and JUST the packages folder)
Just the packages folder should be deleted. Deleting the packages.config will hurt very badly. Also, the problem is probably related to the packages cache -- (IT's TERRIBLE!!! when it happens). But you can clear it. Tools...Options... NuGet Package Manager (see image : https://i.stack.imgur.com/uVdMY.png[^] ) When NuGet works, it works. When it doesn't....agh!!!!
raddevus wrote:
Also, the problem is probably related to the packages cache -- (IT's TERRIBLE!!! when it happens). But you can clear it. Tools...Options... NuGet Package Manager (see image : https://i.stack.imgur.com/uVdMY.png[^] )
It doesn't appear as if that is possible in NuGet 3.4.4... And we can't update VS due to group policies. Once the machine is joined to the network, we can't update Visual studio, so when there’s an important patch, we have to RE-IMAGE our boxes, apply the patches, and then connect it to the network, at which point group policies are applied automatically.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
The fun starts when my colleagues decide to use different versions of e.g. NewtonSoft JSON and everything must be bundled together in one installation directory. When they also decide to mix .NET and .NET Core in one solution things get even more fun :-D
Throw in webforms and you get system.net.http hell.
cheers Chris Maunder
-
It was a virgin install of VS2015.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013There's your problem. Without *all* of the updates installed, VS 2015 doesn't have very good nuget support. 2017+ should be good out of the box, but latest updates are always recommended.
-
There's your problem. Without *all* of the updates installed, VS 2015 doesn't have very good nuget support. 2017+ should be good out of the box, but latest updates are always recommended.
I neglected to see whatnuget version is installed. However, that doesn't solve the problem at work. We don't have an internet connection to our dev boxes, and I've spent the last few hours trying to get a local private extension gallery working so I can update nuget to the latest version for vs2015. VS2015 has update 3 on it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
raddevus wrote:
Also, the problem is probably related to the packages cache -- (IT's TERRIBLE!!! when it happens). But you can clear it. Tools...Options... NuGet Package Manager (see image : https://i.stack.imgur.com/uVdMY.png[^] )
It doesn't appear as if that is possible in NuGet 3.4.4... And we can't update VS due to group policies. Once the machine is joined to the network, we can't update Visual studio, so when there’s an important patch, we have to RE-IMAGE our boxes, apply the patches, and then connect it to the network, at which point group policies are applied automatically.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Sounds like you guys need to do all your development in VMs that are not joined to the domain. That way the IT folks don't have the ability to force policies that keep you from doing your jobs down your throats. I've been working that way for years and it's kept the IT Nazis at bay for the most part.
-
Sounds like you guys need to do all your development in VMs that are not joined to the domain. That way the IT folks don't have the ability to force policies that keep you from doing your jobs down your throats. I've been working that way for years and it's kept the IT Nazis at bay for the most part.
What makes you think his IT Nazi's either ban VM software entirely or only allow VMs tied into their control system and thus subject to the full power of IT stupidity. At my last (dod contractor) job, Windows VMs were generally banned. Not because of normal IT Nazi control freakism; but because their license management cluster:elephant: couldn't tell the difference between free VM licenses from an MSDN sub and licenses that needed pay for via volume licensing, and there was $0 budget for the latter. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
