An ASP.NET corporate news application is used by employees in New Zealand. A label on Default.aspx displays the current date by using DateTime.Now.ToString(\"D\"). You need to ensure that the long date string is formatted correctly for New Zealand users. What should you configure?

Introduction / Context:
ASP.NET applications that are used in different regions must display dates, times, and numbers according to the local culture. The .NET Framework uses culture settings to determine formatting rules for DateTime.ToString and other operations. In this scenario, New Zealand employees need to see dates formatted with the New Zealand regional pattern, which differs from other English speaking regions. Understanding the difference between culture and uiCulture settings is essential for correctly formatting data and resources.

Given Data / Assumptions:

The application uses ASP.NET on the .NET Framework.
Default.aspx has a label that displays the current date using DateTime.Now.ToString(\"D\").
The application is used by employees located in New Zealand.
The goal is to ensure that the date formatting follows New Zealand regional conventions such as day month year order and local day names.
The globalization element in Web.config controls culture and uiCulture for the application.

Concept / Approach:
In ASP.NET, the culture setting controls how dates, numbers, and currencies are formatted and parsed. The uiCulture setting controls which resource files are used for localized user interface strings. To change how DateTime.Now.ToString(\"D\") formats the long date, you must change the culture, not just the uiCulture. For New Zealand, the correct culture name is en-NZ. Setting culture=\"en-NZ\" in the globalization element of Web.config ensures that all date formatting operations use New Zealand formats by default for the request thread.

Step-by-Step Solution:
1. Open the Web.config file for the ASP.NET application and locate the globalization element under the system.web section. 2. Set the culture attribute to en-NZ, which corresponds to English language with New Zealand regional settings. For example: <globalization culture=\"en-NZ\" uiCulture=\"en\" />. 3. Leave uiCulture as appropriate for resource lookup. If you only need one language but a specific regional format, culture is the crucial setting. 4. After updating Web.config, build and run the application, and navigate to Default.aspx to check the current date label output. 5. Confirm that DateTime.Now.ToString(\"D\") now displays the long date according to New Zealand rules, such as including the full day name and using the local date pattern.

Verification / Alternative check:
You can test different culture values (for example en-US, en-GB, en-AU, en-NZ) and compare how the long date format changes. You will see that changing culture, not uiCulture or encoding, is what affects DateTime formatting. Documentation for the globalization element confirms that culture governs numeric and date formats while uiCulture governs resource selection.

Why Other Options Are Wrong:
Setting uiCulture to en-NZ affects only which resource files are selected, not how DateTime values are formatted. Date strings will still follow the culture setting unless you explicitly override it.
Changing responseEncoding to UTF-8 or saving the page as UTF-8 controls how characters are encoded in HTTP responses and on disk, but does not change date formatting patterns.

Common Pitfalls:
A frequent mistake is to assume that uiCulture and culture are interchangeable. Developers also sometimes try to fix formatting problems by changing encoding, which only addresses character representation, not regional formatting rules. Always remember that culture controls data formatting and parsing, while uiCulture controls localized resources such as user interface text.

Final Answer:
You should set the culture attribute of the globalization element in Web.config to en-NZ so that DateTime formatting uses New Zealand regional settings.