LAUNCHER_PATH: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe.LAUNCHER_ARGS: -debug -p "C:\Program Files\dotnet\dotnet.exe" -a "exec \"C:\Users\lextm\documents\visual studio 2017\Projects\WebApplication2\WebApplication2\bin\Debug\netcoreapp1.0\WebApplication2.dll\"" -pidFile "C:\Users\lextm\AppData\Local\Temp\2\tmpFD6D.tmp" -wd "C:\Users\lextm\documents\visual studio 2017\Projects\WebApplication2\WebApplication2".So Visual Studio silently adds the two environment variables when launching IIS Express, so that ASP.NET Core related bits can be injected, Figure 4: Process Explorer shows special environment variables. Hints only come if you ask Process Explorer, Figure 3: Process Explorer shows the special launcher. So what magic does Visual Studio use to launch the web app?
OK, can you follow them? Unfortunately, you cannot this time, as this project (from official template) has no web.config file at all, Figure 2: ASP.NET Core project folder (no `web.config` file). Should you ask Google, you will see tons of posts on them, and people suggest they be set in web.config file. So it seems that there are two environment variables missing. Application ‘MACHINE/WEBROOT/APPHOST/WEBAPPLICATION2’ with physical root ‘C:\Users\lextm\documents\visual studio 2017\Projects\WebApplication2\WebApplication2\’ failed to start process with commandline ‘“%LAUNCHER_PATH%” %LAUNCHER_ARGS%’, ErrorCode = ‘0x80070002 : 0.
0 kommentar(er)
