msbuild

TFS build job failed for Framework 4.7.2

由 ⅰ亾dé卋堺 提交于 2020-05-12 11:13:23
问题 I have installed framework 4.7.2 on TFS 2013 server and trying to build a job using msbuild. I am getting following error: Task Parameter:TargetFrameworkMoniker=.NETFramework,Version=v4.7.2 (TaskId:6) C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1098,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.7.2" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application

TFS build job failed for Framework 4.7.2

由 独自空忆成欢 提交于 2020-05-12 11:12:49
问题 I have installed framework 4.7.2 on TFS 2013 server and trying to build a job using msbuild. I am getting following error: Task Parameter:TargetFrameworkMoniker=.NETFramework,Version=v4.7.2 (TaskId:6) C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1098,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.7.2" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application

Best way to integrate webpack builds with ASP.NET Core 3.0?

由 不想你离开。 提交于 2020-05-09 19:35:19
问题 I'm upgrading my ASP.NET Core app to V3, and using Visual Studio 2019 for development / debugging. The process has been smooth except for this: public void Configure(….. app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions { HotModuleReplacement = false, ReactHotModuleReplacement = false }); UseWebpackDevMiddleware is no more: https://github.com/aspnet/AspNetCore/issues/12890 . I'm now looking to understand the best way to have VS run webpack every time I debug, ideally only on JS code

Visual studio 2017 : nesting files in a class library project

由 烈酒焚心 提交于 2020-05-08 09:45:32
问题 In web projects you have the option of nesting files + startup.cs +--startup.internals.cs +--startup.configuration.cs Is there any way to achieve the same behavior in a class library project as well ? Updates : Partially solved Ok got it , You need to be aware of your files path. for a structure like this (the files are at project level) +-- myProject.csproj +-- startup.cs +-- startup.internals.cs +-- startup.configuration.cs Then this is the configuration you are looking for. <ItemGroup>

Visual studio 2017 : nesting files in a class library project

由 て烟熏妆下的殇ゞ 提交于 2020-05-08 09:45:14
问题 In web projects you have the option of nesting files + startup.cs +--startup.internals.cs +--startup.configuration.cs Is there any way to achieve the same behavior in a class library project as well ? Updates : Partially solved Ok got it , You need to be aware of your files path. for a structure like this (the files are at project level) +-- myProject.csproj +-- startup.cs +-- startup.internals.cs +-- startup.configuration.cs Then this is the configuration you are looking for. <ItemGroup>

What's the right way to suppress EF warnings?

由 喜夏-厌秋 提交于 2020-05-08 06:36:31
问题 I would like to suppress these warnings but I could not figure out how to do it. 回答1: Those are not warnings you are seeing, those are Errors. The output tells you very clearly when a diagnostic message is a warning or an error. You've given the compiler an error number (6002) and told it to suppress the warning with that number, but such a warning does not exist. So, you've only succeeded in creating an additional error In this case, the message you're trying to suppress is a fatal compiler

What's the right way to suppress EF warnings?

由 喜夏-厌秋 提交于 2020-05-08 06:35:19
问题 I would like to suppress these warnings but I could not figure out how to do it. 回答1: Those are not warnings you are seeing, those are Errors. The output tells you very clearly when a diagnostic message is a warning or an error. You've given the compiler an error number (6002) and told it to suppress the warning with that number, but such a warning does not exist. So, you've only succeeded in creating an additional error In this case, the message you're trying to suppress is a fatal compiler

What's the right way to suppress EF warnings?

由 柔情痞子 提交于 2020-05-08 06:35:00
问题 I would like to suppress these warnings but I could not figure out how to do it. 回答1: Those are not warnings you are seeing, those are Errors. The output tells you very clearly when a diagnostic message is a warning or an error. You've given the compiler an error number (6002) and told it to suppress the warning with that number, but such a warning does not exist. So, you've only succeeded in creating an additional error In this case, the message you're trying to suppress is a fatal compiler

[CI&CD]jenkins自动化工具使用教程

由 一个人想着一个人 提交于 2020-05-08 03:25:58
自动化构建、测试、部署、代码检测越来越重要。主要有一下几点原因 1. 企业做大，项目变多，多端支持（ web ， h5 ，小程序等） 2. 微服务提倡高内聚低耦合，项目因拆分变多 3. DevOps 自动化运维流行 4. 集群化，高可用部署方案 5. 避免人工操作出现的错误 6. 集成管理系统，实现提交发布、发布审批、发布等 UI 可视化操作 等等原因，学习使用 jenkins 实现自动化作业非常有必要。这是我学习过程中整理的资料，分享给大家。 欢迎向我推荐更好的资料和讨论关于 jenkins 的问题。 目录 一、 安装 1) Jenkins 安装插件因网络问题报错处理方案 2) 如何将Jenkins 集成到其他系统 ... 3 二、 常见设置 ... 3 本节介绍jenkins常见设置，如中文、job变量使用、查看job历史执行变量、定时构建、清理历史构建等 三、 常用工具cli . 4 本节介绍：git、脚本（shell、bat、powershell），xcopy、7zip等工具 四、 安全设置 ... 5 本节介绍jenkins安全设置，用户权限管理 ... 5 五、 Dotnet 程序编译发布 六、 高可用 ... 7 本节介绍：jenkins master 高可用设计方案、jenkins配置备份、配置变更历史、站点应用备份回滚、监控方案 七、 文件传输 ... 7

.NET Core技术研究-通过Roslyn代码分析技术规范提升代码质量

由 家住魔仙堡 提交于 2020-05-07 16:21:26
随着团队越来越多，越来越大，需求更迭越来越快，每天提交的代码变更由原先的2位数，暴涨到3位数，每天几百次代码Check In，补丁提交，大量的代码审查消耗了大量的资源投入。 如何确保提交代码的质量和提测产品的质量，这两个是非常大的挑战。 工欲善其事，必先利其器。在上述需求背景下，今年我们准备用工具和技术，全面把控并提升代码质量和产品提测质量。即： 1. 代码质量提升： 通过自定义代码扫描规则，将有问题的代码、不符合编码规则的代码扫描出来，禁止签入 2. 产品提测质量： 通过单元测试覆盖率和执行通过率，严控产品提交质量，覆盖率和通过率达不到标准，无法提交测试。 准备用2篇文章，和大家分享我们是如何提升代码质量和产品提测质量的。今天分享第一篇：通过Roslyn代码分析全面提升代码质量。 一、什么是Roslyn Roslyn 是微软开源的 .NET 编译平台(.NET Compiler Platform)。 编译平台支持 C# 和 Visual Basic 代码编译，并提供丰富的代码分析 API。 利用Roslyn可以生成代码分析器和代码修补程序，从而发现和更正编码错误。 分析器不仅理解代码的语法和结构，还能检测应更正的做法。 代码修补程序建议一处或多处修复，以修复分析器发现的编码错误。 我们写下面一堆代码，Roslyn编译器会有如下提示： 通过编写分析器和代码修补程序，主要服务以下场景
订阅 msbuild