Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "nuget"
14 hour deploy.
Four. Teen. Hours.
Fuck you dotnet Core. Fuck you NuGet. Fuck you IIS. Fuck you Windows. Fuck you Microsoft. Fuck it all. I'm fucking tired. Fuck!15
Client so scared someone steal their code (even though we’re the one who make it), they block some access to internet website, also block nuget site11
More like a sub company/department inside a company: Android.
I still use it as my main driver, but every time I try to get back into development with it(did it professionally for 2 years nearing on 3 and was a lead Android dev, mind you not necessarily by merit....) I end up hating everything about it.
The tooling is meh, the API is hideous and even with the addition of Kotlin, which I do find a nicer language over Java I still dislike it. The ammount of shit needed to make something as simple as store data, manage fragments, integrate with the NDK, make JSON API calls or even shake motions is just ludicrous and counter intuitive. I can see why people would hate Java based on Android, a language that I generally love and defend.
I firmly believe that people extend frameworks or tooling for 2 reasons only:
1 the stack is so awesome that you just want to create packages and libraries to extend the functionality of a powerful environment, like gems for Ruby, python packages, Node packages, php composer, nuget etc
2 the stack is so fucking hideous that people need to fix shit: the entire android square utility framework, butterknife, flutter, react native, codenameone, etc etc
The case with Android is the second. I have not met a professional Android developer that completely likes everything about Android, but will seldom find people that HATE other frameworks or environments.
Android it is for me. Still my daily driver and I love every Android phone I have ever owned. It just makes me feel lots of more compassion for fellow Android devs.3
this www.xmlrant.com project I created turns to be quite a learning experience
Things I did for the first time as part of it
- submitted a public nuget package
- worked with .net core library and mvc application
- integrated mvc's app github repo with continious integration platform appVeyor9
Heya devRant people, I haven't been here for a while so I think I may have lost the touch with my rants. But no matter.
Ok, here I go.....
FUCK NUGET AND FUCK VISUAL STUDIO, THE FACT THAT IT KEEPS REDIRECTING A REFERENCE TO THE FUCKING AZURE SDK IS PISSING ME OFF. EVEN MORE SO THAT WHEN I RENAME THE FUCKING .DLL ON THE AZURE SDK SO IT DOESN'T REFERENCE IT, IT JUST DOeS NOT FUCKING RECOGNIZE ANY FUCKING .DLL I POINT IT TO, EVEN IF THE PATH IS CORRECT.
FIX YOUR SHIT MICROSOFT.
(Sorry for caps, I'm just really frustrated.)
My first packages, uploaded to nuget!
A simple neural network library, written in C# (.Net Standard)
Here's a link:
*sends email to ops manager to explain nuget & git (yes, he is THAT guy)
*his reply "what's nuget?"
Ooooooooh! Why don't you open Google and do a fucking search you amazingly stupid twat!!! In what fucking era do you live in? What the fuck are you doing at work everyday, besides complaining about how time consuming your useless mundane tasks are? Take some of your undeserved salary and go educate yourself, you useless sack of shit! FUCK!
*meanwhile... Little grin on my face. *Shift+delete email.1
- assignment is to display a paragraph fit within a rectangle
- takes maybe 10 minutes to write
- 1 error preventing Xamarin Forms solution from building
- googles error and seems to be a version issue with a single package
- upgrade that single package
- 43 errors preventing solution from building
- reverts back to previous package version
- 76 errors preventing solution from building
- angrily turns off laptop and packs away things into laptop case
- talks shit about xamarin and all the annoying nuisances ive dealt with for this stupid mobile app class
- takes laptop back out because deadline is tomorrow and i have to make the solution build even though i want nothing to do with it
- laptop takes 2 hours and 14 minutes to load up Windows (no update or anything. Just me signing in like every other normal day)
- code builds first try without errors
- wait what the fuck
- concludes that i need only verbally intimidate electronics into submission from now on6
When your new feature works (and you installed a new package from Nuget) on your and your co-workers environments. And then you push to the build-QA-server and it breaks...4
"We don't use nuget, it isnt secure. We just put all the dll's into a nuget directory thats available to all of the users in the company."
"But that means your references are all broken and your packages.config are wrong? None of your solutions build that are in source."
"We don't check in solution files either. That causes clutter in TFS."2
For the past 5+ years all I’ve heard from DevA and DevB is what a mess our source control is, we should be using our own custom nuget feeds,..Monday morning quarterback this…Monday morning quarterback that.
This year the department manager gave them the green light to start from scratch. Like ‘green field’ start from scratch. If I were involved, I would have been excited with such an opportunity.
For the past two hours all I’ve heard is ..
DevA: “What should we call this namespace?”
DevB: “I don’t know, I can’t make that decision.”
DevA: “Yea, that’s a business decision. Let’s call it Common for now.”
DevB: “Yea, it’s stupid, but we can change it later.”
DevA: “What about logging project?”
DevB: “Well, how about Core? Every project should have a Core.”
DevA:”Ha ha…like .Net Core. I like it.”
On and on…it’s all I can do from throwing my chair right now.1
I don't know if I should call this a rant or not. I spent most of X-mas hacking away my code I haven't touched over a year and released the library to NuGet. Woot!
This has to be the way devs should spent holidays
Finished a validation library and knowing the common excuse for not using code already written (devs come down with 'not invented here' syndrome) is "I would have used it, if there was documentation". Spent this week documenting each class/method, diagrams, scenario based code examples, sent to my boss for review ...
Boss: "Wow...this is fantastic. All our libraries should have this level of documentation. You even updated the project's Nuget package to include a link to the documentation. Devs won't have an excuse now. I'll clear your plate for the rest of the year so you can get started."
What the hell did I just do to myself? FML.2
Current project I'm working on requires that I import data from an MS Excel workbook using .NET.
No problem, I'll just use the handy OpenXML API. Works just fine. Implement my solution with no hiccups.
The user needs to have the file open at the same time though, so that they can fill in some information in the app's GUI about which columns to pull in. Uh oh.
Turns out that Windows doesn't even let you READ an Excel workbook if anyone has it open. Through the Office GUI I get the option to open it in read-only mode in this case. Through .NET though? Not on your life. Fucking IOException. No matter how I try to open it, doesn't work.
Can't even copy the fucking thing into a temp directory (which makes absolutely no fucking sense).
Only solution I've found to try and get access to the open file is to use Shadow Copy/Virtual Snapshot Service to try and trigger a backup of the file mapped to a virtual directory. Can you say overkill?
Going to try to implement that after lunch. There's a nuget package that wraps the Win32 API at least, but that requires VC++ Redist dependencies with we don't ship with currently.
This has gotten blown way out of proportion. I'm so irritated.8
when your IT policy means that you have to submit a tech request for each nuget package you know you're in for a long day
Took over an open source project today. There's something quite scary deploying a fix to NuGet which has 18,000 downloads 😰4
Fuck MS, why couldn't you update the NuGet API URL when NuGet updated? The warning on nuget.org states,
"This package will only be available to download with SemVer 2.0.0 compatible NuGet clients, such as Visual Studio 2017 (version 15.3) and above or NuGet client 4.3.0 and above"
It says nothing about using the V3 endpoint, so if you''re like me and updated NuGet to 4.5 and still got nothing but
"NU1101: Unable to find package Foo.Bar. No packages exist with this id in source(s): https://www.nuget.org/api/v2/"
...then you'll be very confused until it strikes you that there might be a new API version. Even if MS doesn't want to deprecate the V2 API just yet, it would be awfully nice to just state on the frickin' site that not only do you need NuGet >= 4.3.x, but also the correct feed URL.
$_DEITY knows how many dev-hours have been lost to this shit.
This one is easy, being forced to use visual studio! In fact I made one or two rants about it.
To top it off using NuGet as a pm was also not a great experience to say the least.
Luckily I was not alone and my team agreed and we rewrote the entire legacy code in Java... A much much better experience!
So that was my worst experience.. My best experience was that I started my first big non-school related project and I am super excited!!
Dear Microsoft, I see what you were going for, and I love you for it; but for the love of god, please fucking fix the clusterfuck that is Nuget.
I use a private feed for client work, and I have the public source registered too, so why would installing a new .core template from Nuget fail just because it tried the private feed first and shit itself?
It really shouldn’t be this hard.
WTF is wrong with with you VS?!111 I only updated these efing NuGet packages and my whole project goes down the toilet? Don't tell me these files are not there!! THEY ARE!!!! I SEE THEM!!!
...ohh i forgot, my fault! these files in my packages folder are the new ones and YOU STILL WANT THE OLD FILES BECAUSE YOU FORGOT TO UPDATE YOU FUCKING PROJECT FILE!
A client project came with a bunch of references missing, and nuget wasn't properly restoring them. I've just spent most of my weekend trawling through the dependencies, extracting them from their nuget packages, and putting them in the appropriate folders manually.
Slowly developing a horrid hatred of nuget...
Can I call myself alone when I update Visual Studio or some nuget package and suddenly the project won't compile anymore? Am I the only one?1
> Build project
> 13 Errors: Could not find reference
> Uninstall and reinstall NuGet package
> Build project
> 158 Errors: Could not find reference
Have spent the better part of two days trying to fix the build because I foolishly tried to update some NuGet packages :-(
Ah, the joys of using a bleeding edge web framework! After updating a bunch of NuGet packages, I get the TypeInitializationException from hell. Googling the error message turns up void, because seems to be me and about a dozen other devs using this framework.
2-3 new threads per week in the support forum and mentioned in a total of 288 StackOverflow questions. It feels lonely using this framework, but the design is so darn promising...5
Why the fucking nuget needs a Microsoft/whatever account and asks for it every 3 seconds? FUCK YOU, you can just install dependencies manually without any fucking account why you fucking bug people perpetually with login screens
public Geopoint(double latitude, double longitude)
Latitude = latitude;
Longitude = Longitude;
Me: "why is the longitude always 0"
FUCK FUCK FUCK FUCK FUCK FUCK
Good job that didn't make it onto Nuget... oh, wait, yeah it did.6
Fcuk dotnet and nuget and dotnet restore and nuget package restore and dotnet core and dot net framework and dotnet standard and everything with their unnecessary complexities.
Fcuk them all. Fcuk MS.15
Starting a project on Xamarin.
Cant decide between Shared project or PCL
Want to be able to share code/UI design between multiple apps
Can't find any nuget package to ease REST API consumption.1
Idk if It's my luck or something, but as much as I love Microsoft, EVERY fucking thing of it that I use, has bugs.
I report them, they get fixed (eventually)
Visual Studio enterprise taking 2mins+ to report a simple error on debug
That error happens within one of Microsoft's Nuget Packages for OneDrive Enterprise for UWP
Oh and if that wasn't bad enough, my machine is a Surface Book 2 and the cursor still stutters through it all (and on idle half the time)
Am I cursed or something?2
I'm Beck at my parents home again and wanted to some a problem I'm having with FB "intelligent" aka dumb UI. But my motivation to code jus got thwarted bc VS 2012 is too old... and can't install the Nuget packages I need...2
The lovely moment when you find the library which does everything that you’ve been looking for, install the flippin’ NuGet and get busy....
Next day you compile and run... just to make sure that the old stuff are still working, only to find out that yesterday’s NuGet flipped up everything else’s dependencies.... *fml and let me die !!
I just joined a team using nuget shared packages for a lot of stuff. The Nuget packages get version incremented on merge - but this approach means that if several people are working cross stack and need to change their project and the Nuget package, everyone is going to have to wait their turn to do a merge and ensure their version is correct when merging (or it won't build).
What are the ways around this and still use nuget packages? I can't stand the though of working on totally different functionality to someone else and have to deal with this shit.
A single fucking NuGet package is missing in release mode. That’s the only goddamn explanation I have and it makes no sense. Why the FUCK does ACR.UserDialogs only get compiled in Debug mode?!
God I fucking HATE UWP.1