Hello, I have this problem: I've made some extractions with epplus. I developed them on my computer in a 3.5 .net vb web app. It's an asynchronous method, so the excel files are saved to a location from where I can get them when they're ready. Now I've just released the web app to a client. This app already existed I just added these extractions. On my computer there's no problem with excel files I produce. I brought my client database to my computer to test with their actual data. Problem is that the same extractions (not all but some of them), done on production environment produce files which excel says are corrupted. When I ask to repair them they're identical to the ones done on my computer, no difference. The only difference is that excel states they're corrupted when done directly on the server.
So I took the two xlsx, the one from the server and the one from my computer. Renamed them to zip, extracted all contents (they're very simple, no formulas, no graph no pivot, just extractions of raw data from a SQL store proc) and compared all files. Surprise: no differences, only ID's contained in workbook.xml.rels, workbook.xml and .rels
No differences in data...
So now I'm really confused... Why is this happening? I was with epplus 2.8 version, but I upgraded to the last one just to be sure and problem is still the same.
Please give me some hint because I really don't understand what's going on...
Last thing to say: my computer runs excel 2013, on the web server there's no excel. I'm opening the produced files with my excel 2013 and a 2007 excel on one computer on the client's network, and when it says the file is corrupted, even my excel 2013 says it is, it doesn't seem a problem in excel version...
Let me know, thank you
Vincenzo
Comments: [I might be inferring the wrong way here; apologies in advance & please ignore the following if you're already totally sure that the application runs on exactly the same Framework version in both environments.] [This MSDN article](http://msdn.microsoft.com/en-us/library/jj152935(v=vs.110).aspx) seems to have some useful bits in it about what Framework version an app uses based on three things: the app's configuration file, the presence of the Framework the app was built against, and the latest* Framework version available on the system. [* some important qualifications about "latest" at the article] To be sure of what Framework version your app actually ends up using, I think checking Environment.Version at runtime would suffice.
So I took the two xlsx, the one from the server and the one from my computer. Renamed them to zip, extracted all contents (they're very simple, no formulas, no graph no pivot, just extractions of raw data from a SQL store proc) and compared all files. Surprise: no differences, only ID's contained in workbook.xml.rels, workbook.xml and .rels
No differences in data...
So now I'm really confused... Why is this happening? I was with epplus 2.8 version, but I upgraded to the last one just to be sure and problem is still the same.
Please give me some hint because I really don't understand what's going on...
Last thing to say: my computer runs excel 2013, on the web server there's no excel. I'm opening the produced files with my excel 2013 and a 2007 excel on one computer on the client's network, and when it says the file is corrupted, even my excel 2013 says it is, it doesn't seem a problem in excel version...
Let me know, thank you
Vincenzo
Comments: [I might be inferring the wrong way here; apologies in advance & please ignore the following if you're already totally sure that the application runs on exactly the same Framework version in both environments.] [This MSDN article](http://msdn.microsoft.com/en-us/library/jj152935(v=vs.110).aspx) seems to have some useful bits in it about what Framework version an app uses based on three things: the app's configuration file, the presence of the Framework the app was built against, and the latest* Framework version available on the system. [* some important qualifications about "latest" at the article] To be sure of what Framework version your app actually ends up using, I think checking Environment.Version at runtime would suffice.