Running F# in WebAssembly with Bolero
Jeremy Likness
JeremyLikness
Empowering developers to be their best.
Biography
Jeremy Likness is a Cloud Developer Advocate for Azure at Microsoft. Jeremy has spent two decades building enterprise software with a focus on line of business web applications. He is the author of several highly acclaimed technical books including Designing Silverlight Business Applications and Programming the Windows Runtime by Example. He has given hundreds of technical presentations during his career. In his free time Jeremy likes to CrossFit, hike, and maintain a 100% plant-based diet.
https://blog.jeremylikness.com/
@jeremylikness
Entries
Working with the new Microsoft.Data.SqlClient
Blazor and Customizing the OData entity model
Migrating EDMX projects to Entity Framework Core
Diving into Durable Entities
Building workflows with the Durable Task Framework
Writing tests with F#
Supporting IAsyncEnumerable with LINQ
Supporting Windows Forms and WPF in .NET Core 3
Updating the WinForms Designer for .NET Core 3.0
DevOps For ASP.NET Developers Pt. 8 - Azure DevOps Integration with GitHub
DevOps For ASP.NET Developers Pt.7 - Templates and Scaffolding Tools
Comments
Blazor in the cloud: Hosting a C# SPA app as a static website in Azure Storage
Apply custom domain: https://docs.microsoft.com/azure/cdn/cdn-map-content-to-custom-domain?WT.mc_id=blazor-ch9-jeliknes
Add SSL: https://docs.microsoft.com/azure/cdn/cdn-custom-ssl?tabs=option-1-default-enable-https-with-a-cdn-managed-certificate&WT.mc_id=blazor-ch9-jeliknes
Azure Functions: Less-Server and More Code
@tartufella: that is a great point! I purposefully did not worry about concurrency in this case because it is my link shortener so I don't plan to be concurrent with myself, but absolutely something to think about in the bigger picture. However, concurrency is handled by the Table Storage in my understanding. When the NextId is loaded, there is a unique concurrency identifier in it (that's why we inherit from the TableEntity class) and this is sent back in the update operation. If the timestamp on the entity in storage has changed, it will throw an exception. So I don't believe you can actually end up with duplicate short URLs unless you explicitly disable the concurrency check. If you haven't already, great description in this doc: Managing Concurrency in Microsoft Azure Table Storage.