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"
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 site12
Just need to get this off my chest. Started a new job 3 weeks ago at a company that has been around ~18 years, it is only recently that they have started to grow more rapidly. I was brought in under the guise that they wanted to embrace change and better practices and so said I was up for the challenge.
In my 2nd week I was asked to produce a document on tackling the technical debt and an approach to software development in the future for 3 consultants who were coming in to review the development practices of the company on behalf of the private equity firm who has taken a major stake in the company. I wrote the document trying to be factual about the current state and where I wanted to go, key points being:
Currently a tightly coupled monolith with little separation of concerns (73 projects in one solution but you have to build two other solutions to get it to build because there are direct references.).
Little to no adherence to SOLID principles.
No automated testing whatsoever.
Libraries all directly referenced using the file system rather than Nuget.
I set out a plan which said we needed to introduce TDD, breaking dependencies, splitting libraries into separate projects with nuget packages. Start adhering to SOLID principles, looking at breaking the project down into smaller services using the strangler pattern etc. After submitting what I had written to be part of a larger document I was told that it had been tweaked as they felt it was too negative. I asked to see the master document and it turns out they had completely excluded it.
I’ve had open and frank discussions with the dev team who to me have espoused that previously they have tried to do better, tackle technical debt etc but have struggled to get management to allow them. All in all a fairly poor culture. They seem almost resigned to their fate.
In my first 2 weeks I was told to get myself acquainted and to settle myself in. I started looking at the code and was quite shocked at how poorly written a lot of it was and in discussions with my manager have been critical of the code base and quite passionate and opinionated about the changes I want to see.
Then on Friday, the end of my third week, I was invited to a meeting for a catch up. The first thing I was told was that they felt I was being too openly critical in the office and whether I was a good fit for the company, essentially a stay or go ultimatum. I’ve asked for the weekend to think about it.
I’ve been a little rocked by it being so quickly asked if I was a good fit for the company and it got my back up. I told them that I was a good fit but for me to stay I want to see a commitment to changes, they told me that they had commitments to deliver new features and that we might be able to do it at some point in the future but for now I just needed to crack on.
Ordinarily I would just walk but I’ve recently started the process to adopt kids and changing jobs right now would blow that out the water. At the same time I’m passionate about what I do and having a high standards, I’m not going to be silenced for being critical but maybe I will try and tackle it in a different way. I think my biggest issue is that my boss who was previously a Senior Developer (my current position) has worked at the company for 12 years and it is his only job, so when I’m being critical it’s most likely criticising code he wrote. I find it hard to have the respect of a boss who I had to teach what a unit test was and how to write one. It makes it hard to preach good standards when by all accounts they don’t see the problems.
Just wondering if anyone has suggestions or experience that might help me tackle this situation?12
Fuck spent like 2 days just to figure out dev build packages since they doesn’t allow nuget restore on dev server4
when the junior dev updates all npm & nuget dependencies in the project to the latest beta versions to make an impression right after joining the project...2
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.4
Our project at work goes live in 3 weeks.
The code base has no automated tests, breaks very often, has never had any level of manual testing
will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.
We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.
Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.
We have no testing team, or qa team of any sort.
Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.
We don't use any file streams so everything is just shoved in the buffer on the server.
Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.
No one looks at the pull requests, they just click approve so they may as well push directly to master.
Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.
I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.
Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.
Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.
Our customer facing fe app is not dry because no tests so it was decided it was better this way.
Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.
Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.
Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.7
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.)
installing visual studio & nuget & git integration
- nuget: WORKS
- templates: WORK
- framework: IS COMPLETE
- support for design patterns: UP TO DATE
-have a ide which is clear to be the ide to develop in microsoft/c# area, kept up to date, etc..
installing eclipse & maven
- try to find out which version suits you best in that open source jungle, install it
- install jdk
- play around with the eclipse settings to point it to jdk instead of jre
- google a settings.xml for maven
- fail do create a maven build, so the .mv directory is here, so you can
- place the settings there
- manually import some certs
- try if maven dependencies work
- google how to define running goals
- now define your running goals
- BUT as a reward, the git plugin just works without having to troubleshoot tomorrow too
- hope they wont update soon4
If I have to hear chocolatey, Choco, nuget, or coded ui much more, I'm going to vomit up my spleen.
Give me *nix or give me death.6
Fucking hate working with dotnet. Just spent half an hour fixing the most fucked up bug.
So I installed a nuget package on my computer, tested everything, it worked, and pushed. My classmates then pulled it to their pc, and holy hell broke loose.
Everything was red, it couldn't even import System! By a turn of luck, I looked in the .csproj file, and saw that it had made an absolute path to the nuget package on my computer. Well no fucking wonder it only worked on mine then!
And here's the weird thing: it only did it now, it hasn't done it with the other packages we've imported3
My first packages, uploaded to nuget!
A simple neural network library, written in C# (.Net Standard)
Here's a link:
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
- 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 on7
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
*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
"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
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
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
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
Made a simple jwt auth server with express (node.js) . Used one JWT library that took me no longer than 5 minutes to understand almost all of its functionality and therefore quickly get to work.
Started the JWT auth flow for another app in .NET core 2.0. Microsoft has a recommended JWT library with more than 20 million downloads. Sooooo complex. Every tutorial found is a 50 minute minimum read with an outrageous amount of understanding around the library to even get a JWT token generated.
I guess thats part of the reason I've gone into c# was so i could become much more of a seasoned developer that has a more low level perspective but this is ridiculous.
with the npm library its literally a generateToken method that takes your encryption type string, an object of your claims and your secret to use for signing. With the nuget library im having to do the HMAC hashing manually, utilize more then 10 classes and peace them all together.11
I just woke up and on my computer screen there’s big announcement.
Github launching code package registry beta program.
Available repositories: npm, gem, mvn, docker, nuget.1
When updating nuget packages takes longer than cloning, configuring and compiling the Linux kernel...
Took over an open source project today. There's something quite scary deploying a fix to NuGet which has 18,000 downloads 😰4
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.
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!!
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!
> Build project
> 13 Errors: Could not find reference
> Uninstall and reinstall NuGet package
> Build project
> 158 Errors: Could not find reference
So been doing a TFVC -> Git conversion the last 3 weeks. I'm finally seeing an end to this mind numbing frustrating mess, so I was thinking 'this is a good time to write down my experience in a rant'.
So first of all, I'm working on a project that's about 10 years old, and didn't have a serious refactoring in that time (still runs on .net 4).
The project structure is f*cked up and seriously complicated the git conversion. For example forms only used in the winform application were in a solution for a web app, and file referenced in the windows application. But due to the fact that these forms also needed references to some business logic in the winform app, I had to constantly jump from one project to the other, fixing references to get this shit in NuGet. Sadly this wasn't the only case, and the other 40 project I had to convert from TFVC to Git had equally f*cked up stuff.
Only thing positive to come of this, pretty much decided to leave and start as a freelancer. At least I'll get payed better for doing shit like this, and I know it'll be a temporary thing and can move on after it's done.6
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
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.1
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...
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.
Any .NET Core and Vue.js developers here?
I made this template( Nuget ) showcasing how to use .NET Core MVC with Vue as a multi-page application. You can build multiple "mini spa's" to enhance UI or simply use plain .cshtml and razor if you don't need Vue on a particular page.
I would like to know, how many of you fellow .NET developers actually use full SPA applications and is something like this useful?
It features Vue.js, Typescript, Vuex, Vue router, Bulma, Sass and Webpack 4.
I heavily use Vue CLI and SPA's but have notices that a lot of people around me still like this approach.9
Just joined a new company and can only describe the merge process as madness.....is it or am I the one that is mad?!
They have the following branches:
UAT#_Branch (this kicks of a build to a machine named UAT#)
Each developer has a branch with the # being a number 1 to 6 except 5 which has been reserved for UAT_Testing branch.
They are working on a massive monolith (73 projects), it has direct references to projects with no nuget packages. To build the solution requires building other solutions in a particular order, in short a total fucking mess.
Branch from master with a feature or hotfix branch
Make commits to said branch and test manually as there are no automated tests
Push the commits to their UAT#_Development branch, this branch isn't recreated each time and may have differences to all the other UAT#_Development branches.
Once happy create a pull request to merge from UAT#_Development to UAT#_Branch you can approve your own pull request, this kicks off a build and pushes it to a server that is named UAT#.
Developer reviews changes on the UAT# server.
QA team create a UAT/year/month/day branch. Then tell developers to merge their UAT#_branch branches in to the previously created branch, this has to be done in order and that is done through a flurry of emails.
Once all merges are in it then gets pushed to a UAT_Testing branch which kicks off a build, again not a single automated test, and is manually tested by the QA team. If happy they create a release branch named Release/year/month/day and push the changes into it.
A pull request from the release branch is then made to pre-live environment where upon merge a build is kicked off. If that passes testing then a pull request to live is created and the code goes out into production.
Ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh it's a total mess. I knew when I took on this job it would be a challenge but nothing has prepped me for the scale of the challenge!! My last place it was trunk based development, commit straight to master, build kicks off with automated testing and that just gets pushed through each of the environments, so easy, so simple!
They tell me this all came about because they previously used EntityFramework EDMX models for the database and it caused merge hell.9
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
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
So, do any of your poor fuckers have the opportunity - nay, PRIVILEGE of using the absolute clusterfuck piece of shit known as SQL Server Integration Services?
Why do I keep seeing articles about how "powerful" and "fast" it is? Why do people recommend it? Why do some think it's easy to use - or even useful?
It can't report an error to save its life. It's logging is fucked. It's not just that it swallows all exceptions and gives unhelpful error messages with no debugging information attached, its logging API is also fucked. For example, depending on where you want to log a message - it's a totally different API, with a billion parameters most of which you need to supply "-1" or "null" to just to get it do FUCKING DO SOMETHING. Also - you'll only see those messages if you run the job within the context of SQL FUCKING SERVER - good luck developing on your ACTUAL FUCKING MACHINE.
So apart from shitty logging, it has inherited Microsoft's insane need to make everything STATICALLY GODDAMN TYPED. For EVERY FUCKING COMPONENT you need to define the output fields, types and lengths - like this is 1994. Are you consuming a dynamic data structure, perhaps some EAV thing from a sales system? FUCK YOU. Oh - and you can't use any of the advances in .NET in the last 10 years - mainly, NuGet and modern C# language features.
Using a modern C# language feature REMOVES THE ABILITY TO FUCKING DEBUG ANYTHING. THE FUCKER WILL NOT STOP ON YOUR BREAKPOINTS. In addition - need a JSON parsing library? Want to import a SDK specific to what you're doing? Want to use a 3rd party date library? WELL FUCK YOU. YOU HAVE TO INDEPENDENTLY INSTALL THE ASSEMBLIES INTO THE GAC AND MAKE IT CONSISTENT ACROSS ALL YOUR ENVIRONMENTS.
While i'm at it - need to connect to anything? FUCK YOU, WE ONLY INCLUDE THE MOST BASIC DATABASE CONNECTORS. Need to transform anything? FUCK YOU, WRITE A SCRIPT TASK. Ok, i'd like to write a script task please. FUCK YOU IM GOING TO PAUSE FOR THE NEXT 10 MINUTES WHILE I FIRE UP A WHOLE FUCKING NEW INSTANCE OF VISUAL STUDIO JUST TO EDIT THE FUCKING SCRIPT. Heaven forbid you forget to click the "stop" button after running the package and open the script. Those changes you just made? HAHA FUCK YOU I DISCARDED THEM.
I honestly cant understand why anyone uses this shit. I guess I shouldn't really expect anything less from Microsoft - all of their products are average as fuck.
Why do I use this shit? I work for a bunch of fucks that are so far entrenched in Microsoft technologies that they literally cannot see outside of them (and indeed don't want to - because even a cursory look would force them to conclude that they fucked up, and if you're a manager thats something you can never do).
Ok, rant over. Also fuck you SSIS
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
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 !!
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 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
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
Is there a way to tell NuGet Package Manager to not install/run a package when in certain environments? Just like flags on NPM.
Thanks in advance
I try to do some C# on VSCode and i dont understand why my nuget package won't working ... I just try to install sqlite . 😔1