dotnet-installer/TestAssets/TestProjects/AppWithNet46AndRoslyn/project.json

{
  "buildOptions": {
    "emitEntryPoint": true
  },
  "dependencies": {
    "Microsoft.CodeAnalysis.CSharp": "1.3.0-beta1-20160525-03"
  },
  "frameworks": {
    "net46": { }
  }
}
dotnet build raises errors MVC apps target net46. The issue is when the ProjectContextBuilder sees a CompileTimePlaceholder "_._" file on a full framework, it assumes that dependency has to come from the "Reference Assemblies" directory. If it can't be found there, an error is raised. However, there are other reasons "_._" placeholders are created (when a NuGet package doesn't want its dependencies to be exposed in the Compile dependencies of its consumers). And these placeholders can exist for assemblies that aren't in the full framework - in this case System.Diagnostics.FileVersionInfo and others. To fix this, if the reference can't be resolved from the "Reference Assemblies" folder, it is just skipped. If the compiler really needs that assembly, it will raise an error to the user. Dotnet build shouldn't raise the error. Fix #2906 2016-05-06 19:32:50 +00:00			`{`
			`"buildOptions": {`
			`"emitEntryPoint": true`
			`},`
			`"dependencies": {`
Update Roslyn to beta1-20160525-03. 2016-05-26 18:13:24 +00:00			`"Microsoft.CodeAnalysis.CSharp": "1.3.0-beta1-20160525-03"`
dotnet build raises errors MVC apps target net46. The issue is when the ProjectContextBuilder sees a CompileTimePlaceholder "_._" file on a full framework, it assumes that dependency has to come from the "Reference Assemblies" directory. If it can't be found there, an error is raised. However, there are other reasons "_._" placeholders are created (when a NuGet package doesn't want its dependencies to be exposed in the Compile dependencies of its consumers). And these placeholders can exist for assemblies that aren't in the full framework - in this case System.Diagnostics.FileVersionInfo and others. To fix this, if the reference can't be resolved from the "Reference Assemblies" folder, it is just skipped. If the compiler really needs that assembly, it will raise an error to the user. Dotnet build shouldn't raise the error. Fix #2906 2016-05-06 19:32:50 +00:00			`},`
			`"frameworks": {`
			`"net46": { }`
			`}`
			`}`