How I feel when code is working

Recruiter: this job is about dotNet and git.
Me: I never worked with dotNet before.
Recruiter: Okay, maybe we can get you in for git then.

FML!

I enjoy living dangerously.

im a senior c# .net dev and i wear glasses.
i can c# and cant c# at the same time.
ha! beat that!

So where to start... Let me preface this by saying I am a Software Architect for C# and do 99% dotnet development.

I just received a phone call from our Director of Development asking me to look at adding a feature for SSO with our companies main development project, which is written in PHP. I hope I made the correct changes but since I am not a PHP dev... I am not 100% confident in my code.

Now I am writing this as we are making the deployment Friday, December 29, 2017 at 5:00 pm. I should add that I am going on vacation for the next week.

So let me summarize... I am not a PHP developer, the non-PHP developer is making PHP changes on a Friday Night, and before a long weekend and before going on vacation.

I would like to point out that I said I was not 100% comfortable with this... but well this is what they wanted. I am not even sure what really to say about this though.

NO GOD PLEASE NO

After 3 years of working with Node.js, I have finally snapped

Node.js is cringe

I am .NET gang now

Yes you do

That awkward moment when I was able to run three docker containers on a 512MB server:
1. DotNet core web service
2. MySQL
3. OpenVPN

BUT I cannot run:
1. NodeJs web service
2. MongoDB container

Spent two hours configuring the damn server to get hit by this T_T

November brings .Net 5, for anyone who cares about that, and after listening to my husband watch Ignite "reveal" advertising container, and all the enterprise virtue signaling therein, I am now to the point where the only thing I can think is "Fuck you Microsoft, and Fuck .Net 5."

During a 30 minute speech, the director of the dotnet platform commits the following flagrant faux pas:

1. Introduces tons of visual studio easy buttons for shit we already do, no mention of VS code support.
2. Shows tools that anyone other than the most insular enterprise mouth-breather have been using for no less than 6 years
3. Gives absolutely no credit to the Open Source community projects backing the features he's showing
4. Shows nothing but mono-cloud integration, makes no mention of any other cloud targets for new features
5. Acts like "deploy your app the cloud from IDE" is something anyone should be doing in 2020
6. Showed an API repl that is pathetic compared to httpie when it was in alpha
7. Showed blazor loading from cache and said "Look at how instantaneous it is" (if you ignore the 5mb of cached payload it took to run the hello world demo)
8. Shows Project Tye, presenting it as a new groundbreaking xyz, fails to mention helm already exists

What's absent is what is most offensive:

- acknowledgment of community contribution
- no linux/mac tools, entirely windows-centric (which jives with my prediction of second-class citizenship for the people who contributed to .net core the most)
- cross-cloud capabilities
- bash/zsh (again with the untermensch relegation)

Fucking microsoft back to their old bullshit.

So today, i taught my professor something, and he was genuinely curious. I also told him about my part time job building websites. He is a really cool guy and wasn't a dick about a student knowing something more than himself. There should be more professors like him.
What a wonderful world we live in!

My internship so far :
-SVN
-Visual Basic
-A company proprietary framework that I won't ever use again
-Windows everywhere
It kinda fails my technical expectations. But what's great is that everyone there is very nice and relaxed, Nerf gun fights at 4pm and playing cards after lunch :D

!rant
I'm just amazed what 512MB of RAM can do :O
That's htop from my VPS I feel sorry for the CPU though.

It is running three docker containers:
1. Dotnet Core
2. MySQL
3. OpenVPN

Developed my first app using SQLite. Am I late into the game?

!rant

I used to be someone who disliked microsoft and windows, but with the new CEO Satya Nadella things are going in the right direction. Really love the stuff microsoft is doing right now! bash for windows, 24 bit color console, visual studio code and the monaco editor, dotnet core ... lately I have switched to windows 10 from OSX and I couldn't be happier :)

"Will i be able to understand the da vinci code by the end of my work experience"?

Creating RESTful APIs with dotnet core on Linux, without any pressure from PMs.

Method 1:
1. Read others' people answers on wk70
2. Apply
3. ???
4. Profit
Method 2:
1. cd <ProjectName>
2. git init
3. dotnet new sln
4. dotnet new console #or webapi/lib
5. code .
6. git commit -m "Initial commit"
7. git remote add origin <github link>
8. git push origin master -u
9. profit

dotnet core is not bad stuff. there, I said it.

C# FTW! New features for C#7.0:
blogs.msdn.microsoft.com/dotnet/2016/08/24/whats-new-in-csharp-7-0/
tuples, pattern matching, local functions *coder-gasm*

15 years ago I had a job interview as technical leader. They asked me about the trendy framework in those days, Struts. I didn't know much to be honest. I actually started to study java the month before. I was 30 y.o. and I managed to sell myself well.

I got the job. I never saw Struts, the real job was to migrate a z/OS application written on PL/I for DB2 (all things where new to me, I programmed something in VB when I was younger, before studying a career in statistics). Anyway, somebody else already scaffolded Struts, I implemented some business logic here and there, and mostly tried to make sense of the monster-legacy.

Fast forward now.
Two months ago I was interviewed on the last version of Angular and AWS devops, kubernetes etc. I managed not to look completely idiot, but honestly, I never went beyond an Hello World in Angular, and kubernetes, well, I like the name.

I got the job as Technical Architect.

First project I'm assigned to: migrate a 15 years old Struts application to cloud.
Somebody has containerized everything.
Somebody will scaffold a dotNet application.

