|
I'm not sure it will match the Control Panel, however I would suggest you try CultureInfo.GetCultures()
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.4
|
|
|
|
|
Please go abck and read my original post.
I know what GetCultures does and it doesn't return a valid list of countries. It's missing many countries for example Cuba.
|
|
|
|
|
Oops. Seems like I got distracted and missed half of your post. Sorry. 
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.4
|
|
|
|
|
MrSmoofy wrote: doesn't return all the countries like Cuba
How many were you expecting? I thought there was only one country like Cuba. 
|
|
|
|
|
There is only one Cuba and GetCultures does not include it.
|
|
|
|
|
Windows probably does, but there is an alternative. Haave a look at GeoNames[^] - they has varaious web services which will provide you with such info, even by country code if you need it.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
I know there are external webservices available but our application will not have access to them as it runs on a private network with no external internet access.
|
|
|
|
|
MrSmoofy wrote: Windows must have this list somewhere since they are using it in the Location Tab.
That doesn't mean that it has to be publicly available. Do you allow other vendors to re-use every resource in your application?
You can find the list in the registry, under this key;
HKLM\Software\Microsoft\Windows\CurrentVersion\Telephony\Country List "Cuba" is number 52 in there
Bastard Programmer from Hell 
|
|
|
|
|
Again read my original post. The Telephony Country List is not correct it lists Telephone codes not just countries.
Look at number 5399 "Guantanamo Bay" is not a country
Look at number 800 "International Freephone Service" is not a country
870, 871, 872, 873, 874 are not countries
Also some countries have more then one Telephone code so they are listed twice based on where the town/city/region is in the country.
|
|
|
|
|
MrSmoofy wrote: Again read my original post. The Telephony Country List is not correct it lists Telephone codes not just countries.
I haven't checked the Telephone-codes, I looked in the registry - and Cuba is available.
MrSmoofy wrote: Look at number 5399 "Guantanamo Bay" is not a country
Open up the regional settings and take a look at the "country" list that you wanted - it is also specifying Guantanamo Bay. It's the list that you requested, and no, there is no official list. Here's[^] why.
You're welcome
Bastard Programmer from Hell
|
|
|
|
|
Interesting. My appologies on that one as I didn't see it when I looked.
There are still others on the list that are not countries I guess I will just have to filter them out.
Appears there is an issue on 64bit machines.
string keyPath = @"SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Country List\";
RegistryKey countryKey = Registry.LocalMachine.OpenSubKey(keyPath);
countryKey = null
According to Process Monitor it's trying to access the following key which doesn't exist.
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Telephony\Country List
Also I have found that Servers usually don't have a modem so this registry key doesn't exist.
|
|
|
|
|
MrSmoofy wrote: According to Process Monitor it's trying to access the following key which doesn't exist.
Yes, in short Windows provides separate 32-bit and 64-bit entries. That's described here[^], as well as opening an alternate view.
MrSmoofy wrote: Also I have found that Servers usually don't have a modem so this registry key doesn't exist.
How about exporting the list once from an existing machine to XML or a text-file and use that? Sounds like a good candidate to put in the resources.
Bastard Programmer from Hell
|
|
|
|
|
I wish that was an option.
I've been mandated that we will not be in the business of maintaining the list ourselves. Making it XML does that we would then have to maintain that XML if and when countries change. Microsoft is already maintaining the list. We simply want access to that list.
If I could maintain my own list I would use the ISO list.
|
|
|
|
|
Ah, but you personally may be able to make a few bucks by offering an update service. 
|
|
|
|
|
That goes back to it's been mandated that we are not in the business of maintaing a list or webservice providing the list.
Also where the application is installed won't always have internet access to access such a webservice.
|
|
|
|
|
|
Why would I reinvent the wheel. This already exists. It's not an option if the application is installed on servers that do not have access to these services.
|
|
|
|
|
MrSmoofy wrote: do not have access to these services
No Services involved, just send the client a floppy (or whatever  ) for a small consideration and your boss is none the wiser.
|
|
|
|
|
Thanks, I'd like to keep my job.
|
|
|
|
|
|
MrSmoofy wrote: Also where the application is installed won't always have internet access to access such a webservice.
Someone forgot to think - did a "manager" describe these restrictions? 
How would Microsoft be able to provide updates (aka maintain the list) on a server where there's no internet access? If you can't maintain it, they can't either.
Bastard Programmer from Hell
|
|
|
|
|
Through windows update services. Which would be received from an internal network update server.
So the server is maintained just not directly via the internet to microsoft it's maintained by a central internal update server where the customer controls what windows updates the companies computers get.
|
|
|
|
|
MrSmoofy wrote: So the server is maintained just not directly via the internet to microsoft it's maintained by a central internal update server where the customer controls what windows updates the companies computers get.
Generate the textfile from that server, and distribute it? That way you're not "maintaining" it, and still have it propagate to the rest of the network.
I still doubt that Windows Update actually ever touches that particular registry-key.
Bastard Programmer from Hell
|
|
|
|
|
MrSmoofy wrote: Microsoft is already maintaining the list. We simply want access to that list.
Microsoft provides the list, I doubt that they're adding/removing entries on every Windows update. I'd check that assumption before embarking on a voyage
If they do, then you won't be able to filter out non-countries, as they might add "New York" whenever they feel like it. You'd still need access to the ISO-list to verify whether the new entry is a country or not.
Bastard Programmer from Hell
|
|
|
|
|
I agree with you but those above me maintain that if MS has a list we should be able to use it. My hands are tied on that.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
