Creating new application
Note the red "number-markers" which indicate the sequence of mouse clicks.
Start by selecting the template
skeleton-esnext-aspnetcore (Image 1, marker 1).Then continue with accepting the definition of the location where the application will be persisted (marker 2). This action will invoke the Files Explorer, where you have to define the folder (marker 3) and click on the
Next button (marker 3) to move to the next step.
Note that Monterey will offer the name of the project, so click on the
Next button (marker 1) to accept the name and move to the next step.
Since the project structure is completely defined at this point (remember, Monterey has successfuly parsed all configuration information that is defined in this skeleton folder), you are presented with Monterey's view of the project configuration (Image 3). Click on the
Next button (marker 1) to proceed.
Now (Image 4), we reached the most important step of the Monterey wizard - page where will eventually reside the Monterey workflow plugin. At this time you see the workflow's "place-holder" implemented as a "treeview" of check-boxes presenting the ordered list of application build options that are meaningful in the given context. As Monterey gets able to handle a lot more complex tasks (managing creation, building, testing and deployment tasks of several tens of applications at the same time, the concept of the "workflow of workflows" will be the best way to ensure correct and meaningful definition of all of these tasks running in a conflict-free fashion.
Click on the
Start button (marker 1) initiates the application build and run workflow - as described in Running The App without Visual Studio article.
The next 6 screenshots depict the snapshots of the workflow pipeline - and probably need not additional explanations:
Observe that the task
dotnet run finished and shows the URL to access the just built application - see Image 10, below.
More detailed view of Image 10
Shut the application down.
gulp watch task as well.