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.

!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

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

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

I wrote a prototype for a program to do some basic data cleaning tasks in Go. The idea is to just distribute the files with the executable on our shared network to our team (since it is small enough, no github bullshit needed for this) and they can go from there.

Felt experimental, so I decided to try out F# since I have always been interested with it and for some reason Microsoft adopted it into their core net framework.

I shit you not, from 185 lines of Go code, separated into proper modules etc not to mention the additional packages I downloaded (simple things for CSV reading bla bla)

To fucking 30 lines of F# that could probably be condensed more if I knew how to do PROPER functional programming. The actual code is very much procedural with very basic functional composition, so it could probably be even less, just more "dense"

I am amazed really. I do not like that namespace pollution happens all over F# since importing System.IO gives you a bunch of shit that you wouldn't know where it is coming from unless you fuck enough with Ionide and the docs. But man.....

No need for dotnet run to test this bitch, just highlight it on the IDE, alt enter and WHAM you have the repl in front of you, incremental quasi like Lisp changes on the code can be REPL changed this way, plethora of .NET BCL wonders in it, and a single point of documentation as long as you stay in standard .net

I am amazed and in love, plus finding what I wanted to do was a fucking cakewalk.

Downside: I work in a place in which Python is seen as magic and PHP, VB.NEt and C# is the end all be all of languages. If me goes away or dies there will be no one else in this side of the state to fuck with F#

This language needs to be studied more. Shit can be so compact, but I do feel that one needs to really know enough of functional programming to be good at it. It is really not a pure language like Haskell (then again, haskell is the only "mainstream" pure functional language ain't it not?) but still, shit is really nice and I really dig what Microhard is doing in terms of the .net framework.

Will provide later findings. My entire team is on the Microsoft space, we do have Linux servers, but porting the code to generate the necessary executables for those servers if needed should be a walk in the park. I am just really intrigued by how many lines of code I was able to cut down from the Go application.

Please note that this could also mean that I am a shit Golang dev, but the cut down of nil err checkings do come somewhere.

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

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

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.

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.

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

2020

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

Blazor has an official release for client side webassembly.

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

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.

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.

Rocking some C# swag today 😎

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?

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.

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

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

But l like microsoft and it's stuffs

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

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)

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

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

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

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

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.

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.

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.

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

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.

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.

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

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?

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

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

Even if Microsoft has done considerably steps forward in recent years with dotnet core being an open source platform, it still retains a bit of its microsoftian dna. Let me make an example. Start a new test project with xUnit. It doesn't log to console. Decide to use the standard Microsoft.Extensions.Logging that should be the new, performant way of logging. It comes with 4 providers and **it doesn't log on file system**. Bottom line: all the complexity of a complex stack without the solution you were looking at the beginning. Resorting to thirdy party tools to do the job (serilog).

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.

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

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?

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?

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.

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.

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

Well shit

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

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

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

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.

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?

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

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.

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?

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?

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