I was having an issue with the DateColumn of the grid in the 10.2 release version, so I just tried the 10.3 version with the latest SR (2159) for all the components. This resolved my DateColumn issue, but has caused a serious issue with the loading of Excel XLS files. I have some simple code that uses the Workbook load method to load a file using a stream. It has been working for 1.5 years through several versions of the controls with no issues. I am trying to import the same XLS test files that I have been using all that time with no issues. These files are not even large files (3 or 4 sheets with 50-100 rows at the most). With absolutely no code changes, except changes to reference the new dlls, I now can't import XLS files. There is an unhandled StackOverflowException in the Excel.v10.3.dll assembly that takes my app down. Any ideas, or do I need to go back to an earlier build of the components?
Hi Bob,
Mike has been able to reproduce your issue and I am going to create a case for you so that you will be able to track the issue and its resolution.
You will hear from me shortly concerning the development issue that is being created.
I was able to reproduce this issue in Silverlight only. I have forwarded this post to the Developer Support Manager and a DS engineer will be contacting you about this issue.
I would not recommend mixing builds as that could cause other bugs, although it is probably possible using binding redirects in your application configuration file. I would instead recommend going back to the RTM version of all assemblies until this issue is resolved.
I went ahead and tried dropping back to volume 2 with the latest service release, and it has the same issue. It seems as though I need the volume 2 release version of the Excel component and the service release version of the grid component. Can this be done, and if so, which version of the InfragisticsSL4.v10.2.dll component do I use?
Here is an Excel spreadsheet with the call stack and an example of an XLS spreadsheet that we import and export from our app.
Bob
Can you post the first few lines in the stack trace (the deepest part of the call stack) so I can see if this is a known issue or not?