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.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
I was saturating my WiFi at 25MB/sec and i didn't realize it - thought i was topping out my internet and i was happy with it.
plugged it into a wire today just so i could let the hubby use my wifi dongle because his laptop's built in wifi was dodgy for a bit. i was reinstalling windows so i had to download a bunch of stuff anyway.
The windows install was utter hell. At least a dozen blue screens and i had to run out and buy a DVD-ROM to fix it. It cost me a mint in downtime for work this week too.
So it was nice to bookend this disaster with this wonderful broadband windfall.
Comcast actually wasn't lying when they told me i'd get better than 600MBits/s. I thought it was a sales guy talking up burst rates for the node, but no.
(I broach this subject here because I don't think there's an answer. Note the "rant" icon.)
Consider: ObsoleteAttribute -- Marks the program elements that are no longer in use.
What would be the opposite/complement? A way to mark some code as not-yet-ready-for-primetime?
Not to the extent of throwing a NotImplementedException, because the code exists and works (mostly).
Not a todo either; that's too passive.
But, if I have a kludgey Method I intend to rework at some convenient future time, I want to be reminded about it every time I compile code which calls it. Even if the Method has been compiled into a DLL.
An ObsoleteAttribute will do this -- but I expect that it would be confusing to my colleagues.
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" ...
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...
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.
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.
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
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.
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.)