I'll watch. Maybe I'll write some nice powerpoint presentation. Maybe I'll fill in some business logic in some methods.

I wanted really to be a technical Architect and do things other modern people do.

I actually wanted to learn something.

Anyway.
For 160K$ a year is not bad, I wouldn't complain.

Fun day, lots of relief and catharsis!

Client I was wanting to fire has apparently decided that the long term support contract I knew was bullshit from go will instead be handled by IBM India and it's my job to train them in the "application." Having worked with this team (the majority of whom have been out of university for less than a year), I can say categorically that the best of them can barely manage to copy and paste jQuery examples from SO, so best of fucking luck.

I said, "great!," since I'd been planning on quitting anyways. I even handed them an SOW stating I would train them for 2 days on the application's design and structure, and included a rider they dutifully signed that stated, "design and structure will cover what is needed to maintain the application long term in terms of its basic routing, layout and any 'pages' that we have written for this application. The client acknowledges that 3rd party (non-[us]) documentation is available for the technologies used, but not written by [us], effective support of those platforms will devolve to their respective vendors on expiry of the current support contract."

Contract in hand, and client being too dumb to realize that their severing of the maintenance agreement voids their support contract, I can safely share what's not contractually covered:

- ReactiveX
- Stream based programming
- Angular 9
- Any of the APIs
- Dotnet core
- Purescript
- Kafka
- Spark
- Scala
- Redis
- K8s
- Postgres
- Mongo
- RabbitMQ
- Cassandra
- Cake
- pretty much anything not in a commit

I'm a little giddy just thinking about the massive world of hurt they've created for themselves. Couldn't have happened to nicer assholes.

dotnet core is love,
dotnet core is life (and devRant).

I am using VS Codium instead of VS Code to see what kind of things change when you scrape the Microsoft out of it. Apparently some tools for dotnet core like debugging are locked down and only allowed to run in Microsoft made IDEs.
I hate the sneaky Microsoft API lockdown nonsense and will be steering future projects away from any dotnet core development. I thought this was dead in VS Code but they managed to sneak it in.

Spent a month working on a website that relied on crawled data
Got the memory leaks and usage down from 700mb to ~150mb
CPU usage from ~100% to <5%
Shrink-wrapped the DB requirements based on data
Created self-supporting services and what not

When everything FINALLY worked good enough for me to look at it and go "damn, this actually worked"
the whole monitoring sys got dyed in red :v
A quick look up and my crawlers exhausted my godaddy's per-user db limits.

Kill me.
Just fuckin kill me.

I just started a job as a junior C# dev.
My project at work includes:
-no coding style
-multiple classes in one file
-all classes are static
-who needs interfaces?
-typos in variable names
-more than 3 levels of inheritance
-conf files such as "blabla.xml"
-comments? documentation? nope
-copy&paste everywhere

Client outsourced this project to us to get the job done properly :D

Looks that I have some opportunity to show my talent.

.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

2020

Dotnet Core and dotnet framework are now one (november).

Blazor has an official release for client side webassembly.

The new holy war in C#:

Point p = new Point(5, 3);

vs.
var p = new Point(5, 3);

vs. (new)
Point p = new (5, 3);

and... FIGHT!!

At work, my closest relation is with the DBA. Dude is a genius when it comes to proper database management as well as having a very high level of understanding concerning server administration, how he got that good at that I have no clue, he just says that he likes to fuck around with servers, Linux in particular although he also knows a lot about Windows servers.

Thing is, the dude used to work as a dev way back when VB pre VB.NET was all the rage and has been generating different small tools for his team of analysts(I used to be a part of his team) to use with only him maintaining them. He mentioned how he did not like how Microsoft just said fk u to VB6 developers, but that he was happy as long as he could use VB. He relearned how to do most of the GUI stuff he was used to do with VB6 into VB.NEt and all was good with the world. I have seen his code, proper OOP practices and architectural decisions, etc etc. Nothing to complain about his code, seems easy enough to extend, properly documented as well.

Then he got with me in order to figure out how to breach the gap between building GUI applications into web form, so that we could just host those apps in one of our servers and his users go from there, boy was he not prepared to see the amount of fuckery that we do in the web development world. Last time my dude touched web development there was still Classic ASP with JScript and VBScript(we actually had the same employer at one point in the past in which I had to deal with said technology, not bad, but definitely not something I recommend for the current state of web development) and decided that the closest thing to what he was used was either PHP(which he did not enjoy, no problem with that really, he just didn't click with the language) and WebForms using VB.NET, which he also did not like on account of them basically being on support mode since Microsoft is really pushing for people to adopt dotnet core.

After came ASP.NET with MVC, now, he did like it, but still had that lil bug in his head that told him that sticking to core was probably a better idea since he was just starting, why not start with the newest and greatest? Then in hit(both of us actually) that to this day Microsoft still not has command line templates for building web applications in .net core using VB.NET. I thought it was weird, so I decided to look into. Turns out, that without using Razor, you can actually build Web APIs with VB.NET just fine if you just convert a C# template into VB.NET, the process was...err....tricky, and not something we would want to do for other projects, with that in we decided to look into Microsoft's reasons to not have VB.NET. We discovered how Microsoft is not keeping the same language features between both languages, having crown C# as the language of choice for everything Microsoft, to this point, it seems that Microsoft was much more focused in developing features for the excellent F# way more than it ever had for VB.NET at this point and that it was not a major strategy for them to adapt most of the .net core functionality inside of VB, we found articles when the very same Microsoft team stated of how they will be slowly adding the required support for VB and that on version 5 we would definitely have proper support for VB.NET ALTHOUGH they will not be adding any new development into the language.

Past experience with Microsoft seems to point at them getting more and more ready to completely drop the language, it does not matter how many people use it, they would still kill it :P I personally would rather keep it, or open source the language's features so that people can keep adding support to it(if they can of course) because of its historical significance rather than them just completely dropping the language. I prefer using C#, and most of my .net core applications use C#, its very similar to Java on a lot of things(although very much different in others) and I am fine with it being the main language. I just think that it sucks to leave such a large developer pool in the shadows with their preferred tool of choice and force them to use something else just like that.

My boy is currently looking at how I developed a sample api with validation, user management, mediatR and a custom project structure as well as a client side application using React and typescript swappable with another one built using Angular(i wanted to test the differences to see which one I prefer, React with Typescript is beautiful, would not want to use it without it) and he is hating every minute of it on account of how complex frontend development has become :V

Just wanted to vent a little about a non bothersome situation.

Finally got a job I see myself staying in more than 2 years :) A boss that give us time to write / read blog posts.
Flexible work life.
Working with all the new stuff like dotnet core, docker :)

