摘要

前面介绍了使用vs2015新建asp.net core web的内容,这篇文章学习下project.json文件的内容。

project.json

原文:https://docs.microsoft.com/zh-cn/dotnet/articles/core/tools/project-json

project.json文件用来定义asp.net core项目的元数据,编译信息和依赖。在本篇文章中,你可以看到你能在project.json中定义的所有属性列表。

Note

.NET Core核心工具将在未来的发布版本中从project.json迁移到MSBuild-based项目。建议仍旧在新的.NET Core项目中使用project.json,但在发布的时候,将会把project转换为MSBuild。

For more information, see the Changes to project.json post on the .NET blog and the Using MSBuild to build .NET Core projects topic.

project.json包括的内容如下

{
"name": String,
"version": String,
"description": String,
"copyright": String,
"title": String,
"entryPoint": String,
"testRunner": String,
"authors": String[],
"language": String,
"embedInteropTypes": Boolean,
"preprocess": String or String[],
"shared": String or String[],
"dependencies": Object {
version: String,
type: String,
target: String,
include: String,
exclude: String,
suppressParent: String
},
"tools": Object,
"scripts": Object,
"buildOptions": Object {
"define": String[],
"nowarn": String[],
"additionalArguments": String[],
"warningsAsErrors": Boolean,
"allowUnsafe": Boolean,
"emitEntryPoint": Boolean,
"optimize": Boolean,
"platform": String,
"languageVersion": String,
"keyFile": String,
"delaySign": Boolean,
"publicSign": Boolean,
"debugType": String,
"xmlDoc": Boolean,
"preserveCompilationContext": Boolean,
"outputName": String,
"compilerName": String,
"compile": Object {
"include": String or String[],
"exclude": String or String[],
"includeFiles": String or String[],
"excludeFiles": String or String[],
"builtIns": Object,
"mappings": Object
},
"embed": Object {
"include": String or String[],
"exclude": String or String[],
"includeFiles": String or String[],
"excludeFiles": String or String[],
"builtIns": Object,
"mappings": Object
},
"copyToOutput": Object {
"include": String or String[],
"exclude": String or String[],
"includeFiles": String or String[],
"excludeFiles": String or String[],
"builtIns": Object,
"mappings": Object
}
},
"publishOptions": Object {
"include": String or String[],
"exclude": String or String[],
"includeFiles": String or String[],
"excludeFiles": String or String[],
"builtIns": Object,
"mappings": Object
},
"runtimeOptions": Object {
"configProperties": Object {
"System.GC.Server": Boolean,
"System.GC.Concurrent": Boolean,
"System.GC.RetainVM": Boolean,
"System.Threading.ThreadPool.MinThreads": Integer,
"System.Threading.ThreadPool.MaxThreads": Integer
},
"framework": Object {
"name": String,
"version": String,
},
"applyPatches": Boolean
},
"packOptions": Object {
"summary": String,
"tags": String[],
"owners": String[],
"releaseNotes": String,
"iconUrl": String,
"projectUrl": String,
"licenseUrl": String,
"requireLicenseAcceptance": Boolean,
"repository": Object {
"type": String,
"url": String
},
"files": Object {
"include": String or String[],
"exclude": String or String[],
"includeFiles": String or String[],
"excludeFiles": String or String[],
"builtIns": Object,
"mappings": Object
}
},
"analyzerOptions": Object {
"languageId": String
},
"configurations": Object,
"frameworks": Object {
"dependencies": Object {
version: String,
type: String,
target: String,
include: String,
exclude: String,
suppressParent: String
},
"frameworkAssemblies": Object,
"wrappedProject": String,
"bin": Object {
assembly: String
}
},
"runtimes": Object,
"userSecretsId": String
}

name

类型:String

该项目的名称,用于程序集名称以及包的名称。如果未指定此属性,则使用顶级文件夹名称。

例子:

{
"name": "MyLibrary"
}

description

类型:String

对项目的更详细的描述。用于程序集属性。

例子:

{
"description": "This is my library and it's really great!"
}

copyright

类型:String

