0

I have a REST-Webservice which I developed with Visual Studio 2015 as a "ASP.NET Core Web Application (.NET Core 1.X) → Web API (No Auth per Default)" application and later upgraded my project to Core 2.0 with the first supported VS2017 version. Everything was working fine.

Now I got a new computer and I installed the latest Visual Studio 2017 on my machine.

Before when I published the application I received lots of "Microsoft.AspNetCore...dll" stuff which is included in "Microsoft.AspNetCore.All":

Compiledstuff

...more...

enter image description here

That's running great on my IIS webserver!

Now, with VS2017 the published stuff looks totally different:

enter image description here

When publishing that stuff I have more options, but none of that stuff is working. Publish configuration (Filesystem):

  • Targetframework: netcoreapp2.0
  • Framework dependant (theoretically I prefer this)
  • Standalone (this export way more dll's but is not working)
  • Portable/win-x86/win-x64
  • I tried all combinations, but none of this is working.

Of course I've installed "DotNetCore.2.0.7-WindowsHosting.exe" on the server.

This is the page I am getting in IIS as a result.

enter image description here

I also created a new empty "ASP.NET Core Web Application (.NET Core 2.0)" project with a hello-world site. Even this page is not running on my IIS and shows the same error.

What am I doing wrong and how can I get a result like in VS2015 which was running perfectly good?

Any help is welcome! Thanks!

Stix
  • 455
  • 5
  • 16
  • There is no .NET Core support (officially) in VS2015. Get started from an empty VS2017 project. – Lex Li May 28 '18 at 14:54
  • Oh. You are right. I forgot, that I started with a Core 1.X project and upgraded to the first supported VS2017 version by Core 2.0. Now I do have the latest VS2017 IDE and no publish-able result. I'll correct my question. – Stix May 28 '18 at 19:16
  • 1
    Please carefully update the question to match your situation. Then see if you happen to hit the same issue Microsoft created recently https://stackoverflow.com/questions/50567448/asp-net-core-deployment-persistent-errorcode-0x80004005-8000808c-on-win-20?noredirect=1#comment88149069_50567448 – Lex Li May 28 '18 at 19:18
  • @LexLi updated. – Stix May 28 '18 at 19:20
  • Then you hit exactly the issue I linked I think. – Lex Li May 28 '18 at 19:28
  • @LexLi Tomorrow I'll try to download all the stuff from microsoft again, like in the other question. Otherwise I'll downgrade Core to 2.0.6 and try that. – Stix May 28 '18 at 20:00
  • @LexLi Thanks already. I'll let you know tomorrow if that helped. – Stix May 28 '18 at 20:01
  • You are writing "You probably used Framework Dependent Deployment, instead of Self Contained Deployment, which also amplifies the issue." in the other question. I already tried the Self-Contained-Solution on my webserver which fails with the exact same result. – Stix May 29 '18 at 14:07
  • Great! Installing "AspNetCore.2.0.8.RuntimePackageStore_x64.exe" from "https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.200-sdk-download.md" like you mentioned in the other question was the solution. I can't under stand why the did not officially release all installers in a version 2.0.8. Even the excuse "the versions are independent from each other" is in my opinion absolutely nonsense! Thanks a lot! – Stix May 30 '18 at 09:12
  • Seems like Microsoft just updated that stuff: https://www.microsoft.com/net/download/windows – Stix May 30 '18 at 14:49
  • Yep. That's a move on the right direction. – Lex Li May 30 '18 at 14:50
  • Even better: Now 2.1 is out. ;-) – Stix Jun 04 '18 at 09:28

0 Answers0