tag:blogger.com,1999:blog-5822946.post114350417143890940..comments2014-09-17T10:15:34.033-05:00Comments on Marc's Musings: RE: Enumerating available localized language resources in .NETIDisposablehttp://www.blogger.com/profile/02275315449689041289noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5822946.post-1144876495070557202006-04-12T16:14:00.000-05:002006-04-12T16:14:00.000-05:00It's not that I don't want to handle the translati...It's not that I don't want to handle the translations I don't have... it's that I don't want the exceptions generated when the the appropriate Framework localization doesn't exist.<BR/><BR/>I precisely DO want the list of localizations available FOR the Framework, not mine... I'm the slave to what is installed on the client's server. They control the language packs installed, and I want my list to be driven by what the Framework can offer [in this install].IDisposablehttps://www.blogger.com/profile/02275315449689041289noreply@blogger.comtag:blogger.com,1999:blog-5822946.post-1144871998673638462006-04-12T14:59:00.000-05:002006-04-12T14:59:00.000-05:00Hi Marc,I actually explained the solution in my po...Hi Marc,<BR/><BR/>I actually explained the solution in my post -- rather than getting the Assembly by using a .NET Framework intrinsic type, get it from your own application!Anonymousnoreply@blogger.com