-
Notifications
You must be signed in to change notification settings - Fork 1
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
Start developing Carmel with VS 2017 #8
Comments
Maintaining all * core version numbersCarmel uses the dotnet core / ef core / Identity core components that were released as a part of Visual Studio 2017 Community edition as shown on this screenshot: This is the dialog where these version numbers will be managed in the future, as needed. The summary view of this information is obtain via This command yields the information shown below:
Note: I have no idea what is the significance and meaning of the ItemGroup shown below
|
Creating (and recreating) the Carmel databaseThe database can viewed (both the schema and content) using VS 2017 SQL Server Object Explorer: As an example - here is the content of the Components table: Here is the summary of steps taken to create a new version of this database. In order to avoid any unneeded complications with database migrations, this process assumes that the list of components and its parts comes from this file: Step 1Generate new code file which needs to be used as the replacement for this section of the CatalogContextSeedData.cs (this replacement is done via the editor of course). This code file is created by 1. running this main.js utility application using Visual Studio Code Note that this app uses a local copy of 2. Once you verified that the generated C# code is correct and does what you want, run the command
in the Step 2Delete the current CarmelDb database (using VS 2017 SQL Server Object Explorer) Step 3Run the Carmel app (defined by this Visual Studio solution). Observe that the Carmel app always tries to create the database (this line in Startup.cs class, which does not do anything if the database exists) |
Developing and testing Carmel APIIn order to use the current Carmel app without its user interface clock on the Properties menu item of the Carmel project and uncheck the Launch URL box shown below Then run the app (from Visual Studio, at this time) and use Postman to interact with the app (note that the app uses localhost:8000 port) This specific sample was obtained running the which maps to this method in the |
Introduction
As of 3/13/2017, the application in the dotnet folder is verified as correctly running with the Visual Studio 2017 Community edition
This document describes the details of running and further evolving this application
The text was updated successfully, but these errors were encountered: