Export failed due to error "The Excel limit is 32767 characters per cell"

[DanStevens]

I tried to perform an export of all resource strings in a solution I'm using as I'd like to search them. When I did so I received the following error:

The Excel limit is 32767 characters per cell. This text can't be exported: {"EngineerName":null,"EngineerOrganization":null,"...

I understand this means one of the resource values in the solution has a length that exceeds one of Excel's limits. Unfortunately, this causes the entire export to fail - the result is an invalid Excel file that doesn't contain any data. While we can't fix Excels limitations, it would be better if the extension handled this error more gracefully, for example by truncating long values to the 32767 characters.

An additional option to resolve this would be to add support for CSV export, which being a raw data format isn't affected by Excel's limitations. Also, Excel does seem able to handle opening of CSV files with very long fields by truncating them.

Attached below is a Visual Studio project with a very long resource string that can be used to reproduce this bug:

LongResourceString.zip

[DanStevens]

I thought I'd try selecting all cells and copy-pasting them into Excel, but the Copy button is disabled. Is there a limit to the number of entries that can be copied? The solution I'm working on has just over 10,000 resource strings.

[tom-englert]

I think you can change the export format to CSV in the options

[tom-englert]

Also be aware when text gets truncated during export, the truncated text will later be imprted

[tom-englert]

And there should be no limit on copying

[tom-englert]

https://github.com/dotnet/ResXResourceManager/blob/master/src%2FResXManager.Model%2FExcelExtensions.cs#L296-L299

Maybe here we could just export an empty cell, instead of throwing

[tom-englert]

https://github.com/dotnet/ResXResourceManager/blob/master/src%2FResXManager.View%2FVisuals%2FResourceViewModel.cs#L197-L213

And this are the conditions for copying

[tom-englert]

@DanStevens any input on this?