What technologies are used to implement a client-north application for PCs and other devices with copy protection?

Question

ASP.NET

I want to implement an application similar to CAD / CAM and faced the question of how to protect the application from copying. I rummaged through the Internet and found what technical means of software protection exist. One of the 8 licenses is called "Saas" ( Protection of programs from copying by transferring them to... ).
Quite often I see that now virtually every software is sold under such a license (saas). Maybe I'm wrong...
Moreover, such applications have a common database. The site and the application on the PC, and the application on the smartphone interact with the same database, and for such interaction, in any case, a server must be written that will check the license, process data, etc. I also understand that this task is not for one person, but for a whole team of programmers. But I want to know what technologies are used to implement a client-north application for PCs and other devices with copy protection.
I rummaged even deeper and came across ASP.NET MVO, WCF, ADO.NET Entity Framework...
ASP.NET MVC - serves to develop a web application in a browser. But I need an application not only in the browser but also on the PC.
WCF - designed to implement service-oriented applications. Seems to be what you need, but I doubt it...

Answer 1

Do not ask more than one question in one text.
I'll try to guess what you meant by your strange wording:
SaaS license - doesn't matter.
But the essence of SaaS suits your purpose. What is SaaS - the application remains on your servers on the Internet. In the case of a client-server - only the server remains with you. Therefore, copy protection for the server is not needed.
The task is reduced to that that it is just necessary to check the clients connected to the server. So that they report their license number (here you need to add a bit of cryptography so that the license cannot simply be generated).
And do not allow more than one client to work under one license at the same time.
If your software depends on the server, can't work offline - it can be completed with "copy protection", that's enough.