Reply to thread

Message

[QUOTE="ALX, post: 186363, member: 4770"]
I have made my VB application available to the entire US and it has been running without incident for several months, so I know there are no bugs in the basic code. Recently I have had a few people in India download the application and they have reported an error where the app parses the current date string. I really had not intended to make this app global in scale, but am thinking that I would now like to make it available to countries like India, where there is a large percentage of technically minded and English speaking people. The error occurs where the code is parsing a date into Day, Month and Year. It breaks it down by searching Now.ToShortDateString for the forward slash "/" to divide the date string into individual components. My best guess is that Windows, for the culture settings in India, is not using the forward slash within the date string. [B][I]Does anyone have any insight on this ?[/I][/B]
   Also...
   Rather than go through the entire code to redo any string references to a date, I'd like to force the app to use the English culture entirely as these users are already conversing in English. I'm thinking that the Assembly Information "Neutral Language" setting in VS will use the specified language only as a fallback if no resources for the current culture are found. [B][I]Is this correct ?[/I][/B] I admit that I had not set this Attribute and it was set to "none". I haven't had much luck with Google for this. Can anyone provide some guidance ???
[/QUOTE]

Verification