# skeleton-esnext-aspnetcore

*Creating new application*

## skeleton-esnext-aspnetcore

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.

 ![](https://cloud.githubusercontent.com/assets/2712405/18219405/5e2df228-7137-11e6-96fe-56f8171c2d96.png)\
\
 Image 1

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.

 ![](https://cloud.githubusercontent.com/assets/2712405/18219535/5296fad0-7138-11e6-95a2-8f546eb78f07.png)\
\
 Image 2

Since the project structure is completely defined at this point (remember, Monterey has successfuly parsed all configuration information that is defined in this [**skeleton**](https://github.com/aurelia/skeleton-navigation/tree/master/skeleton-esnext-aspnetcore) folder), you are presented with Monterey's view of the project configuration (Image 3). Click on the `Next` button (marker 1) to proceed.

 ![](https://cloud.githubusercontent.com/assets/2712405/18219578/a71bfb0a-7138-11e6-99ac-31644521de27.png)\
\
 Image 3

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**](https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-esnext-aspnetcore/src/skeleton/README.md#running-the-app-without-visual-studio) article.

 ![](https://cloud.githubusercontent.com/assets/2712405/18219629/16fcf7e4-7139-11e6-9384-e1339afba343.png)\
\
 Image 4

The next 6 screenshots depict the snapshots of the workflow pipeline - and probably need not additional explanations:

 ![](https://cloud.githubusercontent.com/assets/2712405/18219757/3a158a06-713a-11e6-9843-6eef611768dd.png)\
\
 Image 5

 ![](https://cloud.githubusercontent.com/assets/2712405/18219844/d65bb818-713a-11e6-8af7-57b44da11835.png)\
\
 Image 6

 ![](https://cloud.githubusercontent.com/assets/2712405/18219860/04fe26e2-713b-11e6-8fcd-75f0cb7590de.png)\
\
 Image 7

 ![](https://cloud.githubusercontent.com/assets/2712405/18219885/2baefbae-713b-11e6-9576-90a9faaa709a.png)\
\
 Image 8

Observe that the task `dotnet run` finished and shows the URL to access the just built application - see Image 10, below.

 ![](https://cloud.githubusercontent.com/assets/2712405/18219920/67ecdf8c-713b-11e6-994c-707d40054267.png)\
\
 Image 9

 ![](https://cloud.githubusercontent.com/assets/2712405/18219980/ec5314b2-713b-11e6-81c5-438e03044130.png)\
\
 Image 10

More detailed view of Image 10

 ![](https://cloud.githubusercontent.com/assets/2712405/18220031/3b52fd34-713c-11e6-9446-3721030ce3de.png)\
\
 Image 11

Shut the application down.

 ![](https://cloud.githubusercontent.com/assets/2712405/18220069/84a17b00-713c-11e6-8199-36e632ba95fe.png)\
\
 Image 12

 ![](https://cloud.githubusercontent.com/assets/2712405/18220095/c0f7c172-713c-11e6-9a1b-36e2ec563fc4.png)\
\
 Image 13

Ending the `gulp watch` task as well.

 ![](https://cloud.githubusercontent.com/assets/2712405/18220116/f7a9bf68-713c-11e6-8f00-3c0c1aae4509.png)\
\
 Image 14


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://monterey-framework.gitbook.io/monterey-user-manual/creating-new-applications/skeleton-esnext-aspnetcore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.