Run the sample application. If you then check your bin/debug folder, you will see the .xls file that was written. Open that file in Excel 2013 (it could very well happen in other versions of Excel as well) and you will get the "PROTECTED VIEW Office has detected a problem with this file. Editing it may harm your computer. Click for more details."
Hello Jon,
Thank you for your post.
I have been looking into this a bit, and I was initially able to reproduce this issue you are seeing. After reading up on Protected View in Excel, I found that Excel files that originate from the Internet may open in protected view, so I tried opening the "sample breakage.xlsx" file that you have attached in Excel 2013 and found that it was originally in protected view. After setting it to not be in protected view, which essentially then "trusts" the file, I am not seeing the "opens_in_protected_view.xls" file opening in protected view when creating it with the sample project you sent.
I believe that this is likely expected behavior, but I believe I need a little bit of information from you on this matter first. When you try opening the "sample breakage.xlsx" file on your machine, does it open in protected view? If so, then the workbook that is created by loading your file via the Infragistics Excel Engine will load in as "protected" and therefore will export as protected as well. Would it be possible for you to please verify the behavior you are seeing with your "sample breakage.xlsx" so I may continue looking into this issue to find out if it is a bug in the Excel engine or whether this is actually expected behavior?
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support
Sorry. I added another file to the output that was sample_breakage2.xls.
In Excel's Protected View settings, you can uncheck all the protected view settings and it will still open in protected view.
It's a less friendly protected view message where they have to click the message and then click another button inside the settings that says "Edit anyway".
I hope that directing you to the correct file will produce the problem.