4

I am attempting to deploy an ASPNET vNext site onto IIS 8.

The site works wonderfully in development - I can run it using "web" or IISExpress and it builds for all runtime types (coreclr and clr). I can also run the same site on my Mac as well.

However, when I deploy it to IIS, as soon as I attempt to hit the site, I receive a 500 error. The steps I am following to deploy:

  1. Publish the site to local disk. I go through Visual Studio to do so. Again, if I run the "web.bat" file that is created as part of the publishing, it works fine (while on that machine).
  2. I then copy the published files to my IIS host.
  3. I point the website to the "wwwroot" folder. (This is next to the approot folder.) I believe this works to a point because, I once forgot to copy over the approot, and I at least received an error about it. So...something is happening.
  4. I then attempt to hit the URL...and I get a 500.

I have ASP.NET 4.5.2 installed. IIS does have ASP.NET 4.5 + Extensions installed as a feature. When I threw in a quick Index.html page into my web endpoint, it did display, so I believe IIS is at least hosting up information.

I have provided some links to information that I have been able to find on the issue. Nothing has worked so far and it's rather frustrating. I would appreciate any pointing in the correct direction.

Community
  • 1
  • 1
JasCav
  • 34,458
  • 20
  • 113
  • 170
  • Can you find and type the excactly error messages you get from the iis ? http://stackoverflow.com/questions/5385714/deploying-website-500-internal-server-error/5385884#5385884 – Aristos Aug 04 '15 at 22:45
  • This did it, @Aristos! I hadn't known about some of those extra parameters for getting the full error message. Looks like I needed to deploy the coreclr and not the clr. Thanks so much! – JasCav Aug 05 '15 at 03:27
  • You are welcome - if you bealive that this can help give an answer to your question and explain your steps you did to solve it. – Aristos Aug 05 '15 at 07:26

1 Answers1

0

Leveraging the additional information that Aristos provided from this answer, I was able to get better error messages from IIS. Ultimately, I learned that I needed to deploy the coreclr and not the clr with my application.

However, over time, I ended up not using IIS at all as Kestrel was better/easier for this particular situation (and a heck of a lot easier to manage).

Community
  • 1
  • 1
JasCav
  • 34,458
  • 20
  • 113
  • 170