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 site

My code review nightmare part 2

Team responsible for code 'quality' dictated in their 18+ page coding standard document that all the references in the 'using' block be sorted alphabetically. Easy enough in Visual Studio with the right-click -> 'Remove and Sort Usings', so I thought.

Called into a conference room with other devs and the area manager (because 'Toby' needed an audience) focusing on my lack of code quality and not adhering to the coding standard.

The numerous files in question were unit tests files

using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Collections.Generic;
using System.Linq;
<the rest of the usings>

T: "As you can see, none of these files' usings are in alphabetical order"
Me: "Um, I think they are. M comes before S"
T: "The standards clearly dictate system level references are to be sorted first."
Mgr: "Yes, why didn't you sort before checking this code in? T couldn't have made the standards any easier to follow. All you had to do is right-click and sort."
Me: "I did. M comes before S."
T: "No You Didn't! That is not a system reference!"
Me: "I disagree. MSTest references are considered a system level reference, but whatever, I'll move that one line if it upsets you that much."
Mgr: "OK smartass, that's enough disrespect. Just follow the fucking standard."
T: "And learn to sort. It's easy. You should have learned that in college"
<Mgr and T have a laugh>
Me: "Are all your unit tests up to standard? I mean, are the usings sorted correctly?"
T:"Um..well..of course they are!"
Me: "Lets take a look."

I had no idea, a sorted usings seems like a detail no one cares about that much and something people do when bored. I navigate to project I knew T was working on and found nearly all the file's usings weren't sorted. I pick on one..

using NUnit;
using Microsoft.Something.Other;
using System;
<the rest of the usings>

Me: "These aren't sorted..."
T: "Uh..um...hey...this file is sorted. N comes before M!"
Me: "Say that again. A little louder please."
Mgr: "NUnit is a system level nuget package. It's fine. We're not wasting time fixing some bug in how Visual Studio sorts"
Me: "Bug? What?..wait...and having me update 10 or so files isn't a waste of time?"
Mgr: "No! Coding standards are never a waste of time! We're done here. This meeting is to review your code and not T's. Fix your bugs and re-submit the code for review..today!"

Me: What's device and android version do you use on the emulator?

External developer: NuGet

Wtf?

Fucking Nuget...

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?

Refactored an authentication library a while back and teams are now getting around to updating their nuget packages.

It is a breaking change, but a simple one. The constructor takes a connection string, application name, and user name.

A dev messages me yesterday saying ...

Tom: "I made the required changes, but I'm getting a null reference exception when I try to use the authorization manager"

Odd because the changes have been in production for months in other apps, so I asked him to send me a screen shot of how he was using the class (see attached image below).

Me: "Send me a screenshot of how you are using the class"
<I look at what he sent>
Me: "Do you really not see the problem why it is not working?"
<about 10 minutes later>
Tom: "Do I need to pass a real connection string? The parameter hint didn't say exactly what I should pass."
<not true, but I wasn't going to embarrass him any more>
<5 minutes later>
Tom: "The authorization still isn't working"
Me: "Do you still have 'UserName' instead of the actual user name?"
<few minutes later>
Tom: "Authorization is working perfect, thanks!"

A little while later my manager messages me..

B:"I'm getting reports from managers that developers are having a lot of problems with the changes to the authorization nuget package. Were these changes tested? Can you work with the teams to get these issues resolved as soon as possible? I want this to be your top priority today."
Me: "It was Tom"
B: "Never mind."

Fuck spent like 2 days just to figure out dev build packages since they doesn’t allow nuget restore on dev server

Just published my first NuGet Package! 😀

.NET drinking game:
* Drink every time IntelliSense refuses to tell you what the actual error is because it's too busy choking on lambda syntax from a decade ago
* Take a shot every time you discover a closed, unresolved Github issue discussing your current showstopping build/CI problem
* Finish your drink every time the solution to your problem involves either manual edits to your CSPROJ (or whatever) file, or creating a new project altogether and copying all your fucking files over

How to explode a .NET developer, give them this challange:

Write a method.
- I must HTTP Get any site (does not matter what), and return the result
- It must NOT be async, and must directly return the result string (No Task<string>)
- It must use HttpClient
- It must be in .Net framework 4.5 or lower
- No other nuget packages allowed

This was my job today and i want you to share my pain!

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...

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.

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.

No one there understands css properly. Or javascript.

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.

