The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I've got some code still running out in the wild circa 2005-ish, I used next to no external libraries, so there is not much fear of being able to fix an issue (as long as I can get the old IDE working )
I have some newer stuff, code about 3 years old that broke badly when the vender disappeared, and the current framework broke the old vendors code.
I am weary of depending on too much of external libraries like NuGet because of past experiences.
Sure these libraries can speed development up like crazy if you don't care about the product 5 years down the road, or think it will all be re-written by then.
NuGet is a publishing platform. If a vendor up and disappears, your dependence on their library (maybe as an interface for their API or hardware) is still in danger whether they publish their library on NuGet, the web, or a thumb drive. At least with NuGet, you know the library is available in its present form, compared to a website the vendor stops paying for.
In general, a dependency should be easily replaceable if it is intrinsic to functionality. And while larger vendors have a smaller chance of disappearing, a dependency without abstraction can still impose a risk to efficient replacement. Just ask Parler.
So I see three issues mentioned that have nothing to do with NuGet:
1. Version conflicts for common dependencies between libraries
3. Package configurations which say a new version is compatible with your project
NuGet doesn’t magically solve #1 for you, though it *can* update your references for the simple case, if you let it. Which highlights that #2 is not normally the default. Finally, #3 is the fault of the packager, not the deliverer. It’s easy to configure things wrong, and for the misconfiguration to go unnoticed if it’s new or exotic enough.
What NuGet does help you solve is keeping your source control download small, especially if the bulk of your code is libraries, unless someone unknowingly checks in the “packages” folder.
How are you people in Microsoft ecosystem, and not using NuGet pacakges? Is it some kind of April Fools joke? It's been probably one of the biggest productivity improvements in the last decade. We ended up migrating all our internal libraries to NuGet as well, and integrated the process into our CI pipeline. Learn how to use the tool, before complaining about it.
If this is a Leslie, so be it. But for those not initiated, here's a horror video for you, made even more horrifying by the god-awful laugh track. (And don't ask me where the term 'god-awful' comes from - I don't know - yet.)
That was hilarious
Could've done without the laugh track though.
I'm just waiting for my customers to switch from Excel to PowerPoint for doing everything including business critical computations and handling user data
For a while Houdini used a trap door in every show he did - but it was just a stage he was going through.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
I've been quite displeased with VS since 2008. Now I didn't try 2010 but have an install 2015 I use every year or so. There just seems to be an ever-increasing amount of "Stuff" that is peripheral to the code. Something unsavory about the evolution of VS.