Closed gkhanna79 closed 4 years ago
@karelz @danmosemsft @weshaggard PTAL
@gkhanna79 thank you for porting it in the right spot. Any info needed or any help to clear things up on my end I am happy to jump right on it.
I just wanted to report back, I switched to just using the net452
framework for the moment and dropped "Novell.Directory.Ldap.NETStandard": "2.3.6"
. I am working on the POC for the project so dropping LDAP out for the moment is ok. I figured I would share this news in case it helps.
note: I used the templates on a new project and didn't update them, only added the needed items
{
"userSecretsId": "aspnet-fais.printing_services-6f6dbf21-da98-45d2-a187-08ae49d09d62",
"dependencies": {
"Microsoft.ApplicationInsights.AspNetCore": "1.0.0",
"Microsoft.AspNetCore.Authentication.Cookies": "1.0.0",
"Microsoft.AspNetCore.Diagnostics": "1.0.0",
"Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore": "1.0.0",
"Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.0.0",
"Microsoft.AspNetCore.Mvc": "1.0.1",
"Microsoft.AspNetCore.Razor.Tools": {
"version": "1.0.0-preview2-final",
"type": "build"
},
"Microsoft.AspNetCore.Routing": "1.0.1",
"Microsoft.AspNetCore.Server.IISIntegration": "1.0.0",
"Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
"Microsoft.AspNetCore.StaticFiles": "1.0.0",
"Microsoft.EntityFrameworkCore.SqlServer": "1.0.1",
"Microsoft.EntityFrameworkCore.SqlServer.Design": {
"version": "1.0.1",
"type": "build"
},
"Microsoft.EntityFrameworkCore.Tools": {
"version": "1.0.0-preview2-final",
"type": "build"
},
"Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0",
"Microsoft.Extensions.Configuration.Json": "1.0.0",
"Microsoft.Extensions.Configuration.UserSecrets": "1.0.0",
"Microsoft.Extensions.Logging": "1.0.0",
"Microsoft.Extensions.Logging.Console": "1.0.0",
"Microsoft.Extensions.Logging.Debug": "1.0.0",
"Microsoft.Extensions.Options.ConfigurationExtensions": "1.0.0",
"Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0",
"Microsoft.VisualStudio.Web.CodeGeneration.Tools": {
"version": "1.0.0-preview2-final",
"type": "build"
},
"Microsoft.VisualStudio.Web.CodeGenerators.Mvc": {
"version": "1.0.0-preview2-final",
"type": "build"
},
//"Microsoft.NETCore.Portable.Compatibility": "1.0.1-rc2-24027",
//POC needed items
"Microsoft.AspNetCore.ResponseCompression": "1.0.1",
"Microsoft.AspNetCore.Cors": "1.1.1",
"DataTables.AspNet.AspNetCore": "2.0.2",
"hiqpdf": "10.6.0",
//"Novell.Directory.Ldap.NETStandard": "2.3.6"
},
"tools": {
"BundlerMinifier.Core": "2.0.238",
"Microsoft.AspNetCore.Razor.Tools": "1.0.0-preview2-final",
"Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final",
"Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview2-final",
"Microsoft.Extensions.SecretManager.Tools": "1.0.0-preview2-final",
"Microsoft.VisualStudio.Web.CodeGeneration.Tools": {
"version": "1.0.0-preview2-final",
"imports": [
"portable-net45+win8"
]
}
},
"frameworks": {
"net452": {}
},
"buildOptions": {
"emitEntryPoint": true,
"preserveCompilationContext": true
},
"runtimeOptions": {
"configProperties": {
"System.GC.Server": true
}
},
"publishOptions": {
"exclude": [
"wwwroot/prints",
"node_modules"
],
"include": [
"wwwroot",
"**/*.cshtml",
"appsettings.json",
"web.config"
]
},
"runtimes": {
"win10-x64": {}
},
"scripts": {
"prepublish": [ "bower install", "dotnet bundle" ],
"postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
}
}
Looks potentially related to https://github.com/dotnet/corefx/issues/16322.
CC: @mellinoe @ericstj
FWIW, I'm seeing something similar to this when using Roslyn 2.0.0 from within an MSBuild task (the fact that's it's an MSBuild task is probably not germaine, other than that it makes diagnosing the binding problems harder).
I've tried every combination of binding redirects I can think of without luck. I've also tried installing System.IO.FileSystem 4.3.0 directly into the MSBuild task project without any change.
Note that while the example below was created for use in a test, I'm not running it through the unit testing framework here - this is directly calling MSBuild on the test solution from the console to eliminate the unit test framework as a source of problems.
Update: I've been able to work past my particular problem by doing an xcopy of all netstandard libraries required by Roslyn into the MSBuild task project output folder. That suggests this problem may have been related to the binder not being able to find them from the test assembly location. At this point probably not totally related to this issue (other than these assemblies have conflicts in the first place).
I'm closing this as a duplicate of dotnet/runtime#20284.
cc: @karelz another binding-redirects related issue.
@jeremyBass commented on Thu Mar 09 2017
I hope this is the right place for this issue. I have been betting my head on the wall on this.
I will say that I have this on stackoverflow as well, but believe it may be helpful to have it logged here. I realize there are a few other issues that seem related, but they are not 100% the same and I got no traction on a fix/workaround.
I keep getting this error on the server
I have done ever trick I can think of, followed all the newest issues to resolve with no luck. Here is my project file:
So the reason for
.net4.6.1
ishiqpdf
, it is the only thing that is really the reason i had to load it.My app runs on IISExpress, but as soon as i publish it to the IIS box it gets as
HTTP Error 502.5 - Process Failure
. I run the exe in the command prompt as Microsoft asks as got what i put up here.I keep thinking i just have to move the right item in place and it will work on the server. What is the difference? Why does it would great locally but falls on it's face on the server? Can i include System.IO.FileSystem at a version that will fix this? (which i have tried and failed to).
I know the project.json file needs some clean up again, but it is working in one spot so i figured I would keep it here.
Server Details:
Other information I figured it would be worth noting thing i have done that wouldn't be known from this:
System.IO.File
directly at v.4.3.0
but it downgrades to4.0.0.1
I believe.