Abstract

This paper examines the long-standing need within the software engineering discipline for technical design that is authoritative. A design process is authoritative if there exist technical means of materializing the design document as a working product, thus guaranteeing that the end result is indeed as described by the design. We notice the scarcity and inadequacy of existing solutions for software design, we look at solutions in other engineering disciplines, and we conclude with realizations on what it would take to come up with a solution that works for software.

I recently did this at work, and I decided to document the process here in the form of a how-to guide. Please note that I am not an expert, I am learning as I go along, so there may be mistakes.

Sdk-style project files have existed since net5, but when they were introduced they were made compatible with earlier versions of dotnet, such as dotnet framework 4.7.2. The kind of project files we were using before can now be called legacy-style project files.

• Legacy-style project files begin with <Project ToolsVersion="...
• Sdk-style project files begin with <Project Sdk="Microsoft.NET.Sdk">.

Sdk-style project files are necessary if you want to:

• Start using the dotnet command-line utility and all the functionality that it provides.
• Eventually migrate to a modern version of dotnet.

I am giving this tool a try at work, and I am encountering a great many problems with it. I decided to publicly document my findings.

So, I decided to adopt my covid look as my post-covid look.

This means that I should be updating my avatar.

Since my pre-covid avatar will not be used anymore, I thought I should post it here for posterity.

For reference, if you wish.

I recently did this at work, and I decided to document the process here in the form of a how-to guide. Please note that I am not an expert, I am learning as I go along, so there may be mistakes.

It has been more than a year since I created this question on GitHub Community; a couple of days after that I found the solution by myself, so I answered my own question, and to this date comments keep being added by people who were helped by my post.

When I look at it today, I notice that my answer has this particular style, this grumpy indignation which has become so characteristic of me, after a lifetime of battling with lame software, and even worse, with lame error messages.

I thought I should share this on my blog for posterity.

Here is the link:

https://github.com/orgs/community/discussions/23474

And here is the question: