asp.net – MVC应用程序构建速度极慢
发布时间:2020-12-16 03:43:39 所属栏目:asp.Net 来源:网络整理
导读:我正在开发Visual Studio MVC-4项目.构建解决方案大约需要2分钟,这没有任何意义.这是一个包含5个项目的小型解决方案,每个项目中的文件很少(少于几百个).为了进行比较,我们有一个项目大小是该项目(Web表单)的10-15倍,在我的计算机上构建不到3秒. 我听说我们从
我正在开发Visual Studio MVC-4项目.构建解决方案大约需要2分钟,这没有任何意义.这是一个包含5个项目的小型解决方案,每个项目中的文件很少(少于几百个).为了进行比较,我们有一个项目大小是该项目(Web表单)的10-15倍,在我的计算机上构建不到3秒.
我听说我们从MVC2迁移到MVC4,团队记得迁移前解决方案要快得多,但他们无法完全记住它. 它不仅在我的计算机上,而且在团队中的其他计算机上.我很确定它在某种程度上是在解决方案文件中. 我们只有1个帖子构建事件,它没有效果删除它. 关于该怎么做的任何想法? 我试过了什么 符号: 我在这里读了一篇关于设置符号以在本地而不是服务器上运行的帖子.我做到了: 启用“只是我的代码” 删除临时文件夹 删除了计算机上所有不同的临时文件夹. 解决方案文件 Microsoft Visual Studio Solution File,Format Version 12.00 # Visual Studio 2012 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Data","Data","{C337490A-F7A8-4800-9BD3-668F5231AE2D}" EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Web","Web","{58E3725E-75D2-4AB0-A693-D482152A28E5}" EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Business","Business","{8999D8ED-77FD-42F4-A11A-F6F3B4224A41}" EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items","Solution Items","{C1BC5D04-B71F-4E66-9C2F-352ED8A0AF84}" ProjectSection(SolutionItems) = preProject Saxo.Application.Publish.build = Saxo.Application.Publish.build EndProjectSection EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Database","Database","{8F63871C-600E-49E5-9858-D3023485CD06}" EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Changescripts","Changescripts","{B3F72D6C-35EF-4D82-ACB9-5DCAE8F0BCA1}" ProjectSection(SolutionItems) = preProject 30042013-DescriptionNotNull.sql = 30042013-DescriptionNotNull.sql AlterContentTextsAddAllowHtml.txt = AlterContentTextsAddAllowHtml.txt AlterInvoiceAccountsAddVismaSupplierId.sql = AlterInvoiceAccountsAddVismaSupplierId.sql AlterProjectsAddCategorySelfPublisher.sql = AlterProjectsAddCategorySelfPublisher.sql EndProjectSection EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SOMENAME","SOMENAME","{903F385F-C309-4189-BE1C-1598BEF9FBE6}" EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SOMENAME","{797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}" EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SOMENAME","{BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}" EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SOMENAME","{EA172A15-6AE4-4358-8DB9-B75F6CC20458}" EndProject Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Tests","Tests","{5E4C1C3C-AB57-49E6-8C7B-1E69CD3FBF67}" EndProject Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SOMENAME","{97B74D41-8B99-4782-9B64-60BA180ED667}" EndProject Global GlobalSection(SolutionConfigurationPlatforms) = preSolution Debug|Any CPU = Debug|Any CPU Debug|Mixed Platforms = Debug|Mixed Platforms Debug|x86 = Debug|x86 Release|Any CPU = Release|Any CPU Release|Mixed Platforms = Release|Mixed Platforms Release|x86 = Release|x86 EndGlobalSection GlobalSection(ProjectConfigurationPlatforms) = postSolution {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Debug|Any CPU.Build.0 = Debug|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Debug|Mixed Platforms.ActiveCfg = Debug|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Debug|x86.ActiveCfg = Debug|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Release|Any CPU.ActiveCfg = Release|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Release|Any CPU.Build.0 = Release|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Release|Mixed Platforms.ActiveCfg = Release|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Release|Mixed Platforms.Build.0 = Release|Any CPU {903F385F-C309-4189-BE1C-1598BEF9FBE6}.Release|x86.ActiveCfg = Release|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Debug|Any CPU.Build.0 = Debug|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Debug|Mixed Platforms.ActiveCfg = Debug|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Debug|x86.ActiveCfg = Debug|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Release|Any CPU.ActiveCfg = Release|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Release|Any CPU.Build.0 = Release|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Release|Mixed Platforms.ActiveCfg = Release|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Release|Mixed Platforms.Build.0 = Release|Any CPU {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85}.Release|x86.ActiveCfg = Release|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Debug|Any CPU.Build.0 = Debug|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Debug|Mixed Platforms.ActiveCfg = Debug|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Debug|x86.ActiveCfg = Debug|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Release|Any CPU.ActiveCfg = Release|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Release|Any CPU.Build.0 = Release|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Release|Mixed Platforms.ActiveCfg = Release|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Release|Mixed Platforms.Build.0 = Release|Any CPU {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8}.Release|x86.ActiveCfg = Release|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Debug|Any CPU.Build.0 = Debug|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Debug|Mixed Platforms.ActiveCfg = Debug|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Debug|x86.ActiveCfg = Debug|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Release|Any CPU.ActiveCfg = Release|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Release|Any CPU.Build.0 = Release|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Release|Mixed Platforms.ActiveCfg = Release|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Release|Mixed Platforms.Build.0 = Release|Any CPU {EA172A15-6AE4-4358-8DB9-B75F6CC20458}.Release|x86.ActiveCfg = Release|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Debug|Any CPU.Build.0 = Debug|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Debug|Mixed Platforms.ActiveCfg = Debug|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Debug|Mixed Platforms.Build.0 = Debug|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Debug|x86.ActiveCfg = Debug|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Release|Any CPU.ActiveCfg = Release|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Release|Any CPU.Build.0 = Release|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Release|Mixed Platforms.ActiveCfg = Release|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Release|Mixed Platforms.Build.0 = Release|Any CPU {97B74D41-8B99-4782-9B64-60BA180ED667}.Release|x86.ActiveCfg = Release|Any CPU EndGlobalSection GlobalSection(SolutionProperties) = preSolution HideSolutionNode = FALSE EndGlobalSection GlobalSection(NestedProjects) = preSolution {BA8847A7-5EFB-4E1B-A689-4BBC4B6183D8} = {C337490A-F7A8-4800-9BD3-668F5231AE2D} {903F385F-C309-4189-BE1C-1598BEF9FBE6} = {58E3725E-75D2-4AB0-A693-D482152A28E5} {797DCD60-C9C4-4AB4-98FE-2CBB02AA4A85} = {8999D8ED-77FD-42F4-A11A-F6F3B4224A41} {EA172A15-6AE4-4358-8DB9-B75F6CC20458} = {8999D8ED-77FD-42F4-A11A-F6F3B4224A41} {B3F72D6C-35EF-4D82-ACB9-5DCAE8F0BCA1} = {8F63871C-600E-49E5-9858-D3023485CD06} {97B74D41-8B99-4782-9B64-60BA180ED667} = {5E4C1C3C-AB57-49E6-8C7B-1E69CD3FBF67} EndGlobalSection EndGlobal 流程监控 我已经运行了进程监视器,只看了cnc.exe.这是我的结果: 似乎以下记录一次又一次地运行. 解决方法
编译时间太长的一个可能原因是你有< MvcBuildViews>设置为true,这将编译您的视图并提醒您视图中的任何语法错误.因为您可以拥有大量视图,所以此过程可以显着延长构建时间(分钟与秒).
Here is a link to a site将解释如何关闭/打开MvcBuildViews属性.如果站点出现故障,您基本上将以下行添加到解决方案文件中:
启用 <MvcBuildViews>true</MvcBuildViews> 要禁用 <MvcBuildViews>false</MvcBuildViews> 然而(自以为是的dia骂)我不同意你何时应该使用这个功能.他声明你应该只为Release / Production启用这个属性,而我认为你应该只为Debug配置启用它.大多数开发人员将在Debug中完全测试他们的Web应用程序,然后才切换到Release和push.为什么你不想在调试模式下进行编译时检查你正在做什么…调试和检查错误/错误? (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |
相关内容
- 使用ASP.Net MVC3中的jQuery动态填充下拉列表
- asp.net-core – 重置实体框架7迁移
- asp.net – 如何将模型从一个局部视图传递到另一个局部视图
- asp.net-mvc – ASP.NET MVC 4重定向回索引视图
- asp.net – 通过javascript禁止文本框中的退格
- asp.net – 在PreRender上添加控件页面
- IE不保存asp.net身份验证令牌/ cookie
- ASP.net检查页面是http还是https
- asp.net-mvc – 如何让routelink返回正确的URL?
- asp.net – 为什么Visual Studio会拒绝访问,尝试使用NuGet软
推荐文章
站长推荐
- asp.net – 什么是Container.DataItem?
- asp.net – 尝试通过IP地址保护文件夹中的所有as
- asp.net – 如何将onchange事件附加到CheckBoxLi
- asp.net – 如何在Kestrel响应中添加no-cache?
- asp.net – “SELECT * FROM …”VS“SELECT ID
- asp.net-mvc – Globalize.addCultureInfo不是一
- asp.net – 无法将许可证文件转换为二进制资源
- asp.net – 如何在捕获httpwebrequest超时后关闭
- ASP.NET MVC真正注销表单身份验证
- 处理大量的后期变量ASP.Net
热点阅读