A reference list of best practices;
https://abdulrwahab.medium.com/api-architecture-best-practices-for-designing-rest-apis-bf907025f5f
https://zonito.medium.com/best-practice-and-cheat-sheet-for-rest-api-design-6a6e12dfa89f
Sharing libraries between .Net Core and .Net Framework applications
I was trying to reference a DLL targeting FW 4.6 in a host application targeting .NET Core 2.1. I started getting this error;
This is where I started to wonder, What’s the difference? How they can co-exist? How the host application can use them?
Microsoft recommend to target .NET Standard 2.0 when building reusable libraries, unless you need to support an earlier version. Most general-purpose libraries should not need APIs outside of .NET Standard 2.0. .NET Standard 2.0 is supported by all modern platforms and is the recommended way to support multiple platforms with one target.
.NET Core 2.1 and later versions support .NET Standard 2.0 and earlier versions.
There will be no new .NET Standard versions after 2.1. For more information, see .NET 5 and .NET Standard later in this article.
.NET Standard libraries and Visual Studio
In order to build .NET Standard libraries in Visual Studio, make sure you have Visual Studio 2019 or Visual Studio 2017 version 15.3 or later installed on Windows, or Visual Studio for Mac version 7.1 or later installed on macOS.
A good explanation about libraries
Resources
Azure hosted wordpress site
Helpful tips on the topic;
Visual Studio licensing and pricing
There are two models. Subscription based and Volume licensing program; The subscription-based pricing is on Microsoft web site;
https://visualstudio.microsoft.com/vs/pricing/?tab=business
Professional = $45 per month
Enterprise = $250 per month
Microsoft has partners that might be able to help you in lowering subscription pricing by applying discounts that are not available to general public. In one instance I have been offered Enterprise edition @2,500/year for 5 developers.
Estimated pricing for volume licensing program (5 developers);
This program has one-time payment. This is a perpetual license and if software assurance is involved, you are eligible to get newer version. MSDN subscriptions are usually valid for two years. MSDN renewal is a recurring expense and cost about 20-30% of software cost.
Here is the breakdown;
Professional
The minimum limit here is 5 because there is no MSDN subscription.
Microsoft Visual Studio 2019 Professional – License – 1 User – Microsoft Open License – Single Language – PC
$496.57 x 5 = $2,482.85
Professional with MSDN
Microsoft Visual Studio Professional Edition with MSDN – License & Software Assurance – 1 User – Microsoft Qualified – Microsoft Open Business – All Languages – PC
$1,080.87 x 5 = $5,404.35
Enterprise with MSDN
Microsoft Visual Studio Enterprise With MSDN – License & Software Assurance – 1 User – Volume, Microsoft Qualified – All Languages – PC
$8,638.64 x 5 = 43,193.20
If budget is a constraint and wanted software assurance then I will suggest to go for Professional with MSDN. You can pick whatever suits you.
There are 3rd party vendors offer lower rates but not sure how that will work out. Here is one.
Resource
https://visualstudio.microsoft.com/vs/pricing-details/
https://docs.microsoft.com/en-us/visualstudio/subscriptions/volume-license
Install and configure Git for windows
Download Git from here;
https://git-scm.com/download/win
This is required if you want to use git from command prompt. A reboot is required after installation.
Visual Studio 2019 Settings
This is required to integrate with Azure Devops.
Tools -> Get Tools and Features -> Individual components
Search “git”. Select “Git for Windows” from menu;
Visual studio will take some time to reconfigure.
Visual Studio 2017 Settings
Open Visual Studio, Check the Git for Windows in the Tools – Get Tools and Features…), go to “Individual Item” tab, check “Git for Windows”, and click “Modify”. Then it will ask you to update Visual Studio to the latest version, for example 15.9.36.
Click ok to install and close.