项目版本信息,用于程序集属性。

例子:

{
"copyright": "Fabrikam 2016"
}

title

类型:String

项目别名(友好名称),可以包含在使用name属性时,不允许包含的空格和特殊字符。用于程序集属性。

例子:

{
"title": "My Library"
}

entryPoint

类型:String

项目的默认的main进入方法。

例子:

{
"entryPoint": "ADifferentMethod"
}

testRunner

类型:String

测试程序的名称,例如NUnit或者xUnit,使用Project.json的该配置,标识该项目是一个测试项目。

例子:

{
"testRunner": "NUnit"
}

authors

类型:String[]

项目所属人名称。

例子:

{
"authors": ["Anne", "Bob"]
}

language

类型:String

项目语言类型,对应于“中性语言”的编译参数。

例子:

{
"language": "en-US"
}

embedInteropTypes

类型:Boolean

true:嵌入com组件,否则为false。

例子:

{
"embedInteropTypes": true
}

preprocess

类型:带有全局通配符的String或者String[]

定义在预编译的时候应包含哪些文件。

例子:

{
"preprocess": "compiler/preprocess/**/*.cs"
}

shared

类型:带有全局通配符的String或者String[]

定义哪些文件被共享,用于类库导出。

例子:

{
"shared": "shared/**/*.cs"
}

dependencies

类型:Object

定义了项目依赖的包,包名称作为键名,值为版本信息。For more information, see the Dependency resolution article on the NuGet documentation site.

例子:

  "dependencies": {
"System.Reflection.Metadata": "1.3.0",
"Microsoft.Extensions.JsonParser.Sources": {
"type": "build",
"version": "1.0.0-rc2-20221"
},
"Microsoft.Extensions.HashCodeCombiner.Sources": {
"type": "build",
"version": "1.1.0-alpha1-21456"
},
"Microsoft.Extensions.DependencyModel": "1.0.0-*"
}

version

Type: String

Specifies the version or version range of the dependency. Use the * wildcard to specify a floating dependency version.

For example:

"dependencies": {
"Newtonsoft.Json": {
"version": "9.0.1"
}
}

type

Type: String

Specifies the type of the dependency. It can be one of the following values: default, build or platform. The default value is default.

build is known as a development dependency and is only used for build-time. It means that the package should not be published or added as a dependency to the output .nupkg file. It has the same effect of setting supressParent to all.

platform references the shared SDK. For more information, see the section on "Deploying a framework-dependent deployment with third-party dependencies" on the .NET Core Application Deployment topic.

For example:

"dependencies": {
"Microsoft.NETCore.App": {
"type": "platform",
"version": "1.0.0"
}
}

target

Type: String

Restricts the dependency to match only a project or a package.

include

Type: String

Includes parts of dependency packages. It can use one or more of the following flags: all, runtime, compile, build, contentFiles, native, analyzers, or none. Multiple flags are defined by a comma-delimited list. For more information, see the Managing dependency package assets specification on the NuGet repo.

For example:

{
"dependencies": {
"packageA": {
"version": "1.0.0",
"include": "runtime"
}
}
}

exclude

Type: String

Excludes parts of dependency packages. It can be one or more of the following flags: all, runtime, compile, build, contentFiles, native, analyzers, or none. Multiple flags are defined by a comma-delimited list. For more information, see the Managing dependency package assets specification on the NuGet repo.

For example:

{
"dependencies": {
"packageA": {
"version": "1.0.0",
"exclude": "contentFiles"
}
}
}

supressParent

Type: String

Defines additional excludes for consumers of the project. It can be one the following flags: all, runtime, compile, build, contentFiles, native, analyzers, or none. For more information, see the Managing dependency package assets specification on the NuGet repo.

{
"dependencies": {
"packageA": {
"version": "1.0.0",
"suppressParent": "compile"
}
}
}

tools

Type: Object

An object that defines package dependencies that are used as tools for the current project, not as references. Packages defined here are available in scripts that run during the build process, but they are not accessible to the code in the project itself. Tools can for example include code generators or post-build tools that perform tasks related to packing.

For example:

