Only VS 2017 allowed me to ensure the need synchronization with Auth0 developers team - all of their original samples (hundreds of them) were developed with Visual Studio 2015 and before dot net core was available. I had the same history and spent almost a month trying to ensure that my existing code works with their samples. That horrible waste of time was ended when we all agreed to use VS 2017 - which brought the complete and compatible set of dotnet core libs. This document is the definition of the versions that should be used in Carmel-api.
"Standard" way of using local SQL database server
There are too many different versions of that database with too many ways of defining its location. Using VS solves this problem by
Describing the path to the database in the VS project's integral document, which can be manipulated in the "standard way" using VS SQL Server Object Explorer:
VS allows easy viewing and changing the data - if wne where needed
Ensuring easy project portability between our team members
Easy definition of matching libs
Only VS 2017 allowed me to ensure the need synchronization with Auth0 developers team - all of their original samples (hundreds of them) were developed with Visual Studio 2015 and before dot net core was available. I had the same history and spent almost a month trying to ensure that my existing code works with their samples. That horrible waste of time was ended when we all agreed to use VS 2017 - which brought the complete and compatible set of dotnet core libs. This document is the definition of the versions that should be used in Carmel-api.
"Standard" way of using local SQL database server
There are too many different versions of that database with too many ways of defining its location. Using VS solves this problem by