Last post Jun 03, 2020 12:19 PM by Chevy Marl Sunderland
Jun 01, 2020 04:25 PM|Chevy Marl Sunderland|LINK
I have successfully completed my first project in an ASP.NET Core application using Connector/NET Core to explore the possibility to run this application on any .NET Core
This is the tutorial
This project work correctly on http://localhost:XXXX/Tablename
Now I need publish the project on the windows server 2008 for sharing on the web this work
windows server 2008
On the server I have installed dotnet-sdk-3.1.300-win-x64.exe
I have copied the folder and file from project local to remote server c:\inetpub\wwwroot\aspnetcore\mvccore
but if get on the browser the link http://mywebsite/aspnetcore/mvccore/views/tablename/Index.cshtml the return is page
isn't copying the local file and folders on the server enough for the project to work?
I am server administrator... maybe do I have to configure IIS?
can the new configuration create problems to the existing one on IIS?
how to do resolve this?
can you help me, please?
Jun 01, 2020 08:17 PM|bruce (sqlwork.com)|LINK
read the documentation:
you need to instal the aspnet core hosting module. then correctly configure IIS as per the documentation.
Jun 01, 2020 08:56 PM|Chevy Marl Sunderland|LINK
I need publish this project on Windows Server 2008 R2 SP2
According to this guide Host ASP.NET Core on Windows with IIS only Windows Server 2012 and later is supported
for hosting .net core applications on IIS
I have setting my project for run on dotnet-sdk-2.2.207-win-x64.exe for Windows Server 2008 R2 SP2
Windows Server 2008 R2 SP2
How to do for run on IIS 7?
I have to install dotnet-sdk-2.2.207-win-x64.exe on the server or it is enough dotnet-sdk-3.1.300-win-x64.exe?
Any suggestion, please?
I don’t understand because not error when installing dotnet-sdk-3.1.300-win-x64.exe on Windows Server 2008 R2 SP2 … if only
`Windows Server 2012` and later is supported for hosting
`.net core` applications on `IIS`
Windows Server 2008 R2 SP2
Jun 01, 2020 09:34 PM|bruce (sqlwork.com)|LINK
windows 2008 does not support AspNetCore core module 2.0. you must use the asp core module for 2.1 and config as reverse proxy. create an asp.net core 2.1 project t get a sample web.config settings for the core module to use with your 3.1 project.
on the windows server you will need to install asp.net 2.1 core runtime and asp.net core 3.1 runtime. you will need to install aspnet core module 1.0 (designed for 2.1).
you will need to create an unmanaged app pool, and assign to application in IIS. follow direction on this page:
note: I don't know if the core module v1 supports 3.1, you all need to try it. if not you will either
1) fall back asp.net core 2.1 (the supported 2.0 version)
2) manually configure IIS as a reverse proxy, and install your asp.net core 3.1 app as a service that IIS can reverse proxy to.
Jun 02, 2020 06:48 AM|Chevy Marl Sunderland|LINK
but manually configure IIS as a reverse proxy won't the other web applications developed in ASP NET C # work anymore?
I have setting my project for run on .NET Core 2.2 Framework destination
do I have to rewrite the project for .NET Core 2.2 or is that enough?
Jun 02, 2020 05:31 PM|Chevy Marl Sunderland|LINK
I had IIS 7 installed on server.
I installed .Net 4.8 and asp.net 2.1 core runtime and asp.net core 3.1 runtime on the server 2008 R2 SP2
I copied the folder contiaining my published Web site to \inetpub\wwwroot on the server.
With this post I configured MVC website in IIS.
But on the server the return is
What do I do to give the Web site a URL and otherwise make it active as a Web site?
Maybe I have to install more on the server?
Moreover, the .cshtml pages don't work on the server 2008 R2...
could you help me please?
Jun 02, 2020 10:26 PM|bruce (sqlwork.com)|LINK
what your did all not work. for IIS to host asp.net core, you need to install the AspNetCore hosting bundle from 2.1 download page:
then follow the directions on this page:
the alternative to the hosting module is to reverse proxy from IIS. you install the IIS RR module . then you create a vdir and configure the vdir for reverse proxy to your standalone asp.net core app, which you installed as a service.
if your asp.net core is the only website on the server, then it can use port 80 / 443 and IIS is not required.
Jun 03, 2020 10:11 AM|Chevy Marl Sunderland|LINK
Really appreciated your help but I can't solve it
Installed on the server
Jun 03, 2020 10:24 AM|mgebhard|LINK
The site is not deployed correctly. Use Visual Studio to publish the application to a folder on your development machine. Copy the contents of the folder to the web server.
Jun 03, 2020 12:19 PM|Chevy Marl Sunderland|LINK
it finally worked thanks to everyone for the support and help