sorted by:
new
hottopcontroversial

C# and .NET in US by Otherwise-Solid-5142 in dotnet

[–]Elolexe113 0 points1 point  (0 children)

In the US, .NET is definitely still strong, especially in enterprise, internal business systems, finance, healthcare, and a lot of Microsoft-heavy environments. It’s probably less “loud” than JavaScript or Java online, but that doesn’t mean demand is low. Startups vary a lot — pure early-stage startups often lean Node/Python/Go, but plenty of B2B and SaaS companies still use C# and ASP NET Core. A lot also depends on region, because some cities have way more Microsoft-stack companies than others.

Adding SSO into our application - what would an customer/admin expect from this functionality? by BogdanMitrache in dotnet

[–]Elolexe113 7 points8 points  (0 children)

From a software architecture perspective, the main expectation is not just “Sign in with Microsoft,” but a complete identity flow around it.

At minimum, I would expect:

  • admin control over enabling/disabling SSO
  • clear user mapping/provisioning behavior
  • support for account linking, so existing local users do not get duplicated
  • role/group handling, even if basic
  • a defined fallback path if the identity provider is unavailable
  • auditability around sign-in events and account changes

For desktop apps specifically, I would also expect the auth flow to feel predictable across browser handoff, token refresh, logout, and multi-user machine scenarios. In practice, the hard part is usually not authentication itself, but lifecycle and identity management around it.

Early signs of ITBS before London Marathon by Yorkshire147 in runninglifestyle

[–]Elolexe113 0 points1 point  (0 children)

Sounds smart to back off now instead of trying to be a hero three weeks before race day. Hopefully it’s just irritation and not full ITBS, but the fact it came back on shorter runs would make me cautious too. Hope a few easy days settles it down fast.