Piece of shit cake. I'll stab you in the goddamn virtual neck with a screwdriver. Not get my nuget packages. Go fuck yourself in your fat fucking ass. Goddamn, who automated this build process. I did. Fuck me.

Me: I like nuget
Someone: I also like nuggets

So I've created this account specifically for this rant. I usually just browse anonymously.

I've recently been hired in a big company that is one of the biggest Microsoft users in the world and my essentially revolves on making it easier for our collaborators to work with SharePoint (and other ms software)

Never in my life have I hit that much of a roadblock. So for the past week I've been trying to integrate what Ms calls webparts. And to modify the default webparts Ms provides you need to their properties (or Metadata). Except here's the big problem these are NOT documented anywhere (unless I failed to find it, if you do know where it is documented please HMU), so I've found myself trying to reverse engineer the js scripts that are served with SharePoint to figure out what the webpart properties are called and what type of data they are! I've been going through endless github repos using the CSOM nuget package (it's the library everyone uses to interact with SharePoint) and I finally found out about this other library called PnP which is a wrapper around CSOM that makes it easier to use. That wrapper has a way for me to load existing page and look at the properties of existing webparts. So here I thought it was the end of my suffering and I could finally get an idea of what it should be. Turns out this method doesn't work because one of the dependencies it has has had breaking changes and they still updated it even though it breaks their code! So for the past two days I've been trying random combinations of key values with different data types and json serialization methods.

Oh and yeah I've also looked at all the http calls via the chrome network tab, the metadata is not served as an individual file but is computed by Ms servers when they're serving you their html files.

So uh yeah run from CSOM if you can..

nuget is a steaming pile of human shit, fuck the entire microsoft ecosystem and fuck anybody who likes it, and fuck you, and fuck me

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.

Fuck nuget, .NET and whole C#, I'm solving problem with dependencies since yesterday.

this is motherfucking insane, that's why I hate microsoft and always will, fucking daddy will tell me what I can or can't (they do same shit to github and nuget) but look at this.

I don't give a fuck about unknown publisher, this is my PC, if I want to install a virus I want to install a virus! for fuck sake

Initiate update of 1 nuget (20+ projects)
Go poop
Come back
It's not done yet

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.)

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 imported

Fucking java library publishing. It's a nightmare. You have to fucking own a domain to publish a shit onto jcenter/bintray/whatever. You have to own the domain, that your lib's package name is. And you MUST verify it, otherwise you won't publish anything. Or you can shit allover your lib with package name like com.github.dumbcoder.mycoollib.

You must to create a ticket for some shitheads that are going to verify your shit for two weeks. They gonna ask you for source.jar, docs.jar and whatever shit.jar they need.

What THE fuck? Who was the asshole that decided name packages in reverse domain name? No FUCKING more ecosystem has such a bullshit. In .net you just make a lib, create a free nuget account, fill some basic info and boom! you have .net package published. Same for npm and rust for example.

Because the fucking package name should be just for structure not for a some dick to own it. Namespace is name-fucking-space.
FUCK JAVA.

Fuck. I just want to fucking use OpenCV on CLion on Windows. Why the fuck do I need twenty fucking PhD's in quantum rocket science to set up a simple project with Cmake?

During the time I just wasted trying to get the correct library to link properly, I could have rewritten all of Tesla's fucking CV functionality from scratch, but instead here I am spending literal fucking hours googling why the fuck does 'recursive_mutex' not name a fucking type in namespace 'std' on mingw.

Fuck C++ I'm going back to C# where I can literally install OpenCV and all of its fucking dependencies from nuget with ***ONE*** fucking click.

- 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 on

Microsoft :

"YOLO All Devops pipeline are now .net 8"

Me, lunching PROD release : "Whatever, I don't use any advanced shit"

Pipeline : "Can't connect to your nuget soure (private) : 401"

Me : What ? You just connected to it in prevous step in pipeline !

Azure : Yah, but prev st ep was using different syntax so it worked

Me : Ok, here you go, same syntax

Azure : Still nop.
Me : WHY ?!!!
Azure : I won't tell you. 401 !!

Me : Fuck you, I 'll rewrite this step from scrath !
30 mins later

Azure : Naaaan, stil 401.
Me : HOW ?!!! You literally use this nuget feed in 2 prev steps with no issues.
Azure : Fuck you
Me : fuck you too.
15 mins later
me to me... Hmm, I've already restored all packages. They "should" stay where they are..
Me : Take that azure : Ignore restoring for this step"
Azure : Oh yeah, that works ! All compiled !

