iis-express-10

Windows Authentication doesn't work with IIS Express 10

荒凉一梦 提交于 2019-12-24 01:24:21
问题 At work we were forced into a hardware refresh where we went from a Windows 7 box with VS 2013 and IIS Express 6 to a Windows 10 box with VS 2017 and IIS Express 10. The problem is that Windows Authentication refuses to work. I get a 401.2 - Unauthorized with the explanation of "Invalid Authentication Headers". I've checked the web.config and the properties for the web project and they are correct. I've modified the applicationhost.config file in the .vs folder in the project to enable

Dotnet Core Multiple Startup Classes with In-Process Hosting

佐手、 提交于 2019-12-12 08:24:27
问题 I have a dotnet core v.2.1 application that utilizes the "startup-class-by-environment-name-convention" to use different Startup classes for different environment, e.g. development, staging and production. The Program.Main.CreateWebHost method looks similar to this: public static IWebHostBuilder CreateWebHostBuilder(string[] args) { var startupAssembly = Assembly.GetExecutingAssembly(); var webHostBuilder = WebHost.CreateDefaultBuilder(args) .UseStartup(startupAssembly.FullName); return

VS2017 in Windows 7 “An error occured attempting to determine the process id of dotnet.exe”

被刻印的时光 ゝ 提交于 2019-12-07 17:18:57
问题 Project properties -> Enable SSL : false (Off) Selected "IIS Express" as debug option "IIS 10.0 Express" already installed Getting below error always Can any one suggest a fix ? Already tried below URLs, no hope still An error occurred attempting to determine the process id of dotnet.exe which is hosting your application. One or more error occured https://stackoverflow.com/a/43351447/2089963 Also tried uninstalling & installed IIS Express 10 back. Any help? Environment : Windows 7(x64) Visual

Dotnet Core Multiple Startup Classes with In-Process Hosting

不打扰是莪最后的温柔 提交于 2019-12-04 00:53:03
I have a dotnet core v.2.1 application that utilizes the "startup-class-by-environment-name-convention" to use different Startup classes for different environment, e.g. development, staging and production. The Program.Main.CreateWebHost method looks similar to this: public static IWebHostBuilder CreateWebHostBuilder(string[] args) { var startupAssembly = Assembly.GetExecutingAssembly(); var webHostBuilder = WebHost.CreateDefaultBuilder(args) .UseStartup(startupAssembly.FullName); return webHostBuilder; } However, after upgrading to dotnet core v.2.2 (and the startup-switching still works great