NuGET Packagies
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Never used it. Worthless. Leave it for the cargo-cultists.
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
For a long time I tried to stop the use of NuGet packages, but after a bunch of new colleagues arrived they had their way and now the builder is totally dependent on NuGet and the internet. And of course they were totally surprised that suddenly version conflicts arose. But on the positive side: I must admit that last year I tried to get the new NpgSql driver for PostgreSQL working and could not get it done without using NuGet. I even have plans to create a privat NuGet server, see: private-nuget-servers[^] So as the saying goes: "Go with the flow" ... :-\
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I've had a few run-ins with NuGet during my career, but apart from one time, nothing I couldn't fix. What really bothers me is that it tells me to update to package v5.0.0, which I know to be built on .NET 5.0, while my project is .NET Core 3.1. That's not compatible, yet it wants me to update... X| It shouldn't be that difficult to recognize my .NET version and then only show me updates for that particular version, or so you'd think.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
How are you using NuGet? All I do is right-click my project in Visual Studio, Manage NuGet Packages and then install what I need. It's much easier than going out to find the vendor's website, downloading an sdk, and adding references in Visual Studio. And mine don't ever try to update so new versions or url changes don't affect me. I've been using it for the last couple of years and have not had the problems you mentioned so you must be doing something wrong. :)
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
We're using them quite intensively. We create and consume them for internal libraries (for C# and C++ projects) with Azure DevOps feeds and use public nugets available on nuget.org feed No big issues so far. For C++ packages, there seems to be a push to [vcpkg](https://docs.microsoft.com/en-us/cpp/build/vcpkg?view=msvc-160). But heck .. [xkcd: Standards](https://xkcd.com/927/)
I'd rather be phishing!
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
To avoid version conflicts, create your own local NuGet repository and only install from that. That will keep NuGet from automagically "upgrading" your packages, and allow you more control over your upgrading process (upgrade only when you want to).
".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 -
How are you using NuGet? All I do is right-click my project in Visual Studio, Manage NuGet Packages and then install what I need. It's much easier than going out to find the vendor's website, downloading an sdk, and adding references in Visual Studio. And mine don't ever try to update so new versions or url changes don't affect me. I've been using it for the last couple of years and have not had the problems you mentioned so you must be doing something wrong. :)
Wait until you use 3rd party libs that need different versions of dll's, then it's party time :-\
-
How are you using NuGet? All I do is right-click my project in Visual Studio, Manage NuGet Packages and then install what I need. It's much easier than going out to find the vendor's website, downloading an sdk, and adding references in Visual Studio. And mine don't ever try to update so new versions or url changes don't affect me. I've been using it for the last couple of years and have not had the problems you mentioned so you must be doing something wrong. :)
A lot of proprietary libraries. Third party stuff. Microsoft Azure stuff. Packaging my own old libraries in a NuGet library... At least for me the whole process feels painful and time-consuming.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
A lot of proprietary libraries. Third party stuff. Microsoft Azure stuff. Packaging my own old libraries in a NuGet library... At least for me the whole process feels painful and time-consuming.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Deyan Georgiev wrote:
Third party stuff. Microsoft Azure stuff.
That's me too.
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Somewhere a few days ago I posted "NuGet is a virus". ;) What particularly annoys me is:
Crap like that.
Latest Articles:
Client-Side Type-Based Publisher/Subscriber, Exploring Synchronous, "Event-ed", and Worker Thread Subscriptions -
Never used it. Worthless. Leave it for the cargo-cultists.
PIEBALDconsult wrote:
Never used it.
PIEBALDconsult wrote:
Worthless.
How would you know it is worthless, if you never used it? :sigh:
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I like Nuget. We use it for everything in our shop. I can't convince you to like it. I can suggest you learn how to properly work with it, and I say this kindly, and not teasingly. If you have a team of 10 developers and only 2 know how to properly work with Nuget and keep things updated properly, then you are destined for failure, because the other 8 devs will elephant things up for sure. It does have its annoying problems, but they are manageable IMHO. Edit: we have our own Nuget repo (See JSOP's response) and we use this for most of our packages and for the same reasons that John mentioned.
-
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I limit myself to the ones shipped by Microsoft. Ones like the UWP / WPF tool kits. No issues.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
I've had a few run-ins with NuGet during my career, but apart from one time, nothing I couldn't fix. What really bothers me is that it tells me to update to package v5.0.0, which I know to be built on .NET 5.0, while my project is .NET Core 3.1. That's not compatible, yet it wants me to update... X| It shouldn't be that difficult to recognize my .NET version and then only show me updates for that particular version, or so you'd think.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
To avoid version conflicts, create your own local NuGet repository and only install from that. That will keep NuGet from automagically "upgrading" your packages, and allow you more control over your upgrading process (upgrade only when you want to).
".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 -
What do you guys think for these containers? After using them for a while with VS, I think this technology is a rubbish. Too many moving parts. Versioning nightmare. URLs changing, living you high and dry, conflicts between solution and projects etc. Is it just me who is not fully appreciate/understand this library management mechanic?
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
+1 to avoid Nuget. It always was and is COMPROMISE to build process - you nerver be sure smth is not changed. And never sure what and when "it" will download. Definitely "school boys" who bring this sh****t to .NET (from Linux) didn't have enough qualification and enterprise development at all. Say "no" to drugs, say "no-no-never!!" to nuget. :)
-
Technology exists not to "being fixed", but to HELP development! If nuget has defect in working principles, I see no reason even mention this tool.
If technology could never be fixed we'd all be out of a job dead (probably) :~
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
I've had a few run-ins with NuGet during my career, but apart from one time, nothing I couldn't fix. What really bothers me is that it tells me to update to package v5.0.0, which I know to be built on .NET 5.0, while my project is .NET Core 3.1. That's not compatible, yet it wants me to update... X| It shouldn't be that difficult to recognize my .NET version and then only show me updates for that particular version, or so you'd think.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
We just moved from 2.x to 5. Good luck when you get there, take booze!
veni bibi saltavi
-
We just moved from 2.x to 5. Good luck when you get there, take booze!
veni bibi saltavi
I'll skip 5 as it's not an LTS release. Although the move from 3.1 to 5 should be pretty painless... In theory :^) One of my customers, the only one with a software (1-man) team of their own, is on .NET 5 and so far it looks exactly like my 3.1 code :D
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
