.NET naming conventions for a solution with .NET Standard, .NET Core, and .NET Framwork Projects

Question

I did not find anything on the Internet about accepted naming conventions for the .NET solution that contains the .NET Standard, .NET Core, and .NET Framework.

In my case, our .NET Framwork project had the following convention:

[CompanyName].[TechnologyName].[Feature] 

Now we want to port this to .NET Standard and .NET Core. Not all classes inside a function work on all of them, so we have a .NET Standard project referenced by the .NET Core project. The .NET Core project then refers to the .NET Framework project. What should we call our projects now.

One solution would be to include the name Standard or Core in the namespace:

 [CompanyName].Standard.[TechnologyName].[Feature] [CompanyName].Core.[TechnologyName].[Feature] [CompanyName].[TechnologyName].[Feature] 

or

 [CompanyName].[TechnologyName].[Feature].Standard [CompanyName].[TechnologyName].[Feature].Core [CompanyName].[TechnologyName].[Feature] 

But we want to know if there is a global naming convention for this.

Answer 1

I think the initial guide is still worth it. Take a sample of Microsoft.AspNetCore.Mvc . This is a company, a product and everything below. The .NET Standard or .NET Core should ship under the same name that was just packaged for the target framework. Take a sample of Newtonsoft.Json . If the API / feature set changes, go to the version change or change the name of the product.

Do not confuse Core add-ons with Microsoft product names. They decided to make new ASP.NET Core, .NET Core, and EF Core products to avoid erroneous assumptions about a higher version of the product: ASP.NET 5.

Listening to the ASP.NET community. I can tell you that this question came and they came to the conclusion that not everything should be added by the naming part of Core.