Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why VS 2017 - and not cli #15

Open
adriatic opened this issue Apr 5, 2017 · 0 comments
Open

Why VS 2017 - and not cli #15

adriatic opened this issue Apr 5, 2017 · 0 comments

Comments

@adriatic
Copy link
Member

adriatic commented Apr 5, 2017

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

  1. 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:

image

  1. VS allows easy viewing and changing the data - if wne where needed

image

  1. Ensuring easy project portability between our team members
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant