Skip to content

Cli: fix no-ui option for module templates #9391

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jun 22, 2021
Merged

Cli: fix no-ui option for module templates #9391

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f09aea1
Cli: fix no-ui option for module templates
yekalkan Jun 22, 2021
a0ca385
Update Module.md
yekalkan Jun 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 2 additions & 16 deletions docs/en/Startup-Templates/Module.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,23 +20,9 @@ abp new Acme.IssueManagement -t module

- `Acme.IssueManagement` is the solution name, like *YourCompany.YourProduct*. You can use single level, two-levels or three-levels naming.

### Specify the UI Framework

This template provides multiple UI frameworks:

* `mvc`: ASP.NET Core MVC UI with Razor Pages (default)
* `blazor`: Blazor UI
* `angular`: Angular UI

Use `-u` or `--ui` option to specify the UI framework:

````bash
abp new Acme.IssueManagement -t module -u angular
````

### Without User Interface

The template comes with an MVC UI by default. You can use `--no-ui` option to not include the UI layer.
The template comes with MVC, Blazor & Angular user interfaces by default. You can use `--no-ui` option to not include any of these UI layers.

````bash
abp new Acme.IssueManagement -t module --no-ui
Expand Down Expand Up @@ -179,7 +165,7 @@ You should run the application with the given order:

### Angular UI

If you choose `Angular` as the UI framework (using the `-u angular` option), the solution will have a folder called `angular` in it. This is where the client-side code is located. When you open that folder in an IDE, the folder structure will look like below:
The solution will have a folder called `angular` in it. This is where the Angular client-side code is located. When you open that folder in an IDE, the folder structure will look like below:

![Folder structure of ABP Angular module project](../images/angular-module-folder-structure.png)

Expand Down
8 changes: 8 additions & 0 deletions ...src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectBuilding/Templates/Module/ModuleTemplateBase.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,14 @@ private void DeleteUnrelatedProjects(ProjectBuildContext context, List<ProjectBu
"MyCompanyName.MyProjectName.Blazor"
));

steps.Add(new RemoveProjectFromSolutionStep(
"MyCompanyName.MyProjectName.Blazor.Server"
));

steps.Add(new RemoveProjectFromSolutionStep(
"MyCompanyName.MyProjectName.Blazor.WebAssembly"
));

steps.Add(new RemoveProjectFromSolutionStep(
"MyCompanyName.MyProjectName.Blazor.Host",
projectFolderPath: "/aspnet-core/host/MyCompanyName.MyProjectName.Blazor.Host"
Expand Down