.NET Core 3.1 approaches end of life

.NET Core 3.1 approaches end of life

Practical notes

1 min read

.NET Core 3.1 approaches end of life

Inventory dependencies, hosting and update ownership and test an isolated upgrade. Preserve recovery sources and validation rather than changing a version number alone.

Putting implementation and maintenance into practice

Implementation includes normal, empty, error and recovery states. The interface provides feedback while the server owns authorisation, validation and persistence.

Checking the result

Test valid, invalid and missing inputs, including back, retry and duplicate handling. Keep release records and usable recovery material.

.NET Core 3.1 approaches end of life · Working details

Contact OXOAK