Found my old code.

You gotta admit, that's some clean code there, considering I learned C# only for a year at that time.

But those comments....
VeRy WeLl WrItTeN, vErY dEtAiLeD, vErY gOoD

Porting a 7 year old web app from php to dotnet core. Not sure if happy or sad...

Metal sub-genres are really getting out of hand...

Rocking some C# swag today 😎

Dear Microsoft,

you're fucking awesome , can't believe I'm saying this but I couldn't work without Visual Studio anymore.

The last year I had projects on all platforms out there and I've used dotnet for all of them.

Mr Nadella is the best thing that happened to you ever.

Visual Studio is free and like the rest of the tools it's only a matter of Time till you open source Vs.

Thank you !
Proud to be a corporate fanboy.

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

Today I got a segmentation fault in C#.

No pointers. No unmanaged dependencies. Just managed code. Seg fault.

Uhhhh...

This happened 3 years ago in my previous company. It was a small start up company and we worked on PHP stack. One of the its ex-founders had written Windows Mobile App which now had to be upgraded with new features. So we hired this new dot net guy. I always thought dot net guys were ELITE coders and was excited to see how they work.
While I played Xbox and had fun, our dot net guy stuck to his workstation furiously working. My boss who was casually strolling out of his office for a stretch saw dot net guy working hard and suggested we all developers should take him as an example.
20 days went by and each day the dot net guy did the same. He came, he silently worked on his workstation, he left in the evening. In those 20 days my boss asked twice to the dot net guy if he has finished features he was assigned but he said he did not. After a month when he said the same negative answer and had nothing to show for the work he has done he was fired.
I was so curious to see what code that ELITE coder had written for a month but could not deliver a feature(Maybe some error he could not fix?). So I open the code repo on which he worked and I see 30 commits from that guy to it. He had made a single commit each day(Fair enough he wants to commit everday before leaving). It was time to check his commit diffs to see his ELITE code. What do I find? In every fucking commit he either added a blank line to the DocBlock or removed the same. Nothing less nothing more! So much for the hyped not-so-ELITE dot net guy...

My biggest regret was using string builder to build html responses

Hey can I talk to whoever made these constructors at the .net foundation/microsoft?

I'd like to... talk

I just finished upgrading a dotnet core 2.2 WebApi + Console App to dotnet core 3.1 and it was a very smooth process with very minor changes to my code.

Not a rant, just posting because it is the first nice thing that has happened for me in a while now.

There was one time i went to Python dev position. HR company test was first of process and test was all about dotNet and C#, plus VBScript. I sat there until the finish time, did nothing.

As I get deeper into this project the more I fucking LOVE C# 💜

Although I have been using core. I have VS installed but haven’t used the framework yet. Are there any differences I should know about and get used to?

But l like microsoft and it's stuffs

Okay, let's get this fight rolling: here's a typical .net error message:

An error occurred. (An error occurred.) The type of this error was: An error occurred. Additionally, an error occurred while the error was occurring. The type of this error was: An error occurred.

Additional information: NullReferenceException at line... haha not really fucko, an error occurred.

better late than never.
So I just decided to go with Gitlab after being a Microsoft Team Services user.
To do next on my list:
Move away from .Net for backend services, any suggestions? I use dotnet core due to being able to easily finish what I want and with less code to write. Tried Springboot for Java but not a Java fan, might checkout kotlin though

Does anyone know of any apps/companies that are using .Net core in production?

I’ve started a project at work which consists of a webapi written in dotnet core, a react spa for the front end and xunit for testing.

I’m just curious as there are loss of sites about things written in Rails, or django, but almost nothing about dotnet core.

I thought sunday will be the best day to read the dotnet documentation... at the end of the day I can honestly say I know all top rants now.

Ah good ol' refactoring summer.

*Me starts refactoring spaghetti bolognese*

- Hurrah everything can be generic and so much better. I'll just do this and this and this and this, oh and this also needs to be reworked cuz of this.

8 hours later.

- it wasn't that bad!

$ git status

- oh god

$ dotnet test

- welp.... I need something to do tomorrow.

Web Assembly and Dotnet Blazor. Finaly other languages will become aviable on the frontend, dotnet blazor is a good start for C#

During 6 months I updated myself day and night on java, springboot and AWS.

