mirror of https://github.com/abpframework/abp.git
Marcelo M
7 years ago
committed by
GitHub
GitHub
1609 changed files with 22692 additions and 11444 deletions
@ -1,2 +1,2 @@ |
|||
## abp.op |
|||
## abp.io |
|||
Source code of the official web site: https://abp.io |
|||
|
|||
File diff suppressed because one or more lines are too long
@ -0,0 +1,177 @@ |
|||
# VoloDocs |
|||
|
|||
## What is VoloDocs? |
|||
|
|||
VoloDocs is a cross-platform web application that allows you to easily create beautiful documentation and build developer communities. It simplifies software documentation with the help of GitHub integration. You use the power of GitHub for versioning, hosting of your docs. You let your users to edit a document. |
|||
|
|||
## Main Features |
|||
|
|||
- Serves documents from your GitHub repository. |
|||
- Supports Markdown / HTML document formatting. |
|||
- Supports versioning (integrated to GitHub releases). |
|||
- Supports multiple projects. |
|||
- Allows users to edit a document on GitHub. |
|||
- Cross-platform; deployable to Windows / Linux / macOS. |
|||
|
|||
## GitHub Repository |
|||
|
|||
It's free & open-source. You can browse VoloDocs source-code and contribute on GitHub: |
|||
|
|||
https://github.com/abpframework/abp/tree/master/modules/docs |
|||
|
|||
## Download |
|||
|
|||
You can download the VoloDocs release from the following links: |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.win-x64.zip - **Windows 64 bit** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.win-x86.zip - **Windows 32 bit** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.osx-x64.zip - **MacOS** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.linux-x64.zip - **Linux** |
|||
|
|||
Notice that, all installations are self-contained deployments. It means all the required third-party dependencies along with the version of .NET Core is included. So you don't need to install any .NET Core SDK / Runtime. |
|||
|
|||
## Folder Structure |
|||
|
|||
When you extract the `VoloDocs.*.zip` file, you will see a `Web` folder and a `Migrator` folder. The `Web` folder contains the website files and `Migrator` contains the application to build your database. Before publishing your website, you need to create a new database or update your existing database to the latest. If this is the first time you install VoloDocs, `Migrator` will create a new database for you, otherwise it updates to the latest version. The only setting you need to configure, is the `ConnectionString` which is located in the `appsettings.json` file. See the next section to learn how to configure your VoloDocs application. |
|||
|
|||
## Steps by Step Deployment |
|||
|
|||
- ### Database Migration |
|||
|
|||
To update your existing database or create your initial database, go to `Migrator` folder in your VoloDocs directory. |
|||
|
|||
Open `appsettings.json` in your text editor and set your database connection string. If you don't know how to write the connection string for your database system, you can check out https://www.connectionstrings.com/. |
|||
|
|||
After you set your connection string, run `Migrate.bat` for Windows platform and `VoloDocs.Migrator` for other operating systems. That's it now configure your website. |
|||
|
|||
- ### Configuring Website |
|||
|
|||
Go to `Web` folder in your VoloDocs directory. Open `appsettings.json` in your text editor. Set your connection string (same as in the `Migrator`'s `appsettings.json`). Set `title` of your website. This will be written on the left-upper corner of your website. That's it! Now you can publish your website. |
|||
|
|||
If you want to run |
|||
|
|||
- ### Deploying Website |
|||
|
|||
In the previous step, you created or updated your database. Ensure that your database exists on the specified connection string. |
|||
|
|||
- #### Deploying to IIS |
|||
|
|||
- Move `Web` folder to your `wwwroot ` folder. |
|||
- Rename `Web` folder to `VoloDocs` (Now you have `C:\inetpub\wwwroot\VoloDocs`). |
|||
- The `VoloDocs` application pool is being created automatically. Open **Application Pools** and double click `VoloDocs` application pool and set |
|||
- **.NET CLR version**: `No Managed Code` |
|||
- **Managed pipeline mode**: `Integrated` |
|||
|
|||
 |
|||
|
|||
|
|||
|
|||
- If you get the below error, it means don't have the hosting bundle installed on the server. See [this document](https://docs.microsoft.com/aspnet/core/host-and-deploy/iis/#install-the-net-core-hosting-bundle) to learn how to install it or [download Hosting Bundle](https://www.microsoft.com/net/permalink/dotnetcore-current-windows-runtime-bundle-installer) and run on your server. |
|||
|
|||
``` |
|||
Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list using IIS |
|||
``` |
|||
|
|||
- Further information about hosting VoloDocs check out [Microsoft's official document for hosting ASP.NET Core application on IIS](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis). |
|||
|
|||
- #### Deploying to Azure |
|||
|
|||
Microsoft has a good document on how to deploy your ASP.NET Core web app to Azure App Service. We recommend you to read this document https://docs.microsoft.com/en-us/azure/app-service/app-service-web-get-started-dotnet. |
|||
|
|||
- #### Running the Application From Command Line |
|||
|
|||
Alternatively you can run the application from command line, navigate to `VoloDocs\Web` folder and run `VoloDocs.Web.exe` for Windows or `VoloDocs.Web` for MacOS / Linux. |
|||
|
|||
- ### First Run |
|||
|
|||
To start the website, navigate to your address (as configured in the previous section). |
|||
|
|||
When you first open the website, you need to create a project. |
|||
|
|||
#### Creating a Project |
|||
|
|||
Go to the following address to create project |
|||
|
|||
- `http://<yourwebsite>/Account/Login?returnUrl=/Docs/Admin/Projects` |
|||
|
|||
##### Default credentials |
|||
|
|||
To login the admin side, use the following credentials: |
|||
|
|||
* **Username**: `admin` |
|||
|
|||
* **Password**: `1q2w3E*` |
|||
|
|||
##### An example project definition |
|||
|
|||
Here's a sample project information that uses GitHub source. |
|||
|
|||
We will configure the VoloDocs to show ABP Framework's documentation that's stored in GitHub. |
|||
|
|||
Here's the link to ABP Framework GitHub docs folder: |
|||
|
|||
https://github.com/abpframework/abp/tree/master/docs/en |
|||
|
|||
|
|||
|
|||
* **Name**: `ABP Framework` |
|||
|
|||
* **Short name**: `abp` |
|||
|
|||
* **Format**: `markdown` |
|||
|
|||
* **Default document name**: `Index` |
|||
|
|||
* **Navigation document name**: `docs-nav.json` ([see the sample navigation](https://github.com/abpframework/abp/blob/master/docs/en/docs-nav.json)) |
|||
|
|||
* **Minimum version**: *leave empty* *(hides the previous versions)* |
|||
|
|||
* **Main web site URL**: `/` |
|||
|
|||
* **Latest version branch name**: leave empty () |
|||
|
|||
* **GitHub root URL**: `https://github.com/abpframework/abp/tree/{version}/docs/en/` |
|||
|
|||
* **GitHub access token**: [see how to retrieve GitHub access token](#retrieving-github-access-token) |
|||
|
|||
* **GitHub user agent**: [see how to learn your GitHub username](#learn-your-github-username) |
|||
|
|||
 |
|||
|
|||
##### Retrieving GitHub Access Token |
|||
|
|||
To create a personal access token in GitHub, you need to visit the **Settings** of the user account and under **Developer settings** you will find **Personal access tokens**. Select **Generate new token**, enter in a name as the Token description and enable the repo checkbox. Alternatively, to enter generate new token, browse to https://github.com/settings/tokens/new. |
|||
|
|||
###### Generate Token for Public Repositories |
|||
|
|||
To access public repositories, check `public_repo` under the `repo` section. This will enable VoloDocs to access your public GitHub repositories. Click `Generate Token` button on the bottom of the page. |
|||
|
|||
 |
|||
|
|||
###### Generate Token for Private Repositories |
|||
|
|||
To access public repositories, check all items under the `repo` section. This will enable VoloDocs to access your private GitHub repositories. Click `Generate Token` button on the bottom of the page. |
|||
|
|||
 |
|||
|
|||
###### Learn Your GitHub Username |
|||
|
|||
To learn your GitHub username, click on your profile picture on the top-right corner of the GitHub page. You will see your username right after the text "Signed in as ..." |
|||
|
|||
 |
|||
|
|||
|
|||
|
|||
After you save the project, go to root website address and you will see your documentation. |
|||
|
|||
`http://<yourwebsite>/documents` |
|||
|
|||
### Any Issues? |
|||
|
|||
If you encounter any problem or issues about installation, usage or report a bug, follow the link: |
|||
|
|||
https://github.com/abpframework/abp/issues/new |
|||
|
|||
|
After Width: | Height: | Size: 58 KiB |
|
After Width: | Height: | Size: 153 KiB |
|
After Width: | Height: | Size: 146 KiB |
|
After Width: | Height: | Size: 144 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 5.9 KiB |
@ -0,0 +1,174 @@ |
|||
# VoloDocs |
|||
|
|||
## 什么是VoloDocs? |
|||
|
|||
VoloDocs是一个跨平台的应用程序,帮助你简单的创建良好的文档与构建开发人员社区. 它借助Github集成简化了软件文档. 使用Github的强大功能进行版本控制,托管文档,并允许用户编译文档. |
|||
|
|||
## 主要功能 |
|||
|
|||
- 集成Github从仓库提供文档. |
|||
- 支持Markdown/HTML文档格式. |
|||
- 支持版本控制 (集成Github release). |
|||
- 支持多个项目. |
|||
- 允许用户在Github上编辑文档. |
|||
- 跨平台,可部署到Windows/Linux/macOS. |
|||
|
|||
## Github源码仓库 |
|||
|
|||
它是免费并且开源的. 你可以查看VoloDocs源码,我们也欢迎PR: |
|||
|
|||
https://github.com/abpframework/abp/tree/master/modules/docs |
|||
|
|||
## 下载 |
|||
|
|||
你可以在下面的链接下载VoloDocs release版: |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.win-x64.zip - **Windows 64 bit** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.win-x86.zip - **Windows 32 bit** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.osx-x64.zip - **MacOS** |
|||
|
|||
http://apps.abp.io/VoloDocs/VoloDocs.linux-x64.zip - **Linux** |
|||
|
|||
上面所有的release都是自包含运行时的部署文件. 包含所有的第三方依赖与.Net Core Runtime,所以你不需要安装任何.Net Core SDK/Runtime. |
|||
|
|||
## 目录结构 |
|||
|
|||
解压 `VoloDocs.*.zip` 文件, 你会得到一个 `Web` 文件夹和 `Migrator` 文件夹. `Web` 文件夹中包含网站文件, `Migrator` 文件夹中包含构建数据库的应用程序. 在发布网站之前需要创建数据库或将现有的数据库更新到最新迁移. 如果这是你第一次安装VoloDocs, `Migrator` 会创建一个新数据库. 如果是升级已有的VoloDocs则会将数据库升级到最新的迁移. 使用 `Migrator` 你需要在 `appsettings.json` 文件中更改 `ConnectionString`. 参阅下一节了解如何配置VoloDocs应用程序. |
|||
|
|||
## 逐步部署 |
|||
|
|||
- ### 数据库迁移 |
|||
|
|||
进入 `Migrator` 目录中创建或更新数据库. |
|||
|
|||
打开 `appsettings.json` 文件设置连接字符串,如果你不清楚如何编写连接字符串,可以查看 https://www.connectionstrings.com/. |
|||
|
|||
设置连接字符串后运行 `Migrate.bat` 如果是Linux或MacOS运行 `DotNet VoloDocs.Migrator.dll` 命令. |
|||
|
|||
- ### 配置网站 |
|||
|
|||
进入 `Web` 目录下的VoloDocs文件夹. 打开 `appsettings.json` 文件设置连接字符串(与 `Migrator` 的 `appsettings.json` 相同). 你也可以为网站设置你想要的 `title`,它会显示在网站的左上角. 做完这些现在可以发布网站了. |
|||
|
|||
- ### 部署网站 |
|||
|
|||
在上一步我们创建/更新了数据库(确保数据库链接字符串正确). |
|||
|
|||
- #### 部署到IIS |
|||
|
|||
- 移动 `Web` 文件夹到你的 `wwwroot ` 文件夹中. |
|||
- 重命名 `Web` 文件夹为 `VoloDocs` (现在我们有了 `C:\inetpub\wwwroot\VoloDocs`). |
|||
- 创建网站 `VoloDocs` 会自动创建相同名称的应用程序池. 打开 **应用程序池** 并双击 `VoloDocs` 应用程序池做以下设置 |
|||
- **.NET CLR 版本**: `无托管代码` |
|||
- **托管管道模式**: `集成` |
|||
|
|||
 |
|||
|
|||
|
|||
|
|||
- 如果发生发生发现错误,表示未在服务器安装托管捆绑包. 请参阅文档 [this document](https://docs.microsoft.com/aspnet/core/host-and-deploy/iis/#install-the-net-core-hosting-bundle) 了解如何安装或[下载托管捆绑包](https://www.microsoft.com/net/permalink/dotnetcore-current-windows-runtime-bundle-installer). |
|||
|
|||
``` |
|||
Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list using IIS |
|||
``` |
|||
|
|||
- 关于托管VoloDocs的更多信息,请参阅 [在IIS上托管ASP.NET Core应用程序的微软官方文档](https://docs.microsoft.com/zh-cn/aspnet/core/host-and-deploy/iis). |
|||
|
|||
- #### 部署到Azure |
|||
|
|||
微软有一篇关于将ASP.NET Core应用程序部署到Azure App Service的文档. 我们建议你此[文档](https://docs.microsoft.com/en-us/azure/app-service/app-service-web-get-started-dotnet). |
|||
|
|||
- #### 使用命令行运行应用程序 |
|||
|
|||
你可以从命令行运行应用程序,进入 `VoloDocs\Web` 文件夹并运行 `VoloDocs.Web.exe`,如果是Linux或MacOS运行 `DotNet VoloDocs.Web.dll` 命令. |
|||
|
|||
- ### 首次运行 |
|||
|
|||
打开浏览器导航到你的网址. |
|||
|
|||
首次运行网站,我们需要创建一个项目. |
|||
|
|||
#### 创建项目 |
|||
|
|||
跳转到以下网址创建项目 |
|||
|
|||
- `http://<yourwebsite>/Account/Login?returnUrl=/Docs/Admin/Projects` |
|||
|
|||
##### 默认凭据 |
|||
|
|||
使用管理员身份登陆到管理后台,用户名密码如下: |
|||
|
|||
* **用户名**: `admin` |
|||
|
|||
* **密码**: `1q2w3E*` |
|||
|
|||
##### 示例项目的定义 |
|||
|
|||
以下是一个使用了Github源的示例项目信息. |
|||
|
|||
配置VoloDocs展示存储在Github仓库中ABP Framework的文档. |
|||
|
|||
这是ABP Framework文档在Github的链接: |
|||
|
|||
https://github.com/abpframework/abp/tree/master/docs/zh-Hans |
|||
|
|||
|
|||
|
|||
* **名称**: `ABP Framework` |
|||
|
|||
* **简称**: `abp` |
|||
|
|||
* **格式**: `markdown` |
|||
|
|||
* **默认文档名称**: `Index` |
|||
|
|||
* **文档导航名称**: `docs-nav.json` ([参见示例](https://github.com/abpframework/abp/blob/master/docs/zh-Hans/docs-nav.json)) |
|||
|
|||
* **最小版本**: *留空* *(隐藏之前的版本)* |
|||
|
|||
* **主网站网址**: `/` |
|||
|
|||
* **最新版本分支名称**: 留空 |
|||
|
|||
* **GitHub链接**: `https://github.com/abpframework/abp/tree/{version}/docs/zh-Hans/` |
|||
|
|||
* **GitHub访问令牌**: [参见如何创建Github访问令牌](#retrieving-github-access-token) |
|||
|
|||
* **GitHub用户名称**: [参见如何找到自己的Github用户名称](#learn-your-github-username) |
|||
|
|||
 |
|||
|
|||
##### 创建访问令牌 |
|||
|
|||
在Github页右上角找到 `Settings`,然后在左侧导航中点击 `Developer Settings`,在这里选择 `Personal access tokens`. 点击创建新token,输入名称与描述并勾选repo复选框. 如果已有访问令牌但已经忘记,可以选择[重新生成](https://github.com/settings/tokens/new). |
|||
|
|||
###### 创建仅授权访问公共仓库的token |
|||
|
|||
想要仅授权访问公共仓库,仅勾选 `public_repo` 就可以了,然后点击页面底部的 `Generate Token` 按钮完成操作. |
|||
|
|||
 |
|||
|
|||
###### 创建可访问私有仓库的token |
|||
|
|||
想要授权访问私有仓库,勾选 `repo` 下的所有选项. 然后点击页面底部的 `Generate Token` 按钮完成操作. |
|||
|
|||
 |
|||
|
|||
###### 查看你的Github用户名称 |
|||
|
|||
在Github页面右上角点击头像图片,"Signed in as ..." 后面就是你的用户名称 |
|||
|
|||
 |
|||
|
|||
|
|||
|
|||
保存项目后转到网站根地址,你会看到文档已经正常显示. |
|||
|
|||
`http://<yourwebsite>/documents` |
|||
|
|||
### 发现问题? |
|||
|
|||
如果你在安装,使用时遇到问题或者发现bug,请发起issues与我们联系: |
|||
|
|||
https://github.com/abpframework/abp/issues/new |
|||
@ -0,0 +1,33 @@ |
|||
# 领取驱动设计 |
|||
|
|||
## 什么是DDD? |
|||
|
|||
ABP框架提供了**基础设施**使基础**DDD**的开发更易实现. DDD在[维基百科中的定义](https://zh.wikipedia.org/wiki/%E5%9F%9F%E9%A9%B1%E5%8A%A8%E5%BC%80%E5%8F%91)如下: |
|||
|
|||
> **领域驱动设计(DDD)** 是一种通过将实现连接到持续进化的模型来满足复杂需求的软件开发方法. 领域驱动设计的前提是: |
|||
> |
|||
> - 把项目的主要重点放在核心领域和领域逻辑上 |
|||
> - 把复杂的设计放在领域模型上 |
|||
> - 发起技术专家和领域专家之间的创造性协作,以迭代方式完善解决特定领域问题的概念模型 |
|||
|
|||
### 分层 |
|||
|
|||
ABP框架遵循DDD原则和模式去实现分层应用程序模型,该模型由四个基本层组成: |
|||
|
|||
- **表示层**: 为用户提供接口. 使用*应用层*实现与用户交互. |
|||
- **应用层**: 表示层与领域层的中介,编排业务对象执行特定的应用程序任务. 使用应用程序逻辑实现用例. |
|||
- **领域层**: 包含业务对象以及业务规则. 是应用程序的核心. |
|||
- **基础设施层**: 提供通用的技术功能,支持更高的层,主要使用第三方类库. |
|||
|
|||
## 内容 |
|||
|
|||
* **领域层** |
|||
* [实体与聚合根](Entities.md) |
|||
* 值对象 |
|||
* [仓储](Repositories.md) |
|||
* 领域服务 |
|||
* 规约 |
|||
* **应用层** |
|||
* [应用服务](Application-Services.md) |
|||
* [数据传输对象(DTO)](Data-Transfer-Objects.md) |
|||
* 工作单元 |
|||
|
After Width: | Height: | Size: 58 KiB |
|
After Width: | Height: | Size: 153 KiB |
|
After Width: | Height: | Size: 146 KiB |
|
After Width: | Height: | Size: 144 KiB |
|
After Width: | Height: | Size: 6.4 KiB |
|
After Width: | Height: | Size: 6.3 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 5.9 KiB |
@ -0,0 +1,25 @@ |
|||
using Microsoft.AspNetCore.Authentication; |
|||
using Microsoft.AspNetCore.Authentication.JwtBearer; |
|||
|
|||
namespace Microsoft.AspNetCore.Builder |
|||
{ |
|||
public static class ApplicationBuilderAbpJwtTokenMiddlewareExtension |
|||
{ |
|||
public static IApplicationBuilder UseJwtTokenMiddleware(this IApplicationBuilder app, string schema = JwtBearerDefaults.AuthenticationScheme) |
|||
{ |
|||
return app.Use(async (ctx, next) => |
|||
{ |
|||
if (ctx.User.Identity?.IsAuthenticated != true) |
|||
{ |
|||
var result = await ctx.AuthenticateAsync(schema); |
|||
if (result.Succeeded && result.Principal != null) |
|||
{ |
|||
ctx.User = result.Principal; |
|||
} |
|||
} |
|||
|
|||
await next(); |
|||
}); |
|||
} |
|||
} |
|||
} |
|||
@ -0,0 +1,24 @@ |
|||
<Project Sdk="Microsoft.NET.Sdk"> |
|||
|
|||
<Import Project="..\..\..\common.props" /> |
|||
|
|||
<PropertyGroup> |
|||
<TargetFramework>netstandard2.0</TargetFramework> |
|||
<AssemblyName>Volo.Abp.AspNetCore.Authentication.JwtBearer</AssemblyName> |
|||
<PackageId>Volo.Abp.AspNetCore.Authentication.JwtBearer</PackageId> |
|||
<AssetTargetFallback>$(AssetTargetFallback);portable-net45+win8+wp8+wpa81;</AssetTargetFallback> |
|||
<GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute> |
|||
<GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute> |
|||
<GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute> |
|||
<RootNamespace /> |
|||
</PropertyGroup> |
|||
|
|||
<ItemGroup> |
|||
<ProjectReference Include="..\Volo.Abp.Security\Volo.Abp.Security.csproj" /> |
|||
</ItemGroup> |
|||
|
|||
<ItemGroup> |
|||
<PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="2.2.0" /> |
|||
</ItemGroup> |
|||
|
|||
</Project> |
|||
@ -0,0 +1,11 @@ |
|||
using Volo.Abp.Modularity; |
|||
using Volo.Abp.Security; |
|||
|
|||
namespace Volo.Abp.AspNetCore.Authentication.JwtBearer |
|||
{ |
|||
[DependsOn(typeof(AbpSecurityModule))] |
|||
public class AbpAspNetCoreAuthenticationJwtBearerModule : AbpModule |
|||
{ |
|||
|
|||
} |
|||
} |
|||
@ -0,0 +1,9 @@ |
|||
using System; |
|||
|
|||
namespace Volo.Abp.AspNetCore.Mvc.UI.Bootstrap.TagHelpers.Form |
|||
{ |
|||
[AttributeUsage(AttributeTargets.Property)] |
|||
public class DynamicFormIgnore : Attribute |
|||
{ |
|||
} |
|||
} |
|||
@ -0,0 +1,36 @@ |
|||
<Project Sdk="Microsoft.NET.Sdk"> |
|||
|
|||
<Import Project="..\..\..\common.props" /> |
|||
|
|||
<PropertyGroup> |
|||
<TargetFramework>netstandard2.0</TargetFramework> |
|||
<AssetTargetFallback>$(AssetTargetFallback);portable-net45+win8+wp8+wpa81;</AssetTargetFallback> |
|||
<GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute> |
|||
<GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute> |
|||
<GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute> |
|||
<RootNamespace /> |
|||
</PropertyGroup> |
|||
|
|||
<ItemGroup> |
|||
<PackageReference Include="Ionic.Zip" Version="1.9.1.8" /> |
|||
<PackageReference Include="HtmlAgilityPack.NetCore" Version="1.5.0.1" /> |
|||
<PackageReference Include="Microsoft.AspNetCore.Hosting.Abstractions" Version="2.2.0" /> |
|||
<PackageReference Include="System.Text.Encoding.CodePages" Version="4.5.1" /> |
|||
<PackageReference Include="System.Security.Permissions" Version="4.5.0" /> |
|||
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="3.0.0" /> |
|||
</ItemGroup> |
|||
|
|||
<ItemGroup> |
|||
<ProjectReference Include="..\Volo.Abp.Ddd.Domain\Volo.Abp.Ddd.Domain.csproj" /> |
|||
<ProjectReference Include="..\Volo.Abp.Http\Volo.Abp.Http.csproj" /> |
|||
<ProjectReference Include="..\Volo.Abp.IdentityModel\Volo.Abp.IdentityModel.csproj" /> |
|||
<ProjectReference Include="..\Volo.Abp.Json\Volo.Abp.Json.csproj" /> |
|||
</ItemGroup> |
|||
|
|||
<ItemGroup> |
|||
<Reference Include="System.Data.SqlXml"> |
|||
<HintPath>C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Data.SqlXml.dll</HintPath> |
|||
</Reference> |
|||
</ItemGroup> |
|||
|
|||
</Project> |
|||
@ -0,0 +1,32 @@ |
|||
using System.Text; |
|||
using Volo.Abp.Cli.Commands; |
|||
using Volo.Abp.Domain; |
|||
using Volo.Abp.IdentityModel; |
|||
using Volo.Abp.Json; |
|||
using Volo.Abp.Modularity; |
|||
|
|||
namespace Volo.Abp.Cli |
|||
{ |
|||
[DependsOn( |
|||
typeof(AbpDddDomainModule), |
|||
typeof(AbpJsonModule), |
|||
typeof(AbpIdentityModelModule) |
|||
)] |
|||
public class AbpCliCoreModule : AbpModule |
|||
{ |
|||
public override void ConfigureServices(ServiceConfigurationContext context) |
|||
{ |
|||
Encoding.RegisterProvider(CodePagesEncodingProvider.Instance); |
|||
|
|||
Configure<CliOptions>(options => |
|||
{ |
|||
options.Commands["help"] = typeof(HelpCommand); |
|||
options.Commands["new"] = typeof(NewCommand); |
|||
options.Commands["add-package"] = typeof(AddPackageCommand); |
|||
options.Commands["add-module"] = typeof(AddModuleCommand); |
|||
options.Commands["login"] = typeof(LoginCommand); |
|||
options.Commands["logout"] = typeof(LogoutCommand); |
|||
}); |
|||
} |
|||
} |
|||
} |
|||
@ -0,0 +1,67 @@ |
|||
using System; |
|||
using System.Linq; |
|||
using System.Text; |
|||
using JetBrains.Annotations; |
|||
|
|||
namespace Volo.Abp.Cli.Args |
|||
{ |
|||
public class CommandLineArgs |
|||
{ |
|||
[CanBeNull] |
|||
public string Command { get; } |
|||
|
|||
[CanBeNull] |
|||
public string Target { get; } |
|||
|
|||
[NotNull] |
|||
public CommandLineOptions Options { get; } |
|||
|
|||
public CommandLineArgs([CanBeNull] string command = null, [CanBeNull] string target = null) |
|||
{ |
|||
Command = command; |
|||
Target = target; |
|||
Options = new CommandLineOptions(); |
|||
} |
|||
|
|||
public static CommandLineArgs Empty() |
|||
{ |
|||
return new CommandLineArgs(); |
|||
} |
|||
|
|||
public bool IsCommand(string command) |
|||
{ |
|||
return string.Equals(Command, command, StringComparison.OrdinalIgnoreCase); |
|||
} |
|||
|
|||
public override string ToString() |
|||
{ |
|||
var sb = new StringBuilder(); |
|||
|
|||
if (Command != null) |
|||
{ |
|||
sb.AppendLine($"Command: {Command}"); |
|||
} |
|||
|
|||
if (Target != null) |
|||
{ |
|||
sb.AppendLine($"Target: {Target}"); |
|||
} |
|||
|
|||
if (Options.Any()) |
|||
{ |
|||
sb.AppendLine("Options:"); |
|||
foreach (var option in Options) |
|||
{ |
|||
sb.AppendLine($" - {option.Key} = {option.Value}"); |
|||
} |
|||
} |
|||
|
|||
if (sb.Length <= 0) |
|||
{ |
|||
sb.Append("<EMPTY>"); |
|||
} |
|||
|
|||
return sb.ToString(); |
|||
} |
|||
} |
|||
} |
|||
@ -0,0 +1,104 @@ |
|||
using System; |
|||
using System.Collections.Generic; |
|||
using System.Linq; |
|||
using Volo.Abp.DependencyInjection; |
|||
|
|||
namespace Volo.Abp.Cli.Args |
|||
{ |
|||
public class CommandLineArgumentParser : ICommandLineArgumentParser, ITransientDependency |
|||
{ |
|||
public CommandLineArgs Parse(string[] args) |
|||
{ |
|||
if (args.IsNullOrEmpty()) |
|||
{ |
|||
return CommandLineArgs.Empty(); |
|||
} |
|||
|
|||
var argumentList = args.ToList(); |
|||
|
|||
//Command
|
|||
|
|||
var command = argumentList[0]; |
|||
argumentList.RemoveAt(0); |
|||
|
|||
if (!argumentList.Any()) |
|||
{ |
|||
return new CommandLineArgs(command); |
|||
} |
|||
|
|||
//Target
|
|||
|
|||
var target = argumentList[0]; |
|||
if (target.StartsWith("-")) |
|||
{ |
|||
target = null; |
|||
} |
|||
else |
|||
{ |
|||
argumentList.RemoveAt(0); |
|||
} |
|||
|
|||
if (!argumentList.Any()) |
|||
{ |
|||
return new CommandLineArgs(command, target); |
|||
} |
|||
|
|||
//Options
|
|||
|
|||
var commandLineArgs = new CommandLineArgs(command, target); |
|||
|
|||
while (argumentList.Any()) |
|||
{ |
|||
var optionName = ParseOptionName(argumentList[0]); |
|||
argumentList.RemoveAt(0); |
|||
|
|||
if (!argumentList.Any()) |
|||
{ |
|||
commandLineArgs.Options[optionName] = null; |
|||
break; |
|||
} |
|||
|
|||
if (IsOptionName(argumentList[0])) |
|||
{ |
|||
commandLineArgs.Options[optionName] = null; |
|||
continue; |
|||
} |
|||
|
|||
commandLineArgs.Options[optionName] = argumentList[0]; |
|||
argumentList.RemoveAt(0); |
|||
} |
|||
|
|||
return commandLineArgs; |
|||
} |
|||
|
|||
private static bool IsOptionName(string argument) |
|||
{ |
|||
return argument.StartsWith("-") || argument.StartsWith("--"); |
|||
} |
|||
|
|||
private static string ParseOptionName(string argument) |
|||
{ |
|||
if (argument.StartsWith("--")) |
|||
{ |
|||
if (argument.Length <= 2) |
|||
{ |
|||
throw new ArgumentException("Should specify an option name after '--' prefix!"); |
|||
} |
|||
|
|||
return argument.RemovePreFix("--"); |
|||
} |
|||
|
|||
if (argument.StartsWith("-")) |
|||
{ |
|||
if (argument.Length <= 1) |
|||
{ |
|||
throw new ArgumentException("Should specify an option name after '--' prefix!"); |
|||
} |
|||
|
|||
return argument.RemovePreFix("-"); |
|||
} |
|||
|
|||
throw new ArgumentException("Option names should start with '-' or '--'."); |
|||
} |
|||
} |
|||
} |
|||
@ -0,0 +1,35 @@ |
|||
using System; |
|||
using System.Collections.Generic; |
|||
using JetBrains.Annotations; |
|||
|
|||
namespace Volo.Abp.Cli.Args |
|||
{ |
|||
public class CommandLineOptions : Dictionary<string, string> |
|||
{ |
|||
[CanBeNull] |
|||
public string GetOrNull([NotNull] string name, params string[] alternativeNames) |
|||
{ |
|||
Check.NotNullOrWhiteSpace(name, nameof(name)); |
|||
|
|||
var value = this.GetOrDefault(name); |
|||
if (!value.IsNullOrWhiteSpace()) |
|||
{ |
|||
return value; |
|||
} |
|||
|
|||
if (!alternativeNames.IsNullOrEmpty()) |
|||
{ |
|||
foreach (var alternativeName in alternativeNames) |
|||
{ |
|||
value = this.GetOrDefault(alternativeName); |
|||
if (!value.IsNullOrWhiteSpace()) |
|||
{ |
|||
return value; |
|||
} |
|||
} |
|||
} |
|||
|
|||
return null; |
|||
} |
|||
} |
|||
} |
|||
@ -0,0 +1,7 @@ |
|||
namespace Volo.Abp.Cli.Args |
|||
{ |
|||
public interface ICommandLineArgumentParser |
|||
{ |
|||
CommandLineArgs Parse(string[] args); |
|||
} |
|||
} |
|||
@ -0,0 +1,43 @@ |
|||
using System.IO; |
|||
using System.Text; |
|||
using System.Threading.Tasks; |
|||
using IdentityModel; |
|||
using Volo.Abp.DependencyInjection; |
|||
using Volo.Abp.IdentityModel; |
|||
using Volo.Abp.IO; |
|||
|
|||
namespace Volo.Abp.Cli.Auth |
|||
{ |
|||
public class AuthService : ITransientDependency |
|||
{ |
|||
protected IIdentityModelAuthenticationService AuthenticationService { get; } |
|||
|
|||
public AuthService(IIdentityModelAuthenticationService authenticationService) |
|||
{ |
|||
AuthenticationService = authenticationService; |
|||
} |
|||
|
|||
public async Task LoginAsync(string userName, string password) |
|||
{ |
|||
var accessToken = await AuthenticationService.GetAccessTokenAsync( |
|||
new IdentityClientConfiguration( |
|||
"https://localhost:44333", //TODO: Configure
|
|||
"role email abpio_www abpio_commercial", |
|||
"abp-cli", |
|||
"1q2w3e*", |
|||
OidcConstants.GrantTypes.Password, |
|||
userName, |
|||
password |
|||
) |
|||
); |
|||
|
|||
File.WriteAllText(CliPaths.AccessToken, accessToken, Encoding.UTF8); |
|||
} |
|||
|
|||
public Task LogoutAsync() |
|||
{ |
|||
FileHelper.DeleteIfExists(CliPaths.AccessToken); |
|||
return Task.CompletedTask; |
|||
} |
|||
} |
|||
} |
|||
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue