Jeremy Likness

@Aviad:

By convention; the `int id` parameter is matched to the `_id` field. If you omit the id field from the private constructor then EF Core will set the field directly. This is totally reasonable, but you’ll have to suppress compiler warnings that the field is never set.

@damen:

"Recommended" depends on your use case. The SDK is great; the most common use case is for teams already familiar with EF Core who want to take advantage of the conventions and API offered there.

To be fair, I contrived the example to show discriminators but in the "real world" the posts would be an "owned entity" of the blog and get stored as embedded values rather than separate documents. That is possible, just not the scenario that I showed.

No idea. Did you build a Windows container? Is it possible the local script is picking up something in the filesystem?

What part of the process did not work? Were you following these tutorials?

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

@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.