I failed most of the technical interviews on my preferred stack, however I got a job, where the probable stack is C#, dotnet and Azure.

So, I have a couple of weeks of very good quality rant ahead.

I just started.

hmmm let's see, should I use Visual Studio or Visual Studio CODE. I spent the morning before understanding they were different. I could have spent the morning Studying how To Visually fuck you, lame name chooser.

Now I'm following a tutorial.
I need .NET 5.0, but guess what, I have .NET core 3.1.
But wait, fuck, .NET and .NET CORE are not the same thing! Will .net core 3.1 work for a .NET project or not?

And there goes the afternoon. Is he the same guy who choose the names?
I'll tie you with a barbed wire net and fuck you to the core, you asshole

Being a front end developer and working in a team of motivated "full stack" developers sucks big time.
So, recently joined this new company with a very small project which just started, basically a cloud version of a really old desktop app. Few people from the team completely from the asp dotnet background decided the architecture few months before I joined in.
So, they did it something like this -

- mono repo dotnet project with VueJs app served within it (because that would be maintainable 😑)
- vue app served by pointing the built files through dotnet index file (simply because they didn't care about the gift to the front end world which is webpack or even had any knowledge about it 😑)
- added typescript because, u know it's cool 😑, without even knowing that they don't possess that team which know how to write the types (f***ers write classes for every payload object coz they don't know what interfaces are)
- no loader to load typescript, they are running tsc in watch mode and we have .js and .js.map for every .ts file in our project which some teammates are even pushing to repo

Recently, I added eslint with git hooks to the project so that everyone will at least stick to the coding standards. Now, to avoid the errors they are bypassing the git hooks by uninstalling the library and then installing it after the commit😂😂
Then we have a girl who uses document.getElementById to programmatically change styles in a Vue project😑😑😑😂
Then we have dotnet people using dotnet coding conventions all over the front end app.

People, how do I deal with these so called "full stack" people?

Just started working as a student for a big tech company in Belgium. They only allow me to use dotnet core and the only thing I've never ever used is dotnet... Fml.
(any suggestions/tips are welcome)

These are my stickers, there are many like it, but these are mine!
@dfox thank you for the stickers 👍

Happy Ranting!

ME - me, TM - teammate
I was just recruited to the company. We're starting new project based on few modules.

ME: So this module will do X and Y, I will use good old interfaces and design based on abstractions so that stuff does not get glued too much.

TM: But why? Make good old processor with all the logic and throw objects at it.

ME: B-but unit tests, decomposition and othet stuff...

TM: *insists and forces me to agree*

ME: *gets shit done his way, TM checks on code review and complains but generally doesnt give a fuck*

ME: Ok, its done. Lets get shit shipped.

TM: Well, we were just told by PM that we will need to process one more source with much different logic that does not fit current solution (he did meant GOD-PROCESSOR, idea of his).

ME: What do you mean? *injects another contextual implementation of processing logic to template method pattern solution*.

TM: I will tell PM you cant make it because of the implementation.

ME: But I just did it...

TM: Impossible, processor needs to be reimplemented. Get your shit together!

ME: *still doesnt get the shit about the god processor love*

TM: *rage quits next month*

ME: *module gets reused once more 2 month later, profit*

That joy of finally having them all passed.
I had stupid mistakes like: insertNewItem, but inside I use update T_T

project still fairly new, but this time I decided to write unit tests as I go instead of delaying till the end and writing nothing lol

Recruiter: we're looking for someone who knows .Net and "JAVA practices".

Me: <WTF is "java practices">
Me: <googling "java practices">
Me: dear recruiter, I know dotNet and good programming practices but there isn't thing like "java practices" in dotNet.

Recruiter: <no shit given>

Me: <why such incompetency is in charge of my potential future job?>

If it builds ship it!! Its Friday.. cheers! What’s everyone drinking?!

Best Linux distro for a dotnet developer and complete linux noob. Also if it can be really pretty?
😃

dotnet new

Working with Apple subscriptions from Dotnet Core backend. Their API makes no sense IMO. Loved so much working with Stripe, but we had to support In-App Purchases aswell.

Made a small easter egg for futre developers to find. (unreachable code).

After 2 months of working with Android Studio I have to apologise... Im sorry for any bad word Ive ever said about you VisualStudio, I love you!

I hate hate hate writing résumés for dev positions. Each posting requires that you guess wildly about their stack therefore write a totally new résumé. You don't get a job because you omitted the keyword "Newtonsoft" when mentioning your Dotnet Core experience. Hiring departments have one job and they universally suck at it for tech.

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

fuck the guy that writed the api that I consume at my company

he's not the worst guy ever, and he might be going through some stuff in life, or maybe he's just happy. There's no way to know actually.

but fuck him. fuck this fucking guy. fuck him with a thousnd dicks.

this guy defends his postures on the api like this thing was fucking sacred and masterly designed ok?

if I ask him to change one url's method from get to post so that I can send more longer data for the request, he comments "i cant believe they still haven't figured out a get request with a body". I appreciate him caring abkut the correctness.

but this is the same piece of shit that makes NOOO fucking validations on whatever I send to it. I get 500 for fucking EVERYTHING.

And if he does 400, the actual response messages are garbage, the same fucking text with no explanation.

FUCK YOU!!!!!!

I hate the way he structures the names of the url and the parameters, sometimes I have to send arrays of strings, other times arrays of objects, the naming is garbage and INCOSISTENT.

And when we asked him to do the API dotnet core, he was like "nah" FUCK YOU FOR USING SOON TO OBSOLETE TECHNOLOGIES!!!
THIS PIECE OF SHIT IS SLOW, because a coworker did another spi in core and the response times are hugely better.

I wouldnt mind if he was 100% of the time careless, but he actually makes a stand for his ideas, as if he actually gave two shits.

he's actually an ok guy though but... fuck hiim!!!! ive been holding onto this for a while... and I'm sure I have some flaws too.

At my company of open source enthusiasts, I've tried to be the evangelical for dotnet core. It is difficult to convince developers to overlook microsofts long shadow they've casted over the years. They still have this notion that its a microsoft centric atmosphere where winform drag and drop frameworks realm.

"Please come down and hear the good news of the newly agnostic dotnet core and its ability to do like all your other beloved frameworks but with C# and better documentation".

@linuxxx I'm about to found a start-up.

In fact me and my buddy with some freelancing contracts. And we are in need of a dedicated server.

Our plan is to host the clients inside docket container.

Technology would be dotnet core and either react/angular/Vue.js, if that matters.

The host will run on arch, because I feel in love with it! 😍

Do you have any suggestions for a provider for us?

Budget between 100-125€
Location: Germany.

Thanks in advance!

hmmmmmm let me see.

Web based? lets do web based.

Do something simple like a basic crud app on web api format:
Do it with full authorization and authentication.
Start hard. Do it with pure golang using NOTHING but the std libraries.
Now, do it in a magic mvc framework like Rails or Laravel
Now do it on dotnet core
Now do it in django rest.

Watch the differences in all of them, sell your soul to something and now do it in Clojure. If you do it on a Scheme dialect or on Common Lisp my CMS admin will suck your whatever you have. Dude seems to be pretty good at it, we are trying to keep him from pulling tricks on the street but he insists.

Then add a React client with Typescript to get them basic ass endpoints to display nicely.

It should give you a fuckload of perspective amongst the different tools and way we do things and might make you appreciate the differences in paradigms required(pro points for doing modular in c# dotnetcore using different classlibs for the major points of the application using some crazy pattern like the mediator pattern)

I would hire a mfker that throws all this shit at me on a portfolio on the spot.

Idk why dotnet starts with a dot.

GitHub Packages Sucks. Like, it REALLY sucks.

It sounds like the best thing in the world - being able to host your project packages alongside your code! It has full support for Maven, Gradle, Ruby Gems, Node packages, Docker images and even dotnet CLI applications. It even lets you view statistics on how many developers have downloaded a given package! For public repositories, the packages are free to host as well!

So, I decide to use it for my Maven project since it's "so great". I've never used a public Maven repository before, so this was all very new to me. I follow the documentation - simply run "mvn deploy ...." and use a generated GitHub personal access token. No problems there. Deployment is a success and I feel a wave of happiness seeing my packages online. I follow through the various links and it even adds automatically generated usage information for other Maven users - fantastic!

That was, until I decide to try and download one of the files from this package repository. In order to download a file, you must have a GitHub access token. Okay, makes sense I guess? What if another developer wants to use my library? To do so, they have to generate their own GitHub access token, store it in their local ~/.m2/settings.xml file and only THEN can they use my library. So clearly, this is significantly inferior to other public Maven repositories where you don't have to get an access token to simply USE a library.

Upon discovering this, I decide to simply delete all of the packages and continue using whatever previous system I was using. Except of course, they forbid the deletion of public packages because "other projects could depend on it". The only way to delete public packages is to either:

[0] Make the repository private (losing all stargazers and watchers), delete the packages and then make the repository public again
[1] Contact support and ask them to delete the public packages. They say that they'll only do this for "special cases", such as legal issues or GDPR breaches.

I've sent a contact form and I'm currently hoping that they see things in my favor. I mean seriously - a public package repository where in order to use it you have to have a GitHub account and then generate an authentication token - it's absurd!

What the hell happened to the dotnet ecosystem in terms of stacktraces and async.

You used to be able to pin down your issues to the freaking exact line number using a stacktrace, but now im building a azure function and this is the crap im served when it blows up: How do you debug this?

I don't think it could be more .net core than this: Several parts of the application ended up failing because of a too long URL. For example we used a List to store selected items in an array and they each looked like this:
&model.selectedIds[n]=true
The server side made more sense but we were running late with the project so we just went with it and hoped no one would use this feature.

Yay, I've reached bronze rank in C# on Stack Overflow! 💻

When i am trying to compile my dot net project...

The good: dotnet core RTM
The bad: my previous shitty work place, their shitty product, the very shitty TL that had no fucking idea how to lead or manage the team
The ugly: the shit storm I dropped on TL, group leader, CEO/CTO when I left...

Today, I applied StyleCop Analyzer to our project codebase.

over 40k of warnings sounds like fun :D

Domain Drive Design question:

I am working on a simple case to teach how to apply DDD, my case is as follows:
Simple forum with Author, Moderator and Users.

I am using Dotnet core for this. I am not sure how and where I should implement authorization:
1. Author can edit his posts only
2. Moderator edits any post

In dotnet core, we handle roles, policies in the api layer, and its per endpoint, I have an identity layer which handles accounts, registering roles and policies in database.

But I'm not sure if I should or how to handle authorization based on permissions in application layer.

Why does every major version. of dotnet core have a different way of setting up Identity. And why is there so many different contextual meanings of the word Identity. Why in the hell do their docs have to state "Microsoft Identity, not be confused with dotnet core identity". Why cant they just call it JWT issuing and claims building or some shit. I cant keep up with whatever "Identity" Intels with every release. I swear my v3 API auth looks nothing like this v5. Granted teh v5 approach is cleaner and a little more abstracted but damn still.

So I’m starting to learn C# is it a bad idea to use .NET Core to learn the basics of the language? And for the advanced stuff use visual studio when it’s needed? I’m just trying to avoid Visual studio tbh

I am about to start my first project in dotnet core 2, webapi and react after 'stuck' for 4 years at asp.net 3.5, mvc and jquery / Ajax without typescript.

Anyone here who did the same transition allready?
Do you have a few advices?

Working on a tiny new project, can't build DLL libraries from our old projects. Contain mixed version of .Net written in VB and C#
Asked our senior developer to help me out.
...
After an hour, he's still not able to build it.
...
So he basically implemented some features I needed on the fly...
😂
DLL hell is real!

I've been using dotnet and aspnetcore for years. I've heard people complain about MVC but I never really saw the problem. The controllers are easy to set up for basic endpoints, I have my domain models and DTOs, and our views I guess is our standalone webpage just consuming jsons.

Only now I'm having to work with an *actual* aspnet MVC stack - server-rendered cshtml and all - and it's dawning on me like a truck what people were actually referring to.

Out of all the issues I've had so far, they have all been due to black box enigmatic voodoo because don't worry about it, the framework takes care of it - it should just work. But what if it doesn't? I have no idea because the trail ends at the bit that should just work.

I should know better than to criticize an entire framework and paradigm made by devs with vastly superior experience and expertise than me, and my issues are absolutely due to being new and unfamiliar with this, but imagine coming up with an architecture to obsessively separate the MVC concerns, then you make cshtml.

@micheltombroff 👍 best happy face ive seen
@g-m-f pitty i couldn't reply with a pic

While investigating alternatives for translating a query string to a dotnet expression I discovered that roslyn has runtime eval of string as verbatim code.

I had no idea a feature could make me this uncomfortable. It's like discovering an armed bomb under your bed that's "there if you want - it has its uses, just be careful".

At least you have to explicitly reference a package for it. Promise to kill me if I ever am tempted by it.

The position in the company i started working for not long ago was for a dotnet developer. But it ended being heavy sharepoint focused and mostly front end javascript (that i am not very good at, that's why i wanted backend), doing stuff like hide this button, css that input etc. Really confused now and wondering how much il learn from this job considering its my first job as a developer and that i really want to do mvc with dotnet core. 😐😐 Does this have any value or i shouldn't be so picky for a first developer job?

Fuck not-so-old-but-deprecated-nontheless-software! And their also deprecated dependencies.

We're using a year old dotnet version which apparently only works with a specific libicu version.
Then there is node.js, but it has to be version 6 otherwise nothing will work.
If you wish to use VS code you have to manually install a specific version of the c# extension and keep it from auto-updating because project.json is deprecated and not a thing anymore.
Migration is not an option, it fucks the whole project.
I mean it is a great project and all, but the dependencies are driving me crazy!
Why does stuff get deprecated so quickly?

Updated today:
VS 2017 15.3
dotNet Core 2.0
SSDT 17.2 (I think)
SSAS VS 2017 Package
SSRS VS 2017 Package
> Where the hell is the SSIS VS 2017 Package ???
VS Code 32bit
> Found 64bit is out, manually uninstalled 32bit, installed 64bit

Also wrote seed data for my program so I can continue development.

About to checkout Gatling for load test to my REST api, any other suggestions?

So far their docs look straightforward to follow, requires scala but it doesn't look that complicated for that particular case.

Dotnet core devs, do you recommend another tool?

Should've used .NET...

Set up .net core in CentOS 7.
I'm able to access `dotnet --info` but can't access `sudo dotnet --info`.
Provided I can't access root.

It's been a while since i stopped programming.....
It's been so busy with all the school work/assignments/ and the most important part is that school ends at 10pm, arrive home at 11pm, prepare for tomorrow school stuff, sleep at 2am, wake up at 7am next morning, and again ends at 10pm 5 days a week...
It is exhausting, but I am getting used to this routine.
Studying my own programming skills or working on a side project? Not sure when to do it... The only way to continue studying is at breaks at school, or sleep less and study....
But it is impossible....
I have some great projects that are waiting to go out to the world, to list a few:
- cloud gaming
- cloud storage with live streaming
- complete school schedule management
- home automation framework in dotnet
- deepfakes and ai image generation algorithm (~18 months of training till now)
- game cheat engine (20GB total omfg ^^)
- and more
and I don't have time to finish it. lol
I think it will see the bright world after 3 years of high school... By then, my projects will be ancient, probably....

TIme is really short.
24 hours equally, but feels like 8 hours a day....

Should I abandon the project rn and focus on studying? (probably should)
or should i sell the project or open source it?

Also, how do you manage your time between work(study) and side projects (especially big ones)?

You can make WSL and VSCode fight over how a csproj should be written. VS2017 doesn't care and runs no matter who was previous.

Anyone here tried dotnet Blazor yet? seems interesting thus far. I have been toying with it for a good portion of the day and I've got to say that thus far I like what I see.

Random recruiter viewing my linkedin profile:
"oh, this dude knows C#, I gotta send him EVERY single .net job I have"

Nah, mate, I don't know shit about .net or microsoft development in general, furthermore I actually despise developing for either windows or mac os x.
Also, take 2 extra seconds to check I don't have .NET or Microsoft development in my skills list.

.NET Core broke cause of the recent ncurses update… And I just HAD to do a full system upgrade on my Arch laptop right… Guess I'll try to downgrade ncurses now…

Adding a new feature to a mobile app that has a bunch of classes for getting URLs! Want some examples?

FallbackUrlProvider
CompositeUrlProvider
CompositeRouteUrlProvider
CompositeBaseUrlProvider
RootUrlProvider

I was half expecting to find FallbackRootBaseCompositeUrlProvider!

Not only that, but there were a load of interfaces that sometimes didn't match the name of the class!!!

For example,

class RootUrlProvider : ICompositeUrlProvider

Ugh! But I managed to get the new feature in... Somehow... After trying something... Throwing it away... Trying something else... Throwing it away...

😭😭😭

Went on a Hackathon with two friends. They didn't do shit. This week, they told me that they only knew c#, so we should switch to that. (I use Linux so I shouldn't have accepted that) Just learned that they are going to a maths camp this week and the deadline is next Sunday. Dotnet core CANNOT PARSE FUCKING JSON. I'll rewrite it in node.js, and hope that I can type fast enough to finish in time. Fuck me, fuck my lazy friends and especially fuck Microsoft for saying that they support Linux while providing a dotnet for Linux published in 200-fucking-5

Beware of programmers that carry screwdrivers

DOES NOT CHANGE THE FUCKING BASE PATH!!!!

Today I had a CORS error in production, noticed 1 hour in that I accidentally wrote "localhost:5000//API/*"

1 hour, for a extra slash.

How would you handle this:
You generate an id
You chech the db if it is not taken
If it is taken you generate a new one and check again.
You then save the new item with the generated id.

How do you ensure that between the time you checked and the time you added the item some other call did not try to also add an item with the same id.
Async mvc
C# and dotnet core with ef core

Install .net -> install vs code -> install C# vscode extension:
extension not working.
Great job Microsoft!
Booting back to Linux partition.

*updates game core structure*
*game now running 10x slower*

Well shit

Could people kindly stop trying to expand upon the native DI in dotnet!

This is my third project where "you don't just" add new services because you have to carefully conform to hundreds of lines of boilerplate while "remembering to" whatever it demands because someone spent weeks hacking the builtin functionality in order to make it easier and shorten the startup file.

I'm trying to swap out one of the implementations that are used by one other class via DI and so far I've changed 12 files. It's literally more work to do the thing DI is designed to solve compared to not using DI because they "improved" upon it.

Sure, it might be that I'm not using your thing correctly, but that's not much better, is it. Everyone already knows how to use dotnet's DI. Literally noone knows how to use your improved version aside from yourself.

I liked how one of the team members put it after one of the former devs apologetically explained how this was some long-gone dev's baby: The only thing this code does for us is that it needs a diaper change every time we deal with it.

Hello, does anybody know a good templating library like Liquid for .NET?

The problem is that it has to work well with F# and immutable types.

I want to build my own REST NET API, I am familiar with C#. And I was working with Flask, Django and Express.js

The whole webapi structure of dotnet project seems to me a bit strange. Do you have any favourite resources that helped you to get into dotnet?

Random thoughts...
Just implemented policy-based authorization in dotnet core, long story short to lock an endpoint to a certain policy I just add: [Authorization(Policy = "NAME")]
on top of function/controller declaration

Was wondering how it is done in other languages, like NodeJs, Java, Kotlin ...etc

Fuck VS! C# sucks! F# sucks!
I found no way to debug C # and F # without VS(At least the official did not give a plan)! And I can only use macOS now.
After downloading VS for mac, I found that it installed mono automatically! And there is not even a button to open the folder!
Why do you have to wrap a class outside the main function? And their pointers are not flexible at all! Also, unlike C, Go, and Rust, the compiled files are binary files. WTF does DotNet give me? debug directories and .dll files!
I originally planned to learn DotNet core for the convenience of using Azure.
But I found that, through Python, JavaScript, Ruby, C(LLVM-Clang), Go, C ++, Rust, Haskell, Azure can also be used, which gives me more sufficient reasons to give up C #, F #!

Don't you just hate it when there seems to be nothing but in some ways lacking solutions to a definite task in your capability arsenal? Or rather, I don't really know how I should feel about it... I've been developing this solution to receive a 3DES encrypted Azure Service Bus message, decrypting it and chewing the output XML down so as to be digestible to the PHP application whose API the message gets delegated to... but there just seems to be no perfect solution: subscribing to the event topic straight from the target app just... doesn't seem to work properly, a Python implementation.... well, let's just leave it at that... a Node.js implementation would require TS and completely rewriting a proprietary library with 100+ complex types - also, there's some hiccups with both the subscription and the decryption...

I started with an F# implementation (after deeming the PHP one flawed), and it seems it's still the best. But goddamn it I had problems with it on the dotnet core side of thing (decryption output incorrect), so I had to switch to dotnet framework... Now finally everything crucial is peachy, but I can't seem to be able to implement a working serialized domain model pipeline to validate the decrypted message and convert it to something easier to digest for the target application (so that I could use the existing API endpoint instead of writing a new one / heavily modifying the existing implementation and fear breaking something in the process...). I probably could do it in C#, I don't know, but for the love of Linus I'm not going to do it if I can avoid it, when implementing the same functionality I have now without the Dto and Domain type modules would take 3x LoC than the current F# implementation incl. the currently unused modules!

And then there's the problem of deployment... I have no idea what's the best way to deploy a dotnet framework module to an app completely based on MAMP running on a mostly 10yo AWS cloud solution. If I implemented a PHP or Node.js solution, it'd be a piece of cake, but... Phew, I don't know. This is both frustrating, overwhelming and exciting at the same time.

Thank you, .NET Framework, for keeping your GC from destroying my DynamicMethod instance after I've accessed its function pointer!
Unlike another runtime that caused me to waste my weekend hunting a memory corruption bug in a managed language because of a minimal behavioral difference...
/tableflip

So i got this advice from a acquaintance that's the head of some big company that deals with opensource.
"Stay away from .NET, it's the devil's doings"
Didn't quite know what to make of that, took my college degree in CS using java, got my first job with a java codetest and interview.. however I was so nervous I forgot to ask the tech questions about the job.
Anyway, just learnt that I'm now hired as a .NET developer (it's a trainee program so gets to learn it at work).

So, .net.. am I fucked or should I put my prejudices aside and embrace it as something good?

What a productive day! Managed to speed up some code by getting rid of some classic ASP AND sticking it in a dotNET library instead! Ran some benchmarks and it seems to work pretty fast now 😎

At work we only "develop" for Microsoft Sharepoint which consist for the most part writing small javascript based project that on their own are not exciting at all. Problem is that by doing 90% work like this i feel like i am wasting my time by not learning/working on more relevant things for a .net developer, but i have a contract for 2 more years. Except to study and do things i like at home i don't know what much to do.
🤔😑

I am currently playing dumb with a potential hire and it's just so much fun I don't know if I should stop.
We gave the dev a little coding challenge to code a small expense tracking app. Nothing fancy, just to see how he well he could do on his own. We told him to take as much time as he requires.
He submitted it and I tried to run it. It worked alright but I could not register or login.
I debugged the issue with him for a while and told him I would look at it later since I am tied up with other tasks..
We are communicating via an IM.

Him: Or how did you run the project. I wish I was there to run it for you. Lol

Me: dotnet run. start without debugging

Him: From the cmd?

At this point I about to get pissed. Where else would I run 'dotnet run' from??

Me: I would hope so

Him: I always run it from the cmd. With administrative privileges

Me: Really?? Where can I find cmd?

Him: Yes. Do you use a Mac?

Me: nope. I am using windows

I am actually programming in C# and i learned programming with this language, but my problem is that visual c# have mandy dependencies and i need a language which run on a windows 7 as on a windows 10 machine but with no dependencies to any DotNet-Framework oder any special DLL's is there a language for this?

!really a rant

Any vim devs here that code in dotnet?
I use nvim and have tried and tried again to set up proper intellisense and debugging with omnisharp but it just doesn't want to work properly.

Anyone having suggestions / alternatives?

Hello fellow Developers!
Are here Developers that use DevExpress Components? 😁

"We would really prefer it if you didn't attempt to print time zone offset with your DateTime values (because that functionality is utterly borked and prints nonsense)."

From documentation of .Net DateTime.

Yesterday evening: committed my day's work to git. Tested everything and it all worked like a charm apart from a bug in my seeder I intended to fix today.

Today: failed to fix the error for 6 hours. Decided to go back to my commit from the day before only to discover now even my migrations won't work anymore.

Ready to smash my laptop

#whydoivencommit?

Wanna develop android apps, i am a .Net developer and i know xamarin sucks a$$. So was wondering about kotlin but i wonder how close it is to c#. Any ideas on android development for a dotnet developer?

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.

Went to a dotNET interview yesterday and I had to do a simple MCV app. They were using Visual Studio 2017, so I thought "cool! I can use some C# 6-7 features!". But for some reason it didn't build...and the errors were not very helpful!

Also my ajax calls kept refreshing the page, even though I was calling preventDefault() in the form submit action 😣

Jeesh! Trying to untangle a web of task continuations 😫

Tips/Suggestions for using ReSharper? The immediate and obvious benefits are wonderful, but I want to get the most out of it.

What is the point of .NET Core 3 WPF and WinForms? Only thing i can think of is that MS want's to migrate frameworks to .NET Core, but is there anything that those frameworks gain?

Tool question, I can't find any after some googling. But are there any tools out there for dotnet that help you find class, method, and property references outside a solution.

Say I have a bunch of solutions and I need to know where a class is referenced to determine whether or not I can deprecate it. Is there anything out there that would scan other solutions for references to that class?

I'm going to have to go in and add another layer again soon into another program. I'm tired of this. Serious question, are there any good dotnet tools out there that help automatically do this? Or will I have to write my own?

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.

Stupid Nhibernate! Half day to get a domain configuration barely working! I hate you.

P.s.
Someone know some resource to learn about Nibernate by the code? It seems awesome and I'm a noob.

visual basic dotnet
ComboBox and ListBox both have Items property, and also both are descendants from ListControls
but ListControls have no Items property
do those developers understand object oriented programming correctly?

So this the question:
Dapper or OrmLite?

I cannot get started with dot net core ! Tutorials are a walk in the park for windows and windows vs but for mac, everything’s grey and udemy/Lynda tutorials are all outdated.

Duck you ef core, F U C K. Y O U.

Wondering if dotNET MVC was a bane or a boon!

I'll go with the former anyways

Solution for some reason doesn't work correctly on dotnet core so I try with framework => works. Develop a bit further, not touching anything that happens BEFORE the broken point. Then done far enough that actually have to seriously think about deployment. Framework solution is a headache => decide to try dotnet core again and hopefully find a fix for the broken part => magically everything works. What? WHAT?