Click here to Skip to main content
15,895,815 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

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.

 
GeneralRe: I've Gone off NuGet enormously Pin
Richard Deeming22-Jun-17 4:17
mveRichard Deeming22-Jun-17 4:17 
GeneralRe: I've Gone off NuGet enormously Pin
Rob Grainger22-Jun-17 22:36
Rob Grainger22-Jun-17 22:36 
GeneralRe: I've Gone off NuGet enormously Pin
PIEBALDconsult22-Jun-17 9:24
mvePIEBALDconsult22-Jun-17 9:24 
GeneralRe: I've Gone off NuGet enormously Pin
Lucas Vogel23-Jun-17 4:51
professionalLucas Vogel23-Jun-17 4:51 
GeneralRe: I've Gone off NuGet enormously Pin
Steve Naidamast23-Jun-17 6:11
professionalSteve Naidamast23-Jun-17 6:11 
GeneralRe: I've Gone off NuGet enormously Pin
Stuart Dootson23-Jun-17 7:45
professionalStuart Dootson23-Jun-17 7:45 
GeneralRe: I've Gone off NuGet enormously Pin
Kirk 1038982123-Jun-17 8:02
Kirk 1038982123-Jun-17 8:02 
GeneralRe: I've Gone off NuGet enormously Pin
Yortw25-Jun-17 10:54
Yortw25-Jun-17 10:54 
I (and the company I work for) was late to package management, and even now we avoid it where possible, but some Nuget packages have crept in out of necessity. When I first started with it about 2-3 years ago, it worked flawlessly every time for me (though admittedly our usage was light).

Unfortunately it seems to have been broken and then gotten worse with every iteration released since then. I really don't know why. I had a problem the other day where a project showed a broken reference, but Nuget insisted the package was installed ok. Checking the csproj file showed it was referencing version 9.x.x.x of a package, but the packages folder contained only 8.x.x.x. No amount of cajoling would convince Nuget that it needed to download the new version even though VS knew the reference was broken. Only thing that worked was forcing a reinstall of the package.

Having said that not all problems are caused by Nuget itself. Strong named packages are evil - we have some solutions that have a mix of .Net 4 and .Net 4.5 projects in them that all reference the same package (don't ask). All the assemblies ship and run together and it all works fine until you get strong named package and you can't reference the newer version from the .Net 4 projects. Then you're in a world of pain trying to manage the dependencies.

On top of that, at least one of the Microsoft provided Azure packages decided it would be a good idea to rename an entire namespace (or move types to another namespace at the very least), so upgrading from version X to version Y is breaking at the source level with no explanation or release note to say so.

When it works I prefer it to downloading and running installers, then having to manually locate the right assemblies (are they in the gac? in a folder? which folder? somewhere under program files or program files x86? what was the company name again?) etc. Especially nice when you don't have to do this on build servers. Sadly the experience is so broken we do everything we can to avoid it now.

Really the only thing I want from Nuget is for the package restore to work properly, i.e I add a package to a project and check in, my colleague gets latest and builds, and the package is downloaded and referenced correctly on their PC. We've had zero success with this in the last year or so. It's always broken and people are always checking in csproj changes just to fix references/broken reference paths. I really don't get why since it used to work.

Haven't tried Paket - sort of appealing, but I'm led to believe it lacks a GUI so it's a non-starter for some of my colleagues (and I prefer the GUI myself anyway).

GeneralWin10 I/O : Claims another victim Pin
raddevus22-Jun-17 2:02
mvaraddevus22-Jun-17 2:02 
GeneralRe: Win10 I/O : Claims another victim PinPopular
lopatir22-Jun-17 2:04
lopatir22-Jun-17 2:04 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 2:07
mvaraddevus22-Jun-17 2:07 
GeneralRe: Win10 I/O : Claims another victim Pin
Marc Clifton22-Jun-17 2:16
mvaMarc Clifton22-Jun-17 2:16 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 2:30
mvaraddevus22-Jun-17 2:30 
GeneralRe: Win10 I/O : Claims another victim Pin
Kirk 1038982123-Jun-17 8:08
Kirk 1038982123-Jun-17 8:08 
GeneralRe: Win10 I/O : Claims another victim Pin
dandy7222-Jun-17 2:20
dandy7222-Jun-17 2:20 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 2:29
mvaraddevus22-Jun-17 2:29 
GeneralRe: Win10 I/O : Claims another victim Pin
dandy7222-Jun-17 2:33
dandy7222-Jun-17 2:33 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 2:59
mvaraddevus22-Jun-17 2:59 
GeneralRe: Win10 I/O : Claims another victim Pin
Eddy Vluggen22-Jun-17 2:32
professionalEddy Vluggen22-Jun-17 2:32 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 3:06
mvaraddevus22-Jun-17 3:06 
GeneralRe: Win10 I/O : Claims another victim Pin
Eddy Vluggen22-Jun-17 3:22
professionalEddy Vluggen22-Jun-17 3:22 
GeneralRe: Win10 I/O : Claims another victim Pin
Tim Carmichael22-Jun-17 3:53
Tim Carmichael22-Jun-17 3:53 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus22-Jun-17 4:18
mvaraddevus22-Jun-17 4:18 
GeneralRe: Win10 I/O : Claims another victim Pin
Herbie Mountjoy24-Jun-17 9:32
professionalHerbie Mountjoy24-Jun-17 9:32 
GeneralRe: Win10 I/O : Claims another victim Pin
raddevus25-Jun-17 5:02
mvaraddevus25-Jun-17 5:02 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.