WTF ?!!!! And why they release cha ges without even sending a mail. because fuck us apparently.

God I hate devops....

*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.

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 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...

"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."

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.

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

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.

Nuget

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!!

Took over an open source project today. There's something quite scary deploying a fix to NuGet which has 18,000 downloads 😰

When updating nuget packages takes longer than cloning, configuring and compiling the Linux kernel...

while(true)
bang(head, table);

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.

wire hell - > assembler hell -> DLL hell - > npm/nuget hell

History repeats itself.

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!

Nuget Packages...Need I say more?

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

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?

> Build project
> 13 Errors: Could not find reference
> Uninstall and reinstall NuGet package
> Build project
> 158 Errors: Could not find reference

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...

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.

Sincerely,
Brolls

Huge shout out to NuGet for taking 40 minutes to download a package

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.

EPiServer Forms is probably the worst fucking thing to ever exist in terms of Nuget packages. I would rather shove an entire daikon radish up my asshole than trying to debug the stupid fucking mystery that code is. Wanna tie into the JavaScript events to handle payment validation? Go fuck yourself - u can’t use any external functionality.

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#_Development branch
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.

Developer workflow:

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.

This is a continuation of my previous rant about admob being not very informative when it comes to invalid traffic and the resulting restriction in ad delivery.

I then wanted to use admob mediation to hang in facebook ads. My app is written with Xamarin.Forms.

So first I needed to make some facebook configuration - create an account, let my app review, create some ad placements and other shit. I came to the point where I had to put in a link to my privacy policy and the link could not be accepted due to some SSL fuckup -.-'

I then found out that there is an issue with my SSL Chain. With the help of whatsmychaincert.com I solved that issue. Little side note here: I have limited knowledge of that stuff and my cousin helped me set up my homepage so I had no idea what I was doing. Did a snapshot and luckily I did not needed that as everything worked :)
This took me around half an hour just so I can paste the fucking link to activate my app in facebook developer portal.

After that I made the whole mediation configuration shit - not an issue as google documented this quite well but it took some time.

Now comes the shitty part. To use admob mediation you need adapters to the other ad network. I found a nuget package with exactly what I needed just to find out that it is outdated. So I pulled the repo and saw that this thing is an aar binding library. Never did that stuff so I read some docs again. Updated the package and consumed it in my app.

The google docs then said "Use this mediation test shit to check if you did everything correct before going prod" - aar binding nr. 2 (but I am now familiar with that :P). This thing then told me that facebook ads could not be loaded because the SDK version is outdated -.-' SDK version comes from another nuget package which is referenced by the first aar thingie. I tracked that thing back to a repo where I found out that they are indeed totally behind. So I downloaded the aar, made a binding lib and bound that to my first aar binding lib as that depends on this.

Put that all back in my app - tested mediation and fucking finally after 6 hours everything comes together! all lights are green and things work.

Sorry if this is not quite a rant but it was quite a journey and I just had to share it.

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...

Started adding new MVC project to main solution at work. Started getting assembly reference errors across the projects during testing. Figured I might as while update the few assemblies that are complaining instead of trying to downgrade to maintain the current state of things. Shouldn't take too long right?....8 hours of staring at configs and running and rerunning nuget commands to get all the versions lined up across 120 projects....thank God we have extensive unit and integration tests...

