2

I've recently installed Visual Studio 2017 Professional and have just created the boilerplate ASP.NET Core Web Application

This is what happens when I hit Run (With IIS Express):

enter image description here

And this is what Visual Studio 2017's Output window says:

The program '[8260] dotnet.exe' has exited with code -2147450749 (0x80008083).

The program '[6476] iisexpress.exe' has exited with code 0 (0x0).

Steps to fix?

1

3 Answers 3

2

I think it's a bug as per Visual Studio 2017 Doesn't Run Core Apps with IIS Express.

And that the current status is fixed pending release: https://developercommunity.visualstudio.com/content/problem/11391/aspnet-core-iis-express-httplocalhost51733-failed.html

And that the workarounds meanwhile are probably:

  • dotnet run
  • Publish to local IIS. Which is working for me.
  • (Untested: downgrade from core-1.1 to core-1.0)

If you aren't familiar with VS2017/asp.net: You probably have the Debug toolbar visible which shows you a dropdown with a green arrow and 'IIS Express'. Click on that and you should see a 'Run {yourprojectname}' option. This is the equivalent of dotnet run {yourprojectname} from the commandline

Sign up to request clarification or add additional context in comments.

3 Comments

I tried running the project itself, rather than via IIS Express, but I still get the dotnet error.
If you cd to the project directory and do dotnet run do you see any more helpful error?
Or, having chosen 'Run {yourprojectname}' in the debugger toolbar, does it launch in debug? If so, it should break on exceptions and tell you waht the problem is
1

Okay, this worked for me: Install the x86 SDK...

https://www.microsoft.com/net/download/core

1 Comment

Installing x86 sdk made no difference to issue on hand in my case.
1

'The program '[8260] dotnet.exe' has exited with code -2147450749 (0x80008083).'

Could be a x86 x64 related thing. (Same for Console Core Apps)

If you have installed multiple versions of .NET Core like so: enter image description here

You need to set the order in the path environment variable:

enter image description here

So that the one you want to use appears first and then (re-)start Visual Studio. To check which dotnet is currently "active" run: dotnet --info in the console.

1 Comment

This solved my issue. I removed the (x86) version from my Path, restarted Visual Studio (to be sure) and then tried again. This time it ran the project fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.