Sponsorship is available! If you’d like to sponsor CodeOpinion.com and have your product or service advertised exclusively (no AdSense) on every post, contact me.
Here are the things that caught my eye this week in .NET. I’d love to hear what you found most interesting this week. Let me know in the comments or on Twitter.
You might have noticed the recent public discussions
aroundhow to securely build SPAs – and especially about the “weak security properties” of the OAuth 2.0 Implicit Flow. Brock has written up a good summary here.
The whole implicit vs code flow discussion isn’t particularly new – and my stance was always that, yes – getting rid of the tokens on the URL is nice – but the main problem isn’t how the tokens are transported to the browser, but rather how they are stored in the browser
Recently, I’ve been given the opportunity to rebuild an existing web site that is important, but not technically complex. The website has a few content-focused pages, some forms, and a single funnel. The goal with the redesign is to simplify the backend code and leverage more frontend technologies. Given the requirements, I thought it would be a perfect chance to try Razor Pages. In this post, I’ll give my first impressions, what I love about Razor Pages, and what I think could use improvement.
A little over 4 years ago Microsoft announced that they were open sourcing large parts of the .NET framework and as this slide from New Features in .NET Core and ASP.NET Core 2.1 shows, the community has been contributing in a significant way
A simple to use TCP and UDP networking library for .NET, designed to be flexible, scalable and FAST.