Have spent the better part of two days trying to fix the build because I foolishly tried to update some NuGet packages :-(

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.

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

Hi there!

I've been worrying about the following problem for months now and I don't find any solution. Maybe anybody of you can lead me the way.

We are developing a software suite which consists of a number of desktop applications:

* 12 applications written in C++; all over 20 years old; further development by 5 or 6 guys (one man armys) - mainly bugfixing, changes of law implementations, small features
* 2 applications we are currently writing in C#; completely new developments of existing C++ applications; scrum teams with at least 5 guys; this is, where we put our focus in

These applications (C++ and C#) are sharing some core assemblies and are interacting with each other. So they are not independent.

We organize them in a mono repository in one huge solution, which consists currently of about 500 projects.

Advantages:

* With all projects in one solution and through project references, Visual Studio takes care of the right build order
* Code navigation is superb - every single line of code is accessible - this makes refactoring easy
* Every developer can map the branch and build the whole suite locally
* Debugging on the local machine is easy
* DevOps pipeline is straight forward - it just have to build a single solution

Disadvantages:

* The huge solution is extremely slow.
* If you want to build the solution or you want to debug (which does essentially the same as a pre step) Visual Studio is building a lot of projects, although they haven't been changed. Their detection is buggy. So sometimes you wait 2 minutes until it starts the app. That slows us down a lot.
* Full builds need about an hour, because its building the same projects (even if they haven't been changed) over and over again (with ready made nuget packages this could be improved a lot I think)
* If a core team member changes some core apis, he is changing the calling code too, although he doesn't know the calling code, because another team has written it. I don't think, that's best practice and it doesn't scale.
* Often, a C# developer has to mess around with C++ building problems, because the C++ projects are in the same solution
* It gets more and more confusing and frustrating, because there is no clear organizational seperation between apps and nobody can't just focus on his app alone.

Idea:

I was thinking about putting the whole framework and core projects in a new solution (around 100 projects). Then we could take all old C++ projects and put them also in a new solution (around 200 projects). This would leave the newer projects (new applications - C#) in the existing solution.

This should speed up things, and would be a first step to better seperation, BUT:

How should the integration process look like?

Scenario: Core team is changing an API in our framework

Current process: Because all projects are in the same solution, they change the calling code too. So it's immediately integrated and the app developers just have to do "get latest".

New process (?): Core team is providing the changes through a nuget package (new version). So does every developer now has to keep track of if there is a new package version and if yes, do the integration? And how can we coordinate the different teams, so they are upgrading all at the same time? Because we ship our applications as a suite, all apps has to use the same versions. Or should we automate the integration process? Is there a best practice?

I have to add, that our core team is making changes very frequently, so the integration process will have to happen often.

Any ideas/feedback/inspiration?

Thank you so much in advance!

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.

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'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...

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)
but goddamn.
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?

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.

does anyone use nuget in visual studio?

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

We have an internal nuget package that wraps up the IConfiguration+ConfigurationBuilder for various .net core console/service apps (TL;DR, because people got creative), and it has a dictionary property for the common sections we use. AppSettings (for backward compatibility), ConnectionStrings, and ServiceEndpoints. If the need arises, I can add methods to return any type of object (no one has requested yet, we try to keep configs dead simple)

ex. var myDatabaseConnectionString = ConfigurationManager.ConnectionStrings["MyDatabase"];

Code review for someone who updated a .net framework app to .net core and they wrote their own IConfiguration wrapper for accessing the appsettings.json file, so I pointed out that we already had a library for that.
In the reply, he said he couldn't use our library because it had an 'AppSettings' property and since his appsettings.json file didn't have that section, he didn't want to cause a runtime exception.

OK, WTF...I even sent him a link to the documentation (includes explaining the backward compatibility part)...why the frack would you think because a property exists and you don't use it, that would cause some kind of runtime exception?
We have dozens of .net framework apps migrated to .net core with zero code changes and no one ever brought this up as a concern (because, why would they?)

Deep breath...ahhh...I respond that not having an AppSettings section in the appsettings.json file won't cause an exception, if you don't have one, don't need it, you don't have to use it.

He went ahead merged+committed his code anyway with his own IConfiguration+ConfigurationBuilder plumbing.

Code addiction is real kids...it's real.

Damn, .NET devs are really and I mean really bad at writing documentation. It is either over-engineered (anything from Microsoft) to the point you can't find shit. Or it is almost non existent and you have to study the repo and read classes, etc. (ANY .net core nuget for writing CLI apps, heck I would argue almost any nuget in general)

4 pages on github WIKI + examples that cover 20% of use cases are not a bloody documentation mate!!!

I used to be linux + any of Python/Go/JS/Ruby/Elixir guy and almost never had problems with poor documentation.

Now living in Microsoft world with .net and powershell is terrifying.

Any good resource on how to create NuGet from wpf custom control with behaviors? I cant find anything thats somewhere near readable.... I want to make NuGets of CC and behaviors so i can easily implement in my exams and save time during developing 👍

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.

Has any one used spell checker library on nuget package?
My supervisor wants it but I could easily use Javascript plugin.

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 . 😔

Jimmy Bogard purely because he gets loads of hate on social media because of idiots abusing the free libraries he puts up on nuget, and blaming him because they’re dense. And has Nick Chapsas constantly flaming him.

Jimmy doesn’t give two fucks. Be like Jimmy.