违约的VS2015模板问题在于,汇编者是tfrin oslyn <>tfrin oslyn的目录,而是{outdir} oslyn的目录。

在你档案中添加这一法典:

<Target Name="CopyRoslynFiles" AfterTargets="AfterBuild" Condition="!$(Disable_CopyWebApplication) And  $(OutDir)  !=  $(OutputPath) ">
    <ItemGroup>
      <RoslynFiles Include="$(CscToolPath)*" />
    </ItemGroup>
    <MakeDir Directories="$(WebProjectOutputDir)in
oslyn" />
    <Copy SourceFiles="@(RoslynFiles)" DestinationFolder="$(WebProjectOutputDir)in
oslyn" SkipUnchangedFiles="true" Retries="$(CopyRetryCount)" RetryDelayMilliseconds="$(CopyRetryDelayMilliseconds)" />
</Target>

<>strong>TL;DR

在包裹管理员Console实施:

Update-Packagesoft.CodeDom.Providers.DotNetCompilerPlatform -

然后,我看上去了.csproj,并确保包裹的道路是正确的(就我的情况而言,是......包装* );在标签栏内,项目和设计;上和<代码>上;Target>,名称为“EnsureNuGetPackageBuildImports” 这一点载于MVC 5和NET Framework 4.5.2。

清洁和重建为我工作!

NOTE: If you are not interested in using Roslyn, follow this answer and remove it

www.un.org/spanish/ecosoc The Roslyn:

你的建筑试图找到<条形状>,因为以下包裹已添加到你的项目中。 仅审查<代码> 包装。 你们都可以在那里有两人。

Microsoft.CodeDom.Providers.DotNetCompilerPlatform
Microsoft.Net.Compilers

What is Roslyn and Who added them(packages) in the project : If you’re using .net Framework 4.5.2 to create projects using VS2015, you might have noticed that the project templates use Roslyn by default. Actually, Roslyn is one of open-source compilers for .NET languages from Microsoft.

Why should we delete Roslyn: If your project has Roslyn references and you are interested to deploy it on the server, you will get unwanted errors on the website as many hosting providers still have not upgraded their servers and hence do not support Roslyn. To resolve this issue, you will need to remove the Roslyn compiler from the project template.

www.un.org/spanish/ecosoc 如何消除:

1. Remove NuGet packages, use the following commands from Nuget Package Console

PM> Uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
PM> Uninstall-package Microsoft.Net.Compilers

2. After you do this, your web.config file should be auto-updated. In case it is not, look for the below code in web.config file and if it is found, delete this piece of code.

<system.codedom>
    <compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701"></compiler>
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+"></compiler>
    </compilers>
</system.codedom>

Too late for an answer but still posting incase it helps anyone.
Following the below steps fixed the error for me:

1. delete packages folder
2. open VS
3. rebuild
4. observe that NuGet packages are restored, but bin oslyn isnt created
5. unload project
6. reload project
7. rebuild
8. observe that the bin oslyn has been created now.

0. The quick fix

As already noted in the currently highest voted answer, the quick fix is to use the package manager, Tools > Nuget Package Manager > Package Manager Console, to run

Update-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform -r

Here is code that reproduces the error:
https://user.it.uu.se/%7Ehesc0353/SrvrErr-reproduce.zip
(Originally from https://github.com/aspnet/AspNetDocs/tree/master/aspnet/web-api/overview/advanced/calling-a-web-api-from-a-net-client/sample/server/ProductsApp)

Consider trying the example code provided in the zip file above.
If no changes are made, Ctrl+F5 will reproduce the error.

2. A more robust solution

An alternative solution is to remove an attribute from the project s Web.config file.
(Web.config is in the same directory as the .csproj file.)
This will automatically and silently recreate your packages if they are missing.

开放<代码>Web.config文档载于文字编辑或视力室。

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings></appSettings>
  ...
  <system.codedom>
    <compilers>
      <compiler language="c#;cs;csharp" extension=".cs"
        type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
        warningLevel="4" compilerOptions="/langversion:default /nowarn:1659;1699;1701"/>
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
        type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
        warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+"/>
    </compilers>
  </system.codedom>
</configuration>

In the tag configuration > system.codedom > compilers > compiler language="c#;cs;csharp", completely remove the type attribute. – In short, remove the line that starts with type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, . ¹

Visual Studio will take care of the rest. – No more Server Error in / Application.

3. HTTP Error 403

In the example provided above, hitting Ctrl+F5 will now result in an HTTP Error 403.

Try replacing http://localhost:64195 in your web browser with http://localhost:64195/api/products. The web API now displays correctly:

• 复制错误的项目档案

• 原始项目

如的Roslyn项目中所指出的,解决办法(为我工作)只是卸下,在视觉演播室重载该项目。

经过升级的<代码>Microsoft.CodeDom.Providers.DotNetCompilerPlatform从1.0.0到1.0.1对我作了规定。

If you were adding ASPNETCOMPILER to compile your Razor views in MVC, like in this StackOverflow question, then change PhysicalPath to place where Roslyn nuget package is located (usually pointed via $CscToolPath variable):

<Target Name="AfterBuild" Condition=" $(MvcBuildViews) == true ">
<AspNetCompiler VirtualPath="temp" PhysicalPath="$(CscToolPath)" />

In my case by just Deleting everything inside the bin folder and recompiling did all the work for me.

在我的案件中,与Basim相似,有一个NuGet包,告诉我们所需要的C# 6,我们这样做了。

We had to remove the NuGet package Microsoft.CodeDom.Providers.DotNetCompilerPlatform which then removed:

1. <package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="1.0.0" targetFramework="net452" /> from the packages.config file
2. <system.codedom> <compilers> <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701" /> <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+" /> </compilers> </system.codedom>

在<代码>系统中,编码 页: 1

开放项目档案和remove 所有与进口项目有关的参考资料=”。

Open web.config and remove all system.codedom compilers attributes

The problem with the default VS2015 templates is that the compiler isn t actually copied to the {outdir}_PublishedWebsites frin oslyn directory, but rather the {outdir} oslyn directory. This is likely different from your local environment since AppHarbor builds apps using an output directory instead of building the solution "in-place".

为加以确定,在以下各段的末尾添加以下内容:.csproj file right after xml/2005/4 <Target name=“EnsureNuGetPackageBuildImports” before Targets=“PrepareForBuild”>......</Target>

<PropertyGroup>
  <PostBuildEvent>
    if not exist "$(WebProjectOutputDir)inRoslyn" md "$(WebProjectOutputDir)inRoslyn"
    start /MIN xcopy /s /y /R "$(OutDir)roslyn*.*" "$(WebProjectOutputDir)inRoslyn"
  </PostBuildEvent>
</PropertyGroup>

参考:https://support.appharbor.com/discussions/problems/78633-cant-build-aspnet-mvc-project-generated-2015-