The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
As for .NET core it's not something I have experience with.
I would suggest not using it to begin with as it's probably worth getting something working with standard .NET and then if you really need to you can investigate porting it to core.
The reason I say this is because I am aware that core did require some workarounds in the past, which may now be fixed. You only really need to use core if you are not going to be hosting the API on a Windows server.
“That which can be asserted without evidence, can be dismissed without evidence.”
To be honest, for REST I would advise .NET Standard or .NET Core as opposed to the old framework. It's faster, leaner, more likely to be supported and has some great enhancements in the way it takes care of HTTP lifetime.
So you go to the centre of the Catholic church at Easter and are astonished at the crowds
Mind you we did the same in Vietnam wanted to visit the mausoleum on their national day, the queues were kilometers long. Weird thing was the 5 star hotel concierge did not know if the place was going to be open or he was just pissing around with the tourist.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
As someone who has been to Rome many times, over the last several decades, I F***ing hated it, the last time I went there, a few years ago.
I wanted to find a T-shirt printing place that could emblazon T-shirts for me with "Do I look like the kind of moron who wants a F***ing selfie stick?" on the front, and "I Probably know the Vatican better than you do, you F***ing uneducated, half-trained foreigner!" on the back.
Vedi Roma e muori -- da vergogna.
I wanna be a eunuchs developer! Pass me a bread knife!
I bit the bullet and installed the FxCop Analyzer on my own pet home projects...
First I ended up with thousands of warnings
Plenty of them useless....
Well then I embraced the global warning suppression...
It is good, but annoyingly create a GlobaSuppression.cs, it is annoying because I would have edited the error.ruleset file instead, which would be better I guess (more prominent), and sometimes it can be tedious to find the annoying rule one want to suppress in the treeview manually...
after that it did find some vaguely less than desirable code. Yeah!
(Remark, I mean just that, not quite a bug, but less than desirable, like incorrect exception constructor or using string.ToLowerInvariant() which is problematic, advised to use ToUpperInvariant(), or use a TaskScheduler explicitely, or use Array.Empty<T>() instead of new T)
except it is sometimes quite tedious to review 87 warnings in 4 years old code while I got other things to do... (particularly as I am, for once, "productive"... I do not need one more excuse to procrastinate on the feature that defied me for almost 2 years so far... )