-3

I have two identical web applications published on the same server — one for testing and one for live. Recently, the live version started having issues, even though there were no problems before.

Currently, the version in testing is exactly the same as the one in live. The only difference is the connection string to the database. Both applications are published on the same IIS server but use different ports.

The issue I'm facing is related to the date format. Normally, both systems follow the local server date format, which is dd-MMM-yyyy. Because of that, I didn’t explicitly set the date format in the code, as it has always followed the server's locale settings.

However, the live application has recently started showing dates in the M/d/yyyy format, which is confusing for users. Meanwhile, the testing environment is still correctly displaying dates in the dd-MMM-yyyy format.

How is this possible, considering the testing version is exactly the same as the live one? Please advise.

Improve this question
2
  • 1
    How is this possible, considering the testing version is exactly the same as the live one?: It's not possible for anyone on SO to know because we don't have access to your server, nor have you posted any code. However, as you've stated, if you explicitly set the format you won't have this issue. You may consider explicitly setting the value, and move on with life.
    – It all makes cents
    CommentedApr 23 at 3:33
  • Depends entirely on your code. For instance if dates are being passed around as DateTime type and rendered in the web UI then they should be consistent on the same server. If they are passed to the web server as strings though, then the database server datetime formatting can come into play.
    – Steve Py
    CommentedApr 24 at 0:08
Load 6 more related questions Show fewer related questions

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.