Last post Oct 18, 2017 03:58 PM by Solitonman
Oct 16, 2017 04:58 PM|SolitonMan|LINK
I'm having a problem with publishing my projects from VS2017. Everything was working well until I updated to netcoreapp2.0. I had only started with ASP.NET this year, and my first web application worked fine. I published to a web server using web deploy
and the application is running fine in both development and production modes.
I wanted to include email messaging for my next project so I updated to netcoreapp2.0 because my understanding is that the System.Net.Mail isn't available in 1.1. I built my application to the point of testing, everything was running well and working fine
when I launched the application from VS2017. Then went to deploy it to IIS, and that's where everything fell apart.
I cannot get any detail on why I keep seeing the configuration message. No error logs are being created. I've deployed locally (windows 10, iis 10) to no avail. Today I tried to look at my original application (that works when published) and that gives
me the same problem when I deploy it to my local IIS instance.
Any ideas here? My boss is starting to wonder if I know what I'm doing, and really, so am I. My web.config file is pretty simple:
<?xml version="1.0" encoding="utf-8"?>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
<aspNetCore processPath="dotnet" arguments=".\PersonnelManagement.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
I can't get past this issue, I've configured permissions to ensure the account being used to run the application has folder permissions to the physical path for the files in IIS. Without any further messages or detail I have no idea of how to proceed to
fix this. ANY help or insight would be greatly appreciated. Thanks!!
Oct 17, 2017 08:58 AM|Edward Z|LINK
Based on the error message, it seems there is something wrong in your web.config.
>> so I updated to netcoreapp2.0 because my understanding is that the System.Net.Mail isn't available in 1.1. built my application to the point of testing, everything was running well and working fine when I launched the application from VS2017. Then went
to deploy it to IIS, and that's where everything fell apart.
Do you mean you upgrade project from Core 1.1 to Core 2.0? It works at local and fail to run after deploying to IIS?
To check whether it is related with your current project, I suggest you create a new Core 2.0 project, and then deploy it to IIS, will you receive the same error?
What is the function do you use with web.config? In my option, there is no web.config for built-in Core 2.0 project.
Oct 17, 2017 12:57 PM|SolitonMan|LINK
Thanks for your reply! I had come to the same conclusion about testing, and decided to try a very limited item to test.
In my original post, I did not upgrade a Core 1.1 to a Core 2.0 project. I have a project that I've published (and it's working) with Core 1.1. After that project was published I had upgraded my system to include the Core 2.0 items, and my next project
I chose 2.0 as the basis. That is the project that failed. And now when I publish my 1.1 project to a local instance of IIS (not Express) it too fails to publish.
Just prior to replying here, I had tried to do the simplest test I could imagine. I created a new ASP.NET Web Application with C#, and I chose the MVC option for a template. When the project was created I hit CTRL+F5 to run it, and it ran fine out of Visual
Studio. So I published it to my local IIS instance and it failed just as the other projects have. The only difference I can see in web.config is that the DLL it's pointing to is different; otherwise it's identical to that in my OP.
Maybe I can try to run a different project on another machine. As it is I have no idea why this should fail out of the box. I'm guessing there's something wrong with my installation somewhere, but I've got no clue where to look.
Oct 18, 2017 05:08 AM|Edward Z|LINK
>> So I published it to my local IIS instance and it failed just as the other projects have.
Do you mean all projects are failed after publishing to IIS?
>> Maybe I can try to run a different project on another machine.
What is the result that deploy projects to another machine?
Could you share us how you deploy the projects?
It would be helpful if you could upload your demo project, and then we will try to follow your steps to try to reproduce your issue.
Oct 18, 2017 03:58 PM|SolitonMan|LINK
Thanks for the response Edward. I've spent all of yesterday and most of today on this, and I've found that there appears to be a problem with my local installation of Visual Studio and/or IIS. I was able to copy my solution to another machine and run it
in another instance of VS2017. When I did that I found that the project ran as expected. I then published from that VS instance and after some tinkering in the server's IIS instance I was able to get the project to run.
Since then I've not yet understood why I'm having a problem publishing from my local VS instance, but it does appear that the problem is located there and not in the files being published generally. For now I'm going to say this issue is solved, though
what I'll probably do is uninstall VS2017 Pro and try to reinstall it. Even if that doesn't work I know I have other options.
Thanks again for your help!