{
"tools": {
"MyObfuscator": "1.2.4"
}
}

scripts

Type: Object

An object that defines scripts run during the build process. Each key in this object identifies where in the build the script is run. Each value is either a string with the script to run or an array of strings containing scripts that will run in order. The supported events are:

    • precompile
    • postcompile
    • prepublish
    • postpublish

For example:

{
"scripts": {
"precompile": "generateCode.cmd",
"postcompile": [ "obfuscate.cmd", "removeTempFiles.cmd" ]
}
}

buildOptions

Type: Object

An object whose properties control various aspects of compilation. The valid properties are listed below. Can also be specified per target framework as described in the frameworks section.

For example:

 "buildOptions": {
"allowUnsafe": true,
"emitEntryPoint": true
}

define

Type: String[]

A list of defines such as "DEBUG" or "TRACE" that can be used in conditional compilation in the code.

For example:

{
"buildOptions": {
"define": ["TEST", "OTHERCONDITION"]
}

nowarn

Type: String[]

A list of warnings to ignore.

For example:

{
"buildOptions": {
"nowarn": ["CS0168", "CS0219"]
}
}

This ignores the warnings The variable 'var' is assigned but its value is never used and The variable 'var' is assigned but its value is never used

additionalArguments

Type: String[]

A list of extra arguments that will be passed to the compiler.

For example:

{
"buildOptions": {
"additionalArguments": ["/parallel", "/nostdlib"]
}
}

warningsAsErrors

Type: Boolean

true to treat warnings as errors; otherwise, false. The default is false.

For example:

{
"buildOptions": {
"warningsAsErrors": true
}
}

allowUnsafe

Type: Boolean

true to allow unsafe code in this project; otherwise, false. The default is false.

For example:

{
"buildOptions": {
"allowUnsafe": true
}
}

emitEntryPoint

Type: Boolean

true to create an executable; false to produce a library. The default is false.

For example:

{
"buildOptions": {
"emitEntryPoint": true
}
}

optimize

Type: Boolean

true to enable the compiler to optimize the code in this project; otherwise, false. The default is false.

For example:

{
"buildOptions": {
"optimize": true
}
}

platform

Type: String

The name of the target platform, such as AnyCpu, x86 or x64.

For example:

{
"buildOptions": {
"platform": "x64"
}
}

languageVersion

Type: String

The version of the language used by the compiler: ISO-1, ISO-2, 3, 4, 5, 6, or Default.

For example:

{
"buildOptions": {
"languageVersion": "5"
}
}

keyFile

Type: String

The path for the key file used for signing this assembly.

For example:

{
"buildOptions": {
"keyFile": "../keyfile.snk"
}
}

delaySign

Type: Boolean

true to delay signing; otherwise, false. The default is false.

For example:

{
"buildOptions": {
"delaySign": true
}
}

[asp.net core]project.json(1)的更多相关文章

  1. [asp.net core]project.json(2)

    摘要 上篇文章介绍了project.json中的一部分属性.属性真的比较多,所以分开了,考虑到其中的英文比较简单,也不再进行翻译了,从英文原文中,直接粘贴过来了. project.json(1) pr ...

  2. ASP.NET Core的配置(5):配置的同步[ 实例篇]

    ConfigurationBuilder在生成以Configuration对象的时候会利用注册其中的ConfigurationProvider加载原始的配置数据,那么一旦配置源中的数据发生变化,应用程 ...

  3. ASP.NET Core的配置(4):多样性的配置来源[下篇]

    我们在上篇和中篇对配置模型中默认提供的各种ConfigurationProvider进行了深入详尽的介绍,如果它们依然不能满足项目中的配置需求,我们可以还可以通过自定义ConfigurationPro ...

  4. ASP.NET Core的配置(3): 将配置绑定为对象[上篇]

    出于编程上的便利,我们通常不会直接利用ConfigurationBuilder创建的Configuration对象读取某个单一配置项的值,而是倾向于将一组相关的配置绑定为一个对象,我们将后者称为Opt ...

  5. ASP.NET Core的配置(1):读取配置信息

    提到"配置"二字,我想绝大部分.NET开发人员脑海中会立马浮现出两个特殊文件的身影,那就是我们再熟悉不过的app.config和web.config,多年以来我们已经习惯了将结构化 ...

  6. ASP.NET Core的配置(5):配置的同步[设计篇]

    本节所谓的"配置同步"主要体现在两个方面:其一,如何监控配置源并在其变化的时候自动加载其数据,其目的是让应用中通过Configuration对象承载的配置与配置源的数据同步:其二. ...

  7. ASP.NET Core的配置(4):多样性的配置来源[中篇]

    我们在本篇文章中会介绍三种针对物理文件的ConfiguationProvider,它们分别是针对JSON文件的JsonConfiguationProvider,针对XML文件的XmlConfiguat ...

  8. ASP.NET Core的配置(4):多样性的配置来源[上篇]

    较之传统通过App.config和Web.config这两个XML文件承载的配置系统,ASP.NET Core采用的这个全新的配置模型的最大一个优势就是针对多种不同配置源的支持.我们可以将内存变量.命 ...

  9. ASP.NET Core的配置(2):配置模型详解

    在上面一章我们以实例演示的方式介绍了几种读取配置的几种方式,其中涉及到三个重要的对象,它们分别是承载结构化配置信息的Configuration,提供原始配置源数据的ConfigurationProvi ...

随机推荐

  1. Java多线程与并发库高级应用-传统线程互斥技术

     线程安全问题: 多个线程操作同一份数据的时候,有可能会出现线程安全问题.可以用银行转账来解释. 模拟线程安全问题 /** * 启动两个线程分别打印两个名字,名字按照字符一个一个打印 * * @aut ...

  2. bzoj 1257

    商最多有sqrt(n)个. #include<iostream> #include<cstdio> #include<cstring> #include<al ...

  3. Leetcode 313. super ugly number

    Write a program to find the nth super ugly number. Super ugly numbers are positive numbers whose all ...

  4. K-means之matlab实现

    引入 作为练手,不妨用matlab实现K-means 要解决的问题:n个D维数据进行聚类(无监督),找到合适的簇心. 这里仅考虑最简单的情况,数据维度D=2,预先知道簇心数目K(K=4) 理论步骤 关 ...

  5. linux远程登陆其他主机并执行命令的若干方式

    一.命令行登陆 ssh后,一定后边加双引号 写命令,否则命令实在本地执行的,多条命令的话用双引号隔开, ssh user@remoteNode "cd /home ; ls" 二. ...

  6. 关于PHP代码审计和漏洞挖掘的一点思考

    这里对PHP的代码审计和漏洞挖掘的思路做一下总结,都是个人观点,有不对的地方请多多指出. PHP的漏洞有很大一部分是来自于程序员本身的经验不足,当然和服务器的配置有关,但那属于系统安全范畴了,我不太懂 ...

  7. 如何自己编写一个easyui插件续

    接着如何自己编写一个easyui插件继续分享一下如何从上一节写的“hello”插件继承出一个“hello2”. 参考了combobox的源码中继承combo,当然我这个简单很多了.都是根据自己的理解来 ...

  8. U型进度条

    今天同事说要做一个U型进度条的效果. 本打算上网找一个,结果找了一个纯CSS3打造的,不过最坑人的是他把进度条从1到100,挨个设置了CSS属性. 这不得活活累死宝宝~~~~~~~~~~~~~~. 于 ...

  9. iOS - 沙盒中,如何判断存在文件、目录

    在iOS开发中,在沙盒中创建沙盒一些存储各个功能的文件目录或者文件. 使用: [NSFileManager defaultManager] 1.判断目录,用她可以. 2.判断文件,用她可以. 3.创建 ...

  10. UVA10054The Necklace (打印欧拉路)

    题目链接 题意:一种由彩色珠子组成的项链.每个珠子的两半由不同的颜色组成.相邻的两个珠子在接触的地方颜色相同.现在有一些零碎的珠子,需要确定他们是否可以复原成完整的项链 分析:之前也没往欧拉路上面想, ...