Route stopped working only in release version

Asked

Viewed 33 times

0

I have software here at the company, and it worked perfectly. However, I made a small layout change and my machine works perfectly. When I publish the application, the route (/Configurations) returns error 404, as if the route did not exist.

I created another route (/Config), with the same content and it doesn’t work either.

Any idea what could be causing this?

c# asp.net-core
  • 1

    And what is the difference between the two environments? in production it is published in a subdomain or virtual directory?

  • No difference, apart from the access ip. It is a server on the network. It makes no sense not to open the route, at least not for me...

  • You can guarantee that it is not an Exception being popped and is being redirected as "not found"?

  • How do I check this? I have no debug in release...

  • Is it published on IIS? Is there a way to share Startup?

  • I managed to. Thank you.

Show 1 more comment

1 answer

0


I was able to solve the problem as follows:

I went back to a "commit" that worked in git , and went "eating" one by one and publishing. Until I discovered the commit.

What happened was that a developer created a routine that needed of a file. This file, by chance, existed in the repository, however, was not created by C# when compiled the solution. This caused an exception that was not returned due to server settings.

Adjusting the system to create the file if it did not exist solved the problem.

Browser other questions tagged c# asp.net-core

You are not signed in. Login or sign up in order to post.