Skip to main content

Date format problem with ASP.NET calendar and IIS

Today I was working on an existing ASP.NET application. The application is using an ASP.NET calendar control. We were creating a new environment for the testing team. The application was working fine but suddenly we realized there is some problem. The problem was with the date format. The expected date format was mm/dd/yyyy but we were getting mm-dd-yyyy (even after formating). I started working on this.

First thing I thought was that it has something to do with the environment as the code is fine (as it is working fine on other machines).

I googled a bit and found out that it is a common problem. So I thought about blogging about it in hope that it will help others.

I found out that the problem is with the "Region and Language". For that go to control panel. You need to change the date format and the region as required.


Now you need to restart the system. 

Sometimes even after doing that you will not get the desired result. Then go to Administrative tab and choose this two checkboxes as shown in the image below.


Also change the System locale. 


and restart the system.

If then also the problem persists then check with which language the account on with which you are running the application is created and then change it to required language.

Hope this will help.

Happy coding.

Labels:

Comments

  1. ayaan aslamDecember 13, 2011 at 12:11 AM

    this is the manual way to change the date format of the calendar , can it is possible by coding to change the date format of the calendar , so that other system setting remains unchanged .?
    please reply soon

    ReplyDelete

Post a Comment

Popular posts from this blog

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon.    php artisan migrate:install Error :                                                     [PDOException]                                       SQLSTATE[HY000] [2002] No such file or directory                                              Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver'    => 'mysql', 'host'      => 'localhost',     'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database'  => 'wedding', 'username'  => 'root', 'password'  => '', '
6 comments
Read more

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.
Post a Comment
Read more

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo
2 comments
Read more