No, not some internal company, just Microsoft being Microsoft. So all Windows pipelines. They also have Linux based pipelines so not completely all pipelines.
But given that a lot of people build dotnet stuff on Azure, the 'windows-latest' image is usually the default. So a lot of pipelines
That's not a Discord bot, it's a Slack RSS App / RSS subscription.
Event Source: https://status.dev.azure.com/_event/543117809
It's pretty useful 'for work' because occasionally you'll get notifications when parts of infra might be down (like your build server)
It’s more the fault of the implementation and documentation.
Yea sure. Though it's slightly XMLs fault for allowing that kinda implementations. Every random thing is in it's own obscure namespace with 20 levels of nested objects in different namespaces, and if you get anything wrong it barely explains what's wrong, and just refuses to work.
It's mostly WCFs fault. I just automatically associate XML with nightmare flashbacks of implementing WCF stuff
Uh-huh... ever tried to integrate with a poorly implement WCF service? Like communication from a Java service to a dotnet service through a WSDL?
I'll take a json API over XML any day
At some I added logging to a thread pool, when it gave up on child-threads, it would be logging things like
"Child 123 is being aborted"
Not the best of phrasing for people that didn't know what that was about...
Omg it’s sooo daammmn slooow it takes around 30 seconds to bulk - insert 15000 rows
Do you have any measurements on how long it takes when you just 'do it raw'? Like trying to do the same insert though SQL Server Management Studio or something?
Because to me it's not really clear what's slow. Like you're complaining specifically about the Microsoft ODBC driver - but do you base that on anything? Can you insert faster from Linux or through other means?
Like if it's just 'always slow' it might just be the SQL Server. If you can better pinpoint when it's slow, and when it's fast(er) that probably helps to tell how to speed it up
When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap.
It's probably not 'that much of a leap' as you imagine. If you're looking at Git tutorials, they're usually covering all kinda complex scenarios of how to 'properly use Git'. But a lot of people barely care about 'properly using Git' and they just kinda use it as a substitute for SVN... You create branches, you merge them back and forth, and that's about it.
Like if you want to contribute to an open source project, all you have to do is create a fork (your own branch in SVN terms) - commit some stuff to it, and create a pull request (request to have your changes merged) back to the original branch. git pull is just svn update - getting someone elses commits
Not saying there aren't more complex features in git, or that learning git properly isn't worth it, just saying, I don't think you have to see it as a 'giant conceptual leap' that's preventing you from jumping back into programming. Easiest approach just to get started would be probably to just download a GUI like Sourcetree or Fork, and you just kinda pretend you're still using SVN - approach wise
That laser at the end should have been Java Technology™ ;
You point it at anything, and end up with a huge dumpster fire... Sounds like Java to me
In C# I'm generally using Verify for these happyflow tests - So instead of explitly testing every individual property, you just do Verify(state); and compare the entire state against a json saved state.
A little bit for the same reason of "testing fatigue" - having to manually rewrite assertions of a lot of tests is getting annoying. With that approach you just do a merge compare between results, accept them, and you're done
It's a bit of a vague question, generally an API is backend - and you're kinda asking "should I make a frontend for this?" - hard to tell without context...
If you just want a "semi-developer-ish" frontend, you could look into just making an OpenAPI spec for it, and using something like Swagger as a frontend. Then at least you have some kind of GUI
Problem Details for HTTP APIs - I have to work and integrate with a lot of different APIs and different kinda implementations of error handling. Everyone seems to be inventing their own flavor of returning errors.
My life would be so much easier if everyone just used some 'global unified' way to returning errors, all in the same way
That doesn't really work all the time, because large files or large commits are lazy loaded on scroll, so what you're searching might not have loaded yet
The code search does a server side search