Using Attached Sample App
Open App
Click in Cell I10
Right Click
Select Format from context menu.
You then get this error message
An unhandled exception of type ‘System.NotSupportedException’ occurred in mscorlib.dll
Additional information: Culture ‘zh-CHT’ is a neutral culture. It cannot be used in formatting and parsing and therefore cannot be set as the thread’s current culture.AposeExcelGridCultureError.zip (159.5 KB)
Any Help would be great.
Thanks
Thanks for the sample project with template file.
I have tested your scenario/case using your sample project and template file with Aspose.Cells.GridDesktop v18.6 (latest version/fix) but could not reproduce the issue. I do not find any exception when opening the Format Cells context menu option, see the screenshot for your reference:
Which version of Aspose.Cells.GridDesktop you are using? I am running your project in us-english locale/regional settings. Could you elaborate on how could we reproduce the issue on our end.
Hi
I tested it with 18.6
us-english regional settings.image.png (8.7 KB)
I am using the .net 2.0 version of the dll and my project is set to run as .net 2.0 project.
If I change my project to .net 4.0 it seems to work like yours.
Can you validate if are running as .net 2.0 project?
It is really strange. I too .NET 2.0 as target framework version, see the screenshot for your reference:
And, I use english ( Singapore) as my region and language settings.
image.png (17.8 KB)
My region settings are attached
We are getting this on at least three machines all Windows 10 64bit
We tested your scenario/case using your sample project and template file and following your steps but still could not reproduce the issue on our systems (i.e., Windows8 and Window7 64-bit OS with english locale). To investigate your issue (as you are using Windows 10) further, I have logged a ticket with an id “CELLSNET-46191” . We will look into it soon.
Once we have an update on it, we will let you know here.
We did some more testing and found a windows 10 machine that it worked on that had not
applied the windows updated.
We then let if finishing updating to the current version windows 10 1803 and now it is broke.
Attached Windows Update Before That worked.
Before_Windows_update.PNG (19.7 KB)
Attached Windows Update After that now has the error.
After_Windows_Update.jpg (27.9 KB)
So maybe you can check if you have this update yet.
Thanks for your findings.
We have logged your findings against your issue “CELLSNET-46191” into our database. We will investigate your issue soon.
Once we figure it out or some new information available, we will let you know.
Any luck reproducing?
We still could not evaluate your issue thoroughly.
Once we have any new information, we will share it with you.
If you come up with something we can do to help let me know.
Thanks
We are not able to reproduce the issue on our end. Could you provide details what culture/locale settings you are using?
Did you make sure on window 10 you had installed 1803 update?
Below is the information you requested
In Region & Language
Region=United States
Languages= English(united states)
Below output from.net
Output from
Threading.Thread.CurrentThread.CurrentCulture
{en-US}
Calendar: {System.Globalization.GregorianCalendar}
CompareInfo: {CompareInfo - 1033}
CultureTypes: SpecificCultures Or InstalledWin32Cultures Or FrameworkCultures {70}
DateTimeFormat: {System.Globalization.DateTimeFormatInfo}
DisplayName: “English (United States)”
EnglishName: “English (United States)”
IetfLanguageTag: “en-US”
IsNeutralCulture: False
IsReadOnly: True
KeyboardLayoutId: 1033
LCID: 1033
Name: “en-US”
NativeName: “English (United States)”
NumberFormat: {System.Globalization.NumberFormatInfo}
OptionalCalendars: {Length=2}
Parent: {en}
TextInfo: {TextInfo - 1033}
ThreeLetterISOLanguageName: “eng”
ThreeLetterWindowsLanguageName: “ENU”
TwoLetterISOLanguageName: “en”
UseUserOverride: True
Output from
Threading.Thread.CurrentThread.CurrentUICulture
{en-US}
Calendar: {System.Globalization.GregorianCalendar}
CompareInfo: {CompareInfo - 1033}
CultureTypes: SpecificCultures Or InstalledWin32Cultures Or FrameworkCultures {70}
DateTimeFormat: {System.Globalization.DateTimeFormatInfo}
DisplayName: “English (United States)”
EnglishName: “English (United States)”
IetfLanguageTag: “en-US”
IsNeutralCulture: False
IsReadOnly: True
KeyboardLayoutId: 1033
LCID: 1033
Name: “en-US”
NativeName: “English (United States)”
NumberFormat: {System.Globalization.NumberFormatInfo}
OptionalCalendars: {Length=2}
Parent: {en}
TextInfo: {TextInfo - 1033}
ThreeLetterISOLanguageName: “eng”
ThreeLetterWindowsLanguageName: “ENU”
TwoLetterISOLanguageName: “en”
UseUserOverride: True
Thanks for providing details.
we have recorded the details against your issue “CELLSNET-46191” into our database. We will evaluate and also try to install your mentioned update on Windows 10 (if possible).
Once we have any new information, we will let you know here.
Could you set the culture, then check whether you still reproduce the issue in your environment:
e.g
Sample code:
........
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles Me.Load
Dim ci As CultureInfo = New CultureInfo("en-US")
Thread.CurrentThread.CurrentUICulture = ci
Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture(ci.Name)
We tried the above code after simulating your environment,but still could not reproduce it.
Tried the about code, still have the issue.
Did you guys try the windows update?
We are working on this issue and will provide you feedback soon. We are sorry for the delayed response.
We have installed Windows 10 update (1803) but still could not reproduce this issue. Can you show the detailed stack trace message. Another test you can do, if you comment the import file line of code, thus just get an empty worksheet:
e.g
Sample code:
// Me.GridDesktop1.ImportExcelFile("TrainABDay2Export.xlsx")
then choose “Format Cells” from the right content menu from any cell, Does this issue occur?
Thanks for your confirmation with stack trace.
We have recorded it against your issue “CELLSNET-46191” into our database. We will evaluate your issue further.
Once we have any new information, we will let you know.