Hosting in IIS 8 (on an Azure VM) #452
I'm setting up a vNext app server-side (IIS 8 on an Azure VM WS2012):
I setup the path to the site trying both wwwroot and the parent of wwwroot; but when I browse the site, I'm getting 403: Forbidden either way ... what am I missing?
Also, what's the AppPool for these? ... should it be "No Managed Code"
Are there any Advanced Settings for the AppPool that I need to deal with?
... and I should add that this is a CoreCLR app. I'm interested in setting up IIS 8 without having to use .NET Framework 4.5.1, as the Minimum Requirements call for ... if that's possible.
... and the 403 is not a general folder permissions issue. I have a test.htm file in wwwroot, and that page loads just fine. It's when I browse the MVC portion of the app that the 403 is triggered.
First issue (probably) solved. Adding
Next issue encountered:
I thought with CoreCLR and
Am I missing values here for the CLR and it's version?
... if so, how are these to be populated? manually?
You need to install ASP.NET on the server. Helios requires ASP.NET >= 4.5.1 even if you wan to run CoreCLR apps on IIS today.
Is talking about the runtime itself (dnx/xre/kre), not the application's packages. Did you include the
I had 4.5.2 on that VM, so I was good there. YES! Thanks @davidfowl ... That got it. It's probably best if I put my steps here for anyone else doing this. There were a few "gotchas" to watch out for:
Note that I'm using nightly builds ... in Adobe Brackets. Therefore, "publishing" was done by manually copying the contents of my
--> Indeed, you do need >= 4.5.1 installed on the server. If it's not installed (and it might not be on a WS2012 (not R2) VM, use the Web Platform Installer to get it.
Note that on WS2012 (not R2) that your sites/app pools will say that they are using .NET Framework v4.0.30319 even when 4.5.x is installed and is the framework in use. Turns out that 4.5.x is an in-place upgrade on WS2012/IIS 8, and 4.5.x will not appear in any dropdown for setting the framework version. Apparently, on WS2012 R2, which came with 4.5.x out-of-the-box, you will see 4.5.x listed and it will show up in dropdowns in IIS 8.5.
If you still have issues, make sure that you go through server
--> Make sure you have
--> Of course, do a
--> Go for a
--> Setup your IIS website the way you normally would with a
Note that some SO answers talk about permissions issues and adding
--> If you are using a 32-bit CLR, go to the
I'm definitely not an IIS expert, so please anyone jump in and correct me or add anything else that I missed.
CORRECTION: Update to the WebDeploy command that I provided above.
When you run WebDeploy from the command line to publish the app to your VM, you might try providing the IIS website name as I showed above for the
... but that's not going to work. The result of this is that the folders
The way to make it work is to specify the destination explicitly in the WebDeploy command, like this:
... note that the destination path for