Routing And Links Not Working When Publishing Razer Page CRUD Application

Question

Routing And Links Not Working When Publishing Razer Page CRUD Application

Tweedy, Danny 0

I'm having a routing and link generation issue with a CRUD application that I created Visual Studio 2022 in Razer Pages.

The application runs fine in Visual Studio, the all links generated from the asp-page tag helper are created as expected, and you can navigate to all the pages via the links in the buttons just fine. However, when the application is published to a local folder (or a folder on test/staging server) and run from IIS, links for any page that is NOT the index page in the root subfolder are not being generated AND the routing doesn't appear to be working, as evidenced when you try to get to a page by simply typing the full url to the page you want to get to (eg.http://localhost:88/Solutions/Create ); you simply get the HTTP ERROR 404 "This localhost page can’t be found" error.

Here is a snapshot of the link as it's generated when the app is run (just fine) from Visual Studio:

LinkGood

Here is what the link looks like when from from IIS after publishing the app into a folder on my machine (Note: The same occurs if published local to the IIS Web Server):

BadLink

And again, if you force the path after run in IIS you get the 404 error, suggesting the routing just isn't working:

PageNotFound

Everything is present in the application code necessary for routing and link generation, otherwise the links wouldn't generate and routing wouldn't work when run from within Visual Studio, so I'm guessing that some additional configuration is needed in IIS?

The application is built using ASP.NET Core 7:

dotnet_info

Any tips, suggestions, or guidance would be greatly appreciated.

Thanks!

Anonymous

2023-06-26T01:55:24.8566667+00:00

Hi @Tweedy, Danny

Try to add the @addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers on the top of _ViewImports.cshtml view or in your view page.

Besides, try to republish the application and selected the "Delete existing File" options. I also created a Asp.net 7 application to test, no matter on the local environment or on the IIS server, they all work well.

Tweedy, Danny 0

These already exist in the _ViewImports.cshtlm, always have:

ViewImports Maybe the web.config is missing something?

Mine looks like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath=".\AppTracking.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    </system.webServer>
  </location>
</configuration>
<!--ProjectGuid: 6a5d729e-2c30-40cb-9f6c-a9a7d5bccfa3-->

Tweedy, Danny 0 Reputation points

2023-06-26T13:18:53.72+00:00

And I've always had the "Delete existing File" option checked, and sometimes I just manually clear out the folder I publish to to make sure it's empty. Did it this morning and published again. Same thing. So I'm wondering if there's something I need to change in IIS or add to the web.config?

1 answer

Your answer

Anonymous

2023-06-26T01:55:24.8566667+00:00

Hi @Tweedy, Danny

Try to add the @addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers on the top of _ViewImports.cshtml view or in your view page.

Besides, try to republish the application and selected the "Delete existing File" options. I also created a Asp.net 7 application to test, no matter on the local environment or on the IIS server, they all work well.
Tweedy, Danny 0 Reputation points

2023-06-26T13:14:57.93+00:00

These already exist in the _ViewImports.cshtlm, always have:

Maybe the web.config is missing something?

Mine looks like this:

<?xml version="1.0" encoding="utf-8"?> <configuration> <location path="." inheritInChildApplications="false"> <system.webServer> <handlers> <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" /> </handlers> <aspNetCore processPath=".\AppTracking.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" /> </system.webServer> </location> </configuration> 
Tweedy, Danny 0 Reputation points

2023-06-26T13:18:53.72+00:00

And I've always had the "Delete existing File" option checked, and sometimes I just manually clear out the folder I publish to to make sure it's empty. Did it this morning and published again. Same thing. So I'm wondering if there's something I need to change in IIS or add to the web.config?

Answer 1

Tweedy, Danny 0

These already exist in my _ViewImports.cshtlm, always have:

ViewImports

Anonymous

2023-06-29T05:26:37.0666667+00:00
Hi @Tweedy, Danny

Try to add the @addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers on the first line, like this:

@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers @using AppTracking @namespace AppTracking.Pages

Besides, if still not working, try to directly set the href attribute, instead of using the Asp-page attribute to generate the href attribute.

For example:

using the following code:

<a class="nav-link text-dark" href="/Privacy">Home</a>

instead of

<a class="nav-link text-dark" asp-area="" asp-page="/Privacy">Privacy</a>

Best regards,
Dillion

Share via

Routing And Links Not Working When Publishing Razer Page CRUD Application

1 answer

Your answer