I'm developing a web app in .Net Core 3.0 (Stable Release). It is almost completed and is doing well in my local PC.
Issue is, When i deployed the app on server, it just shows PAGE NOT FOUND error.
I'm very confused now as when i try manual URL to open any specific page (which require authorization) it land me to the Login URL withReturnUrlQuery Parameter but the Login page also shows 404 error. This means
the app code is doing well but i don't know why it's not showing pages.
1 thing i got wonder about is, instead ofViewsdirectory, my published source is havingXXX.Views.dll andViewsdirectory is
not there. (this is actually new for me)
I'm like stuck at this point. Please help with this issue.
in core 3.0, views are compiled to dlls, so there is no view folder required. the 404 could be a bad parameter to the login page. what happens if you try to access the login page directly. also maybe the error page is missing. check the network logs to see
if there is a redirect.
None
0 Points
1 Post
404 Page not found error in .Net Core 3.0 after deployment.
Nov 13, 2019 05:50 PM|MayurP|LINK
Hello,
I'm developing a web app in .Net Core 3.0 (Stable Release). It is almost completed and is doing well in my local PC.
Issue is, When i deployed the app on server, it just shows PAGE NOT FOUND error.
I'm very confused now as when i try manual URL to open any specific page (which require authorization) it land me to the Login URL with ReturnUrl Query Parameter but the Login page also shows 404 error. This means the app code is doing well but i don't know why it's not showing pages.
1 thing i got wonder about is, instead of Views directory, my published source is having XXX.Views.dll and Views directory is not there. (this is actually new for me)
I'm like stuck at this point. Please help with this issue.
Thanks.
All-Star
54724 Points
13878 Posts
Re: 404 Page not found error in .Net Core 3.0 after deployment.
Nov 13, 2019 06:25 PM|bruce (sqlwork.com)|LINK
in core 3.0, views are compiled to dlls, so there is no view folder required. the 404 could be a bad parameter to the login page. what happens if you try to access the login page directly. also maybe the error page is missing. check the network logs to see if there is a redirect.