When trying to Workbook.Load("file.xlsx") we get
This only happened after upgrading to 18.1 (from an - I think - about six year old version).
If there is no workaround: can we downgrade only the excel library and still use the 18.1 WPF components to fix this?
We need an excel file that reproduces this to test with to look into what is happening. Please provide us with an excel file that we can use for testing.
Thank you for looking into this, Alan. We have tested this with 15.2 and it works. No luck with 18.1.
The formula mentioned in the exception message seems not to correlate with the actual file.
I followed the steps you suggested and was unable to reproduce the behavior you're describing.
I created a sample with version 18.1.20181.105 and 18.1.20181.223 and load the excel sheet you provided.
I run the sample and not getting any exception.
I have attached the sample project I used to test this. Please test this project on your PC; whether or not it works correctly may help indicate the nature of this problem.
If the project does not work correctly, then the change in behavior is due to differences in your environment from mine and these differences can be anything from operating system version to the specific version of the Infragistics DLL versions used. My test was performed using version 18.1.20181.223 and 18.1.20181.105 also .
Please provide more details about your machine and version of the assemblies that you are referencing so that I can modify the environment that I am testing in to match yours.
If the project does show the product feature working correctly, then more information will be needed to reproduce the issue in a sample that can be used for debugging. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing. This can be done by either making the sample that I provided more like your application or by isolating the behavior from your application by removing dependencies on any third parties or databases.
Please let me know if I can provide any further assistance.
Is it Christmas already? We updated everything to 18.1.20181.176 and it works like a charm again. Thank you a lot for digging into this. Without the sample application which clearly demonstrated that we have this problem in 18.1.20181.82 but not in 176, we would have rather down- than upgraded.
Hello Tim ,
Thank you for the update that upgrading the application to latest SR did solve the issue.